Backpack security: daily proof of reserves, verified by OtterSec

Risk warning. Not financial advice. Crypto is highly volatile and may drop in value significantly. You may lose the amounts you invest and your investments do not benefit from any form of financial protection.

Backpack Exchange publishes a proof of reserves every day that is independently verified by OtterSec and reconciled internally every 10 minutes, covering spot balances, margin positions and unrealised PnL. This page lists what that proves, what it does not, and which security facts Backpack has not yet published.

Is Backpack Exchange safe? What can be verified

registers read 11 Oct 2026

No page can settle that question for you, and this one does not try. It lists the claims about Backpack that have a source, who issued each one and when it was read. Two labels show how far each claim goes. "Published on a register" means the regulator's own record was opened. "Stated by Backpack" means the only source is a Backpack page.

Security and oversight claims, with evidence, issuer, date and status
ClaimEvidenceIssuerDateStatus
A proof of reserves is published every dayBackpack's Learn article says the proof is published daily and independently verified by OtterSec. The home page carries the same verifier label.Backpack; verifier named: OtterSecRead Stated by Backpack
Balances are reconciled every 10 minutesThe same article describes an internal reconciliation that runs every 10 minutes.BackpackRead Stated by Backpack
Client assets are segregatedThe same article says user assets are kept apart from platform assets under more than one regulatory framework.BackpackRead Stated by Backpack
EU investment firm licenceTrek Labs Europe Ltd, CySEC licence no. 273/15, in the CySEC register entry.CySECLicence dated ; read Published on a register
EU crypto-asset service provider authorisation"Trek Technologies" SIA, LEI 6488C2PNI17093U2YA18, in the ESMA interim MiCA register. No licence number is published.Latvijas Banka, through the ESMA registerAuthorisation dated ; read Published on a register
Dubai spot exchange licenceTrek Labs Ltd FZE, VASP Licence VL/23/07/001 for Exchange Services, status active, in the VARA public register (search "Trek Labs").VARAIssued ; read Published on a register
US money services business registrationTrek Labs, Inc., FinCEN registration no. 31000339714338, as listed on Backpack's US licences page. Not checked in the FinCEN registrant search.Backpack, naming FinCENRead Stated by Backpack
A security.txt file is publishedA 216-byte file at backpack.exchange/.well-known/security.txt.BackpackRead Stated by Backpack

Insurance cover, security certifications, the cold-storage share, penetration-test results, a bug bounty programme and an incident log were not found on the Backpack pages read on 6 October 2026, so this page says nothing about them.

Daily proof of reserves

source: Backpack Learn article and home page

A proof of reserves sets what an exchange holds against what it owes its clients on a given day. The steps below are Backpack's own description of its process. The general method and its limits are explained in the guide on what a proof of reserves does and does not prove.

How Backpack's daily proof of reserves is put together What Backpack owes clients (spot balances, margin positions and unrealised PnL) and what Backpack holds are set against each other in a daily proof built with zero-knowledge proofs and reconciled internally every 10 minutes. Backpack says OtterSec verifies the proof, which is published every day. The reserve figure is not quoted on this page. Owed to clients spot, margin, unrealised PnL liabilities Held by Backpack set against client balances assets Daily proof of reserves zero-knowledge proofs reconciled every 10 minutes method stated by Backpack Verified by OtterSec as stated by Backpack no report link in the sources Published every day reserve figure not quoted on the live reserves page
Figure 1. What Backpack owes clients and what it holds meet in a daily proof, which Backpack says OtterSec verifies. Drawn from Backpack's statements, read 6 October 2026.

What is published each day

Backpack says it publishes a proof of reserves every day and, between publications, reconciles balances internally every 10 minutes. Its home page describes the result as a way to track assets and liabilities in real time. The proof is shown on the reserves page of the main site, backpack.exchange/reserves.

Who verifies it

Backpack names OtterSec as the independent verifier. OtterSec describes itself as a provider of security audits for blockchain projects. The sources read for this page contain no OtterSec report, link or date for a specific day's proof, so the verification is recorded here as Backpack's statement.

What the proof covers

According to Backpack, the proof covers spot balances, margin positions and unrealised PnL, and it is built with zero-knowledge proofs. A zero-knowledge proof lets one party show that a statement is true without revealing the data behind it. Both terms are in the glossary: Merkle tree and zero-knowledge proof definitions.

What the proof does not show

