Ecosystem Strategy

How TrustBid moves from being an app that verifies NGOs to being trust infrastructure that other projects, protocols, and Stellar developers consume.

1. From app to protocol

The tagline says it: "transparency infrastructure." Infrastructure is not used alone — others build on top of it.

TrustBid is not the final destination of the data. It is the source of truth that others query: on-chain record + standard schema + open contracts/SDK/API.

That turns TrustBid from an app into a protocol — and that is where the defensible moat is.

Analogy: on Ethereum, EAS / Verax (Ethereum Attestation Service) are infrastructure that hundreds of apps query. TrustBid can be the impact attestation and fund traceability registry for Stellar. Whoever defines the schema, defines the standard.

2. The model — attestation layer

TrustBid badges/ACTAs (Soulbound Tokens on Soroban) and their proofs live on-chain, with a public and standard schema. That makes them queryable by anyone, without asking TrustBid for permission.

+-----------------------------------------------+
|  TrustBid: issues verifiable attestations     |
|  (KYB, completed milestones, executed funds)  |
+----------------------+------------------------+
                       | on-chain, standard schema
+----------------------+------------------------+
|          Public read layer                    |
+------+--------+--------+--------+-------------+
       |        |        |        |
   wallets  anchors   DeFi/   grants/    watchdogs
                    lending   DAOs      auditors

3. Integration surfaces

Attestations as a public good (read layer)

Composable primitives on Soroban

Contracts that others call from their own contracts:

• Attestation registry (public read): verify_org(address) -> Status, get_badges(address)
• Milestone escrow: releases funds when a TrustBid attestation confirms a milestone — any crowdfunding/grant plugs in without building their own verification logic
• Reusable ZK verifier (groth16_verifier): others prove compliance without exposing data, reusing TrustBid's primitive

SDK + API for developers

JS SDK + REST/GraphQL — a developer adds "TrustBid Verified" to their app in a few lines. Webhooks when an attestation is issued or revoked.

Monetization with MPP: the API charges per query (pay-per-verification), settled in USDC on Soroban.

Accountability layer on top of SDP

The Stellar Disbursement Platform moves money outward; no one certifies it arrived and worked. TrustBid is that proof layer.

One-line positioning: "the accountability layer on top of SDP." This is a framing the Stellar Development Foundation understands immediately.

4. Standard strategy

Composability requires shared schemas. If TrustBid defines the schema, TrustBid becomes the de facto standard.

• Propose a SEP / schema for "impact attestations and fund traceability"
• Being the reference implementation = being the standard
• Open-source the attestation contracts → developer adoption → TrustBid tooling becomes the ecosystem default

5. Go-to-ecosystem

Stellar Community Fund (SCF)

Building a public good for financial transparency in LatAm is exactly what the SDF funds and promotes. Provides funding + distribution + credibility.

Read partnerships

Integrating the badge in 1–2 wallets and 1 regional anchor creates the first network effect.

Complement, not compete

Positioning alongside the SDP (not against it) opens the door to direct collaboration with the SDF.

6. Defensible moat

• Standard: whoever defines the attestation schema wins ecosystem lock-in.
• Network effect: every wallet/anchor/protocol that reads TrustBid increases the value of being TrustBid-verified.
• Data: the audited fund history is a cumulative asset that is hard to replicate.

7. Next steps

1. Define and publish the attestation schema (fields, version, revocation)
2. Deploy the attestation registry on Soroban (Testnet) + public read contract
3. Publish a minimal SDK (verify_org, get_badges) and developer documentation
4. Get 1 wallet + 1 anchor to display/consume the badge (proof of network)
5. Apply to SCF with the "accountability layer on top of SDP" framing

Relation to other docs: Stellar Integrations covers the technical what — SEPs and Stellar tools mapped to TrustBid's processes. This document covers the strategic how — turning those integrations into a layer the ecosystem consumes.