Your keys. Your rules. Your machine.

One budget, several entries

Arm buy orders on several coins from the same wallet balance. Whichever triggers first takes the funds. Entries that trigger later cancel themselves if the money is gone.

The exit exists before the entry

Attach take-profit and stop-loss to a buy order before it fills. The moment the buy confirms on-chain, the exit rule is armed. There is no window where you hold a position without a plan.

Keys stay on this machine

Your wallet is generated locally and encrypted locally. Keys are decrypted only in memory while the app is unlocked. There is no server and no custody.

Rules, not a cloud

Orders are plain rules the app evaluates while it runs on your machine. Nothing monitors or executes while it is closed. The code is AGPL-3.0, so you can verify exactly what it does.

$ New order type

= 1 file + 1 line

Order rules live in a registry. Write a rule file, register it with one line. All five built-in rules work exactly this way.

$ New chain

= 1 adapter + 2 lines

Chains sit behind a single adapter interface with one watcher loop. Implement the adapter, wire it in, and the rule engine runs on your chain.

Headless core

The engine runs without the UI. Lifecycle, rules, adapters and signing form a core the desktop app consumes.

Docs that exist

README, CONTRIBUTING, SECURITY policy, CODE_OF_CONDUCT and a full ARCHITECTURE.md are already written.

Open core

The code that handles keys and orders stays open. Anyone can verify it.