# TSC - Wallets Working Group

{% hint style="danger" %}
**ARCHIVED**

This page has been archived. It's content might be outdated.
{% endhint %}

{% hint style="info" %}
Page last updated; 2024-07-29
{% endhint %}

## Purpose / Goal

To further the development of Cardano’s wallet ecosystem. By providing a place for wallet stakeholders to share insights and work towards solving existing and future problems.

### Motivation

* Unlike other blockchains Cardano has a large and diverse wallet ecosystem, this brings strength via diversification, but introduces complexity in coordination.
* Via the wallets working group, we want to address issues of wallets and their stakeholders.
* By working together we want to be able to tackle the largest and toughest ecosystem-level problems.
* We want to amplify the voice of the quiet, to identify and improve wallets for all.

## Working group leads

* [Ryan Williams](https://twitter.com/Ryun1_)
* [Vladimir Kalnitsky](https://twitter.com/klntsky)
* [Adam Dean](https://twitter.com/adamKDean)

## Working group members

Calls and communications open to all, no set attendance.

## Working group deliverables

### Wallets Product Backlog

WIP, dependent on maturity of Cardano backlog committee.

### Wallet Connectors Initiative

* [See folder in shared drive.](https://drive.google.com/drive/folders/1wctnLBRQsEc-kWzDGmaIjLjqci-wtF23?usp=drive_link)
* Cardano does not have an optimal state of connectors.
* The majority of issues on CIPs repo are CIP-30 related.
* Although CIP-30 facilitated the launch of dApps on Cardano, we believe we as an ecosystem are out growing it.
* Once we have described the issue we can then talk about how to solve it.

#### Deliverables

* [CPS-10 | Wallet Connectors](https://github.com/cardano-foundation/CIPs/tree/master/CPS-0010) ✅
* CIP-???? | Extensible Wallet Connector Framework ⏳
* CIP-???? | Extensible Wallet Connector  Connection - Injected Javascript  ⏳
* CIP-???? | Extensible Wallet Connector  API - Legacy Interface  ⏳

### Query Layer Initiative

* Lead by Vladimir 💪
* [See folder in shared drive](https://drive.google.com/drive/folders/1baSYHfWJdUh5dwRkHjY7qnaufjuO8sP2?usp=drive_link)
* Cardano lacks a standardized query layer. This can lead to suboptimal tooling, dApp and wallet architecture.
* Every data provider creates its own query layer, this adds complexity to wallets and dApp designs.
* By having a standardized query layer we could allow users to choose data providers for their wallets.

#### Deliverables

* [CPS-12 |](https://github.com/cardano-foundation/CIPs/pull/625) [Query Layer Standardization](https://github.com/cardano-foundation/CIPs/pull/625) ⏳
* CIP-???? | Standardized Query Layer ⏳
* [CPS-11 |](https://github.com/cardano-foundation/CIPs/blob/master/CPS-0011) [Universal JSON Encoding for Domain Types](https://github.com/cardano-foundation/CIPs/blob/master/CPS-0011) ✅
* [CIP-116 | Standard JSON encoding for Domain Type](https://github.com/cardano-foundation/CIPs/tree/master/CIP-0116) ✅

### Other Work

* [CIP-???? | Wallet Best Practices](https://github.com/cardano-foundation/CIPs/pull/815) ⏳

## Collaboration channels 

* Shared meeting calendar [Luma calendar](https://lu.ma/wwg)
* [Discord channel](https://discord.gg/gCw5HQJsxG) via CIP discord
* [Shared Google drive](https://drive.google.com/drive/folders/1gYGeVJBLmDhCGEp1mTkCrsJYspd5hSoM?usp=sharing) (with all meeting recordings/slides)

## Working Group Meeting date and time

* Every fourth Thursday 4pm UTC.
* Shared meeting calendar [Luma calendar](https://lu.ma/wwg)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://groups.docs.intersectmbo.org/groups-overview/working-groups/wallets-working-group.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.