How an instrument works
1
Rendered
Counsel writes a versioned template. Your specific parameters, the amounts, the agent, the counterparties, the term, are filled in and the document is rendered deterministically. The same parameters always produce the same bytes.
2
Signed
You sign a typed message containing the document’s hash, the subject it governs, a nonce, and an expiry. Some instruments need a second signature: an agent’s key, or a wallet consenting to be bound.
3
Recorded
The hash is stored on-chain in the object the instrument governs. The rendered document is stored by its hash, and a copy is kept by Tythe.
4
Verifiable
Anyone with the template version and your parameters can re-render the document, recompute the hash, and confirm it matches the chain.
The final text of each instrument is being drafted by counsel for the governing law of each launch market and will be linked here before launch. The summaries below describe what each covers and are not the instruments themselves.
1. Account Agreement
The terms of holding a Tythe Account. That you own your keys and your account and Tythe holds neither. That Tythe is a noncustodial protocol operator, underwriter, and information provider, and is not a custodian, bank, or asset manager. Your responsibility for your keys. The fee schedule. The dispute process. How Tythe may restrict service in a jurisdiction. Governing law.
2. Agent Authorization
You appoint the named agent, identified by its ERC-8004 identity, as your agent. You accept responsibility for what it does within any mandate you issue to it. You warrant that you control its key. The agent’s co-signature is evidence that the key is yours to authorise; it is not consent by a legal person, because an agent is not a party. Without both signatures and this instrument, no agent can be bound.
3. Delegation Instrument
The mandate in prose. Budget and rolling period. Maximum per transaction. Counterparties. Permitted rails. Credit share and maximum tenor. Earn and lend authority. Expiry. Escalation threshold. Whether sub-delegation is allowed and to what depth. The values stated are the ceiling you granted; the instrument states that the effective value may be set below the ceiling by the Intelligence Layer and never above it. Revocation terms. A sub-delegation’s instrument references its parent’s, so the chain of authority is readable end to end.
4. Master Credit Agreement and Loan Schedules
The credit terms that govern every Loan you or your agents draw. Governing law. That Loans drawn by your mandated agents bind you. The lien over a fraction of your account balance as a security interest. Capture of revenue-tagged inflows to the schedule. That rate and term are fixed at origination. The capped late fee and the absence of origination, application, and prepayment fees. Default, the loss waterfall, legal recourse, and how recoveries are unwound. Each Loan Schedule states the principal, rate, term, schedule, floor, lien amount, and capture parameters of one Loan.
5. Subscription Agreement
The disclosures of lending. That you are supplying a pooled on-chain market and hold shares in it. The first-loss reserve and the waterfall order. The liquidity buffer and the redemption queue. That losses beyond the waterfall reduce share value pro-rata. Your representations as a verified participant. Risk of loss.
6. Data Consent
The provider, the accounts and the data scope, the purpose (underwriting only), encryption and access limits, retention, and your right to revoke, with the purge window that follows.
In the order you meet them
Verifying what you signed
Every signed instrument is shown in your console beside its hash. To verify one independently: take the template version and the parameters, both public; render them with the published renderer; hash the result with the template identifier and version. The hash matches the one on-chain, or the document is not the one you signed.Agreements
The same instruments from the legal side.
Operators and keys
The keys that sign them.