Release v10.0.0-rc.18 — Base Sepolia contract redeploy + version bump

[branarakic]

rc18 release — Base Sepolia contract redeploy + version bump

Release-prep PR for v10.0.0-rc.18 (testnet). Cuts from current main (includes #1107). Two commits: contract addresses + version bump.

Contracts — redeployed to Base Sepolia (base_sepolia_v10, chainId 84532)

The 7 V10 contracts changed since rc.17 were redeployed. Hub unchanged (0xC056e67D…09F6); 22 contracts re-initialized via Hub.setAndReinitializeContracts (7 new + 15 dependents). ACL is onlyContracts (Hub-membership), so Hub registration authorizes the new contracts everywhere.

Contract	Version	Address
RandomSampling	10.2.0	0xDe7a7A160B7ACa9406c881fB76a35C3A3f58C96f
RandomSamplingStorage	10.1.0	0x49368C5Af425970494d55600EE2A84756c938156
KnowledgeAssetsLifecycle	10.1.1	0xC3D61e31dC5e13717Cf34Fe16DA885D5d3727a49
DKGKnowledgeAssets	10.1.0	0x061658356662ac675421d936C67bCE96Dd0fa34C
PublishingConviction	10.0.4	0x9Ce0F3F8EA504c4ad7f040DF9c593389daBB0CE0
PublishingConvictionStorage	10.0.3	0xfd95E0eF68606264d0CAd9D6e4D1213B914Dd46d
DKGPublishingConvictionNFT	10.0.3	0x02b0C9840Ff92127B2B2788E1C18AabE0702638A

Version

10.0.0-rc.17 → 10.0.0-rc.18 across 19 package.json (16 public validated == rc.18 for the npm-publish gate).

What rc18 contains (already merged to main)

• RFC-49 "hosting follows access" — full ciphertext→catalog cutover (RFC-49 agent half: catalog model + SWM recovery + curator-leader convergence + strict curator-ack gate #1201, RFC-49 ciphertext→catalog cutover (WS-A..E) — full reconciliation onto the agent half #1203, feat(rfc49): cut the curated UPDATE path over to the catalog model #1208)
• OT-RFC-51 publishing allocation (feat(evm-module): OT-RFC-51 Publishing Allocation — committed-budget node scoring #1195)
• Proof-of-storage content-binding / Bounty the context graph explodes even after 4-5 rounds in the game #3 (fix(random-sampling): content-bind storage proofs (close caller-supplied-leaf gap) #1213)
• rc.17 fresh-main QA fixes (fix: resolve all 14 issues from rc.17 fresh-main QA validation (#1093–#1106) #1107)
• daemon HTTP admission control (feat(daemon): HTTP admission control — cap concurrent in-flight requests #1209), node-ui replication memo (perf(node-ui): memoize polled replication rollups (dashboard query cost) #1210)

After merge

Tag v10.0.0-rc.18 → npm-publish (reviewer-gated) → manual GitHub release → update testnet nodes + validate (publish + RS proof + catalog-sampling).

⚠️ Testnet cutover: the 7 addresses changed — nodes/partners must move to rc18 and re-publish; stale RS challenges drop on re-sync.

🤖 Generated with Claude Code

[otReviewAgent]

🔴 Bug: The Base Sepolia manifest now records a freshly deployed DKGKnowledgeAssets asset-storage address, alongside fresh RandomSamplingStorage and PublishingConvictionStorage, but the bundled network/testnet.json chainResetMarker is still the old v10-rc12-ka-rename-2026-06-01. Existing auto-updated nodes persist that marker, so chain-reset-wipe will not clear store.nq, random-sampling.wal, or publish journals even though Hub now resolves storage contracts with empty/new state. That leaves nodes serving and reconciling local KAs, random-sampling challenges, and PCA state from the previous contract set. Bump the marker in the same release as this storage redeploy so operators wipe derived chain state on restart.