---
id: TIP-0000
title: TIP Process
description: Defines the Tempo Improvement Proposal lifecycle from draft to production.
authors: Internal
status: Draft
related: N/A
---

# TIP-0000: TIP Process

## Abstract

This TIP defines the lifecycle for a Tempo Improvement Proposal, from draft through mainnet activation. It sets clear decision gates, required reviews, and ownership expectations so proposals are evaluated consistently before they are scheduled and rolled out.

**External TIP submissions are not accepted at this time.**

## Motivation

This process gives the team one shared path from idea to production. A consistent lifecycle improves decision quality, keeps security and ecosystem impact visible, and helps prioritize changes that solve real user problems.

---

# Specification

## Status Lifecycle

`Draft` → `In Review` / `Rejected`

`In Review` → `Ready for Consideration` / `Rejected`

`Ready for Consideration` → `Approved` / `Backlog` / `Rejected`

`Backlog` → `Ready for Consideration` / `Rejected`

`Approved` → `Scheduled` → `Testnet` → `Mainnet`

## Status Definitions

- `Draft`: The idea is being developed into a complete TIP and is not yet in formal review.
- `In Review`: The TIP is under structured technical, security, and implications review.
- `Ready for Consideration`: Required review is complete and the TIP is ready for a network upgrade call decision.
- `Backlog`: The TIP is directionally supported, but deferred until there is clear product or customer pull.
- `Approved`: The TIP is accepted and eligible for upgrade scheduling.
- `Scheduled`: The TIP is assigned to a specific upgrade.
- `Testnet`: The TIP is released on testnet and monitored against success criteria.
- `Mainnet`: The TIP is released on mainnet.
- `Rejected`: The TIP does not move forward in its current form.

## 1. Propose a TIP

Goal: Turn an idea into a complete, reviewable specification.

1. Share the problem and proposed direction early to gather feedback.
2. Assign one TIP owner who is accountable for moving the TIP forward.
3. Pick the lowest available TIP number and create branch `tip/xxxx`.
4. Create `tip-xxxx.md` using the [TIP Template](./tip_template.md) and open a draft PR.
5. Complete the draft with: problem statement, design, assumptions, alternatives considered, threat model, expected tooling/user impact, and success criteria.
6. When ready, set status to `In Review` and request stakeholder review.

## 2. Review the TIP

Goal: Validate the proposal's value, feasibility, and risk.

1. Run stakeholder review in the PR and keep the TIP updated.
2. Provide evidence that the problem is real and worth solving now.
3. Run a whiteboard session if needed to align context.
4. Complete engineering review and confirm the design is feasible and robust.
5. Complete a security review.
6. Complete an implications review for tooling, integrations, and partners, and share outcomes with affected stakeholders.
7. Obtain engineering, research, and security approval.
8. Before merging, set status to `Ready for Consideration`, then merge.

## 3. Consideration and Decision (Network Upgrade Call)

Goal: Move each `Ready for Consideration` TIP to a clear decision.

1. The TIP owner flags with the network upgrade call chair that a decision is needed ahead of the call.
2. The TIP owner presents review outcomes, key tradeoffs, and major spec changes.
3. The call records one outcome: `Approved`, `Backlog`, or `Rejected`.
4. If `Approved`, confirm a target upgrade when possible.
5. If `Backlog`, record what signal is needed to revisit it.

## 4. Scheduling Criteria

A TIP can move from `Approved` to `Scheduled` only if:

1. Engineering capacity is available.
2. A target upgrade is identified.
3. Inclusion timing is explicit (`Why include? Why now?`).
4. The TIP spec is complete and implementation-ready.

## 5. Ship a TIP

Goal: Implement the approved TIP and prepare it for rollout.

1. Implement the TIP and keep the spec aligned with what is built.
2. Implementation can still surface learnings; updates and scoped changes are welcome.
3. If implementation materially changes the TIP, request another approval from the same engineering, research, and security stakeholders. This second approval should be fast and focused on the implementation delta.

## 6. Testnet Release Readiness

Before moving an upgrade to `Testnet`:

1. Publish technical communication, including tooling and user impact.
2. Ensure dashboards and alerting are in place for success criteria.