No reserve ratio and no report link can be quoted on this page. When the live reserves page was read on 6 October 2026, its server HTML held no figures; the numbers appear only after scripts run. The sources read do not document how a client can check that their own balance is included. A proof of reserves describes one day. It does not remove market risk, and it says nothing about lending and borrowing risks.

More background on how a proof of reserves works is in the security guides on Backpack Learn.

Segregation of client assets

Backpack's Learn article on the exchange, read on 6 October 2026, says: "User assets are segregated from platform assets, subject to requirements across multiple regulatory frameworks."

Segregation means client assets are held apart from the company's own. It is not insurance, and it does not protect against a fall in prices. Backpack's footer adds that it is a financial services platform and not a bank, and that banking services come from its bank partners.

Custody architecture, key management and the split between cold and hot wallets are not described in the sources read, so nothing is written about them here.

Check that you are on an official Backpack site

Fake sites and accounts copy an exchange's name and design to collect sign-in details. Check the address in your browser before you sign in. Backpack uses these domains:

  • backpack.exchange
  • eu.backpack.exchange
  • support.backpack.exchange
  • learn.backpack.exchange
  • docs.backpack.exchange
  • backpack.app

Apps and social accounts are on the contact page, with the official domains and how to report a problem.

For vulnerability reports, Backpack publishes a security.txt file, the standard place for a site to say how researchers should reach it: backpack.exchange/.well-known/security.txt.

Account security settings are not described in the sources read, so none is listed here.

November 2022: the FTX treasury loss

In November 2022 Backpack lost 88% of its corporate treasury on FTX, according to the timeline on its own About page (read 6 October 2026). That was before the exchange existed: Backpack Exchange was incorporated in March 2023 and opened in beta in November 2023.

The entry describes company funds held at another exchange. It is listed here because a reader weighing counterparty risk should know it.

Backpack has published no incident log in the sources read, and this page makes no statement about whether a security incident has occurred.

Regulatory oversight

one line per company

Oversight differs by company and by product. No single licence covers every product in every country.

Trek Labs Europe Ltd EU
Licensed by CySEC as a Cyprus Investment Firm, licence no. 273/15. Perpetual futures in the EU.
"Trek Technologies" SIA EU
Authorised as a crypto-asset service provider by Latvijas Banka on 27 May 2026, LEI 6488C2PNI17093U2YA18. Crypto services in the EU.
Trek Labs Ltd FZE UAE
Licensed by VARA for Exchange Services, licence no. VL/23/07/001. Spot trading only: no futures or margin trading in the UAE.
Trek Labs, Inc. US
Registered with FinCEN as a Money Services Business, registration no. 31000339714338, by Backpack's own statement. A registration, not a licence.
Trek Brokerage Services Limited Stocks
Described on the live stock pages as licensed by the Anjouan Offshore Finance Authority. No licence number is shown.

Security FAQ

Is Backpack Exchange legit?

Backpack is provided by named companies whose licences and registrations can be checked. Trek Labs Europe Ltd holds CySEC licence no. 273/15. "Trek Technologies" SIA is in the ESMA interim MiCA register with an authorisation date of 27 May 2026. Trek Labs Ltd FZE holds VARA licence no. VL/23/07/001 for spot trading, and Trek Labs, Inc. states FinCEN registration no. 31000339714338. Each covers certain products and regions only.

Who verifies the proof of reserves?

OtterSec, according to Backpack. Backpack's Learn article says the daily proof of reserves is independently verified by OtterSec, a firm that describes itself as a provider of security audits for blockchain projects. The sources read for this page include no OtterSec report or link for a specific day, so the claim is recorded as Backpack's statement.

How often is the proof of reserves published?

Every day, according to Backpack. Its Learn article says a proof of reserves is published daily and that balances are reconciled internally every 10 minutes between publications. This page gives no date for the latest proof, because the live reserves page shows its figures only after scripts run.

What does the proof of reserves cover?

Spot balances, margin positions and unrealised PnL, according to Backpack, which says the proof is built with zero-knowledge proofs. A proof of reserves describes one day. It is not a forecast, no reserve ratio is quoted on this page, and it does not remove the risk that prices fall.

How do I report a vulnerability?

Start with Backpack's security.txt file at backpack.exchange/.well-known/security.txt. A security.txt file is the standard place where a site says how security researchers should report a vulnerability. For an account problem that is not a vulnerability, use the support routes on the contact page instead.

Other topics are in the account, deposit and support questions. If a problem is not resolved, see what to do if something goes wrong. For information only. Not investment advice.

Understand the method before you rely on it

The guide explains how a proof of reserves is built, what a reader can check and where the method stops.