Documentation
How to install and operate the Remiora runtime on macOS, Windows, and Linux. It grows alongside the build, so expect it to change between releases.
Install and first run
Take the .dmg on macOS, the .exe installer on Windows, or the AppImage / .deb on Linux (macOS 12+ (Apple Silicon & Intel) · Windows 10/11 x64 · Linux x86_64 (glibc 2.31+)), verify the checksum, and launch. On first run Remiora generates or imports a wallet and encrypts the key at rest on your own disk. Nothing is uploaded, and there is no account to create.
Agents and missions
An agent handles one task and stops. A mission runs unattended toward a goal you define: a deadline, a capital cap, and a maximum loss. Each session locks its mode and its permission level at the start, and neither can widen while it runs.
Approvals and limits
In restricted mode every signing action pauses for a one-tap approval. Requests expire after an hour so a mission is never stuck waiting on you. In full mode there is no pause, but the swap and bridge safety gate still runs before every execution.
Failure and risk
The gate fails closed: when a check cannot be completed, the trade does not happen. Missions end with a stated reason and blocked attempts are logged next to the wins. Trading is risky, this software is early, and you should only run it with capital you can afford to lose.
Install by platform
Release 0.1.0 ships for all three desktop platforms. Every artifact is signed and listed with a checksum.
macOS
macOS 12 Monterey or newer · Apple Silicon and Intel
- Download the .dmg build and open it.
- Drag Remiora into Applications, then launch it once from Finder.
- Compare the published SHA-256 against `shasum -a 256 Remiora.dmg` before you open it.
Windows
Windows 10 or 11 · x64
- Download the signed .exe installer and run it.
- Allow the installer through SmartScreen if the signature matches the published certificate.
- Verify with `Get-FileHash Remiora-Setup.exe` in PowerShell.
Linux
x86_64 · glibc 2.31 or newer
- Download the .AppImage, `chmod +x` it, and run it — or install the .deb with `sudo apt install ./remiora.deb`.
- Verify with `sha256sum` against the checksums file.
- AppImage needs FUSE; on minimal distros install `libfuse2` first.
Your first mission
Create or import a wallet
Pick a fresh wallet for the runtime. Set an unlock passphrase — it encrypts the keystore on disk and is not recoverable, so store it somewhere you trust.
Choose the session mode
Agent for a single task, mission for unattended runs. This is locked for the whole session; to change it, end the session and start a new one.
Set the permission level
Restricted asks before every signature. Full signs on its own. You can narrow permission mid-run at any time; widening it always requires a new session.
Define the constraints
Deadline, capital allocation, maximum loss, and the venues you allow. Anything outside these is not a suggestion the agent weighs — it is a hard boundary.
Run it and read the log
Wins, losses, and blocked attempts stream to the same local log. Export it when you want a record; publishing is opt-in and never includes your strategy.
How the runtime holds the line
The safety gate
One mandatory check sits in front of every swap and every bridge. It reads the route, the venue, the token, the slippage, and the size, and it is the same code path in restricted and full mode. It fails closed: an unreachable price feed or an unresolved contract stops the trade instead of guessing. The model cannot disable it, argue with it, or route around it, because it lives outside the model entirely.
Mission stop conditions
A mission ends on exactly one of five reasons: the deadline passes, the allocated capital is depleted, the maximum loss is reached, no viable opportunity remains inside the constraints, or you hit emergency stop. Every ending is written with its reason, so a silent stop is treated as a bug rather than a shrug.
Local memory
Working memory holds the active run. Recent memory keeps lessons from the last sessions. Long-term memory keeps conclusions that survived. Lesson strength halves every thirty days without ever hitting zero, and promotion to long-term is decided by a local judge that fails closed, so a malformed verdict promotes nothing.
Keys and custody
Keys are generated or imported on your machine and stored encrypted at rest. They are never transmitted, never part of a backup or restore payload, and never placed in the model context. Seed phrases and private keys are redacted before anything is written to memory or logs.
$REM in the runtime
$REM launches on Solana, while the runtime itself trades across Solana & Ethereum. Trading fees generated by the runtime fund buybacks, and verified track records become followable: you can mirror a published strategy inside limits you set locally. Holding $REM is not required to run the app, and it confers no claim on revenue.
When something goes wrong
The app will not open on macOS
Gatekeeper quarantines downloads. Open it once from Finder with right-click → Open, or clear the flag with `xattr -dr com.apple.quarantine /Applications/Remiora.app`.
Windows SmartScreen blocks the installer
Check the publisher on the certificate against the one listed on the release page. If it matches, choose More info → Run anyway. If it does not, delete the file.
A mission stopped almost immediately
Read the stated reason in the log. Most early stops are a maximum loss set tighter than normal spread, or a venue list too narrow to hold any viable route.
Every trade is being blocked
The gate fails closed, so a dead RPC endpoint or a stale price feed blocks everything. Check your endpoint in settings before assuming the strategy is wrong.
An approval request disappeared
Approvals expire after one hour so a mission is never stuck waiting on you. The run continues without the action, and the expiry is recorded.