docs: move both contract baselines to the GA v2.0.0 tags - #17
Merged
Conversation
The release candidates the corpus pinned are superseded: both contracts tagged v2.0.0 and the GA AtomicAssets build is what the testnets execute, byte-verified against the Release checksum. atomicmarket v2.0.0 is the same commit as rc2. The atomicassets GA diff moves every citation past the acceptauswap hunk by three lines and accepts the acceptance-date boundary second the candidates rejected, so the affected sections state the GA behavior and every shifted citation was re-verified against the tag.
This was referenced Aug 18, 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
1 participant
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 this change claims, in one sentence:
Every fact pinned to the contract release candidates now reads at the GA
v2.0.0tags, whose AtomicAssets build is byte-identical to what both testnets execute, and the one behavior delta the GA diff carries (theacceptauswapboundary second is accepted) is stated where the pages describe it.Source:
atomicmarket-contractv2.0.0is the same commit asv2.0.0-rc2(git rev-parse v2.0.0-rc2^{} == v2.0.0^{} == b7b757b0), so its re-pin changes no line.atomicassets-contractv2.0.0-rc4..v2.0.0inserts a net +3 lines insidesrc/atomicassets.cpp(createauswap comment, acceptauswap restructure) and changesinclude/checkformat.hppconst-qualifiers only; all 136 shiftedsrc/atomicassets.cppcitations were re-verified againstgit show v2.0.0:src/atomicassets.cppsymbol by symbol, the author-swap sections were re-read in full (exact GA spans: createauswap 357-381, acceptauswap 390-420, rejectauswap 427-445), andinternal_create_templateis now cited at its real bounds 1582-1658 (the previous 1613-1689 missed the function on both ends under either tag). Deployment proof:POST /v1/chain/get_code_hash {\"account_name\":\"atomicassets\"}onwaxtestnet.greymass.comandjungle4.api.eosnation.ioboth return962a93e1..., equal to theatomicassets.wasmline of thev2.0.0ReleaseSHA256SUMS.Tier: source-read for the re-anchored citations and the boundary fact; live-chain for the new deployment paragraph (an already-both page, so no tier moves).
Row in
reference/validation.mdupdated: yes; both contract baselines and every row naming an rc tag now readv2.0.0, and the caveat paragraph no longer speaks of rc source. The CHANGELOG carries a2026.08.1section on the assumption this merges next; renumber if another merge lands first.One deliberate leftover:
reference/atomicassets/actions.mdstill namesv2.0.0-rc1once, in the historical note about the descoped custodial-rentals design, which is about the candidates by nature.