Glossary
| Term | Meaning |
|---|---|
| Bond | Funds locked in a vault to cover merchants if the payer overspends or double-spends |
| Confirmed | The settlement program has verified and paid a voucher. The only state in which funds have moved |
| Digest | sha256 of a voucher's signing message, used to tell a replay from a double-spend |
| Domain prefix | 0xff followed by contingency-voucher, prepended to every signed voucher message |
| Double-spend | Two different vouchers signed with the same sequence number |
| ed25519 program | Solana's built-in program that verifies ed25519 signatures before a transaction runs |
| Hop | One phone-to-phone transfer in the mesh. Messages can take up to 7 |
| Mesh | Phones relaying messages to each other over Bluetooth Low Energy, without internet |
| Offline vault | A Solana account holding funds reserved for offline payments |
| Overspend | Vouchers settling for more than a vault's balance |
| PDA | Program-derived address: an account address computed from seeds and the program id |
| Relayer | Whoever submits vouchers to Solana. Can earn the vouchers' tips |
| Replay | Submitting a voucher that has already been settled |
| Replay window | The last 128 sequence numbers a vault remembers |
Sequence number (seq) | Unique, increasing number on every voucher from a vault |
| Settlement | Submitting a voucher to the settlement program so funds move |
| Store and forward | A relay holding a message until the next phone comes into range |
| Tip | Optional payment to the relayer, in basis points of the amount, at most 5% |
| Voucher | A 227-byte signed payment instruction |
| Voucher signer | The key, usually on the payer's phone, that signs a vault's vouchers |