Developers
How it’s built.
SafeSend is a Manifest V3 browser extension. Everything runs on your device; there is no backend. Here is how the pieces fit together, and what is still a prototype.
One phrase, seven chains
A single BIP39 recovery phrase derives an address on every supported network, each on its standard path:
| Network | Curve | Derivation |
|---|---|---|
| Solana | ed25519 (SLIP-0010) | m/44'/501'/0'/0' |
| Ethereum · Base · Polygon · Monad | secp256k1 | m/44'/60'/0'/0/0 |
| Bitcoin (native segwit) | secp256k1 | m/84'/0'/0'/0/0 |
| Sui | ed25519 | m/44'/784'/0'/0'/0' |
Transactions are built in the client
EVM transfers are EIP-1559, RLP-encoded and signed with secp256k1 in the extension — no wallet library in the signing path. Bitcoin uses native segwit (P2WPKH). Solana uses web3.js. Swaps route through the Jupiter aggregator.
The reversible mechanism
A protected transfer funds a fresh escrow account and keeps its key. Cancelling sweeps the escrow back to the sender; claiming sweeps it to the recipient.
Current status: the escrow is a one-time keypair the wallet holds. That makes the claim link bearer money — whoever has it can claim. A PDA-based on-chain program that binds the transfer to a named recipient is written and proven on a local validator, but is not yet wired into the extension. Until it is, treat claim links as cash.
What is real, and what isn’t
- Real funds on mainnet across all seven networks. No devnet, no test mode.
- Reversible transfers are proven end-to-end with real funds on Solana. On Ethereum and Bitcoin the transaction math is verified but has not yet moved real coins.
- The code is not independently audited.