Most of our security writing tells you what to watch out for. This page is the other half: what is built into Loop itself, so you know what you are relying on.
The key is yours, and only yours
Loop is non-custodial. Your private key is generated for you and stays with you. We do not hold it, store it, or keep a copy anywhere.
This is the foundation everything else sits on. Nobody at Loop can move your assets, sign on your behalf, or open your wallet, because there is nothing on our side to open it with.
The same fact has a cost, and we would rather you know it now than learn it later: if you lose your key, nobody can restore it. Not us, not anyone claiming they can.
Your wallet does not depend on Loop being online
On Canton, your identity is hosted on a validator node. If a wallet hosts you on its own node alone, then that company going down, or away, takes your access with it.
Loop is multi-party hosted. Every participant is onboarded not only to Five North, but at the same time to independent co-validator nodes run by other organisations. There is no single point of failure and no single point of trust.
In plain terms: if Loop were unavailable, your wallet would still exist on the network and you would still control it. This was built with MPCH and Digital Asset, and it was announced publicly on the Canton Network forum rather than being something you have to take our word for.
Independently audited, and the report is public
Loop Wallet has been independently audited and penetration tested by an outside firm, Verified by Humans. The review covered the wallet, the SDK and the APIs, along with penetration testing across our systems.
You do not have to take that on trust either. The audit is published:
Findings were worked through rather than filed away. We would rather be audited and fix things than claim to be perfect.
Reporting a security problem
If you believe you have found a vulnerability, please tell us privately first, so it can be fixed before anyone can use it.
Email security@fivenorth.io, or use the Report a vulnerability button on the Security tab of the affected repository on GitHub.
Please do not open a public issue, pull request or discussion describing it.
Useful to include: what the issue is and what you think it allows, the steps to reproduce it or a proof of concept, the affected component and environment, and any fix you would suggest. The team aims to acknowledge reports within a few business days, confirm whether it can be reproduced, and keep you posted until a fix ships. If you would like to be named, we are glad to credit you once it is resolved.
There is no paid bounty programme at the moment. Credit is what we can offer.
What is in scope
Loop Wallet, including the web application and its backend services. The Loop SDK. The USDC Bridge interface. Public repositories under the fivenorth-io organisation.
Out of scope: automated scanner output with no demonstrated exploitable impact, volumetric denial of service, social engineering of staff or users, physical attacks, third-party services we do not operate, and missing best-practice headers with no demonstrated impact.
Good-faith research is welcome. Work only with accounts you own, do not touch other people's data, and give us reasonable time to fix something before disclosing it. If you are unsure whether something is in bounds, ask at the address above before you try it.
The part that is yours
Architecture protects the wallet. It cannot protect a key you hand to somebody, or a signature you approve without reading.
Reach Loop by typing the address yourself rather than through a link. Never share your private key, password, passkey or verification codes with anyone, including anyone claiming to be us. Read every signing request before approving it, and refuse anything you cannot explain.
Loop does not use a seed phrase, so there is no set of recovery words to give away either. If somebody asks you for your Loop seed phrase, that alone tells you they are not from Loop.