RISEx

Mainnet RISEx session authorization, native signed orders and account recovery.

RISEx execution is introduced in MarketLab 0.1.145 under risexf. This integration is mainnet-only. Testnet requests are rejected and never fall through to mainnet.

Join and connect

New users can join through Furge's RISEx invite. Complete the exchange's own onboarding and fund the account there, then choose Accounts → RISEx in Furge. Existing users can connect directly.

Furge creates a separate session signer in memory. The connected owner wallet signs RISEx's RegisterSigner typed data; the session key signs VerifySigner. The API domain, authorization contract and nonce are fetched at setup, and the chain is checked against RISEx mainnet. The owner private key is never imported.

The session lasts 30 days. The connection flow verifies activation and saves the session key through the existing encrypted runtime credential store. Session permissions are defined by RISEx; the adapter does not claim that native registration is a withdrawal-disabled key. Furge's exposed transport is restricted to trading and account reads.

For a pre-authorized standalone session key:

mlab auth set risex --agent --account 0xYOUR_ACCOUNT

Enter the session key at the hidden prompt. --agent-stdin is available for secret input without command-line arguments. Never import the owner wallet key.

Trading

The adapter supports market and limit orders, GTC, IOC, post-only limits, reduce-only orders, cancellations and integer leverage. Native market IDs, tick/lot sizes and minimum base quantity are checked before submission. Market orders include a worst accepted price.

Every action has an EIP-712 permit. Nonces use RISEx's anchor/bitmap scheme with a durable, owner-checked local cursor. The router is discovered from system configuration; it is distinct from the authorization contract used in the signing domain. Packed order, cancellation and leverage hashes follow the current mainnet integration guide.

Native attached TP/SL and OCO submission are not enabled by this adapter. Unsupported requests fail explicitly.

Fees, account events and recovery

The invite slug is not a builder ID. RISEx builder attribution uses a registered numeric ID, configured independently in the node's fee policy. Fee units are hundredths of a basis point: 100 native units is 1 bps. The deployed mainnet contract currently caps builder fees at 3 bps (300 native units). Furge defaults to 3 bps manual / 1 bp automation. The connection flow completes native builder approval and verifies it against the exchange before order fees are enabled, without a separate Furge fee checkbox. An unconfigured policy does not become zero-fee trading.

Authenticated WebSocket orders, positions and fills use the session key. Streaming consumers share account events within their runtime. Live fills and account history normalize to the same fill identity, price, size, fee and execution time. Position events trigger a portfolio refresh for venue-reported values.

Delta Neutral and liquidity-hedge runs use authenticated HTTP snapshots and order reconciliation. The run page can show RISEx’s public funding rate. Confirmed RISEx settlement history is currently unavailable through this integration.

RISEx meters order placement with a per-account TX quota. The provider reads it using a short-lived JWT held only in memory, authenticated by the registered session signer. That token is used only for quota reads; trading continues to use native permits. When quota cannot be verified or is exhausted, submission falls back to the documented one-order-per-second path. Requests that exceed admission limits fail before sending instead of waiting with a stale quote. Cancellations have reserved gateway capacity. Public indexing and private accounts share the physical node’s configurable budgets.

A submission's stable client order ID is persisted before sending. If the connection fails after sending, recovery searches bounded account history for that same identity. It does not replay an uncertain signed request. Batches keep input ordering and expose individual failures.

Books, trades, candles and volume-based strategies reuse the Furge RISEx index. No complete native CLI ticker stream is advertised.

Current RISEx integration guide.

Native rejections include a sanitized RISEx reason and request ID in CLI errors. An approval error such as BuilderFeeBpsExceedsCap => (500, 300) means the configured 5 bps ceiling exceeds the exchange’s 3 bps cap. Update that node’s fee policy, refresh the connection setup and retry. A runtime upgrade does not change the server-owned fee policy.

On this page