Concepts
Non-custodial model
LayerHop never holds user funds or keys — transactions go from the user's wallet straight to audited provider contracts.
What LayerHop touches, and what it does not#
| LayerHop | |
|---|---|
| User funds | Never. Funds move from the user's wallet directly into the provider's contracts. |
| Private keys | Never. The user's wallet signs. The API, SDK and widget never ask for a key or seed phrase. |
| Smart contracts | None of its own (yet). Transactions target the providers' audited contracts. |
| Transaction data | Built by the provider. LayerHop returns it as-is so your user's wallet can show and sign it. |
| Signed bytes | Only for submitViaApi transactions, which LayerHop forwards unchanged. |
Why it matters#
- No honeypot. There is no LayerHop pool or vault to drain.
- No custody risk. If LayerHop goes offline, nothing is stuck with LayerHop. In-flight cross-chain orders are settled or refunded by the provider's protocol.
- The wallet is the last line of defence. Users see the real destination contract and calldata in their wallet before signing.
Your responsibilities as an integrator#
- Show the user the route (
provider), the expected and minimum output, and the fees before they sign. - Check that
recipientis what the user intended — especially when it is not the connected wallet, and when it is on another chain family (an EVM address cannot receive on Solana and vice versa). - Never collect private keys to "sign on the user's behalf". That would make you custodial.
Coming soon
LayerHop's own intent protocol (escrow per order, 0-TVL), audited before it handles funds. Partner routes stay available as fallbacks.