research: add TrusTrove Stellar Wave submission

[Halimatyemisi]

Overview

This PR adds a complete research submission for TrusTrove, a decentralized trade finance protocol on Stellar, to the Stellar Wave Hub. SMEs tokenize unpaid trade invoices as Stellar assets and receive immediate USDC funding from a shared liquidity pool at a small discount — replacing the 30–90 day wait for buyer payment and the gatekeeping of traditional invoice factoring.

The submission was researched independently from the project's website, GitHub repositories, documentation, the Drips Stellar Wave registry, and live on-chain explorer data. It covers the four Soroban contracts, the invoice lifecycle state machine, the attestation/underwriting flow, fund flow, team and community information, and documented centralization risks and roadmap.

Related Issue

Closes #315

Changes

📝 Research File

• [ADD] research/trustrove-stellar-wave-submission.md
  • Project identity, category, and Stellar Wave program verification (Drips-approved, Stellar Wave GitHub label).
  • Original problem description (292 words) on the $2.5T global trade finance gap and how TrusTrove addresses it.
  • How the project uses Stellar: Soroban contracts, USDC/Stellar Asset Contract, fast finality + low fees, anchor network.
  • Technical approach: 4-contract architecture, invoice lifecycle, attestation/underwriting flow, fund flow, LP accounting, known centralization risks and roadmap.
  • Team and community info: founder (K1NG4DVID), org stats, contribution pipeline, Stellar Wave participation details.
  • Category (defi) and relevant tags.
  • Supporting sources and on-chain verification details.

🖼️ Supporting Screenshot

• [ADD] research/trustrove-architecture.png
  • Architecture and on-chain verification diagram (contract interaction map + verified addresses).

👥 Contributors

• [MODIFY] CONTRIBUTORS.md — add Halimatyemisi as Researcher — TrusTrove.

Verification Results

On-chain verification (Stellar Expert Testnet REST API, 2026-08-31):
✅ registry_contract CABGWVIZFF62FG67ZGFEP67NEEY4WYTMFURDMFTKKNRDAFPKPOJDTN4C — created 1781353193
✅ invoice_contract  CA4O3MR7LWHRSUDBNU6FY6UDFFYBN7TGBZXBDZB4OYYXFYXIFJ6RJF6B — created 1781353238
✅ escrow_contract   CAJWGUKDTTC3SKN4RAAY72J4DVIIYSCFHX6GIMNTT22ABMISJK4GBCEH — created 1781353283
✅ pool_contract     CAKEWH7SJCXGV2MH2WZYIX3QDPTSSBQFXYVYBOWAGLNBBZMPLE2US6CS — created 1781353308
✅ All 4 contracts share deployer GDDWFYWXCSBI6RNS5TV2ZZSBYY35MDKHR2424O7RVL6LDC4DUTBTVR2Z
✅ Confirmed approved on Drips Stellar Wave registry (waveProgramId fdc01c95-...)
✅ Confirmed NOT already listed on Stellar Wave Hub
✅ Original description = 292 words (meets >=200 requirement)

Acceptance Criteria	Status
This is a Stellar Wave Program project	✅ Approved on Drips Stellar Wave registry + Stellar Wave GitHub label
The project was not already listed on Stellar Wave Hub	✅ Search returned 0 results at submission time
The description is original and contains at least 200 words	✅ 292 words in problem section
The research goes beyond the project's marketing material	✅ Threat model, storage schema, events, attestation flow, known gaps (Issue #56) covered
Stellar accounts or Soroban contracts have been verified	✅ 4 contracts verified live on testnet via Stellar Expert API
The category and tags are accurate	✅ defi / trade-finance, invoices, soroban, stellar, usdc, escrow, rwa
Supporting screenshots have been included	✅ research/trustrove-architecture.png
CONTRIBUTORS.md was updated or a research.md file was added	✅ Both

[vercel]

@Halimatyemisi is attempting to deploy a commit to the webverse Team on Vercel.

A member of the Team first needs to authorize it.

[samieazubike]

Kindly complete the requirements on the issue

[Halimatyemisi]

Thanks for the feedback! I have now completed all the requirements on the issue, including the one that was missing — actually submitting TrusTrove to the Hub.

What was incomplete

The previous revision only added the research documentation (research/trustrove-stellar-wave-submission.md + architecture diagram + CONTRIBUTORS.md entry). The research file claimed the project was "submitted," but the project record was not actually created in Stellar Wave Hub — a live GET /api/projects/queue returned no TrusTrove entry, so there was nothing for an administrator to review.

What I did to complete it

1. Registered on the Hub and logged in with a contributor account.
2. Uploaded the research image (architecture & on-chain verification diagram) via the Hub's /api/upload (research-images bucket).
3. Submitted the project through the Hub's Submit-a-Project flow (POST /api/projects) with:
   • Name: TrusTrove
   • Category: defi (trade finance / invoice factoring)
   • Network: testnet (matches the four verified Soroban contracts)
   • Verified Soroban contract ID: CABGWVIZFF62FG67ZGFEP67NEEY4WYTMFURDMFTKKNRDAFPKPOJDTN4C (registry)
   • Verified Stellar account: GDDWFYWXCSBI6RNS5TV2ZZSBYY35MDKHR2424O7RVL6LDC4DUTBTVR2Z (deployer)
   • GitHub repos (contract + app), tags, website, and the research image.
   • Original description of 276 words (≥ 200 required).
4. Confirmed the record is live in the Hub's submission queue — GET /api/projects/queue now returns TrusTrove as Hub project ID 128, slug trustrove, status submitted (awaiting admin review), attributed to user Halimatyemisi.

Updated in this PR (commit 25f4a8d)

• research/trustrove-stellar-wave-submission.md: replaced the unverified "Submission Details" section with a Hub Submission Confirmation section documenting the real project ID (128), slug, status, submitted network, and the uploaded research-image URL — matching the format used by accepted submissions (e.g. AgentPay research: add AgentPay Wave profile #357, OverSync research: add OverSync Wave profile #358).

Validation checklist status

• Stellar Wave Program project (Drips-approved, Stellar Wave GitHub label)
• Not already listed on Stellar Wave Hub
• Original description ≥ 200 words (276)
• Research goes beyond marketing material (threat model, storage schema, events, attestation flow, known gaps)
• Stellar/Soroban contracts verified on-chain (4 contracts via Stellar Expert testnet API)
• Accurate category (defi) and tags
• Supporting screenshots included
• CONTRIBUTORS.md updated AND research/ file added
• Project actually submitted to the Hub (ID 128) — ready for administrator review

[Halimatyemisi]

@samieazubike Hi! This PR is open and ready for review — happy to address any feedback. Thanks!