One market, any leverage
Each index and expiry gets one shared order book.
You pick your direction, size and leverage, up to 50x, and everyone trades against the same bids and asks. A 2x trader and a 50x trader can trade with each other.
In design and prototyping · not live yet
Each index and expiry gets one shared order book.
You pick your direction, size and leverage, up to 50x, and everyone trades against the same bids and asks. A 2x trader and a 50x trader can trade with each other.
You choose leverage when you enter. Your maximum gain and maximum loss are both the entry price divided by your leverage.
At 5x, your payoff moves while the index is between 80 and 120. The most you can gain or lose is 20 per unit.
Inside that range, your profit or loss moves one-for-one with the index. Outside it, it stops changing.
Leverage goes up to 50x; the exact menu at launch depends on the finished risk model. The cap applies at expiry: touching the edge of your range before then does not close your position.
The trade-off: your upside is capped too, and a shared book can't guarantee you a good price if you exit early.
Your position keeps its original entry price and range. Closing it early at a new price needs clear, fair valuation rules that can't be gamed by repeated trading or cooperating accounts.
We will publish our solution with the market spec.
Committed · the second stage
Every capped future settles against the oracle, and market makers need fresh data to keep their quotes accurate. The rebuild focuses on trust and speed.
The oracle should be useful even to people who never trade. Our goal is for anyone to run an agent that finds missing price data, collects evidence and submits it under public rules.
Our plan for the first months
A new market is only useful if there are real bids and asks in it.
Two concrete roles, both tied to how the protocol works
Anyone can post orders on the book. Makers who want official market maker status post an AMBA bond. In return they get fee rebates, and they commit to clear rules on spread, size and uptime.
Browsing hardware prices on the website stays free for everyone. Agents and developers who want machine-readable oracle data stake or pay AMBA for access, with faster and deeper data at higher tiers.
This ties AMBA directly to the oracle's main goal: becoming the reference price for hardware that both people and agents rely on.
Directions, not dates · each depends on the layers before it
Start with DRAM and NAND, then expand. The goal is to be the first place people and agents check to see what hardware actually costs.
Product histories, specs, sources and availability, readable by both people and machines.
The bigger goal is to connect markets to real production. An agent should eventually be able to spot demand, price the inputs, raise capital, contract for output and have the result verified.
One idea we're researching is longer-dated contracts backed by delivery promises. Before that can work, we need clear answers: who owes delivery, what backs the promise, how completion is verified, and what happens if delivery fails.
The order book gives agents a place to trade. The oracle gives those trades a trusted reference. Production is where both become useful in the real world.