Zero-trust infrastructure for trading venues
Trading software that cannot touch your money.
Garos Labs builds smart-contract infrastructure where custody is impossible by construction. Operators launch their own venue on it. Traders keep the keys. We run the service, and the code keeps us honest.
Zero trust, defined
Trust is what you need when the code is not enough.
Most venues ask you to trust the house: its honesty, its keys, its word. Ours are built so none of that is required. Three properties, each enforced on-chain, each checkable by anyone.
Only your signature can take funds out.
Deposits sit in contracts that answer to one key: the trader's. No admin key, no operator key, no Garos Labs key can initiate a withdrawal. If every one of our keys leaked tonight, not one withdrawal could be made from a trader's account.
Every parameter we control has a bound we cannot move against you.
Fees, leverage, margin, oracles: a venue has settings and someone holds the keys to them. Ours are bounded in the contract at deployment, and a bound moves only in the trader's favour. Unbounded control over settings is custody by another name.
The rules are published, and the code is the proof.
What a contract does is public. What an operator must do is public. What we say about the software is true, or we do not say it. You do not have to believe any of it: you can read it.
Architecture
Three layers. Three owners. One place where money lives.
An operator owns the venue. Garos Labs runs the engine. The contracts own nothing and release funds only to the trader. Hover a layer to see who controls it.
Venue
owned by the operatorThe brand, the interface, the client terms and the admission policy. The operator decides who it serves, where, and on what commercial terms. It never touches a client's key.
Engine
run by Garos LabsOrders, risk, pricing and operations, run as a managed service. It can instruct the contracts within their bounds. It cannot move a deposit, and it cannot widen a bound.
Contracts
owned by no oneWhere the money lives. Deposits, settlement and every bound, on-chain and immutable. One function releases funds, and nothing releases them without the trader's signature.
Security model
What we cannot do, by design.
A security model that depends on our good behaviour is not a security model. Ours depends on what the contracts refuse to execute, whoever is asking.
- 01We cannot withdraw a trader's funds.
There is no function that lets us. Not with one key, not with all of them.
- 02We cannot change a deployed contract.
No proxy, no upgrade path. A new version is a new contract that traders choose to move to, or not.
- 03We cannot raise a parameter past its bound.
Fees, leverage, margin: each has a frozen limit on the trader's side. The limit moves only toward the trader.
- 04We cannot stop a trader from leaving.
Withdrawal of free balance is a right written in the contract, not a service we provide. It survives the engine, the operator and us.
- 05We cannot say what the code does not support.
Rule 2 binds every operator to this. We hold ourselves to it first.
For operators
Launch a venue your clients never have to trust.
You bring the brand, the market and the clients. We bring the software that has already answered the hardest question a client asks: where is my money, and who can move it.
You get
- A live trading venue under your brand
- Contracts that make custody impossible
- A managed engine, run and watched by us
- Model client terms and policies that meet the Rules
- Your own commercial terms, fees and markets
You run
- Your brand, interface and support
- Admission: who you serve and where
- Client terms, in every language you sell in
- Marketing, bound by Rule 2: nothing false
- Your relationship with your clients, never ours
We run
- The contracts: deployment and verification
- The engine: orders, risk, pricing, uptime
- Bounds set on the client's side at deployment
- Interpretive Notices as the Rules evolve
- No key that can take a client's money out
Proof
Do not take our word for it.
What you need to check is in the open. The contracts go on-chain with their source verified, and the addresses are published at launch. The operator duties are published here. The claims on this page are claims about code, and code can be read.
Questions
The ones we get first.
The trader, through a contract that answers only to their key. Not the operator, not Garos Labs, not the engine. A venue built on our software cannot be a custodian even if it wanted to be.
Withdrawal of free balance is a function of the contract, not a service we run. It keeps working without our engine, our servers or our keys.
Everything commercial: brand, markets, fees within their bound, who it admits. Nothing about custody, settlement or the bounds themselves.
No. A deployed contract is final. A new version is a new contract, and moving to it is the trader's decision.
A normal exchange asks you to trust its balance sheet and its keys. Ours removes the question: there is no balance sheet holding your funds and no key but yours that can take them out.
No. Garos Labs is a software company. It builds and runs the software; operators run venues on it under their own brand and terms.
Build on contracts that cannot betray your clients.
We are taking a small number of operators for the first venues. Write to us with the market you want to serve and where your clients are.