Stellar Integrations

Technical integration map. Maps each piece of the Stellar ecosystem to TrustBid's core processes: reputation, audit, financial management, donations, and anti-impersonation.

1. How Stellar fits TrustBid

TrustBid needs three things that Stellar solves natively:

• An immutable, live ledger where every fund leaves a trace — Stellar's ledger (~5s, ~$0.00001 per tx)
• A stable asset to move real money without volatility — USDC on Stellar (issued by Circle)
• Identity and compliance standards already written (the SEPs) — no need to reinvent KYC/KYB, auth, or ramps

The trust layer (badges, proofs, reputation) is built on Soroban — Stellar's smart contract platform.

2. Integration map

3. Identity and anti-impersonation

SEP-1 — stellar.toml

The organization publishes a file at https://theirdomain.org/.well-known/stellar.toml declaring their identity, accounts/assets, signing keys, and KYC server URL.

In TrustBid: each verified NGO has their stellar.toml. It links the real domain (controlled by the org) with their Stellar accounts. Impersonation would require controlling the domain — the first anti-fraud barrier.

SEP-10 — Stellar Web Authentication

Challenge-response login: the server sends a transaction that only the account owner can sign. Upon signing, the user receives a session token (JWT). Proves account control, not just password knowledge.

In TrustBid: authenticates NGOs and wallets before any sensitive action (viewing funds, issuing badges, requesting KYB). Prerequisite for SEP-12.

SEP-45 is the equivalent for Soroban contract accounts.

SEP-12 + SEP-9 — KYC / KYB

SEP-9 defines the standard field catalog (person and organization: organization.name, registration, address, etc.). SEP-12 is the API (PUT/GET /customer) to submit and query that information in a structured way. Requires SEP-10.

In TrustBid: we run (or integrate) a KYC_SERVER declared in the stellar.toml. For KYB, we collect SEP-9 organization fields and validate them against a business verification provider (Sumsub, Persona, etc.) or manually in Phase 1. The KYB result feeds directly into the reputation badge (section 4).

Anti-impersonation stack: SEP-1 (domain) + SEP-10 (account control) + SEP-12/KYB (validated business) + reputation SBT (section 4). Four layers.

4. Verifiable reputation

Badges as Soulbound Tokens (SBT)

An SBT is a non-transferable token tied to an account — ideal for credentials: they cannot be sold or faked, and they are verified by reading the chain without calling the issuing entity.

Reference pattern: Chaincerts already issues verifiable non-transferable certifications via Soroban contracts.

In TrustBid: each time an NGO meets an objective (project milestone, correct fund execution, approved audit), TrustBid issues a badge/ACTA as an SBT to their account. A donor views the account and verifies on-chain which goals were met — they see it, not just believe it.

Zero-knowledge proofs on Soroban

Since Protocol 22 (CAP-0059), Soroban includes host functions for the BLS12-381 curve, enabling on-chain verification of zk-SNARKs (Groth16). A reference contract exists (groth16_verifier).

In TrustBid: proving claims without exposing private data. Example: "this project spent within budget and met the funder's criteria" can be proven and verified on-chain without publishing sensitive financial detail.

Maturity: Phase 3, after SBT and audit are working.

5. Donations and crowdfunding

Stellar Wallets Kit (SAK)

Library (@creit.tech/stellar-wallets-kit) that connects all Stellar wallets with a single API: Freighter, xBull, Albedo, Rabet, and WalletConnect.

In TrustBid: "Donate" button → donor connects their wallet → signs USDC transfer to the project. The donation is signed by the donor (verifiable) and on the ledger (traceable).

SEP-7 — Payment URI scheme

Generates web+stellar:pay?... links and QR codes with preset destination, amount, and memo.

In TrustBid: each campaign/project has its donation link and QR (shareable on social media, email, in person). The memo tags the donation to the correct project — automatic traceability.

SEP-24 / SEP-6 — Ramps (fiat ↔ USDC)

Allow donating by card or bank transfer (fiat) and receiving USDC via an anchor. SEP-24 is interactive flow (hosted); SEP-6 is programmatic.

In TrustBid: Phase 2, for donors without crypto. We integrate a regional LATAM anchor offering USDC on-ramp.

MPP — Machine Payments Protocol (exploratory)

Payment protocol over HTTP (extends 402 code) designed for AI agents and APIs. Relevant for TrustBid in two future cases: (a) monetizing our data/verification API per query, and (b) AI-initiated donations. Not on the critical path.

6. Fund disbursement to beneficiaries

Stellar Disbursement Platform (SDP)

Open-source platform from the Stellar Development Foundation for mass payments: upload a list of recipients and amounts (up to 10,000 payments per batch) and disburse. Natively integrates SEP-10 and SEP-24.

In TrustBid: when an NGO distributes aid to many beneficiaries (subsidies, scholarships, field payments), we use SDP. Each payment lands on the ledger and feeds directly into audit and reports.

SEP-8 — Regulated Assets (optional)

The asset issuer approves (or rejects) each transfer via an approval server.

In TrustBid: if a funder requires that funds only reach pre-approved recipients, SEP-8 enforces that rule at the protocol level.

7. Audit and traceability

Horizon API (and/or Soroban data) exposes the complete transaction history of each account/project, live. In TrustBid: we index the movements of each project and generate certified financial reports, segmented by period. Since the source is the immutable ledger, the report is independently verifiable — auditors can cross-check against the chain.

8. Tech stack

9. Phased roadmap

Phase 1 — Trust base and donations

SEP-1 + SEP-10 + Stellar Wallets Kit + SEP-7 + USDC + ledger reading for basic audit. Enables: identity, in-platform donations, traceability.

Phase 2 — Compliance and scale

SEP-12/KYB + SDP (disbursements) + SEP-24 ramps + SBT badges. Enables: KYB, fund distribution, verifiable reputation, fiat donations.

Phase 3 — Advanced privacy

ZK proofs (Soroban BLS12-381) + SEP-8 if a funder requires it. Enables: proving compliance without exposing data.

Exploratory

MPP for monetized API / AI agents.

Sources

• MPP on Stellar
• Stellar Disbursement Platform
• Stellar Wallets Kit
• SEP-0012 (KYC API)
• SEP-0009 (Standard KYC Fields)
• Protocol 22 — BLS12-381
• groth16_verifier
• Chaincerts SBT on Soroban