The rule
Tythe builds what no one else does: the underwritten principal, the mandate enforced at your account, the agent underwritten on conduct, the on-chain credit market, and the intelligence that compounds from every transaction. Tythe rents what others already do best: the chain, the stablecoin, the payment rail, the venues, identity, verification, bank-data access, oracles, and screening. Routed costs are passed through at cost. Every provider below is a counterparty you can inspect. Contract addresses are listed under Contract addresses once deployed.Chain and settlement
Base
Base
The only chain in V1. Every Tythe contract, account, mandate, Loan, and market lives on Base. Tythe’s oracle router enforces the Base sequencer-uptime check on every price read, so a sequencer outage can never serve a stale price into a credit or coverage calculation. Ethereum venues are on the roadmap.
USDC
USDC
The only account asset in V1. Chosen because it is the native asset of x402, because a single asset per account keeps accounting and liens exact, and because USDC’s contract supports contract-account signatures, which is what lets your account be an x402 payer directly. Additional stablecoins are priced through the oracle router when added.
Agent payments
x402
x402
The agent payment rail. A resource returns HTTP 402 with its price; the agent signs a stablecoin authorisation; a facilitator verifies and settles it on-chain. Originated by Coinbase in May 2025, now governed by the x402 Foundation under the Linux Foundation with backers including Cloudflare, Stripe, AWS, Google, Visa, and Circle.On Tythe, your account is the payer. Your agent opens a payment session that reserves a bounded amount and a range of one-time nonces; the account validates each payment intent against the agent’s mandate through the ERC-1271 signature standard that USDC’s contract honours; the facilitator cannot change the amount or the destination. No funds leave your account before the moment of payment.
Facilitators
Facilitators
Sellers choose the facilitator that settles their x402 payments. Tythe-operated paths use the Coinbase Developer Platform facilitator at launch, which screens transactions against sanctions and risk lists, with a self-hosted facilitator kept ready as a fallback. A facilitator can only broadcast what your account signed.
Direct payments and fiat rails
Direct payments and fiat rails
Direct payments to counterparties on your allowlist settle as USDC transfers from your account. Where a principal needs regulated fiat rails, Paxos-class providers are used. Tythe runs no on- or off-ramp of its own in V1.
Venues
Save deposits go from your account to curated venues on Base through a stateless adapter that holds nothing between calls. Every venue is a standard ERC-4626 vault; Tythe reads value from the venue’s own accounting, never from a spot price.
Further curator vaults are added as Tythe’s venue intelligence clears them; the live allowlist, with each venue’s signals and flags, is in the Intelligence dashboard. Tythe curates and publishes; you or your agent allocate. Tythe never moves funds into a venue on its own initiative.
Venue selection is informed by live verification, not by advertised yield. Tythe’s own testing found curated vaults that were at their supply cap, and one that had renounced ownership so its configuration can never change. Those facts are published as flags, not hidden.
Identity and verification
ERC-8004
ERC-8004
The agent identity, reputation, and validation standard, live on Ethereum since January 2026 and deployed on Base, backed by the Ethereum Foundation, Coinbase, Google, and MetaMask. Every Tythe agent is an ERC-8004 identity. Tythe publishes bounded standing summaries to the reputation registry and mandate-compliance facts to the validation registry, so a Tythe agent’s record is verifiable by any counterparty that reads the standard. Publication can be turned off per agent.
Sumsub
Sumsub
Identity verification for individuals; business verification, beneficial-ownership checks, and sanctions screening for entities. Documents stay with the provider. Tythe stores only a verification reference on-chain.
Bank data
With a principal’s explicit, recorded consent, bank balances and transactions are read through a regional provider to strengthen underwriting: Plaid in the United States, Tink or Salt Edge in the EU and UK, Lean in the UAE and wider MENA, Belvo in Latin America. Data is encrypted with per-principal keys, used only by the underwriting pipeline, never written to the chain, and purged on revocation. See Data and privacy.Oracles
Chainlink is the primary price source and RedStone the secondary. Every read checks staleness, checks divergence between the two, and checks the Base sequencer feed. A read that fails any check reverts rather than returning a price.Compliance screening
Sanctions and wallet-risk data from established providers maintain the denylist that every mandate references and feed the Agent Engine’s monitoring. Tythe does not build screening.Smart-account standards
Tythe accounts are ERC-4337 modular smart accounts built on OpenZeppelin’s audited implementation, with Tythe’s mandate check installed as the account’s validator and Tythe’s hook as its guard. Agents are registered on the account as scoped session signers. These are open standards; the contracts are Tythe’s and are listed under Contract addresses.What Tythe does not rent
The mandate check, the entity account and its hook, the credit market, capture, the lien, the loss waterfall, the first-loss reserve, the attestation registry, and the three engines of the Intelligence Layer. These are Tythe’s, on-chain and off, and they are what the rented layers above are wrapped in.Provider choices are current as of launch planning and may change. Any change to a provider that touches your funds or your data is announced before it takes effect.
Verify further
Contract addresses
Every Tythe contract, venue, registry, and feed on Base.
Trust and transparency
What is on-chain, what is attested, and what Tythe cannot do.