Skip to content

v0.25.0 — the bot now refuses pools it cannot build a proper range on

Choose a tag to compare

@CryptoGnome CryptoGnome released this 26 Aug 11:29
· 42 commits to main since this release
460e5ac

Nothing about how the bot trades changes today. Both changes are verified no-ops on the current book.

  • New entry gate. Some pools use very fine price steps, so a 40%-deep range would need 256 or 512 bins when the bot can only place 138. It used to quietly enter with a third of the range it meant to — that is how positions ended up 11–15% deep against a floor of 40, with nothing in the logs saying so. Now it skips the pool, logged as range_too_shallow. Checked against history: 0 of 142 meme positions would have been blocked.
  • Majors untouched. The fine-step pools are ANSEM / PUMP / MET / ORE. They trade those legitimately and plan their ranges through a separate path, so the sleeve is unaffected — a gate applied there would have blocked 29 of 34 of its positions.
  • No new setting to manage. The gate reads min_down_pct and max_position_accounts, so it always matches the depth floor you configured.
  • stop_loss_sustain_polls_in_range added and proven to do nothing. The stop had no wick tolerance while in range. Tested 1→4 over 138 replayed positions: no effect at any value, because every stop on the book fires below range, where the existing 4-poll wait already applies. Kept as instrumentation; default 1 is exactly today's behaviour.

Caveat: the measurement behind the gate is driven by the majors cohort, not the meme sleeve. It is a guard against silently entering a partial range, not a proven profit improvement.