Skip to content

docs(t5): fill in missing T5 callouts on TIP-20 spec, overview, payment-lane spec, and MPP guide#450

Merged
max-digi merged 1 commit into
mainfrom
docs/t5-spec-callouts-and-cleanup
May 28, 2026
Merged

docs(t5): fill in missing T5 callouts on TIP-20 spec, overview, payment-lane spec, and MPP guide#450
max-digi merged 1 commit into
mainfrom
docs/t5-spec-callouts-and-cleanup

Conversation

@max-digi
Copy link
Copy Markdown
Contributor

@max-digi max-digi commented May 28, 2026

Triple-check pass over the T5 callout rollout from #405.

Surfaced by looking at the published TIP-20 overview — the page advertises T5 features but the spec had no T5 content at all.

T5 coverage gaps filled

  • protocol/tip20/spec.mdx — add T4 → T5 migration appendix covering:

    • TIP-1026logoURI() view, setLogoURI(string), LogoURIUpdated event, LogoURITooLong/InvalidLogoURI errors, on-chain validation rules (256-byte cap, scheme allowlist), and the new 7-arg createToken overload on TIP20Factory.
    • TIP-1035system_transfer_from(from, to, amount) semantics: not in the public ABI, skips allowance checks but enforces balance/TIP-403/AccountKeychain, emits standard Transfer. Generalizes the existing system-only path to a hardfork-gated allow-list.
    • TIP-1034 — cross-reference to the TIP20ChannelReserve precompile at 0x4D505000…0000 as a TIP-20 consumer.

    Appendix only (no top-of-page Coming with T5 callout) — preserves Josh's prior decision in docs: add T5 network upgrade page + T4 → T5 migration appendices #405 not to put one on the spec.

  • protocol/tip20/overview.mdx — new Coming with T5 callout summarizing the three TIP-20 features above with a link to the spec appendix.

  • protocol/blockspace/payment-lane-specification.mdx — new Coming with T5 callout for TIP-1045 (consensus-level payment-lane classification) covering the new selector allow-list and that the TIP20ChannelReserve precompile is first-class payment-lane traffic.

  • guide/machine-payments/pay-as-you-go.mdx — new Coming with T5 callout for TIP-1034 channel reserve precompile with the precompile address and the gas-savings note from TIP-1035 implicit approvals.

Verification

$ pnpm check && pnpm check:types
# both clean (the 3 pre-existing biome warnings in scripts/lighthouse.ts are unrelated)

Amp-Thread-ID: https://ampcode.com/threads/T-019e6e22-0805-7628-b3b5-899366ecd1f6

@vercel
Copy link
Copy Markdown

vercel Bot commented May 28, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tempo-docs Ready Ready Preview, Comment May 28, 2026 3:34pm

Request Review

