Open
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
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.
T3 activated on mainnet today (Apr 27, 2026, 16:00 CEST), so several T3 callouts and examples that framed T3 as upcoming are no longer accurate.
Changes
Removed
T3 will change this spec/precompilebanners (the screenshot one) from:src/pages/protocol/tip20/spec.mdxsrc/pages/protocol/tip20-rewards/spec.mdxsrc/pages/protocol/tip403/spec.mdxsrc/pages/protocol/transactions/AccountKeychain.mdxsrc/pages/protocol/transactions/spec-tempo-transaction.mdxRenamed
## Upcoming changes→## T3 changeswith past/present tense reframing in:src/pages/protocol/tip20/spec.mdxsrc/pages/protocol/tip20-rewards/spec.mdxsrc/pages/protocol/tip403/spec.mdxsrc/pages/protocol/transactions/spec-tempo-transaction.mdxRemoved
:::info[T3 examples]banners (T3 is now the baseline shape) from:src/pages/guide/tempo-transaction/index.mdxsrc/pages/protocol/transactions/index.mdxUpdated
tempo_forkScheduleexample response insrc/pages/protocol/rpc/index.mdxwith the live mainnet values (T3 active,forkId: 0xd2087b77,activationTime: 1777298400,active: "T3"), pulled fromhttps://rpc.tempo.xyz.Out of scope (follow-up)
The
## T3 changessections remain as appendices on each spec; folding the deltas back into the main spec body so post-T3 behavior reads as the canonical baseline is left for a follow-up. The inlineT2 -> T3 changessubsections inAccountKeychain.mdxare also kept as migration guidance for now.