INTRODUCTION

The walkaway test

Here's the question we hold every design decision against: if Tab Labs walked away tomorrow — servers off, team scattered, domain expired — would the users still have their money?

What survives

• The contracts. TabRouter and TabBotRouter are immutable. They keep settling payments forever, with or without us.
• The wallets. Keys are on user devices, encrypted under their PINs. They can be exported to any EVM wallet — they are just plain secp256k1 keys.
• The on-chain history. Every settled payment is a public event. Anyone with an RPC and the ABI can rebuild the ledger.

What goes away

• The hosted relayer, so users pay their own gas until someone else runs one.
• The hosted checkout pages and the off-chain handle resolver, so you'd need to know the recipient's wallet address directly.
• The webhooks and the dashboard, both replaceable with a general-purpose indexer.

The point

Every product decision is supposed to maintain that property. If a new feature would put Tab in the path of the funds — even briefly, even just for convenience — it doesn't ship. The walkaway test is the single hardest constraint in the codebase, and it's why the contracts are this short.