Comment thread scripts/check-upgrade-coverage.ts Outdated
@@ -0,0 +1,166 @@
/**
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what script is this?

Copy link
Copy Markdown
Contributor Author

@max-digi max-digi May 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

@max-digi max-digi changed the title docs(t5): fold missing T5 surface into TIP-20 spec + clean stale T2 → T3 appendices docs(t5): fill in missing T5 callouts on TIP-20 spec, overview, payment-lane spec, and MPP guide May 28, 2026
jenpaff pushed a commit that referenced this pull request May 28, 2026
T3 mainnet activated on Apr 27, 2026, over a month ago — well past the
integrator cooldown period the 'will be removed in a future docs
revision' note was meant to cover. Each canonical spec already
describes the post-T3 surface as the source of truth, so the
appendices are redundant noise.

Removed from:

- protocol/tip20/spec.mdx — virtual-address recipient resolution
  notes (already covered inline in 'Virtual Address Recipients')
- protocol/tip20-rewards/spec.mdx — setRewardRecipient virtual
  address rejection note (covered inline elsewhere)
- protocol/tip403/spec.mdx — virtual-address rejection in policy
  config + master-wallet resolution notes
- protocol/transactions/AccountKeychain.mdx — 110-line legacy T2
  interface block, selector tables, and migration summary
- protocol/transactions/spec-tempo-transaction.mdx — pre-T3
  KeyAuthorization reference block
- sdk/foundry/index.mdx — post-T3 cast selector check (redundant
  with the canonical cast keychain examples already on the page)

Follow-up to #450 (T5 content sweep) — splitting cleanup into its
own PR per review feedback.

Amp-Thread-ID: https://ampcode.com/threads/T-019e6e22-0805-7628-b3b5-899366ecd1f6

Co-authored-by: Amp <amp@ampcode.com>
@max-digi max-digi force-pushed the docs/t5-spec-callouts-and-cleanup branch 2 times, most recently from 0b3ce15 to ed6aae2 Compare May 28, 2026 12:06
@max-digi max-digi requested a review from malleshpai May 28, 2026 13:59
Comment thread src/pages/protocol/tip20/spec.mdx Outdated
) external returns (address token);
```

Use an SVG for `logoURI` so it renders crisply at any resolution across wallets and explorers (see [tokenlist Icon Requirements](/quickstart/tokenlist#icon-requirements)).
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmmm 1026 says: Rasterized formats (PNG / WebP / static, single-frame) are recommended over SVG;

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch — fixed in latest force-push. Replaced the SVG note with a pointer to TIP-1026's Recommended Formats (square PNG / WebP, single-frame). The same incorrect SVG note also appears on t5.mdx, create-a-stablecoin.mdx, manage-stablecoin.mdx, and the tokenlist Icon Requirements page — opening a separate follow-up PR for those.

# Payment Lane Specification

:::info[Coming with T5]
The [T5 network upgrade](/protocol/upgrades/t5) moves payment-lane classification from a builder-level, locally-subjective policy into consensus via a calldata selector allow-list ([TIP-1045](https://tips.sh/1045)). The allow-list covers TIP-20 calls and the new `TIP20ChannelReserve` precompile ([TIP-1034](https://tips.sh/1034)), so payment-channel reserve transactions become first-class payment-lane traffic. Indexers, explorers, and payment processors that classify "payments" should pick up the new selector list before activation. Until T5 activates, the prefix-based classification described below still applies.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The [T5 network upgrade](/protocol/upgrades/t5) moves payment-lane classification from a builder-level, locally-subjective policy into consensus via a calldata selector allow-list ([TIP-1045](https://tips.sh/1045)). The allow-list covers TIP-20 calls and the new `TIP20ChannelReserve` precompile ([TIP-1034](https://tips.sh/1034)), so payment-channel reserve transactions become first-class payment-lane traffic. Indexers, explorers, and payment processors that classify "payments" should pick up the new selector list before activation. Until T5 activates, the prefix-based classification described below still applies.
The [T5 network upgrade](/protocol/upgrades/t5) replaces the pre-T5 TIP-20 prefix-only consensus classifier with TIP-1045’s allow-listed call shapes ([TIP-1045](https://tips.sh/1045)). The allow-list covers TIP-20 calls and the new `TIP20ChannelReserve` precompile ([TIP-1034](https://tips.sh/1034)), so payment-channel reserve transactions become first-class payment-lane traffic. Indexers, explorers, and payment processors that classify "payments" should pick up the new selector list before activation. Until T5 activates, the prefix-based classification described below still applies.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Applied in latest force-push.

Comment thread src/pages/protocol/tip20/spec.mdx Outdated
string memory name,
string memory symbol,
string memory currency,
ITIP20 quoteToken,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
ITIP20 quoteToken,
address quoteToken,

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Applied in latest force-push. address matches the actual TIP-1026 spec definition.

…nt-lane spec, and MPP guide

Triple-check pass over the T5 callout rollout from #405.

Surfaced by looking at the published TIP-20 overview (which advertises
T5 features) vs the spec (which had no T5 content at all).

## T5 coverage gaps filled

- protocol/tip20/spec.mdx — add T4 → T5 migration appendix covering
  TIP-1026 (logoURI / setLogoURI / LogoURIUpdated / 7-arg createToken
  overload / on-chain validation), TIP-1035 (Implicit Approvals List
  and system_transfer_from semantics), and TIP-1034 cross-reference
  to the TIP20ChannelReserve precompile. Appendix only — preserves
  Josh's prior decision in #405 not to put a top-of-page Coming-with
  callout on the spec.
- protocol/tip20/overview.mdx — Coming-with-T5 callout summarising
  the three TIP-20 features above with a link to the spec appendix.
- protocol/blockspace/payment-lane-specification.mdx — Coming-with-T5
  callout for TIP-1045 (consensus-level payment-lane classification).
- guide/machine-payments/pay-as-you-go.mdx — Coming-with-T5 callout
  for TIP-1034 channel reserve precompile with the precompile address
  and the gas-savings note from TIP-1035 implicit approvals.

Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019e6e22-0805-7628-b3b5-899366ecd1f6
@max-digi max-digi force-pushed the docs/t5-spec-callouts-and-cleanup branch from ed6aae2 to f69a194 Compare May 28, 2026 15:28
@max-digi max-digi merged commit 07862ee into main May 28, 2026
10 checks passed
@max-digi max-digi deleted the docs/t5-spec-callouts-and-cleanup branch May 28, 2026 18:55
max-digi added a commit that referenced this pull request May 28, 2026
The 'use an SVG for logoURI' note I added in #405 contradicts the
actual TIP-1026 spec, which says:

  Rasterized formats (PNG / WebP / static, single-frame) are
  recommended over SVG; integrators that accept SVG must follow
  the SVG-handling guidance in Security Considerations.

Flagged by malleshpai on #450 for the TIP-20 spec appendix (fixed
in that PR). This PR fixes the same incorrect note on the remaining
three pages it shipped to:

- protocol/upgrades/t5.mdx (TIP-1026 integration changes section)
- guide/issuance/create-a-stablecoin.mdx (Coming with T5 callout)
- guide/issuance/manage-stablecoin.mdx (Coming with T5 callout)

Each now points at TIP-1026's 'Recommended Formats' section and
notes that SVG is allowed by the scheme allowlist but not
recommended, mirroring TIP-1026 verbatim.

The quickstart/tokenlist.mdx Icon Requirements section is a separate
off-chain API contract (the tokenlist serves vector icons via its
own /icon endpoint) and is intentionally not changed here.

Amp-Thread-ID: https://ampcode.com/threads/T-019e6e22-0805-7628-b3b5-899366ecd1f6
Co-authored-by: Amp <amp@ampcode.com>
max-digi added a commit that referenced this pull request May 28, 2026
The 'use an SVG for logoURI' note I added in #405 contradicts the
actual TIP-1026 spec, which says:

  Rasterized formats (PNG / WebP / static, single-frame) are
  recommended over SVG; integrators that accept SVG must follow
  the SVG-handling guidance in Security Considerations.

Flagged by malleshpai on #450 for the TIP-20 spec appendix (fixed
in that PR). This PR fixes the same incorrect note on the remaining
three pages it shipped to:

- protocol/upgrades/t5.mdx (TIP-1026 integration changes section)
- guide/issuance/create-a-stablecoin.mdx (Coming with T5 callout)
- guide/issuance/manage-stablecoin.mdx (Coming with T5 callout)

Each now points at TIP-1026's 'Recommended Formats' section and
notes that SVG is allowed by the scheme allowlist but not
recommended, mirroring TIP-1026 verbatim.

The quickstart/tokenlist.mdx Icon Requirements section is a separate
off-chain API contract (the tokenlist serves vector icons via its
own /icon endpoint) and is intentionally not changed here.

Amp-Thread-ID: https://ampcode.com/threads/T-019e6e22-0805-7628-b3b5-899366ecd1f6

Co-authored-by: Amp <amp@ampcode.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants