Sui Basecamp · Presentation ↗

Deploy the Sui Rebalancer.

A standalone process that reads a real Sui wallet and market, evaluates price limits, and prepares a swap for simulation. No AEX account is required.

1. Prepare Node 24

Install Node.js 24 if it is not already available. The console checks the version before deployment.

Get Node 24 ↗

2. Download and open the kit

Download Rebalancer kit

Unzip the download first. The extracted folder is named sui-rebalancer.

Console: http://127.0.0.1:8788. This selection updates launch commands and console links in this guide, the companion and the deck in this browser. It does not start or move a server.

Mac

  1. Open Terminal.
  2. If you extracted the kit in Downloads, copy and paste the command below, then press Return. Otherwise type cd , drag the extracted folder into Terminal, press Return, then run the selected-port command below from that folder.
  3. The console opens in your browser. Keep Terminal open while building.
cd ~/Downloads/sui-rebalancer && PORT=8788 node server.mjs --open

Start.command is an optional double-click launcher. If macOS says it cannot verify the file, dismiss the dialog and use the Terminal command above to run the kit’s source directly. Typing start.command alone does not launch a file from the current folder.

Windows (PowerShell)

Open PowerShell in the extracted folder and run the selected-port command:

$env:PORT="8788"; node server.mjs --open
Node version or console already running?

Run node --version. This kit requires v24.x; v26 is not the tested runtime. After installing Node 24, open a new Terminal and check again.

If a Rebalancer console already uses the selected port, the updated launcher opens that console without starting another. It may be running locally or connected to Studio. With an older kit, EADDRINUSE means that port is occupied: open the local console link below. For a separate local instance, select 8789 above and run its command. For clean configuration, extract a new kit into a different folder first; ports do not isolate saved files. Leave the existing console running.

If your default Node is v26, from the extracted kit folder use this command to launch with Node 24:

PORT=8788 npx --yes --package=node@24 -- node server.mjs --open
Open local console ↗

3. Deploy, run and inspect

  1. Check runtime: verify Node 24 and the recipe files. Opening the console has not yet installed the agent.
  2. Wallet + configure: open Wallet in step 02. Copy node wallet-setup.mjs into a second terminal in the kit folder. Choose Create account or Sign in, enter your own email and hidden password, then approve the email if prompted. Copy the returned Sui address into Strategy and save. Already have a web wallet with email-link or social login? Copy its Sui mainnet receive address directly and skip the CLI helper; CLI Sign in needs a password.
  3. Funding: enter your email in the console’s Funding screen. The saved Sui address is included automatically. Or scan the Funding QR and enter your email and address there. No workshop code is needed. The first 30 unique registrations get funded places; later submissions join the waitlist. The host reviews the export and distributes funds separately. The 15-minute reminder is not a submission cutoff.
  4. Install agent: click Install dependencies. This runs npm ci --ignore-scripts --no-audit --no-fund and shows its output. Wait for installation to complete; the agent has not started yet.
  5. Run once: read actual balances and the live market. Inspect the strategy outcome.
  6. Inspect: distinguish an observation, quote, unsigned build and transaction simulation.
  7. Modify: stop scheduled runs, change one rule, then run again.
  8. Stop: stop the process and schedule, then save the output.

The wallet field starts empty. Enter a verified wallet you control. Older installations may show a historical example address; do not fund that address. An empty wallet returns a funding error; it never becomes sample holdings.

Current execution mode

Live mainnet reads and unsigned transaction simulation. The kit contains no signer and cannot submit a swap. A successful simulation is separate from a confirmed transaction. No AEX, WaaP or transaction fee is charged by this unsigned path; normal internet and local compute costs apply.

Workshop funding registration ↗ · Canonical recipe ↗ · More starter sources ↗

Guardian and the earlier browser decision exercises remain secondary until this full recipe has passed a funded rehearsal.