T3 docs cleanup: make T3 canonical, consolidate T2 deltas into migration appendix#350
Open
T3 docs cleanup: make T3 canonical, consolidate T2 deltas into migration appendix#350
Conversation
T3 activated on mainnet today (Apr 27, 2026, 16:00 CEST), so the 'T3 will change this spec/precompile' callouts at the top of these spec pages are no longer accurate. Amp-Thread-ID: https://ampcode.com/threads/T-019dd0dc-6a9c-7239-90cf-3737ae460bfa Co-authored-by: Amp <amp@ampcode.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…rs, update RPC example - Rename '## Upcoming changes' -> '## T3 changes' in TIP-20, TIP-403, TIP-20 rewards, and Tempo Transaction specs; reframe intros and applicable bullets in past/present tense now that T3 is live. - Remove ':::info[T3 examples]' banners from the Tempo Transaction guide and the protocol transactions index — T3 is now the baseline. - Update the tempo_forkSchedule example response in the RPC docs to reflect mainnet (T3 active, real fork IDs and activation time). Amp-Thread-ID: https://ampcode.com/threads/T-019dd0dc-6a9c-7239-90cf-3737ae460bfa Co-authored-by: Amp <amp@ampcode.com>
max-digi
changed the title
…ndix For each protocol spec, fold the T3 deltas into the body so the spec reads as post-T3 baseline, and consolidate T2 -> T3 migration content into a single `## T2 → T3 migration` appendix at the bottom of the page. The appendix is kept for an integrator cooldown period and will be removed in a future docs revision. Specs updated: - AccountKeychain.mdx (full rewrite — was 21 inline T2 -> T3 subsections) - tip20/spec.mdx (added Virtual Address Recipients section) - tip20-rewards/spec.mdx (folded virtual-address rejection into Opt-In Model) - tip403/spec.mdx (folded virtual-address handling into Usage with TIP-20 Tokens) - spec-tempo-transaction.mdx (updated KeyAuthorization, TokenLimit, authorization hierarchy, spending-limit, call-scope, contract-creation, RLP encoding, examples, and intrinsic-gas pseudocode) Amp-Thread-ID: https://ampcode.com/threads/T-019dd0dc-6a9c-7239-90cf-3737ae460bfa Co-authored-by: Amp <amp@ampcode.com>
max-digi
changed the title
Same treatment as the protocol specs in this PR: remove the two inline '#### T2 -> T3 changes' sections, reword surrounding prose as T3-canonical (drop 'Post-T3 / pre-T3' future-tense framing in the forge-create note, the access-key CREATE restriction, the cast keychain intro, and a code comment), and consolidate the legacy authorizeKey ABI + selector-check material into a '## T2 → T3 migration' appendix at the bottom with the same :::info[Migration appendix] callout used on the spec pages. Amp-Thread-ID: https://ampcode.com/threads/T-019dd9ac-1e55-70ed-89d6-0764dccdf9e8 Co-authored-by: Amp <amp@ampcode.com>
tmm
approved these changes
Apr 30, 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
4 participants
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.
T3 activated on mainnet on Apr 27, 2026 (16:00 CEST). This PR makes T3 the canonical baseline across the protocol specs and the Foundry SDK page, and consolidates T2-era deltas into a single
## T2 → T3 migrationappendix at the bottom of each affected page. The appendix is kept for an integrator cooldown period and will be removed in a future docs revision.Changes
Banners removed (the original screenshot ask)
:::info[T3 will change this spec/precompile]banners removed fromtip20/spec.mdx,tip20-rewards/spec.mdx,tip403/spec.mdx,transactions/AccountKeychain.mdx,transactions/spec-tempo-transaction.mdx.:::info[T3 examples]banners removed fromguide/tempo-transaction/index.mdxandprotocol/transactions/index.mdx— T3 is now the baseline shape.Specs rewritten as T3-canonical with consolidated migration appendix
transactions/AccountKeychain.mdx— full rewrite. Was 21 inline#### T2 -> T3 changessubsections plus a top-of-page## Account keychain post-T3block and a separate### T2 interfacesection. Now reads as a single post-T3 specification, with all T2 deltas, the legacyauthorizeKeyselector/encoding, and the legacy interface listed under## T2 → T3 migrationat the bottom.tip20/spec.mdx— added a## Virtual Address Recipientssection describing TIP-1022 resolution as canonical TIP-20 behavior. T3 deltas summarized in## T2 → T3 migration.tip20-rewards/spec.mdx— virtual-address rejection insetRewardRecipient(...)is now part of the Opt-In Model section.tip403/spec.mdx— virtual-address rejection on policy-config functions and resolution behavior on TIP-20 policy checks are now inUsage with TIP-20 Tokens.transactions/spec-tempo-transaction.mdx—KeyAuthorizationstruct now includesallowed_calls,TokenLimitincludesperiod, plus newCallScopeandSelectorRulestructs. RLP encoding, authorization hierarchy, spending-limit enforcement (with recurring rollover), call-scope enforcement, contract-creation restriction, theKeyAuthorizationexample, the precompile querying example, and the intrinsic-gas pseudocode are all updated to T3.SDK docs
sdk/foundry/index.mdx— applies the same T3-canonical pattern as the protocol specs above (originally split out as docs(sdk/foundry): make T3 canonical, consolidate T2 deltas into migration appendix #363, now folded in here). Removes the two inline#### T2 -> T3 changesheadings, dropsPost-T3 / pre-T3future-tense framing in theforge createnote, the access-key CREATE restriction, thecast keychainintro, and a code comment, and consolidates the legacyauthorizeKey(...)ABI migration note + the fullCheck your authorizeKey(...) migration with castsection into a## T2 → T3 migrationappendix at the bottom.RPC docs
protocol/rpc/index.mdx—tempo_forkScheduleexample response updated to live mainnet values (T3 active,forkId: 0xd2087b77,activationTime: 1777298400,active: "T3"), pulled fromhttps://rpc.tempo.xyz.Affected pages (preview)
Out of scope (kept for a future PR)
## T2 → T3 migrationappendices on each spec/page are deliberately left in. They should be deleted in a follow-up once the cooldown period is over. Removability is straightforward: each appendix is the trailing section of its file with no incoming anchors, so a singlesedloop can drop or replace them in one shot.protocolVersion: T3) on TIP-1011/1016/1020/1022 and the/protocol/upgrades/t3page itself are historical metadata; left as-is.sdk/typescript/index.mdxstill has one "pre-T3 / post-T3" sentence describing the Accounts SDK status — it's factual rather than future-tense, but worth a follow-up to mirror the same canonicalization pass.