Skip to content

Prepare v1.0.0: migrate Slotstrike to SOF runtime and harden release flow#10

Merged
Lythaeon merged 2 commits into
mainfrom
release/v1.0.0-sof-runtime
Mar 30, 2026
Merged

Prepare v1.0.0: migrate Slotstrike to SOF runtime and harden release flow#10
Lythaeon merged 2 commits into
mainfrom
release/v1.0.0-sof-runtime

Conversation

@Lythaeon

Copy link
Copy Markdown
Owner

Summary

This branch prepares v1.0.0 and contains two main changes:

  1. Release workflow hardening
  • skip cargo publish when the target crate version already exists on crates.io
  • update the Intel macOS release runner target
  • bump the crate version to 1.0.0
  1. Runtime migration onto SOF
  • replace the legacy ingress stack with SOF-native websocket, gRPC, and private-shred runtime paths
  • add sof-tx submission integration, including direct routing support and direct leader schedule management
  • source swap blockhashes from the SOF control-plane adapter when local blockhashes are available, and require a local blockhash on private_shred
  • move Raydium candidate detection to structured transaction classification
  • remove legacy FPGA/network-path/log-stream plumbing that is no longer part of the runtime path
  • update config parsing, example config, README, and quality-gate wiring for the new runtime model
  • replace the old ingress e2e coverage with focused runtime/unit coverage plus a live dry-run replay test

Risk Notes / Regressions Considered

  • This is a large runtime refactor. The old ingress-specific modules and ports were removed, so existing deployments must use the SOF-based configuration model.
  • private_shred now depends on SOF local recent-blockhash state before building swaps. That is intentional for low-latency correctness, but it means startup before control-plane warmup can refuse a trade instead of falling back to RPC.
  • The inline SOF candidate path no longer blocks on the sniper ingress queue. Under overload it now drops candidate events and logs the drop count instead of backpressuring ingress.
  • Release behavior changes slightly: publish is skipped if the exact version is already present on crates.io.

Validation Performed

  • cargo make format-check
  • cargo make test
  • cargo make clippy
  • cargo make deny
  • cargo make audit
  • cargo test --locked

Results:

  • formatting passed
  • tests passed
  • clippy passed with -D warnings
  • deny passed
  • audit passed
  • locked test run passed after the 1.0.0 version bump

@Lythaeon Lythaeon merged commit c5ee585 into main Mar 30, 2026
1 check passed
@Lythaeon Lythaeon deleted the release/v1.0.0-sof-runtime branch March 30, 2026 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant