Skip to content

docs: update T7 scope and rollout dates#533

Open
max-digi wants to merge 5 commits into
mainfrom
max/t7-partner-recap
Open

docs: update T7 scope and rollout dates#533
max-digi wants to merge 5 commits into
mainfrom
max/t7-partner-recap

Conversation

@max-digi

@max-digi max-digi commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Rework the T7 upgrade page to follow the T6-style public structure with status, timeline, overview, features, compatible release guidance, and operator/integrator notes.
  • Update the final T7 scope so TIP-1066 is included without stretch-goal language.
  • Sync the network upgrades page with the new dates: Jun 29 release publication, Jul 2 testnet rollout, and Jul 9 mainnet rollout.

Testing

  • Checked for stale T7 dates and internal rollout wording.
  • Ran git diff --check -- src/pages/docs/protocol/upgrades/t7.mdx src/pages/docs/guide/node/network-upgrades.mdx.
  • Ran ./node_modules/.bin/vite build successfully. Existing dependency warning remains: wagmi imports a viem Tempo wallet action named send that is not exported.

@vercel

vercel Bot commented Jun 23, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
tempo-docs Ready Ready Preview, Comment Jun 23, 2026 2:40pm

Request Review

@max-digi max-digi changed the title docs: update T7 partner recap and rollout dates docs: update T7 scope and rollout dates Jun 23, 2026
Comment on lines +83 to +89
### For dynamic base fee

Wallets, SDKs, and infrastructure should read the current base fee from the network instead of assuming one fixed value.

- Fee estimators should be tested on testnet after T7 rollout.
- User interfaces should show the current estimated fee at send time.
- Monitoring should track base fee movement before mainnet rollout.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

@klkvr I think we could highlight the lowest vs max (current) fee as values?

TLDR: cheaper if not congested, and current/regular fee if congested

@max-digi max-digi requested a review from klkvr June 23, 2026 15:05
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.

2 participants