Build an institutional Earn program
Choose the company you are building for. Every guide starts with a deployable file structure and continues through credentials, complete product data, customer eligibility, transaction signing, canonical completion, events, reconciliation, testing, and production controls.
Start with the complete credit lifecycle. It is the shared product contract from discovery, deposit, tranches, yield, and redemption through impairment monitoring, optional Distressed Recovery Fund participation, claims, and final reconciliation. Every audience guide applies that lifecycle to its own wallet, custody, ledger, tenant, and support boundaries.
controlled developer access. The documentation is public. Applications, credentials, SDK packages, role scopes, Sepolia access, and production admission remain controlled controlled distribution access.
Wallet-native Earn
Discovery, wallet consent, canonical completion
Load deep vault, market, liquidity, and eligibility state.
Show the exact product, amount, fees, and prepared intent.
The customer wallet simulates and submits the transaction.
Wait for final_success, then reread the position.
Catalog, vault detail, position, and redemption views.
Origin-bound challenge and short-lived customer authority.
Prepare, register, and canonical transaction tracking.
Signed events plus canonical resource rereads.
Distribute Torq Earn
Build and package Earn products
Integrate Torq into an existing protocol
One non-negotiable completion rule
All seven architectures follow the same trust boundary:
Torq canonical resources -> proposed action -> prepared transaction -> customer-owned signer
-> registered transaction -> canonical final_success -> affected-resource rereadNever calculate product-visible shared state from RPC, accept caller-constructed contract calls,
credit a customer from a transaction receipt alone, or expose a secret key in a browser. Use the
API reference, SDK reference, AI integration guides, and the checked-in
examples/developer-platform/earn-program-reference implementation together with the selected
playbook.