The first weekly development report brings node reliability, explorer improvements and the EVM, DEX, bridge and aggregator work into one dated record. The next node binary remains in consolidation.
Explorer transaction lookup, exact receipt accounting and analytical charts were published on 16 September.
Persistent node recovery passed local state-equivalence and crash-restart tests. Linux and current-mainnet qualification remain open.
EVM, native DEX, bridge and aggregator development are being consolidated before selecting the next node release.
02 / STATE OF THE CODE
Six fronts. One shared view.
Engineering review
01Validation pending
Node & consensus
The published Genesis-4 binary is the 14 September release. A local candidate adds persistent committed state, bounded tail replay, corrupt-cache fallback and incomplete-log recovery.
What remains
Reconcile development branches with released consensus history; qualify the pinned Linux build, mixed versions and recovery against the complete current log.
Evidence & scope
Local candidate: 382 node tests and 423 committee debug tests passed. These do not establish a production recovery SLA.
Transaction lookup now distinguishes missing receipts from service failures, preserves exact integer accounting and shows allocation charts. Analytics adds epoch activity, slot fill and proposer coverage.
What remains
Continue historical indexer coverage and source-freshness validation; avoid treating unavailable or partial data as zero.
Evidence & scope
Explorer production deployment and fixture-based browser checks completed on 16 September.
Signed EVM execution, local developer examples and experimental Reth storage integration are implemented. A local EVM is distinct from settlement on Bloch.
What remains
Complete native settlement, authenticated finality and proof integration; qualify the complete execution and state-restoration path.
Evidence & scope
Source review of the modular execution README and delivery plan; production Bloch settlement is not established.
PosternDEX has an external-EVM interface. Separately, native Bloch assets, pool custody and canonical transaction integration are being developed behind inactive or laboratory gates.
What remains
Unify the released consensus baseline, integrate all pool state with restart/reorg recovery, finish cross-component tests and review an activation plan.
Evidence & scope
An external-chain DEX interface is not evidence that native Bloch pools are active.
Reference bridge components, local roundtrips and read-only deposit/release observers exist. Native gateway operations retain explicit custody and authorization boundaries.
What remains
Authenticate finality, finalize production routes and custody, reconcile backing and redemptions, and complete independent review before enabling public native deposits.
Evidence & scope
No public Bloch bridge deposit or withdrawal service is claimed by this report.
The wallet includes LI.FI route comparison and a restricted Across ETH execution/recovery path. Current source also adds local signing and receipt-bound delivery checks.
What remains
Complete the intended route and wallet matrix, rejection/recovery tests and source/destination receipt checks. Keep external-EVM routes separate from native Bloch settlement.
Evidence & scope
Scope follows the wallet README and recent implementation commits; this report does not qualify every route or asset.
Readiness is evidence-based. No completion percentages or promised dates.
PendingNode release
Freeze a compatible node candidate
Collect final agent commits, preserve live activation rules and test old and new nodes together.
PendingNode release
Make restart predictable
Finish cache-version policy, cold genesis/carryover initialization, snapshot cost and resource limits; measure real Linux recovery.
In progressProtocol integration
Connect EVM execution to native settlement
Complete authenticated state/finality and the proof/settlement boundary beyond local execution.
In progressProtocol integration
Complete native DEX and bridge integration
Cover pool reserves, gateway liabilities, replay protection and all state in atomic execution, reorgs and persistent recovery.
In progressApplication release
Qualify wallet and aggregator delivery
Verify supported networks, quote execution, rejection paths and receipt-based recovery for the defined integration scope.
PendingOperations
Publish one tested binary with operator guidance
Pin source, compiler, features and hashes; run a standby/canary, retain rollback instructions and coordinate independent validators.
04 / SOURCE ACTIVITY
Changes you can inspect.
Commits show source activity. They do not prove a deployment.
Release 1 combines a September 16 engineering review with public repository activity since September 9. Local work in progress can be newer than published branches. Unavailable sources are shown explicitly.
Weekly source activity is collected from public repositories. Engineering status changes require a dated roadmap review. Each edition preserves its source snapshot and review date; a missing source is reported as unavailable.