Credential Lifecycle

​

Creation

1. Worker authenticates with a Stellar wallet.
2. Backend indexes incoming payments.
3. Backend stores exact payment amounts as authenticated ciphertext.
4. Worker classifies qualifying income payments.
5. Worker selects a proof type and condition.
6. Backend evaluates the condition.
7. Backend creates a canonical credential payload.
8. Backend signs the credential with the configured credential signing secret.
9. Backend returns a proof ID, signed credential, and public verification URL.
10. If enabled, backend contract anchoring registers the proof commitment on Soroban through the deployed proof registry.

​

Credential Shape

{
  "id": "proof_01JXYZ123",
  "version": "1.0",
  "type": "minimum_income",
  "issuer": {
    "id": "issuer_earnproof",
    "name": "EarnProof",
    "publicKey": "G..."
  },
  "subject": {
    "walletHash": "sha256:..."
  },
  "network": "stellar-testnet",
  "asset": {
    "code": "USDC",
    "issuer": "G..."
  },
  "claim": {
    "operator": "greater_than_or_equal",
    "threshold": "1000",
    "frequency": "monthly",
    "satisfied": true
  },
  "disclosure": {
    "exactAmountRevealed": false,
    "sourceTransactionsRevealed": false,
    "senderRevealed": false
  },
  "expiresAt": "2026-08-13T12:00:00Z",
  "commitment": "0x...",
  "signature": "..."
}

​

Verification

• schema version,
• signature,
• expiration,
• revocation,
• issuer metadata,
• optional on-chain commitment status,
• disclosed claim result.

​

Expiration

​

Revocation

​

Portability