Skip to content

data(algorand): record the Tellor BTC/USD feed and link its Medianizer - #3604

Open
CodeRabbit-byte wants to merge 1 commit into
Chain-Love:mainfrom
CodeRabbit-byte:data-algorand-tellor-feed
Open

data(algorand): record the Tellor BTC/USD feed and link its Medianizer#3604
CodeRabbit-byte wants to merge 1 commit into
Chain-Love:mainfrom
CodeRabbit-byte:data-algorand-tellor-feed

Conversation

@CodeRabbit-byte

Copy link
Copy Markdown
Contributor

Coverage lane from the weekly digest — a small, first-party-sourced addition to oracles.

The Algorand tellor-mainnet row links Tellor's own feed list but records nothing about what the feed actually carries, and does not link the deployed contract. Both facts are published by Tellor and verifiable on-chain.

What changed

One row, one file, two cells:

  • dataTypes["BTC/USD"]. Tellor's algorandTellorV2 README — already the row's own Price Feeds button — lists BTC/USD as the only feed currently available on Algorand, and says explicitly: "These are the current feeds avialable on Algorand. For additional feeds please submit an issue in this repo." The canonical tellor offer carries ["Asset Prices"], which is right for Tellor generally but says nothing about what exists on this network.
  • actionButtons → adds [Medianizer Contract]. The same README gives the mainnet Medianizer application ID 733871808, alongside five TellorFlex feed contracts. The Medianizer is the one a consumer reads, so that is the one linked.

Verification

The application was confirmed live on-chain before linking, rather than trusted from the README:

GET https://mainnet-api.algonode.cloud/v2/applications/733871808
-> app id 733871808, not deleted

Its approval program decodes to a contract carrying median, median_timestamp, timestamp_freshness, last_value and five app_N keys, which matches a medianizer over five feed contracts.

The explorer URL follows the convention already used in this network's listings — lora.algokit.io appears in two other Algorand rows. It returns 200, as do allo.info and explorer.perawallet.app for the same application if a different explorer is preferred.

Scope

validate_csv.py, csv_to_json.py and validate.py were run locally against this branch and pass. 2 cells, 1 row, 1 file, nothing existing modified and no rows added. dripLimit-style fields are untouched because Tellor publishes no such figure for this deployment.

Tellor's algorandTellorV2 README, already linked from this row, lists
BTC/USD as the only feed currently available on Algorand and gives the
mainnet Medianizer application ID 733871808.

The application was confirmed live on-chain via the Algonode mainnet API
before the link was added.
@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown

Summary

Status Count
🔍 Total 3
🔗 Unique 3
✅ Successful 3
⏳ Timeouts 0
🔀 Redirected 0
👻 Excluded 0
❓ Unknown 0
🚫 Errors 0
⛔ Unsupported 0

Full Github Actions output

@USS-Supervisor USS-Supervisor left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: REQUEST_CHANGES
Risk: MEDIUM
Summary: The Tellor Algorand dataTypes addition is supported by the linked README and the Medianizer application ID is live, but the row now violates the repository's actionButtons convention. Required validation and current-cycle link-check both passed, but this is still a blocking data-shape/style issue for the row.
Findings:

  • MEDIUM listings/specific-networks/algorand/oracles.csv, tellor-mainnet, actionButtons: this row now has three buttons (Price Feeds, Docs, and Medianizer Contract), while the current Common Columns rule says actionButtons has a max of 2 buttons. Please remove one button or fold the contract reference into one of the existing links so the row stays within the documented limit.
    Confidence: HIGH

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants