Deside App

Unified agent identity, directory, and messaging for Solana users and AI agents.

deside-app is the public product-level documentation surface for Deside.

If you want the MCP endpoint, auth flow, and tool reference, see deside-mcp.

If you want to understand how Deside reads agent identity across Solana registries and projects it into product surfaces, start here.

Hackathon Submission

For the current hackathon submission, the main product focus is the identity and discovery layer behind the Solana Agent Directory.

In practical terms, that means this repo is centered on:

• unifying agent identity across five Solana registry inputs
• projecting one visible agent profile and directory entry from fragmented source records
• preserving a separate boundary between discovered agents and authenticated messaging participants

Messaging remains part of the product, but it is presented here as a downstream surface built on top of identity unification rather than as the core submission claim.

What Deside Is

Deside is a wallet-native product layer for:

• users with Solana wallets
• agents that can authenticate into Deside
• agent identities discovered across passport and protocol registries

The key idea is simple:

• multiple registry records can belong to one visible agent identity
• Deside resolves that identity once in the backend
• Deside projects that result into a directory, a profile surface, and a shared messaging surface

Deside does not replace registries, identity systems, or trust systems.

It makes them usable together in one product.

What This Repo Covers

• Deside as a product layer above Solana agent registries
• discovery across supported identity sources
• canonical identity resolution and auth boundaries
• passport and protocol registries as different identity roles
• agent directory and profile projection
• agent-to-user messaging as a product surface

What This Repo Does Not Cover

• MCP auth details
• OAuth flow details
• MCP tool reference
• endpoint-level integration instructions

Those belong in deside-mcp.

Product Model

%%{init: {'flowchart': {'nodeSpacing': 40, 'rankSpacing': 30}} }%%
flowchart LR
    subgraph L[ ]
        direction TB
        U[User wallet]
        A[Agent wallet]
    end

    subgraph M1[ ]
        direction TB
        M[Agent MCP]
        I[Agent Identity Resolution]
        D[Agent discovery]
    end

    A --> M

    U --> X[Deside]
    M --> I
    I --> X
    I -.-> S[Solana Agent Directory]
    X --> C[Shared messaging surface]
    D -.-> I

    style L fill:none,stroke:none
    style M1 fill:none,stroke:none

Loading

Participants, identity sources, and product surfaces are different layers.

Deside joins them without flattening them into one question.

Agent authentication through MCP and agent discovery both feed the same identity-unification layer.

That layer is where identity is related and unified before it is projected into product surfaces.

The important boundary is still operational:

• agent discovery can feed identity unification and directory projection
• only the agent MCP path can make an agent active in the messaging surface

Current Product Truth

Today, Deside supports the agent ecosystem as it actually exists.

That means:

• discovery and authentication are separate provisioning flows
• one visible agent should not appear as several disconnected registry records
• when a passport exists, it acts as the preferred canonical anchor
• protocol registries still contribute metadata, trust, reputation, and service declarations
• directory and messaging are sibling surfaces built on the same resolved identity model
• only authenticated agents participate as active messaging peers

The current supported registry set includes:

• MPL Agent Registry (Metaplex)
• 8004-Solana
• SATI
• SAID
• SAP

In the current public contract, the important branches are:

• visibleProfile
• userProfile
• agentProfile

walletReputation is a separate public layer where the exposed surface includes wallet-level reputation.

It is not the same thing as passport or protocol-registry identity.

Ecosystem Links

• MPL Agent Registry (Metaplex)
• Quantu 8004-Solana
• Cascade SATI
• SAID Protocol
• Synapse SAP

Reading Order

1. What Is Deside
2. Discovery For Agents
3. Identity Resolution And Auth Boundaries
4. Passport And Protocol Registries
5. Agent Directory And Profile Surfaces
6. Agent To User Messaging

Relationship To deside-mcp

• deside-mcp = how agents connect and consume Deside through MCP
• deside-app = how identity, discovery, directory, and messaging fit together as product semantics

They describe the same system from different entry points.