Intersect Committees
Intersect Knowledge BaseIntersect Website
Intersect - Committees & Groups
Intersect - Committees & Groups
  • Committee Overview
    • Committees Overview
      • Committee Maturity Framework
      • Committee Guiding Principles
      • Committee Reporting
      • Committee Communications
      • Committee Glossary of Terms
      • Committee Links
      • Committee Contact Information
  • Groups Overview
    • Groups Overview
      • Intersect Working Groups
      • Technical Working Groups
      • Special Interest Groups (SIGs)
      • Working Group Frequently Asked Questions (FAQs)
    • Working Groups
      • ISC - Intersect Governance Working Group
      • MCC - Community Hubs Working Group
      • MCC - Annual Members Meeting Design
      • MCC - Community Support
      • TSC - Wallets Working Group
      • Product - Research Working Group
      • TSC - Hard Fork Working Group
      • MCC - Working Group and Interest Group Process Design
        • General Framework
      • Budget - DReps Budget Working Group
        • DReps WG - Meeting Notes
          • October
      • MCC - Cardano Marketing Working Group
      • TSC - Certification Working Group
      • TSC - Core Infrastructure Roadmap Working Group
      • OSC - Developer Experience Working Group
      • TSC - Infrastructure Working Group
      • Civics - Media Standards Working Group
      • OSC - Governance Tools Working Group
      • OSC - Project Incubation Working Group
      • OSC - Oracles Working Group
      • OSC - Open Source Libraries Working Group
    • Technical Working Groups
      • Consensus
      • Ledger
      • Networking
      • Node, CLI and API
      • Plutus
      • 🐉Hydra
      • Partner Chains
      • Tech Support
    • Special Interest Groups
      • MCC - Transparency Special Interest Group
      • MCC - Decentralized Education Interest Group
      • MCC - Fundraising Special Interest Group
    • WG - [name] - template
  • Archived WGs and SIGs
    • Archives
      • Voltaire Ecosystem Mapping Working Group
Powered by GitBook
On this page
  • Purpose / Goal
  • Motivation
  • Working group leads
  • Working group members
  • Working group deliverables
  • Wallets Product Backlog
  • Wallet Connectors Initiative
  • Query Layer Initiative
  • Other Work
  • Collaboration channels
  • Working Group Meeting date and time
  1. Groups Overview
  2. Working Groups

TSC - Wallets Working Group

PreviousMCC - Community SupportNextProduct - Research Working Group

Last updated 9 months ago

Page last updated; 2024-07-29

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

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

  • 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

  • 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 💪

  • 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

  • CIP-???? | Standardized Query Layer ⏳

Other Work

Collaboration channels

Working Group Meeting date and time

  • Every fourth Thursday 4pm UTC.

✅

⏳

✅

✅

⏳

Shared meeting calendar

via CIP discord

(with all meeting recordings/slides)

Shared meeting calendar

Ryan Williams
Vladimir Kalnitsky
Adam Dean
See folder in shared drive.
CPS-10 | Wallet Connectors
See folder in shared drive
CPS-12 |
Query Layer Standardization
CPS-11 |
Universal JSON Encoding for Domain Types
CIP-116 | Standard JSON encoding for Domain Type
CIP-???? | Wallet Best Practices
Luma calendar
Discord channel
Shared Google drive
Luma calendar
Page cover image