When to republish
- New Move module or function.
- Breaking type change (struct field added/removed).
- New event you want indexed.
Pre-flight
Republish recipe
Reset Published.toml
Newer Sui CLI gates re-publish on this. Either delete or clear the entry under
[published].Restart indexer
Indexer event streams are scoped to the new package id. Restart the container or the dev process.
What does NOT need re-bootstrap
- PredictManager. Belongs to Predict, not DarkPool.
- DeepBook V3 BalanceManagers + TradeCaps. Belong to V3, not DarkPool.
- Per-market binary packages. Each one is its own independent package.
- V3 YES/NO pools. Same.
Fallback for CLI flakiness
CLI 1.65.x sometimes emits gRPC-style JSON thatparse-publish-output can’t read. Recover ids manually:
scripts/finish-create-market.ts --digest … recovers from a half-completed publish + create_market.
Republish history
- 2026-06-10. Published all 7 modules incl.
dark_pool, deletedposition.moveandoutcome_market.move. The current live deployment.