tempoxyz/tempo

the blockchain for payments

View on GitHub ↗Jump to charts ↓Open shareable report →

tempoxyz/tempo has 1k+ stars and 350+ forks on GitHub, is written in Rust, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 4 minutes ago
Added to GitGenius on December 12th, 2025
Created on June 2nd, 2025
Open Issues & Pull Requests: 194 (+0)
GitHub issues: Enabled
Number of forks: 370
Total Stargazers: 1,035 (+0)
Total Subscribers: 13 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.8 hours
Mean response time: 11.1 days
90th percentile: 28.5 days
Tracked items: 504

Maintainer activity

25 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 10% of issues opened in the past year have never received a reply. 87% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "F-allegretto" is answered fastest, typically in under an hour, while "A-consensus" waits about 6 days. 52% of tracked open issues have had no activity in three months. 86% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 61
New in 7 days: 7
Closed in 7 days: 3
Avg open age: 57 days
Stale 30+ days: 48
Stale 90+ days: 32

Recent activity

Opened in 7 days: 6
Closed in 7 days: 3
Comments in 7 days: 2
Events in 7 days: 18

Top labels

  • C-enhancement (138)
  • C-Bug (60)
  • A-precompile (54)
  • S-needs-triage (54)
  • A-consensus (49)
  • C-audit (22)
  • C-perf (21)
  • A-evm (20)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Tempo is a blockchain specifically engineered for stablecoin payments at scale, written in Rust and documented at docs.tempo.xyz. The project positions itself as payment infrastructure designed for financial institutions, payment service providers, and fintech platforms, with a focus on high throughput, low cost, and features expected from modern payment systems.

The repository's core innovation centers on payment-specific blockchain features rather than general-purpose smart contract execution. Tempo introduces the TIP-20 token standard, which represents enshrined ERC-20 extensions tailored for payments. The protocol includes dedicated payment lanes reserved for TIP-20 transfers to eliminate noisy-neighbor contention and ensure predictable payment throughput. Native reconciliation capabilities support on-transfer memos and commitment patterns for handling off-chain personally identifiable information and large data without exposing sensitive details on-chain.

Compliance infrastructure is built directly into the protocol through the TIP-403 Policy Registry, which allows a single policy to be shared across multiple tokens, updated once, and enforced everywhere. Fee structure is designed for payment use cases, with users paying gas directly in USD-stablecoins at launch. The Fee AMM automatically converts payments to validators' preferred stablecoins, and TIP-20 transfers target sub-millidollar costs below $0.001.

Tempo Transactions provide native smart account functionality including batched payments for atomic multi-operation payouts like payroll and settlements, fee sponsorship allowing applications to pay users' gas costs, scheduled payments with protocol-level time windows for recurring disbursements, and modern authentication via passkeys using WebAuthn and P256 standards. The execution layer builds on the Reth SDK for performance and uses Simplex Consensus via Commonware for sub-second finality under normal conditions with graceful degradation during adverse network conditions.

The platform maintains full Ethereum Virtual Machine compatibility targeting the Osaka hardfork, allowing developers to deploy smart contracts using familiar tools like Solidity, Foundry, and Hardhat. All Ethereum JSON-RPC methods work out of the box, though Tempo introduces payment-specific optimizations documented in its compatibility guide.

The project provides multiple integration paths including a public testnet at chain ID 42431 with RPC endpoints, SDKs in TypeScript, Rust, Go, and Foundry, and installation options via pre-built binaries, source builds, or Docker. The repository includes comprehensive documentation for users, operators, and developers, along with contribution guidelines and security policies. Tempo is currently undergoing audit and does not yet have an active bug bounty program.