Wallet and Protocol Authority

Who authorizes a TSN payment and which protocol layer verifies private state or controls settlement.

The connected owner’s wallet remains the source of owner authorization. The application prepares the information for review and requests the wallet signature; TSN services and Crankers do not receive the owner’s wallet private key.

Each layer has a separate role:

• TIP manages transfer identity and route information. Wallet recovery uses an encrypted record separate from the main TIN registry account.
• GPRU guards the integrity and privacy of the user’s private state presented to TCAP. A proof is not a payment authorization or a funds key.
• TCAP governs accepted assets and reserve liquidity, and applies valid authorized changes atomically.
• Cranker submits authorized transactions and pays their network fees. Fee payment does not grant authority to edit the transaction’s terms.

The hidden-head proof path is not established end to end. An application should not promise that a proof, key commitment, or service response alone enables a settlement.

Credential custody, key rotation, and operator configuration are implementation and operations topics documented in the repository runbooks.