Repository navigation
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Collaborator
🟡 Heimdall Review Status
|
This branch was successfully deployed
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.
What changed? Why?
Closes Base Knowledge Base gap
gap-20261001-recover-funds-entry-says-seizewithmemo-not(gaps log, DEVREL-859). Question: "Is seizeWithMemo now available on mainnet, and should the guide and index be updated?"The Recover Funds guide already says
seizeWithMemoshipped with Cobalt. The B20 changelog's Beryl entry still contradicted it: it listedseizeWithMemo, six policy scopes (including the seize scopes), theSEIZEpause feature, and seize memo variants under Beryl, and it markedburnBlockeddeprecated at Beryl. This PR corrects the Beryl entry indocs/specifications/b20/changelog.mdx:PausableFeatureat Beryl:TRANSFER,MINT, andBURNburnBlockedandBURN_BLOCKED_ROLElisted as added at Beryl, not deprecatedseizeWithMemo, theSEIZEpause feature, the seize policy scopes, and theburnBlockeddeprecationNotes to reviewers
Primary sources:
PausableFeaturewithoutSEIZE,burnBlocked, memo variants without seize): base/basecrates/common/precompiles/src/common/abi/v1.rsSEIZE=3pause ordinal, two new policy slots, andburnBlockeddeprecated but still callable at Cobalt:docs/base-chain/specs/reference/b20/changelog/02-cobalt-b20-seize.mdx(master)docs/specifications/b20/concepts/roles-and-pause.mdx(master)docs/upgrades/cobalt/overview.mdxand the Cobalt table already in the changelogThis replaces the B20 changelog part of #2092 for this gap. The other files in #2092 are out of scope here.
No SME confirmation needed. The Beryl entry still lists
UNIONandINTERSECTpolicy types, while the Cobalt table lists composite policies as a Cobalt change. That is a separate gap and is not changed here.How has it been tested?
node scripts/lint-mdx.js --files-from=<changed files>: passed, 0 errors, 0 warningsnode scripts/validate-docs-structure.js: reports 2 redirect errors for/upgrades/denim/eip-8130. These also fail on master and are unrelated to this change/base-chain/specs/reference/b20/changelog/02-cobalt-b20-seizeexists indocs/docs.jsonand as a fileScreenshots
N/A (text-only change)
Generated with Toshi