How funding works
When a sender funds an epoch, the signed transaction sends tokens directly to the epoch treasury token account. The funding transaction deliberately excludes the opaque slot. The treasury increments its aggregate pending liability to reflect the incoming funds.Opaque slots and the treasury
The opaque slot is derived by Node/Mother with HMAC-SHA256 usingTSN_NODE_CLAIM_SLOT_HMAC_SECRET. It is deliberately absent from the funding transaction. The EpochClaimSlot PDA is derived from the epoch treasury and opaque slot, and the TSN program initializes it on the first valid settlement or refund. This means the slot does not appear on chain until settlement or refund occurs.
The first valid operation wins atomically. A slot marked SETTLED or REFUNDED can never be reused.
Operational visibility
Operational dashboards may show aggregate counts, transaction signatures, and slot resolution status. They never decrypt or persist the private payment binding. The binding is encrypted off-chain by Node/Mother, and the encryption key never leaves Node/Mother.Epoch close gate
An epoch can close only after pending liability reaches zero and every opaque slot is resolved asSETTLED or REFUNDED. This is enforced by the TSN program, not just by Node attestation.
Related pages
- Mother authority for how the SettlementDna PDA and opaque slots are managed
- Funding and accepted intent for the developer flow from funding to intent acceptance