Security model

Reroute never holds your money. The rest of this page covers what makes that true and what it protects you from.

No custody

Your creator fees land in a vault that is controlled by an on-chain program, not by a person or a company. There is no admin backdoor, no support-team override, no way for the Reroute team to redirect your fees. The program is the only signer on your vault, and it can only do what it was programmed to do: split fees according to your route.

You own your route

Your route configuration is signed by your wallet and stored on-chain. Only that wallet can change it. If someone else tries to modify your split, the transaction fails on-chain before it does any damage.

Every distribution is checked

On every distribution, the program verifies that the amount sent out equals the amount coming in. No fee gets lost, no fee gets duplicated. If the math does not add up, the whole transaction reverts and your fees stay in your vault.

All-or-nothing splits

A distribution either lands to every destination in your split, or nothing lands at all. There is no state where one destination got paid and another got skipped. This is enforced on-chain, not by our infrastructure.

Public and auditable

Everything happens on-chain: your route, your vault balance, every distribution. You can watch all of it live on any Solana explorer without trusting Reroute for the numbers. The dashboard on this site is a convenience view, not the source of truth. The chain is.

Reroute has been reviewed

Before mainnet launch the router went through:

Automated fuzz testing that ran billions of random scenarios against the program looking for exploitable behavior.
A defense-in-depth review against known Solana attack patterns. No exploitable findings.
An independent monitor that watches the router in production and alerts if anything looks off.

This is not a substitute for a formal third-party audit. Treat reroute the way you treat any early on-chain program: with caution, and only with funds you are comfortable being on-chain.

Reroute is source-available

The program, SDK, and frontend are all in one repository. Read the code, or have someone you trust read it.

What could still go wrong?

The honest list:

Bugs. All on-chain programs can have bugs. Ours has been fuzzed and reviewed, but there is no such thing as bug-free code. Do not route fees you cannot afford to have delayed or stuck.
Solana network issues. If the Solana network stalls, distributions stall until it recovers. Your fees are safe in your vault the whole time, but they are not moving until the network moves.
Wrong destination. If you paste a wrong destination address into your route, we cannot recover the fees sent there. Double check your addresses.
You lose your wallet. If you lose access to the wallet that created your route, you lose the ability to change the split. The fees still route to the destinations you set, but you cannot rebalance without that wallet.

Support

Reroute is a small project. Support runs through GitHub issues and the community. Because reroute is non-custodial, no one has access to your fees, so there is nothing to "refund." What we can do is help you diagnose an issue, walk you through closing a route, and improve the code.