Repository navigation
fix(0336): allow-list the securities-ledger wasm family as not a venue - #407
Merged
adamkoot merged 2 commits intoOct 23, 2026
Merged
Conversation
The 2026-10-19 manual sweep after 0334 still found four contracts, all new instances of wasm f3dd3edf…, which 0334 allow-listed by one contract id. A [[wasm]] entry may now carry not_a_venue = true in place of until, for a family whose code cannot be a market; the ledger moves to one such entry.
stkrolikiewicz
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
coverage-sweep-unclassifiedhas been in ALARM since 2026-10-12. The manual sweep after the 0334 deploy (2026-10-19 09:03 UTC) still found 4 contracts, 15 events:CAKQ6DWL…,CCLN72NM…,CBZYHS2D…,CB4B4ELL…. All four are new instances of wasmf3dd3edf…, the securities-financing ledger that 0334 allow-listed by one contract id (CDU47AIU…). They were created after the 2026-10-12 window, and the family keeps deploying more, so a[[contract]]entry for each would page again every Monday.[[wasm]]entry can now carrynot_a_venue = truein place ofuntil, for a family whose code cannot be a market we price. The validator refuses an entry with both or with neither. This is an explicit exception to 0100's D4.f3dd3edf…moves from theCDU47AIU…[[contract]]entry to one such[[wasm]]entry. New tests cover the new field and check that all 5 known instances match the wasm entry.not_a_venue: the wasm itself rules out a market, not the size of the instances seen so far.make deploy-production-eventbridge, then one manual probe invoke, which should logunclassified=0and bring the alarm back to OK within about an hour.