Skip to main content

Wallet Integration & Developer Experience

Introduction​

This session focused on gathering feedback on the current state of the Cardano developer experience and providing a technical overview of Wallet Integrations. Emmanuel Titi led a discussion on the specialized needs of developers and demonstrated how wallets can be used for payments, authentication, and user onboarding.

What you'll learn:

  • Community feedback on the Cardano Developer Experience.
  • Three core wallet integration patterns: Payments, Authentication, and Wallet-as-a-Service.
  • Tools and SDKs recommended for building on Cardano (MeshJS, Blockfrost, Cardano Serialization Library).

1. Community Feedback: The State of DevX​

The session opened with an open floor for attendees to share their hurdles and wins.

Key Insights​

  • Fragmentation: Documentation is often scattered. While the Intersect DevX practices are helping centralize resources, connecting the dots (e.g., from "Hello World" to "Running a Node") remains a challenge for beginners.
  • Learning Styles: There is a strong demand for video tutorials to complement written documentation, especially for complex setups like Cardano Nodes.
  • Incentives: Participants highlighted the need for better reward mechanisms to sustain open-source contributions.
  • Entry Barrier: The "Zero to One" phase (setting up environments) is still the hardest part for new developers.

2. Technical Deep Dive: Wallet Integrations​

Emmanuel presented three distinct ways to integrate wallets into dApps:

A. Payments & Transactions​

The most common use case: enabling users to send ADA or tokens.

  • Tools: MeshJS is highly recommended for its documentation and feature set.
  • Verification: Developers need backend verification to confirm on-chain settlement.
    • Blockfrost: Third-party API for easy transaction querying.
    • Cardano Node + CLI: Self-hosted verification for total sovereignty.
    • Cardano Wallet API: Useful for managing user wallets programmatically.

B. Authentication (CIP-8 / CIP-30)​

Using a wallet as a "Login" mechanism instead of email/password.

  • Mechanism: The user provides a cryptographically signed message using their wallet's private key. The backend verifies this signature against the user's public address.
  • Use Case: Tipping platforms, gated content, and decentralized identity.

C. Wallet-as-a-Service (WaaS)​

For applications targeting non-technical users who don't want to manage seed phrases.

  • Solution: Services (referred to as UTXO management services in the session) allow apps to manage keys securely on behalf of users (custodial/semi-custodial).
  • Trade-off: Removes UX friction but introduces centralization and cost.

3. Tooling Recommendations​

  • IDEs: VS Code remains the standard.
  • AI Assistants:
    • Warp: An AI-integrated terminal that improves CLI productivity.
    • Claude: Recommended by the community for coding assistance.
  • SDKs: MeshJS and Cardano Serialization Library (CSL) are the go-to libraries for TypeScript/JavaScript developers.

Resources​

Last updated on