Reckonzthesis → basket

Non-custodial execution and risk tooling for tokenised equities on X Layer. You write the thesis; Reckonz maps it, sizes it against real depth, and enforces the exits on chain.

X Layer testnet 1952 · 7 contracts liveX Layer mainnet 196 · 8 contracts liveguard: gap ≤ 60 · ≤ 100bp off fair value · ≤ 50bp impactgemini-3.6-flash (live)
  1. compile
  2. universe
  3. allocate
  4. triggers
  5. capacity
  6. guard

7 · Create a mandate

The mandate is yours: you are owner because you send this transaction, your funds never leave your wallet, and the policy below is what PolicyGuard enforces on every future fill — reverting in the trade's own transaction if one breaches it. You are also the agent, so no key of ours can propose anything against it.

Connect a wallet to create one.

9 · Published theses

A thesis is published on chain before it is executed, and every fill carries its hash. What follows is the join: the claim, then what the chain recorded against it. The basket is derived from settled fills rather than from the thesis text — the text is a claim, the fills are the half that cannot be rewritten.

Reading both registries from the chain…

10 · Execute a fill

The quote, the oracle read and the guard's verdict come from the server; the approval, the signature and the transaction happen in your wallet. Nothing is signed on your behalf, and the permit below authorises one token, one amount, one contract, for twenty minutes.

Connect a wallet to place one.

11 · Exit a position

The reverse trade, and the same division of labour: the server simulates every fee tier and asks the guard, your wallet does the approving, the signing and the sending. The permit here names the asset rather than USDG, so each xStock needs its own one-off Permit2 approval.

Connect a wallet to sell one.

Deployed on X Layer