Skip to content
Docs

System overview

The parts of UNRLZD and what each one may do: the code in your browser, your trading account on NEAR, and the services we run.

UNRLZD has three kinds of parts: code in your browser, contracts on NEAR, and services we run. Your funds sit in a contract on NEAR that your wallet owns, and that contract checks every call made on it. The services hold no key that can move funds out of it.

Who can do what with your trading account

Your wallet owns the trading account and can withdraw, add a device and approve updates. The trading key in your browser trades within the account's rules while unlocked. The 24/7 key sends only orders you placed, within the terms you stored. Swaps go to venues and the output comes back to the account. Deposits and withdrawals on other networks go through NEAR Intents. Other networks NEAR Intents Deposits and withdrawals Owner Your wallet Withdraws, adds devices, approves updates On NEAR Trading account Holds your NEAR and tokens. Checks every call it gets. {16 hex}.trade.unrlzd.near In this browser Trading key Trades within the account's rules Our order service 24/7 key Sends only your orders, on the terms you stored Venues Rhea, Rhea DCL, Plach and supported launchpads owns in · out swaps

Who can do what with your trading account

Your wallet owns the trading account and can withdraw, add a device and approve updates. The trading key in your browser trades within the account's rules while unlocked. The 24/7 key sends only orders you placed, within the terms you stored. Swaps go to venues and the output comes back to the account. Deposits and withdrawals on other networks go through NEAR Intents. Owner Your wallet Owns the account Other networks NEAR Intents In and out On NEAR Trading account Holds your NEAR and tokens. Checks every call. {16 hex}.trade.unrlzd.near In this browser Trading key Trades within rules Order service 24/7 key Sends your orders Venues Rhea, Rhea DCL, Plach, launchpads
Figure 1.Your wallet owns the account. Two keys can call it, each for a narrow job. Swaps go out to venues and the tokens come back to the account.

The parts

Section titled “The parts”
Part Runs Holds, or may do
Terminal your browser No key. Builds every trade and reads the chain
Signer frame your browser, its own origin The trading key on this device, which can’t be exported
Wallet bridge your browser, its own origin Your wallet session, for owner calls
Trading account NEAR Your funds, and the rules every call must pass
Factory NEAR Creates trading accounts
Engine our servers Market data and the order list
24/7 executor our servers A 24/7 key that may call execute_order only
Watcher our servers A key that can only sign a pause

The signer frame and the wallet bridge each run on their own origin, so a script on the terminal page can’t read the trading key or your wallet session.

Your account and its keys

Section titled “Your account and its keys”

Each trading account is its own contract on NEAR, with no full-access key, created for your wallet by the factory from one shared contract. Your wallet keeps recovery. Verify the contracts shows how to check the account’s code against the published source.

Three kinds of key act on the account:

  • Your wallet is the owner. It calls the owner_* methods: withdrawals, keys, caps, recovery.
  • The trading key sits in the signer frame on each device you set up. It may call only a fixed list of methods on the account itself.
  • The 24/7 key may call only execute_order, which runs an order you stored, exactly as you stored it.

We can’t move or freeze your money.

A trade end to end

Section titled “A trade end to end”

The terminal builds the trade from its own reads of the chain, and checks the minimum it will sign against a price it read there. The signer frame checks the call again before it signs. The trading account checks it once more on chain before anything moves. The terminal reads the result from the chain itself.

Where each read comes from

Section titled “Where each read comes from”

The rule from our external review: nothing the engine sends is trusted for anything that gets signed or that guards your funds. Every read that a signed value rests on comes from public RPC providers we don’t run, and prices are cross-checked against on-chain pools. 24/7 orders are kept in the engine’s list, but each reply is compared with the order you asked for before the terminal arms it, and the orders on your account are read from the chain.

Market data

Section titled “Market data”

Our engine follows every block on NEAR, decodes swaps and launches, and builds candles, stats, holders and top traders. It streams them to the terminal over a WebSocket.

24/7 orders and the watcher

Section titled “24/7 orders and the watcher”

A 24/7 order is stored on your trading account with its terms. When its trigger is reached, the executor sends it with the 24/7 key, and the account checks the call against the stored order. An independent watcher checks every send the 24/7 key makes against the chain, and can stop the executor. A pause can only stop sends; it can’t move funds or change an order.

Other networks

Section titled “Other networks”

Deposits and withdrawals to other networks go through NEAR Intents, with quotes from the 1Click API. The terminal checks the quote’s signature before it signs, and the trading account checks that signature again on chain.

Last verified 15 October 2026 against R4.