Identity & DIDs

Every Flowsta user gets a W3C-compliant Decentralized Identifier.

W3C DIDs

Flowsta generates a W3C DID for each user based on their Ed25519 public key:

did:flowsta:uhCAk7JpEWfkiV_RdAFfCnRZcJ9PwJR4yTLN-E3EcVU7KYCnRRZc

DID Properties

Property	Value
Method	did:flowsta
Key type	Ed25519
Self-sovereign	User owns the DID, not Flowsta
Portable	Works with any DID-compatible system
Verifiable	Cryptographically linked to user's keypair
Deterministic	Same recovery phrase always produces the same DID

Accessing a User's DID

Via OAuth:

const auth = new FlowstaAuth({
  clientId: 'your_client_id',
  redirectUri: 'https://yourapp.com/callback',
  scopes: ['openid', 'did']
});

const user = await auth.handleCallback();
console.log('DID:', user.did);
// did:flowsta:uhCAk7JpEWfkiV_RdAFfCnRZcJ9PwJR4yTLN-E3EcVU7KYCnRRZc

Via userinfo API:

{
  "sub": "550e8400-...",
  "did": "did:flowsta:uhCAk...",
  "agent_pub_key": "uhCAk7JpEWfkiV..."
}

Agent Public Keys

Each user also has a Holochain agent public key (uhCAk... format). This is the raw Ed25519 public key used for:

• Signing Holochain actions
• Agent linking attestations
• Identity verification on the DHT

The DID and agent public key represent the same underlying Ed25519 keypair in different formats.

Identity Linking

Users can prove their Flowsta identity across multiple Holochain apps using agent linking. Each app has its own agent key, but IsSamePersonEntry attestations on the DHT prove they belong to the same person.

Next Steps

• Agent Linking - Cross-app identity verification
• Holochain Architecture - DHT and DNA details
• For Holochain Developers - Integration guide