Repository navigation
Proving Node v2.0.2
Proving Node 2.0.2 fixes object store persistence in the new prover stack and adds requestor priority tiers.
⚠️ READ FIRST: submit your PoVW work receipts before you stop your proverIf you shut down or recreate your prover containers without first submitting your outstanding PoVW work receipts, that work and the associated PoVW rewards will be lost.
Submit first, upgrade second. See the Migration Guide below.
Components in this release
| Component | Tag | Track |
|---|---|---|
| Broker | broker-v2.0.2 |
2.x |
| Prover | prover-v2.0.2 |
2.x |
Bento (legacy 1.x stack) and the CLI are unchanged this round and are not re-tagged.
Highlights
Object store persistence
The prover object store, which holds unsubmitted PoVW work receipts, is now backed by a persistent Docker volume, so it survives container recreation. In the Redis prover stack (prover-compose.yml), the object store (--storage-dir) now uses a named Docker volume (object-store-data) instead of the container’s ephemeral filesystem. No config changes needed pull the updated prover-compose.yml and redeploy.
Requestor priority levels
The broker now respects priority.level (0–100) on requestor list entries when ranking orders for pricing and commitment. Requestors without an explicit level default to 50. Static priority_requestor_addresses entries also get level 50.
To give a requestor top priority in your lists:
"extensions": {
"priority": {
"level": 100
}
}
No broker.toml changes required. This applies automatically when using a requestor list that includes priority extensions.
Migration Guide
🛑 Mandatory: submit outstanding PoVW work receipts BEFORE upgrading
Why this matters. Each completed proving job writes a PoVW work receipt to
work_receipts/{job_id}.bincodein the prover's object store. On the prover stack, that store lives on therest_apiservice's filesystem under./data/object_store/work_receipts/. Before v2.0.2 this directory was not backed by a Docker volume. This means that every work receipt that has not already submitted is lost.v2.0.2 fixes this by adding a persistent volume, but the volume only protects receipts created after you are on v2.0.2. Receipts you are holding right now, on your current pre-2.0.2 stack, must be submitted before upgrade.
Step 1 — Submit outstanding PoVW work receipts (on your current, still-running stack)
Do this before you stop or pull anything. Your prover stack must be up so the REST API can serve the receipts.
# 1. Build a log-update proof from every unsubmitted work receipt
# currently in the object store. Reads via the prover REST API.
boundless rewards prepare-mining
# 2. Submit the prepared log update on-chain.
boundless rewards submit-mining
# 3. Confirm there is nothing left to submit.
boundless rewards inspect-mining-stateIf prepare-mining reports 0 new mining work receipts, you are clear to proceed. If it produces an update, you must submit it before continuing — receipts left behind cannot be recovered after the container is recreated.
Step 2 — Stop the stack
just prover downStep 3 — Check out v2.0.2 and pull the new images
git fetch origin
git checkout v2.0.2The v2.0.2 prover-compose.yml adds the persistent object-store volume:
environment:
STORAGE_DIR: /app/data/object_store
volumes:
- object-store-data:/app/data/object_store
# ...
volumes:
object-store-data:Step 4 — Bring the stack back up
just prover upThe compose files are pinned to the minor tags (broker-v2.0, prover-v2.0), which now resolve to the v2.0.2 images. From this point on, the object store — and any unsubmitted work receipts — survives down / up --force-recreate / redeploys.
Component releases
- Broker: https://github.com/boundless-xyz/boundless/releases/tag/broker-v2.0.2
- Prover: https://github.com/boundless-xyz/boundless/releases/tag/prover-v2.0.2
Full changelog
- #2025 — BM-3026: Persist Prover object store across container recreation
- #2012 — BM-3012: Enable requestor priority levels when ranking orders
- #2018 — BM-3017: Add market-price buffer to requestor auto-pricing
- #1993 — BM-2981: boundless-market: encode
GuestEnv::stdinas MessagePack bin - #1979 — BM-2951: pin cargo-binstall to v1.17.9 for rustc 1.89 compatibility