1. Strategic Context
This feature is a focused TRON integration sprint. The strategic rationale:
• TRON hosts over $86 billion in stablecoin supply — the dominant USDT settlement layer globally.
• TRON DAO expanded its AI Fund to $1 billion in March 2026, with agent identity systems listed as a primary investment vertical.
• TRON joined the Linux Foundation's Agentic AI Foundation (AAIF) as a Gold Member with a Governing Board seat.
• AINFT/Bank of AI, TRON's in-house AI agent stack, implements a proprietary identity protocol (8004) with weak W3C alignment. OP is the open-source, standards-compliant alternative.
• TRON uses secp256k1, which is architecturally compatible with OP's existing cryptographic stack.
The goal of the feature is a working TRON demo with USDT-TRC20 flowing through OP-attested agent identity using OP's existing did:web — sufficient to open BD conversations without any TRON commitment required first.
2. Objectives
01 TRON payment rail live: Add USDT-TRC20 to OP's multi-rail payment stack. Minimum viable unlock for any TRON BD conversation.
02 TRON agent demo: A working single-agent demo: agent holds a TRON wallet, transacts with USDT-TRC20, OP did:web attests to the interaction, VAC issued on-chain.
03 Differentiation narrative: A clear, public-facing technical comparison of OP vs. AINFT/8004, establishing OP as the W3C-standards-compliant open alternative.
3. Workstreams
Workstream 1 — TRON Payment Rail Integration
Add USDT-TRC20 to OP's existing multi-rail payment architecture alongside Lightning/L402, x402, Solana, Tether WDK, and Stripe MPP. Uses OP's existing did:web — no new DID method required.
Note: A TRON-native DID method is explicitly out of scope. did:web works with TRON wallet keypairs today and is sufficient for the demo and for BD conversations. A native DID method is only on the table after a TRON commitment — and should be scoped and potentially funded as part of that engagement.
Workstream 2 — TRON Agent Demo
A minimal but complete single-agent demo showing an OP-registered agent transacting with USDT-TRC20 on TRON, with OP did:web attestation and VAC issuance. This is the BD-facing artifact.
Workstream 3 — Differentiation Narrative & BD Materials
Non-build workstream. Produces materials to open BD conversations with TRON AI Fund, AINFT, JustLend, and other ecosystem targets.
4. Milestones & Timeline
Phase 2 total estimate: 5–6 weeks from kickoff, assuming Leo can shift primary focus after OWS demo stabilizes.
Milestone Description Target
M1 TRON payment rail live on testnet — USDT-TRC20 send/receive from agent wallet with did:web attestation. Week 2
M2 OP vs. 8004 comparison published and TRON BD one-pager updated. Week 2
M3 TRON demo 4-act flow running end-to-end on testnet. Observer API TRON endpoints live. Week 4
M4 Full demo validated on TRON mainnet with real USDT-TRC20 transaction. Week 5
M5 TRON AI Fund outreach sent. AINFT and JustLend BD materials complete. Week 5
M6 Phase 2 complete. OP positioned as open W3C identity layer for TRON AI agents. Week 6
5. Dependencies & Risks
Dependencies
• OWS demo reaching stable state before Leo pivots primary focus to TRON workstreams.
• TronGrid API access and TRON Nile testnet availability for integration testing.
• Grace H. (TRON DAO AI Fund) relationship: outreach timing tied to demo milestone M4.
• AIP v0.2 stability — no spec changes assumed during this sprint.
Risks
• secp256k1 / TVM compatibility edge cases may require additional time in WS1. Mitigation: spike on TronGrid integration in week 1 before committing to timeline.
• AINFT/Bank of AI may accelerate 8004 development. Mitigation: prioritize WS3 differentiation materials early, independent of build completion.
• TRON DAO AI Fund application process not yet publicly defined. Mitigation: use Grace H. relationship to get ahead of formal process.
6. Out of Scope
Explicitly deferred. Do not build these in this feature regardless of technical feasibility.
• TRON-native DID method — deferred until TRON commitment exists. Potentially a funded deliverable in a future engagement.
• EVM / BTTC integration — relevant for ETHGlobal; evaluated separately.
• JustLend or SunSwap smart contract integrations — BD conversation first, technical integration is Phase 3.
• TRC-10 token support — USDT-TRC20 (TRC-20) only for Phase 2.
• Sovereign AT TRON wallet login flow — Phase 3.
• TRON-specific AIP extensions — AIP v0.2 used as-is.
7. Success Criteria
The feature is complete when all of the following are true:
• An OP-registered agent can send and receive USDT-TRC20 on TRON mainnet using did:web identity.
• OP issues a Verifiable Agent Credential referencing a real TRON transaction hash.
• The TRON 4-act demo flow runs end-to-end and is documented for async sharing.
• The OP vs. 8004 technical comparison is published.
• At least one TRON AI Fund / ecosystem BD conversation is initiated using the demo as the hook.
1. Strategic Context
This feature is a focused TRON integration sprint. The strategic rationale:
• TRON hosts over $86 billion in stablecoin supply — the dominant USDT settlement layer globally.
• TRON DAO expanded its AI Fund to $1 billion in March 2026, with agent identity systems listed as a primary investment vertical.
• TRON joined the Linux Foundation's Agentic AI Foundation (AAIF) as a Gold Member with a Governing Board seat.
• AINFT/Bank of AI, TRON's in-house AI agent stack, implements a proprietary identity protocol (8004) with weak W3C alignment. OP is the open-source, standards-compliant alternative.
• TRON uses secp256k1, which is architecturally compatible with OP's existing cryptographic stack.
The goal of the feature is a working TRON demo with USDT-TRC20 flowing through OP-attested agent identity using OP's existing did:web — sufficient to open BD conversations without any TRON commitment required first.
2. Objectives
01 TRON payment rail live: Add USDT-TRC20 to OP's multi-rail payment stack. Minimum viable unlock for any TRON BD conversation.
02 TRON agent demo: A working single-agent demo: agent holds a TRON wallet, transacts with USDT-TRC20, OP did:web attests to the interaction, VAC issued on-chain.
03 Differentiation narrative: A clear, public-facing technical comparison of OP vs. AINFT/8004, establishing OP as the W3C-standards-compliant open alternative.
3. Workstreams
Workstream 1 — TRON Payment Rail Integration
Add USDT-TRC20 to OP's existing multi-rail payment architecture alongside Lightning/L402, x402, Solana, Tether WDK, and Stripe MPP. Uses OP's existing did:web — no new DID method required.
Note: A TRON-native DID method is explicitly out of scope. did:web works with TRON wallet keypairs today and is sufficient for the demo and for BD conversations. A native DID method is only on the table after a TRON commitment — and should be scoped and potentially funded as part of that engagement.
Workstream 2 — TRON Agent Demo
A minimal but complete single-agent demo showing an OP-registered agent transacting with USDT-TRC20 on TRON, with OP did:web attestation and VAC issuance. This is the BD-facing artifact.
Workstream 3 — Differentiation Narrative & BD Materials
Non-build workstream. Produces materials to open BD conversations with TRON AI Fund, AINFT, JustLend, and other ecosystem targets.
4. Milestones & Timeline
Phase 2 total estimate: 5–6 weeks from kickoff, assuming Leo can shift primary focus after OWS demo stabilizes.
Milestone Description Target
M1 TRON payment rail live on testnet — USDT-TRC20 send/receive from agent wallet with did:web attestation. Week 2
M2 OP vs. 8004 comparison published and TRON BD one-pager updated. Week 2
M3 TRON demo 4-act flow running end-to-end on testnet. Observer API TRON endpoints live. Week 4
M4 Full demo validated on TRON mainnet with real USDT-TRC20 transaction. Week 5
M5 TRON AI Fund outreach sent. AINFT and JustLend BD materials complete. Week 5
M6 Phase 2 complete. OP positioned as open W3C identity layer for TRON AI agents. Week 6
5. Dependencies & Risks
Dependencies
• OWS demo reaching stable state before Leo pivots primary focus to TRON workstreams.
• TronGrid API access and TRON Nile testnet availability for integration testing.
• Grace H. (TRON DAO AI Fund) relationship: outreach timing tied to demo milestone M4.
• AIP v0.2 stability — no spec changes assumed during this sprint.
Risks
• secp256k1 / TVM compatibility edge cases may require additional time in WS1. Mitigation: spike on TronGrid integration in week 1 before committing to timeline.
• AINFT/Bank of AI may accelerate 8004 development. Mitigation: prioritize WS3 differentiation materials early, independent of build completion.
• TRON DAO AI Fund application process not yet publicly defined. Mitigation: use Grace H. relationship to get ahead of formal process.
6. Out of Scope
Explicitly deferred. Do not build these in this feature regardless of technical feasibility.
• TRON-native DID method — deferred until TRON commitment exists. Potentially a funded deliverable in a future engagement.
• EVM / BTTC integration — relevant for ETHGlobal; evaluated separately.
• JustLend or SunSwap smart contract integrations — BD conversation first, technical integration is Phase 3.
• TRC-10 token support — USDT-TRC20 (TRC-20) only for Phase 2.
• Sovereign AT TRON wallet login flow — Phase 3.
• TRON-specific AIP extensions — AIP v0.2 used as-is.
7. Success Criteria
The feature is complete when all of the following are true:
• An OP-registered agent can send and receive USDT-TRC20 on TRON mainnet using did:web identity.
• OP issues a Verifiable Agent Credential referencing a real TRON transaction hash.
• The TRON 4-act demo flow runs end-to-end and is documented for async sharing.
• The OP vs. 8004 technical comparison is published.
• At least one TRON AI Fund / ecosystem BD conversation is initiated using the demo as the hook.