Tempo — Machine Payments Protocol rail
What one unit is, what it costs to enter, and what we can observe onchain.
- Week2026-W43
- Updated2026-10-19
Memo-tagged pathUSD transfers on Tempo: not enough readings in the 7 days to 2026-10-19 (n=0).
- One unit is
- TIP-20 transfer carrying an invoice memo (MPP-SHAPED, not proof of an MPP payment)
- Entry costs
- n/a — a rail
Trend — registered, week over week
Gaps in a line are weeks the value was unknown. Chains are never combined.
What we measured
Tempo
▸▾ Not enough readings this window (n=0) — 3 readings, not findings
▸▾ How these were measured
- MPP can settle over other rails and other TIP-20s, and any transfer may carry a memo. This is a sampled count over one token on one chain — RATES between the three rows are valid, the counts are floors over the sampled blocks.
Confirmed contracts
Every address here was confirmed on-chain twice: bytecode present, and the block explorer's verified contract name matching the claim. A confirmation older than the re-check interval renders as stale rather than as a number that looks current.
| Chain | Contract | Role | Confirmed |
|---|---|---|---|
| Tempo | pathUSD TIP-20 (Tempo)0x20c0000000000000000000000000000000000000 | settlement-token | 2026-09-01 · source |
How this is measured
eth_getLogs for TransferWithMemo(address,address,uint256,bytes32) on pathUSD over a stratified 7-day window on https://rpc.tempo.xyz (chain 4217).
Each figure is read per chain and per lifecycle stage and is never added to another. A rate computed on fewer than 20 observations is stored and shown as “not enough readings”, never as a finding; a value that could not be read says “not measured” with the reason. Some readings on this page are in that state.
What this page cannot settle
- MPP can settle over other rails and other TIP-20s; any transfer may carry a memo. Nominal, single-token, single-rail.
- Headline safety: Only with 'memo-tagged pathUSD transfers' named as the unit.
- Some rates on this page are computed on a handful of wallets. They are shown with their sample size and marked below the publishable threshold — they are observations, not findings.
- A memo-tagged transfer is MPP-shaped, not proof of an MPP payment; MPP can settle over other rails and other tokens.
In the directory as Tempo MPP Specs.
Cite this
Sato Hub, "Tempo — Machine Payments Protocol rail — measured on-chain", satohub.ai/agent-economy/tempo_mpp, as of 2026-10-19. CC-BY.
Data: satohub.ai/api/export/adoption.json?venue=tempo_mpp (CC-BY, current week; every row carries its method, evidence tier and sample size).
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Tempo — Machine Payments Protocol rail
- What is one unit of Tempo — Machine Payments Protocol rail?
- TIP-20 transfer carrying an invoice memo (MPP-SHAPED, not proof of an MPP payment). Counting anything else as a "Tempo — Machine Payments Protocol rail agent" would compare different objects, so every row on this page names the stage it counts.
- What does it cost to enter Tempo — Machine Payments Protocol rail?
- n/a — a rail. Entry cost is why raw sizes are not comparable across venues: free and permissionless is a different market from bonded.
- How is Tempo — Machine Payments Protocol rail measured?
- Public chain reads on 1 chain, keylessly, once a week — this view is the week beginning 2026-W43. Each row carries its method, evidence tier and sample size, and a row we could not read is null rather than zero.
- Does a count here say the agents work?
- No. A registration, a launch or a staked service is an entry in a contract. Nothing about funding, activity, competence or safety is implied, and what happens after entry is measured as its own stage.
SourcesWhere the data comes fromShowHide
Sources — the standards this venue implements
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Tempo — Machine Payments Protocol rail — measured on-chain." Sato Hub, updated 2026-10-19, accessed 2026-10-21. https://satohub.ai/agent-economy/tempo_mppData last refreshed 2026-10-19; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.