Skip to main content
tellortellor
Menu
  • Home
  • Data Feeds
  • Developers…
    • Docs
    • New Price Feed Request
    • New Custom Data Feed Request
  • Whitepaper
  • Blog
  • Tools…
    • Data Feeds
    • Operator Dashboard
    • Block Explorer
    • Hub (bridge, delegate, etc.)
    • Query ID Station
  • More…
    • About the Team
    • TRB, the Tellor Token
    • Use Tellor
    • Become Reporter
    • Email info@tellor.io
  • twitter youtube github discord
Press enter to begin your search
Close Search

New Custom Data Feed Request

Need something that's not a price feed? Fill this form out and the team can help you coordinate with the Tellor network.

(For price feed requests, go here.)

How can we get in touch with you if we need more info?
Choose a new, unregistered PascalCase name. Existing specification names include SpotPrice and EVMCall; TRBBridge is a legacy specification name. Layer compares names case-insensitively.
Purpose of the new query type and suggested usecases.
This changes how reporters serve the query and how you read it.
How often do you need this feed updated?

Query Parameters

Parameters vary per instance of the type. Names should be mixedCase. Types are Ethereum ABI types — Layer uses the same encoding so values can be bridged to EVM without a second spec.

Each parameter needs:

  • Name
  • Description / allowed values
  • ABI type (string, uint256, bytes, etc.),
  • Order (this is the encode order for query data below)

Example — SpotPrice:

1. asset
- description: Asset ID (e.g. btc)
- value type: string
2. currency
- description: Selected currency (e.g. usd)
- value type: string

For a type with no semantic parameters, include a single empty bytes argument named 'phantom'

1. phantom

- description: Empty bytes, required for query types with no arguments
- value type: bytes
Name, description, ABI type, in encode order. Use the format from the example above.

Layer disputes a reporter, not a floating value. This section guides reporters and voters; it does not stop a dispute or guarantee a report. Be specific enough that an honest reporter knows what "correct" means.

How to fetch it, how to encode it, and when a submission is wrong. What if an API is down or sources disagree?
Where reporters can retrieve the response programmatically. Prefer multiple sources.

Build with Tellor

Tellor is the oracle layer for secure, censorship-resistant data creation and distribution. Built to be the source of truth, not just middleware, it is unlike any other data provider in the industry.

Get Started

For Builders

Data Feeds
Docs
Use Tellor
Become a Reporter

Tellor

The Team
Whitepaper
Blog

X
YouTube
GitHub
Discord
Close Menu
  • Home
  • Data Feeds
  • Developers…
    • Docs
    • New Price Feed Request
    • New Custom Data Feed Request
  • Whitepaper
  • Blog
  • Tools…
    • Data Feeds
    • Operator Dashboard
    • Block Explorer
    • Hub (bridge, delegate, etc.)
    • Query ID Station
  • More…
    • About the Team
    • TRB, the Tellor Token
    • Use Tellor
    • Become Reporter
    • Email info@tellor.io