Skip to content

docs(tips): add Compatibility section to TIP template#402

Open
max-digi wants to merge 2 commits into
mainfrom
docs/add-compatibility-section-to-tip-template
Open

docs(tips): add Compatibility section to TIP template#402
max-digi wants to merge 2 commits into
mainfrom
docs/add-compatibility-section-to-tip-template

Conversation

@max-digi
Copy link
Copy Markdown
Contributor

Adds a Compatibility section to the TIP template so authors always describe external-system impact (indexers, market makers, analytics, wallets, tooling, on-chain events/IDs) or explicitly write N/A.

Mirrors the section already used ad hoc in TIPs like TIP-1056.

Authors must describe external-system impact (indexers, market makers,
analytics, wallets, tooling, etc.) or write N/A. Mirrors the section
already used in TIPs like 1056.

Amp-Thread-ID: https://ampcode.com/threads/T-019e20ca-9ef7-729e-86b9-bf790c2c9df8
Co-authored-by: Amp <amp@ampcode.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 13, 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 13, 2026 1:45pm

Request Review

This section should describe invariants that must always hold, and outline the critical cases that the test suite must cover.
This section should describe invariants that must always hold, and outline the critical cases that the test suite must cover.

# Compatibility
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.

would change order and move up before invariants

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