Skip to content

docs: position Tempo as its own L1, not just another EVM chain#481

Open
snario wants to merge 1 commit into
mainfrom
docs-evm-positioning
Open

docs: position Tempo as its own L1, not just another EVM chain#481
snario wants to merge 1 commit into
mainfrom
docs-evm-positioning

Conversation

@snario
Copy link
Copy Markdown
Contributor

@snario snario commented Jun 6, 2026

Updates the wording on the quickstart pages so they describe Tempo as its own Layer 1 that runs the EVM, rather than as another EVM chain. Tone and framing only, no behavior changes.

The learn/ pages already describe Tempo as a payments-first L1, but the quickstart pages led with "fully compatible with the EVM, everything works" and "connect like you would with any other EVM chain." That undersells what Tempo is and oversells how much works unchanged. The fact that gas is in USD and there is no native token was tucked away as the reason a balance check looks odd, when it is one of the main things that makes Tempo distinct.

Changes:

  • integrate-tempo: open with Tempo as a payments-first L1 (own consensus, sub-second finality, USD gas) that runs the EVM as its execution engine.
  • connection-details: "like any other EVM chain" becomes "standard EVM tooling"; the wallet balance note now explains USD gas instead of calling it a quirk.
  • evm-compatibility: retitled "EVM Differences" to "EVM Compatibility"; says plainly that Tempo is its own chain, not an Ethereum network; presents the differences (no native token, state-creation costs) as design choices.
  • vocs.config: sidebar label follows the retitle.

Page URLs and section anchors are unchanged, so existing links still work. bun run build and bun run check pass locally.

Reframe the quickstart pages so they lead with Tempo's identity as a
payments-first Layer 1 with its own consensus, sub-second finality, and
USD-denominated gas, rather than self-categorizing as "another EVM chain."

- integrate-tempo: drop "fully compatible... everything works"; lead with
  Tempo as an L1 that runs the EVM as its execution engine
- connection-details: "like any other EVM chain" -> "standard EVM tooling";
  reframe the native-balance warning from a "quirk" to USD gas by design
- evm-compatibility: retitle "EVM Differences" -> "EVM Compatibility";
  state plainly that Tempo is its own chain, not an Ethereum network, and
  frame the deltas (no native token, state costs) as deliberate design
- vocs.config: sidebar label "EVM Differences" -> "EVM Compatibility"

No behavior or protocol changes; positioning and tone only.
@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 6, 2026

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

Project Deployment Actions Updated (UTC)
tempo-docs Ready Ready Preview, Comment Jun 6, 2026 4:32pm

Request Review

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.

1 participant