Expand description
rungbot-exec — opt-in live execution.
This crate is deliberately not a dependency of the rungbot crate. The rungbot
binary holds no venue key and contains no request signing, and a test asserts that
stays true. Everything that can move money lives here, behind its own binary that you
have to install and arm on purpose.
The order of operations is the safety property:
- The ladder decides, in
rungbot-core, with no credential in the process. guard::checkrefuses anything outside the rails.journalwrites a deterministic id before the venue is called.- Only then does a venue client (
gate,revx,binance) sign a request. - [
reconcile] later reads back what the venue did and books it, andhousekeepingacts on it: cost basis, paired sells, retries, reprices, drift.
Every network call goes through http::Transport, which refuses all of them while
RUNGBOT_OFFLINE is set.
Re-exports§
pub use binance::Binance;pub use clients::Clients;pub use gate::Gate;pub use gate::PairInfo;pub use guard::Caps;pub use guard::Context;pub use guard::Intent;pub use guard::Mode;pub use guard::Refusal;pub use http::VenueError;pub use journal::client_id;pub use journal::root_id;pub use journal::Journal;pub use journal::Order;pub use journal::Side;pub use keys::Credentials;pub use keys::KeyError;pub use reconcile::reconcile;pub use reconcile::settle_cancel;pub use reconcile::Adopted;pub use reconcile::Reconciled;pub use reconcile::Settled;pub use reconcile::VenueSource;pub use revx::Revx;pub use revx::RevxCredentials;pub use venue::Balance;pub use venue::Limits;pub use venue::ParsedOrder;pub use venue::Venue;
Modules§
- balances
- The balance bridge: one read-only balance read per venue, written where the keyless layers pick it up.
- binance
- The Binance spot client.
- clients
- One client per venue, each built the first time it is needed.
- dashboard
rungbot-exec snapshot: the read-only dashboard collector.- deploy
- The monthly-capital deploy layer: fresh stable on a venue becomes resting limit-buy zones below spot (“let price come to us”) instead of a market buy the day it lands.
- deposits
- The deposit check: money that arrives from outside the bot starts a run within a minute, not at the next half-hour tick.
- gate
- The Gate.io spot client.
- guard
- The rails. Every order passes through here, and the defaults are deliberately small.
- health
rungbot-exec health: is the scheduled run still running, and can it trade?- heartbeat
- The heartbeat: one GET to a dead-man’s-switch URL after each completed run.
- housekeeping
- What a live run does before it looks at a single new signal.
- http
- The one door every venue call goes through.
- ids
- What each venue accepts as a client order id, and how a journal id becomes one.
- import
- Importing an order journal written by another implementation of this journal format.
- journal
- The idempotent order journal.
- keys
- Loading venue credentials, and refusing to load them carelessly.
- pyfmt
- Text formats the journal and the venue clients share with the reference implementation.
- reconcile
- Polling the venues and writing what really happened into the journal.
- revx
- The Revolut X spot client.
- run
rungbot-exec run: one 30-minute cycle of the live runtime.- sellcheck
- Could the held amount of each coin be sold at its venue right now?
- shadow
- The shadow run: the whole live cycle against a copy of the state, with every venue write simulated and none sent.
- store
- Where the journal lives on disk, and who may touch it.
- venue
- The surface every venue client offers, and the order shape they all parse into.
Constants§
- USER_
AGENT - The User-Agent of requests that are not venue calls.
- VERSION