Open
Conversation
Adds a new page under Integrate Tempo covering data-layer differences analysts and indexers need to know when querying Tempo: USD-denominated fees, TIP-20 6 decimals, Transfer events vs tx.value, fee_payer attribution, system transactions, and supply derivation. Also includes key precompile addresses and network details. Amp-Thread-ID: https://ampcode.com/threads/T-019e0366-1385-70ac-8cf3-1738206b7d0e Co-authored-by: Amp <amp@ampcode.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
max-digi
force-pushed
the
mmp/docs-querying-tempo
branch
from
04e9919 to
d2bcc93
Compare
…lyQuery Address PR feedback: replace static SQL examples for the Transfer-based sections (volume, supply) with the existing <IndexSupplyQuery> component so readers can edit and run them against Tempo mainnet via Index Supply. Gas-fee, fee_payer attribution, and system-tx examples remain static blocks because they reference Tempo-specific columns (effective_gas_price, fee_payer) not exposed in IndexSupply's standard schema. Amp-Thread-ID: https://ampcode.com/threads/T-019e0366-1385-70ac-8cf3-1738206b7d0e Co-authored-by: Amp <amp@ampcode.com>
Upstream TIPs occasionally include GitHub handles like @0xrusowsky in the authors field. The leading @ is a YAML reserved character and breaks the build. Quote the value defensively when it begins with any YAML reserved char. Amp-Thread-ID: https://ampcode.com/threads/T-019e0366-1385-70ac-8cf3-1738206b7d0e Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019e0366-1385-70ac-8cf3-1738206b7d0e Co-authored-by: Amp <amp@ampcode.com>
…interactive Amp-Thread-ID: https://ampcode.com/threads/T-019e0366-1385-70ac-8cf3-1738206b7d0e Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019e0366-1385-70ac-8cf3-1738206b7d0e Co-authored-by: Amp <amp@ampcode.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new "Querying Tempo" page under Integrate Tempo for analysts, data engineers, and indexers writing queries against Tempo data.
It covers the EVM/data-layer differences that silently produce wrong numbers if you carry over Ethereum assumptions:
tx.valueis always 0 — useTransferevents for volumeCOALESCE(fee_payer, from)for sponsored-tx attributionfrom = 0x0…0) when measuring user activityTransferevents, notMinteventsAlso includes key precompile addresses (FeeManager, DEX, TIP-20 Factory, PathUSD) and mainnet/Moderato network details.
Placement
Sidebar entry added to
Integrate Tempobetween Wallet Developers and Contract Verification.Preview
/quickstart/querying-tempo