Tycho RPC
Last updated
Last updated
Tycho exposes data through two mechanisms, the RPC and the stream. The RPC provides you access to static data, like the state of a component at a given block or extended information about the tokens it has found. For streaming data, we recommend using the Tycho Client. This guide documents the RPC interfaces.
Tycho stream provides only the token addresses that Protocol Components use. If you require more token information, you can request using Tycho RPC's #v1-tokensendpoint. This service allows filtering by both quality and activity.
The quality rating system helps you quickly assess token's specific properties:
100: Normal ERC-20 Token behavior
75: Rebasing token
50: Fee-on-transfer token
10: Token analysis failed at first detection
5: Token analysis failed multiple times (after creation)
0: Failed to extract attributes, like Decimal or Symbol
This section documents Tycho's RPC API. Full swagger docs are available at: https://tycho-beta.propellerheads.xyz/docs/
This endpoint retrieves components within a specific execution environment, filtered by various criteria.
Currently supported Blockchains
Filter by component ids
Filters by protocol, required to correctly apply unconfirmed state from ReorgBuffers
The minimum TVL of the protocol components to return, denoted in the chain's native token.
OK
This endpoint retrieves the state of protocols within a specific execution environment.
Max page size supported is 100
Currently supported Blockchains
Whether to include account balances in the response. Defaults to true.
Filters response by protocol components ids
Filters by protocol, required to correctly apply unconfirmed state from ReorgBuffers
OK
This endpoint retrieves tokens for a specific execution environment, filtered by various criteria. The tokens are returned in a paginated format.
Currently supported Blockchains
Quality is between 0-100, where:
Filters tokens by addresses
Filters tokens by recent trade activity
OK
This endpoint retrieves the state of contracts within a specific execution environment. If no
contract ids are given, all contracts are returned. Note that protocol_system
is not a filter;
it's a way to specify the protocol system associated with the contracts requested and is used to
ensure that the correct extractor's block status is used when querying the database. If omitted,
the block status will be determined by a random extractor, which could be risky if the extractor
is out of sync. Filtering by protocol system is not currently supported on this endpoint and
should be done client side.
Maximum page size for this endpoint is 100
Currently supported Blockchains
Filters response by contract addresses
Does not filter response, only required to correctly apply unconfirmed state from ReorgBuffers
OK