RFP ID
RFP-020 — RedStone Off-Chain Oracle Adaptor for LEZ
Your Project Name
Multi-Oracle Adapter for LEZ
Team or Organization Name
DIA Oracles
Primary Contact
Dillon Hanson - dillon.hanson@diadata.org ; TG: @DIABDteam
Team Members
Product and Engineering:
Name: Samuel Brack
Social links: Github // LinkedIn
Role: Cofounder; CTO
Status: Full-time
Name: Philipp Pade
Social links: Github // LinkedIn
Role: Lead Integrations Developer
Status: Full-time
Name: Nitin Gurbani
Social links: Github // LinkedIn
Role: Senior Developer
Status: Full-time
Name: Zygis Marazas
Social links: LinkedIn
Role: Product Lead
Status: Full-time
Name: David D'Amario
Social links: LinkedIn
Role: QA Lead
Status: Full-time
Name: Arounen Murdhen
Social links: LinkedIn
Role: Technical Product Manager
Status: Full-time
Business Development
Name: Paul Claudius
Social links: LinkedIn
Role: Cofounder; CBO
Status: Full-time
Name: Dillon Hanson
Social links: LinkedIn
Role: Head of Business Development — primary point of contact with Logos
Status: Full-time
Name: Josh Bellerive
Social links: LinkedIn
Role: Business Development Manager
Status: Full-time
Marketing & Community
Name: Carl Bruns
Social links: LinkedIn
Role: Cofounder; CMO
Status: Full-time
Name: Mikel Garcia
Social links: LinkedIn
Role: Head of Marketing
Status: Full-time
Name: Anze Noc
Social links: LinkedIn
Role: Community Lead
Status: Full-time
Project Summary
DIA's take on the RF:
This proposal delivers a production-grade oracle on LEZ from day one, together with the architecture to scale it: DIA’s Multi-Oracle Adapter. The adapter enables additional independent oracle providers to be added over time without re-architecting the underlying integration, once their feeds are live on LEZ and the necessary data-usage rights are confirmed by their respective operators.
This Proposal Has Two Parts:
First, DIA: live, first-party-sourced oracle price feeds for BTC/USD, ETH/USD, SOL/USD, XMR/USD, and ZEC/USD, backed by DIA's production track record since 2020, with no third-party data-rights dependency attached to that initial delivery.
Second, the Multi-Oracle Adapter: the extensibility layer that enables LEZ to onboard additional oracle providers over time, on demand, once each provider's data-usage rights are confirmed by the party operating that connector, rather than locking the network to a single vendor from the outset.
No third party other than RedStone itself can assert the right to redistribute RedStone's data today, and RFP-020 itself does not resolve that question in advance. What DIA can deliver with certainty, and commit to operating under SLA, is production-grade oracle infrastructure live on day one, on an architecture that removes single-vendor lock-in from LEZ's oracle layer permanently, not just for this integration.
Why it Matters:
LEZ's privacy-DeFi thesis depends on reliable USD reference prices for privacy collateral, namely Monero (XMR) and Zcash (ZEC), to make the reflexive stablecoin (RFP-013), the privacy-preserving DEX (RFP-004), wrapped privacy assets, and other cross-chain primitives function. The on-chain TWAP tier in RFP-019 cannot carry this alone: DEX TWAP security scales with pool depth, which is thin on a new chain, and a DEX TWAP oracle only produces a price for pairs that exist as LEZ pools at all. An external price feed is required to get any XMR/USD or ZEC/USD reference on chain at all.
Whichever oracle source a network relies on, a single provider is a single point of failure, both for liveness (DNS, TLS, and regional hosting availability all become dependencies) and for governance (the network is structurally locked to one vendor's terms, pricing, and roadmap). DIA's proposal addresses both halves of that problem directly: it puts live, first-party-sourced oracle price feeds on LEZ from day one with no third-party terms-of-use dependency attached to that initial delivery, and it builds the adapter layer so that LEZ is never architecturally locked to a single source, regardless of which additional providers become available on LEZ later.
Technical Approach
2. Solution
2.1 DIA: Live From Day One
DIA is an established, production-grade oracle network, deployed as LEZ's day-one price source with no third-party data-rights dependency attached to that delivery.
DIA is a cross-chain oracle provider focused on data transparency, customization, and accessibility. Unlike traditional oracles that rely on opaque third-party data aggregators, DIA sources raw trade data directly from 100+ centralized and decentralized exchanges. This first-party sourcing approach ensures 100% transparency at the exchange level, eliminating black boxes and providing verifiability for developers and users alike.
With This Architecture, DIA Delivers:
- 2,500+ cryptocurrency token feeds
- 5,000+ real-world asset price feeds
- Customizable oracles to support diverse protocol needs on Logos Network
How DIA Works: DIA's modular architecture consists of three core layers:
Data Sourcing: Collect real-time data from decentralized exchanges (DEXs), centralized exchanges (CEXs), and other sources through DIA's decentralized Feeders Network. This decentralized network of nodes ensures that data is accurate, timely, and sourced directly from the market.
Data Computation: Process and verify the collected data on-chain, using open source Pods and Aggregators smart contracts within the DIA Lumina infrastructure.
Publication: Publish verified prices directly on-chain via the LEZ program described in this proposal (Section 3.3), with no external bridge or cross-chain messaging dependency for this deployment.
This system is further supported by a robust monitoring framework, ensuring data accuracy, uptime, and resilience through node redundancy. For a breakdown of each component, please visit: https://www.diadata.org/docs/reference/architecture.
Capabilities & Feasibility: DIA oracles are deployed across leading chains including Ethereum, Arbitrum, Polygon, Optimism, Near, Avalanche, Base, and BNB Chain, and many more. Importantly, DIA is not limited to EVM-compatible chains and has a proven track record of successful deployments on non-EVM environments (such as XRPL, Stacks, Soroban Network, Cardano, Midnight Network, Near, Solana, Alephium, Aleph Zero, Astar-WASM, Vara, and more), demonstrating the ability to adapt and successfully implement DIA oracles on networks with different technical architectures.
For LEZ specifically, this means BTC/USD, ETH/USD, SOL/USD, XMR/USD, and ZEC/USD go live on devnet/testnet using proven, battle-tested first-party oracle infrastructure, not a net-new build. No third party other than RedStone itself can assert the right to redistribute RedStone's signed data today. DIA's commitment in this proposal is to what it can deliver with certainty: a live, production oracle, operating under SLA, from day one.
DIA oracles will be deployed on Logos Network via smart contract. The smart contract is a key/value store and contains two values per asset, the timestamp of the last update and the value of the asset price. The asset price is stored with 18 decimals by default.
2.2 Multi-Oracle Adapter: Built for Growth
The Multi-Oracle Adapter is the mechanism that keeps LEZ from ever being locked to a single oracle provider, including DIA.
The Single-Provider Lock-In Problem: Once an oracle-dependent program is deployed, the oracle path can be difficult or impossible to change. If LEZ's price infrastructure depends on a single provider, that provider becomes a permanent operational dependency rather than a replaceable infrastructure component. The core insight, already proven in DIA's Multi-Oracle Adapter product for immutable lending markets, is that oracle resilience has to be designed in at deployment time: a consuming application should read from a stable adapter interface, while the adapter manages provider diversity, source validation, and failure handling behind that interface.
How It Works on LEZ: The adapter separates two concepts:
Price Source: the underlying authority or method for price truth, such as DIA's first-party exchange-sourced data today, or another provider's data in the future.
Price Transporter: the delivery mechanism that brings a given source's price on-chain.
The adapter accepts price updates only from whitelisted proposers, validates freshness, source identity, transporter identity, and value bounds before accepting a new answer, and compares provider values to reject updates that diverge beyond a configured threshold. Consuming applications read the adapter as a single stable interface and are not exposed to which specific source is live behind it at a given moment.
The same adapter is also designed to be able to read the on-chain TWAP tier from RFP-019 as one of its sources where pool liquidity and volume are sufficient to make it a robust input, adding a third layer of redundancy beyond DIA and any future external provider.
Removing Friction, Not Just for RedStone: Adding a new oracle to LEZ would otherwise mean every consuming application individually integrating, auditing, and trusting that specific provider. With the multi-oracle adapter in place, onboarding a new source is a configuration change, a provider add, disable, or replacement, through a defined admin path, not a rebuild and not a migration for every application already live on the network. This is what actually reduces vendor lock-in, more than a single-source integration ever could: it means LEZ can add RedStone, or any other oracle, the moment that provider's data-usage rights are confirmed by whoever operates the connector, without touching the applications already built on top of DIA's feed. If DIA, Logos, or any LEZ ecosystem team secure those rights directly in the future, RedStone's or any other oracle provider's feeds can be delivered to the network through this same adapter, activated, not rebuilt.
3.3 Technical Scope
On LEZ, this proposal delivers:
1. Push-Mode Oracle Aggregator: A public-mode LEZ program that validates DIA price updates against configurable feeder-threshold, freshness, and value-bound requirements before publishing accepted prices to a canonical public price account.
2. Public-Mode Pull Verification: A reusable verification path that allows a public consumer program to validate and consume a DIA price update directly within its own transaction, without relying on the shared aggregator account.
3. Canonical Price Account Integration: Price data published using the canonical LEZ oracle account structure defined under RFP-019, ensuring compatibility with downstream applications and future oracle providers.
4. Relayer and Operator Infrastructure: A relayer delivered both as a Logos module and as a standalone headless service, including configuration, monitoring, retry handling, and complete operator documentation covering installation, setup, and ongoing operation.
5. Administration and SPEL Integration: Integration with the RFP-001 administrative-authority model through SPEL, enabling authorised registration, modification, and removal of supported price sources.
6. SPEL Framework Enhancement: An extension to the SPEL framework that enables new LEZ programs to integrate DIA feeds through either push- or pull-based consumption patterns.
7. Developer Interfaces: An IDL for the adaptor program and the canonical price account standard, defining the interfaces required for applications to submit, verify, and consume DIA price updates.
8. Developer Tooling: An SDK covering both push and pull modes, a CLI for submitting updates, querying prices, and managing feed registration, two reference consumer programs demonstrating aggregator-read and public-mode pull integration patterns, and a mini-app dashboard, with Figma designs, for monitoring feed status and testing the pull verification path without an on-chain transaction.
9. Initial Feed Deployment: BTC/USD, ETH/USD, SOL/USD, XMR/USD, and ZEC/USD feeds deployed and operational on LEZ devnet/testnet, sourced through DIA's first-party data infrastructure.
10. Performance and Cost Benchmarking: Measurement of the complete in-program RISC-V verification path for both push and public pull modes, including compute usage, proof-generation time, proof size, and per-update or per-read cost. Benchmarking begins alongside implementation rather than being deferred until the end of development.
4. Impact
Multiple independent oracle sources materially reduce the risk that a single provider's downtime, censorship, or compromise degrades or halts a LEZ consumer protocol. This is the production norm in DeFi oracle design, and it is exactly the layering RFP-020 already endorses between off-chain feeds and on-chain TWAP. DIA's proposal delivers that first layer live on day one, covering all five day-one assets (BTC, ETH, SOL, XMR, and ZEC), and builds the Multi-Oracle Adapter to enable additional independent sources to be added without re-architecting anything. This is especially critical for XMR and ZEC, the two assets that matter most to LEZ's privacy-DeFi thesis and that have no TWAP fallback on a new chain.
Concretely, this proposal is a direct enabler for:
- RFP-013 (reflexive stablecoin) and RFP-004 (privacy-preserving DEX), both of which RFP-020 itself identifies as needing these reference prices to function.
- Any consumer protocol on LEZ that wants a bounded, canonical price for BTC, ETH, SOL, XMR, or ZEC without the network being structurally locked to any single oracle provider as an unmitigated single point of failure.
Milestones, Payout and Timeline
Milestones, Payout, SLA, and Timeline
Total Requested Budget: $230,000, including the third-party audit.
Consistent with DIA's standard structure for grant-funded oracle integrations:
One-time deployment fee: Covers software delivery, including the Section 3.3 deliverables, plus two years of operating the feed infrastructure under the SLA proposed below.
Service agreement thereafter: Covers continued operation of the feeds beyond the initial two-year window, consistent with RFP-020's servicing period running through March 2028.
Budget Summary
| Component |
Amount |
| Software delivery (Milestones M1–M5) |
$75,000 |
| Third-party audit (Milestone M6) |
$45,000 |
| Operating period, Year 1 |
$55,000 |
| Operating period, Year 2 |
$55,000 |
| Total |
$230,000 |
Milestone Breakdown
M1: Core Verification and Push-Mode Aggregator
Payout: $26,000
Duration: 2.5 weeks
Scope: In-program verification path for DIA's push-mode aggregator, publishing prices that meet DIA's configurable m-of-N feeder threshold; RFP-019 canonical price account write; SPEL framework enhancement to hook push and pull feed modes into new programs; IDL for the adapter program and canonical price account; admin authority integration under RFP-001/SPEL for feed and source registration; commencement of cost-measurement instrumentation, carried throughout the build; and unit and integration tests for push mode.
M2: Public-Mode Pull Verification Library
Payout: $13,000
Duration: 1.5 weeks
Scope: Shared verifier exposed as a reusable library callable from third-party consumer programs; consumer-supplied signer-set and configuration handling, never sourced from the payload; both reference consumer programs, covering aggregator-read and public-mode pull; and unit and integration tests for pull mode.
M3: DIA Oracle Integration, Relayer, and SDK/CLI
Payout: $15,000
Duration: 1.5 weeks
Scope: Integration of DIA's first-party price infrastructure as the live day-one source through the push aggregator; relayer packaged as both a Logos module and a standalone background service, with operator setup documentation covering installation, configuration, operation, and monitoring; SDK covering both modes; CLI supporting submit, query, register, deregister, and dry-run functionality; and day-one BTC, ETH, SOL, XMR, and ZEC feed registration on devnet/testnet.
M4: Multi-Oracle Adapter Extension and Dashboard
Payout: $10,000
Duration: 1 week
Scope: On-chain account structure for storing each price source's data; admin-registration path for adding pluggable additional price sources; quorum and deviation-based consensus logic; mini-app dashboard, including a panel that allows an operator to test and verify a signed price payload without submitting an on-chain transaction; and Figma designs.
M5: Cost Measurement Analysis, End-to-End Testing, and Documentation
Payout: $11,000
Duration: 1.5 weeks
Scope: Cost-measurement analysis and reporting, including per-mode compute units, RISC0 proof time and size, comparison against published EVM oracle-connector gas ranges, and a precompile-delta write-up; end-to-end integration tests against a LEZ sequencer, with green CI on the default branch; README documentation; SDK documentation packet; and CLI documentation packet.
M6: Third-Party Security Audit
Payout: $45,000
Duration: 2 weeks
Scope: Independent security audit of the push-mode aggregator program, public-mode pull verification library, and Multi-Oracle Adapter logic as deployed on LEZ, followed by remediation of any findings prior to mainnet deployment. The audit may be contracted by DIA as a pass-through expense or contracted directly by Logos.
Operating Period, Year 1
Payout: $55,000
Duration: 12 months, beginning at software readiness following completion of M6 and the third-party audit.
Operating Period, Year 2
Payout: $55,000
Duration: 12 months
The operating period will run through March 2028 at minimum, representing one year beyond the planned LEZ mainnet launch under RFP-020. Continued operation beyond the initial two-year window will be covered through a subsequent service agreement.
Proposed SLA Targets
| Parameter |
Target |
| Feed availability |
99.9% monthly |
| Heartbeat |
1 hour for BTC, ETH, SOL, XMR, and ZEC, widened only where an asset cannot economically sustain that cadence |
| Deviation threshold |
0.5% for the day-one pairs |
| Incident response |
Acknowledge within 1 hour; mitigate within 4 hours; named on-call contact (Samuel Brack, Cofounder; CTO); root-cause summary following any SLA breach |
| Reporting |
Monthly operating reports covering uptime, cadence adherence, update and rejection counts, incidents, and wallet-funding status, plus live dashboard read access for the Logos ecosystem team |
Total Requested Budget (USD)
$230,000
Relevant Experience
Proven Track Record: DIA was founded in 2018, and has a proven track record of deploying decentralized oracle infrastructure across diverse blockchain environments since its product launch in 2020. The DIA team's core mission has been to expand cross-chain oracle access and empower developers to build secure, data-driven dApps. Today, DIA is live across 65+ Layer 1 and Layer 2 blockchains, with 100+ data sources integrated and 250+ dApps powered by DIA, including markets on Morpho, Euler, and Silo, serving as a critical data layer for some of the most innovative ecosystems and applications in Web3. For the full ecosystem of protocols built on DIA, see https://www.diadata.org/ecosystem/.
Team Expertise: The DIA team combines deep expertise in smart contract development, blockchain infrastructure, and data engineering. Since 2018, DIA has built robust oracle solutions including:
- Customizable Token Price Feeds (2,500+ crypto assets)
- RWA and Traditional Finance Data Feeds (5,000+ assets)
- Net Asset Value Price Feeds for Vault Tokens
- Liquid Staked Token feeds & Contract Exchange-Rate Price Feeds
- NFT Floor Price Oracles
- Randomness Oracles (RNG)
Trust, Accountability & Transparency: DIA's architecture is fully open-source and 100% transparent at the data source level. All data is aggregated directly from first-party exchanges (DEXs and CEXs) using open scrapers and transparent methodologies, ensuring developers and users can audit every feed. This commitment to verifiability and openness ensures the highest levels of trust and accountability.
Relevant Resources and Links to Shipped Products GithHub Repositories:
- DIA Documentation
- DIA Core Data & Oracle Platform
- Spectra Interoperability
- PushOracleReceiverV2.sol
- RequestOracle.sol
- ProtocolFeeHook.sol
- OracleTriggerV2.sol
- Lumina Decentralized Feeder
- Lumina Feeder Library
- Fair-Value Feeder
- DIA Oracle Monitoring
Integration Repositories on Non-EVM Chains:
- DIA Cardano Oracle
- DIA Soroban Oracles
- DIA NEAR Oracle
- DIA Kadena Oracle
- DIA WASM Oracle
- DIA Substrate Oracle Pallet
- DIA Oracle Integration Library
Post-Delivery Plan
DIA will operate, monitor, and maintain the oracle feeds on LEZ for two years from the start of the operating period, under the SLA targets proposed in this submission. A service agreement will be available to continue operations beyond the initial two-year term.
Protocols building on Logos that require custom oracle feeds can contact DIA directly through its existing support channels, including Discord, Telegram, and direct Telegram or Slack groups with the DIA team.
DIA will also establish a dedicated support channel with the Logos team, through Slack or Telegram, to manage:
- Ongoing technical and operational support
- Custom oracle deployment requests
- Additional asset price feed requests
- Incident response in accordance with the thresholds defined in the Proposed SLA Targets
Primary Points of Contact
-
Samuel Brack — Cofounder and CTO
Primary point of contact during the technical integration for architecture, implementation, and specification-related questions.
-
David D'Amario — QA Lead
Primary operational contact for feed monitoring, alert management, incident triage, and coordinating response and remediation in accordance with the committed SLA thresholds.
-
Dillon Hanson — Head of Business Development
Primary contact for additional asset and oracle requests.
-
Josh Bellerive — Business Development Manager
Secondary contact for additional asset and oracle requests.
DIA is open to establishing additional ecosystem support channels as needed, including a dedicated support channel in the Logos Discord for DIA Oracle inquiries or participation in Logos ecosystem Telegram groups, to provide superior support for the Logos team and its ecosystem builders.
On behalf of DIA, we are committed to the Logos Ecosystem for the long term, and very much keen to play a supporting role in the growth of the ecosystem for all years to come.
Permissions and Consent
Program Requirements
RFP ID
RFP-020 — RedStone Off-Chain Oracle Adaptor for LEZ
Your Project Name
Multi-Oracle Adapter for LEZ
Team or Organization Name
DIA Oracles
Primary Contact
Dillon Hanson - dillon.hanson@diadata.org ; TG: @DIABDteam
Team Members
Product and Engineering:
Name: Samuel Brack
Social links: Github // LinkedIn
Role: Cofounder; CTO
Status: Full-time
Name: Philipp Pade
Social links: Github // LinkedIn
Role: Lead Integrations Developer
Status: Full-time
Name: Nitin Gurbani
Social links: Github // LinkedIn
Role: Senior Developer
Status: Full-time
Name: Zygis Marazas
Social links: LinkedIn
Role: Product Lead
Status: Full-time
Name: David D'Amario
Social links: LinkedIn
Role: QA Lead
Status: Full-time
Name: Arounen Murdhen
Social links: LinkedIn
Role: Technical Product Manager
Status: Full-time
Business Development
Name: Paul Claudius
Social links: LinkedIn
Role: Cofounder; CBO
Status: Full-time
Name: Dillon Hanson
Social links: LinkedIn
Role: Head of Business Development — primary point of contact with Logos
Status: Full-time
Name: Josh Bellerive
Social links: LinkedIn
Role: Business Development Manager
Status: Full-time
Marketing & Community
Name: Carl Bruns
Social links: LinkedIn
Role: Cofounder; CMO
Status: Full-time
Name: Mikel Garcia
Social links: LinkedIn
Role: Head of Marketing
Status: Full-time
Name: Anze Noc
Social links: LinkedIn
Role: Community Lead
Status: Full-time
Project Summary
DIA's take on the RF:
This proposal delivers a production-grade oracle on LEZ from day one, together with the architecture to scale it: DIA’s Multi-Oracle Adapter. The adapter enables additional independent oracle providers to be added over time without re-architecting the underlying integration, once their feeds are live on LEZ and the necessary data-usage rights are confirmed by their respective operators.
This Proposal Has Two Parts:
First, DIA: live, first-party-sourced oracle price feeds for BTC/USD, ETH/USD, SOL/USD, XMR/USD, and ZEC/USD, backed by DIA's production track record since 2020, with no third-party data-rights dependency attached to that initial delivery.
Second, the Multi-Oracle Adapter: the extensibility layer that enables LEZ to onboard additional oracle providers over time, on demand, once each provider's data-usage rights are confirmed by the party operating that connector, rather than locking the network to a single vendor from the outset.
No third party other than RedStone itself can assert the right to redistribute RedStone's data today, and RFP-020 itself does not resolve that question in advance. What DIA can deliver with certainty, and commit to operating under SLA, is production-grade oracle infrastructure live on day one, on an architecture that removes single-vendor lock-in from LEZ's oracle layer permanently, not just for this integration.
Why it Matters:
LEZ's privacy-DeFi thesis depends on reliable USD reference prices for privacy collateral, namely Monero (XMR) and Zcash (ZEC), to make the reflexive stablecoin (RFP-013), the privacy-preserving DEX (RFP-004), wrapped privacy assets, and other cross-chain primitives function. The on-chain TWAP tier in RFP-019 cannot carry this alone: DEX TWAP security scales with pool depth, which is thin on a new chain, and a DEX TWAP oracle only produces a price for pairs that exist as LEZ pools at all. An external price feed is required to get any XMR/USD or ZEC/USD reference on chain at all.
Whichever oracle source a network relies on, a single provider is a single point of failure, both for liveness (DNS, TLS, and regional hosting availability all become dependencies) and for governance (the network is structurally locked to one vendor's terms, pricing, and roadmap). DIA's proposal addresses both halves of that problem directly: it puts live, first-party-sourced oracle price feeds on LEZ from day one with no third-party terms-of-use dependency attached to that initial delivery, and it builds the adapter layer so that LEZ is never architecturally locked to a single source, regardless of which additional providers become available on LEZ later.
Technical Approach
2. Solution
2.1 DIA: Live From Day One
DIA is an established, production-grade oracle network, deployed as LEZ's day-one price source with no third-party data-rights dependency attached to that delivery.
DIA is a cross-chain oracle provider focused on data transparency, customization, and accessibility. Unlike traditional oracles that rely on opaque third-party data aggregators, DIA sources raw trade data directly from 100+ centralized and decentralized exchanges. This first-party sourcing approach ensures 100% transparency at the exchange level, eliminating black boxes and providing verifiability for developers and users alike.
With This Architecture, DIA Delivers:
How DIA Works: DIA's modular architecture consists of three core layers:
Data Sourcing: Collect real-time data from decentralized exchanges (DEXs), centralized exchanges (CEXs), and other sources through DIA's decentralized Feeders Network. This decentralized network of nodes ensures that data is accurate, timely, and sourced directly from the market.
Data Computation: Process and verify the collected data on-chain, using open source Pods and Aggregators smart contracts within the DIA Lumina infrastructure.
Publication: Publish verified prices directly on-chain via the LEZ program described in this proposal (Section 3.3), with no external bridge or cross-chain messaging dependency for this deployment.
This system is further supported by a robust monitoring framework, ensuring data accuracy, uptime, and resilience through node redundancy. For a breakdown of each component, please visit: https://www.diadata.org/docs/reference/architecture.
Capabilities & Feasibility: DIA oracles are deployed across leading chains including Ethereum, Arbitrum, Polygon, Optimism, Near, Avalanche, Base, and BNB Chain, and many more. Importantly, DIA is not limited to EVM-compatible chains and has a proven track record of successful deployments on non-EVM environments (such as XRPL, Stacks, Soroban Network, Cardano, Midnight Network, Near, Solana, Alephium, Aleph Zero, Astar-WASM, Vara, and more), demonstrating the ability to adapt and successfully implement DIA oracles on networks with different technical architectures.
For LEZ specifically, this means BTC/USD, ETH/USD, SOL/USD, XMR/USD, and ZEC/USD go live on devnet/testnet using proven, battle-tested first-party oracle infrastructure, not a net-new build. No third party other than RedStone itself can assert the right to redistribute RedStone's signed data today. DIA's commitment in this proposal is to what it can deliver with certainty: a live, production oracle, operating under SLA, from day one.
DIA oracles will be deployed on Logos Network via smart contract. The smart contract is a key/value store and contains two values per asset, the timestamp of the last update and the value of the asset price. The asset price is stored with 18 decimals by default.
2.2 Multi-Oracle Adapter: Built for Growth
The Multi-Oracle Adapter is the mechanism that keeps LEZ from ever being locked to a single oracle provider, including DIA.
The Single-Provider Lock-In Problem: Once an oracle-dependent program is deployed, the oracle path can be difficult or impossible to change. If LEZ's price infrastructure depends on a single provider, that provider becomes a permanent operational dependency rather than a replaceable infrastructure component. The core insight, already proven in DIA's Multi-Oracle Adapter product for immutable lending markets, is that oracle resilience has to be designed in at deployment time: a consuming application should read from a stable adapter interface, while the adapter manages provider diversity, source validation, and failure handling behind that interface.
How It Works on LEZ: The adapter separates two concepts:
Price Source: the underlying authority or method for price truth, such as DIA's first-party exchange-sourced data today, or another provider's data in the future.
Price Transporter: the delivery mechanism that brings a given source's price on-chain.
The adapter accepts price updates only from whitelisted proposers, validates freshness, source identity, transporter identity, and value bounds before accepting a new answer, and compares provider values to reject updates that diverge beyond a configured threshold. Consuming applications read the adapter as a single stable interface and are not exposed to which specific source is live behind it at a given moment.
The same adapter is also designed to be able to read the on-chain TWAP tier from RFP-019 as one of its sources where pool liquidity and volume are sufficient to make it a robust input, adding a third layer of redundancy beyond DIA and any future external provider.
Removing Friction, Not Just for RedStone: Adding a new oracle to LEZ would otherwise mean every consuming application individually integrating, auditing, and trusting that specific provider. With the multi-oracle adapter in place, onboarding a new source is a configuration change, a provider add, disable, or replacement, through a defined admin path, not a rebuild and not a migration for every application already live on the network. This is what actually reduces vendor lock-in, more than a single-source integration ever could: it means LEZ can add RedStone, or any other oracle, the moment that provider's data-usage rights are confirmed by whoever operates the connector, without touching the applications already built on top of DIA's feed. If DIA, Logos, or any LEZ ecosystem team secure those rights directly in the future, RedStone's or any other oracle provider's feeds can be delivered to the network through this same adapter, activated, not rebuilt.
3.3 Technical Scope
On LEZ, this proposal delivers:
1. Push-Mode Oracle Aggregator: A public-mode LEZ program that validates DIA price updates against configurable feeder-threshold, freshness, and value-bound requirements before publishing accepted prices to a canonical public price account.
2. Public-Mode Pull Verification: A reusable verification path that allows a public consumer program to validate and consume a DIA price update directly within its own transaction, without relying on the shared aggregator account.
3. Canonical Price Account Integration: Price data published using the canonical LEZ oracle account structure defined under RFP-019, ensuring compatibility with downstream applications and future oracle providers.
4. Relayer and Operator Infrastructure: A relayer delivered both as a Logos module and as a standalone headless service, including configuration, monitoring, retry handling, and complete operator documentation covering installation, setup, and ongoing operation.
5. Administration and SPEL Integration: Integration with the RFP-001 administrative-authority model through SPEL, enabling authorised registration, modification, and removal of supported price sources.
6. SPEL Framework Enhancement: An extension to the SPEL framework that enables new LEZ programs to integrate DIA feeds through either push- or pull-based consumption patterns.
7. Developer Interfaces: An IDL for the adaptor program and the canonical price account standard, defining the interfaces required for applications to submit, verify, and consume DIA price updates.
8. Developer Tooling: An SDK covering both push and pull modes, a CLI for submitting updates, querying prices, and managing feed registration, two reference consumer programs demonstrating aggregator-read and public-mode pull integration patterns, and a mini-app dashboard, with Figma designs, for monitoring feed status and testing the pull verification path without an on-chain transaction.
9. Initial Feed Deployment: BTC/USD, ETH/USD, SOL/USD, XMR/USD, and ZEC/USD feeds deployed and operational on LEZ devnet/testnet, sourced through DIA's first-party data infrastructure.
10. Performance and Cost Benchmarking: Measurement of the complete in-program RISC-V verification path for both push and public pull modes, including compute usage, proof-generation time, proof size, and per-update or per-read cost. Benchmarking begins alongside implementation rather than being deferred until the end of development.
4. Impact
Multiple independent oracle sources materially reduce the risk that a single provider's downtime, censorship, or compromise degrades or halts a LEZ consumer protocol. This is the production norm in DeFi oracle design, and it is exactly the layering RFP-020 already endorses between off-chain feeds and on-chain TWAP. DIA's proposal delivers that first layer live on day one, covering all five day-one assets (BTC, ETH, SOL, XMR, and ZEC), and builds the Multi-Oracle Adapter to enable additional independent sources to be added without re-architecting anything. This is especially critical for XMR and ZEC, the two assets that matter most to LEZ's privacy-DeFi thesis and that have no TWAP fallback on a new chain.
Concretely, this proposal is a direct enabler for:
Milestones, Payout and Timeline
Milestones, Payout, SLA, and Timeline
Total Requested Budget: $230,000, including the third-party audit.
Consistent with DIA's standard structure for grant-funded oracle integrations:
One-time deployment fee: Covers software delivery, including the Section 3.3 deliverables, plus two years of operating the feed infrastructure under the SLA proposed below.
Service agreement thereafter: Covers continued operation of the feeds beyond the initial two-year window, consistent with RFP-020's servicing period running through March 2028.
Budget Summary
Milestone Breakdown
M1: Core Verification and Push-Mode Aggregator
Payout: $26,000
Duration: 2.5 weeks
Scope: In-program verification path for DIA's push-mode aggregator, publishing prices that meet DIA's configurable m-of-N feeder threshold; RFP-019 canonical price account write; SPEL framework enhancement to hook push and pull feed modes into new programs; IDL for the adapter program and canonical price account; admin authority integration under RFP-001/SPEL for feed and source registration; commencement of cost-measurement instrumentation, carried throughout the build; and unit and integration tests for push mode.
M2: Public-Mode Pull Verification Library
Payout: $13,000
Duration: 1.5 weeks
Scope: Shared verifier exposed as a reusable library callable from third-party consumer programs; consumer-supplied signer-set and configuration handling, never sourced from the payload; both reference consumer programs, covering aggregator-read and public-mode pull; and unit and integration tests for pull mode.
M3: DIA Oracle Integration, Relayer, and SDK/CLI
Payout: $15,000
Duration: 1.5 weeks
Scope: Integration of DIA's first-party price infrastructure as the live day-one source through the push aggregator; relayer packaged as both a Logos module and a standalone background service, with operator setup documentation covering installation, configuration, operation, and monitoring; SDK covering both modes; CLI supporting submit, query, register, deregister, and dry-run functionality; and day-one BTC, ETH, SOL, XMR, and ZEC feed registration on devnet/testnet.
M4: Multi-Oracle Adapter Extension and Dashboard
Payout: $10,000
Duration: 1 week
Scope: On-chain account structure for storing each price source's data; admin-registration path for adding pluggable additional price sources; quorum and deviation-based consensus logic; mini-app dashboard, including a panel that allows an operator to test and verify a signed price payload without submitting an on-chain transaction; and Figma designs.
M5: Cost Measurement Analysis, End-to-End Testing, and Documentation
Payout: $11,000
Duration: 1.5 weeks
Scope: Cost-measurement analysis and reporting, including per-mode compute units, RISC0 proof time and size, comparison against published EVM oracle-connector gas ranges, and a precompile-delta write-up; end-to-end integration tests against a LEZ sequencer, with green CI on the default branch; README documentation; SDK documentation packet; and CLI documentation packet.
M6: Third-Party Security Audit
Payout: $45,000
Duration: 2 weeks
Scope: Independent security audit of the push-mode aggregator program, public-mode pull verification library, and Multi-Oracle Adapter logic as deployed on LEZ, followed by remediation of any findings prior to mainnet deployment. The audit may be contracted by DIA as a pass-through expense or contracted directly by Logos.
Operating Period, Year 1
Payout: $55,000
Duration: 12 months, beginning at software readiness following completion of M6 and the third-party audit.
Operating Period, Year 2
Payout: $55,000
Duration: 12 months
The operating period will run through March 2028 at minimum, representing one year beyond the planned LEZ mainnet launch under RFP-020. Continued operation beyond the initial two-year window will be covered through a subsequent service agreement.
Proposed SLA Targets
Total Requested Budget (USD)
$230,000
Relevant Experience
Proven Track Record: DIA was founded in 2018, and has a proven track record of deploying decentralized oracle infrastructure across diverse blockchain environments since its product launch in 2020. The DIA team's core mission has been to expand cross-chain oracle access and empower developers to build secure, data-driven dApps. Today, DIA is live across 65+ Layer 1 and Layer 2 blockchains, with 100+ data sources integrated and 250+ dApps powered by DIA, including markets on Morpho, Euler, and Silo, serving as a critical data layer for some of the most innovative ecosystems and applications in Web3. For the full ecosystem of protocols built on DIA, see https://www.diadata.org/ecosystem/.
Team Expertise: The DIA team combines deep expertise in smart contract development, blockchain infrastructure, and data engineering. Since 2018, DIA has built robust oracle solutions including:
Trust, Accountability & Transparency: DIA's architecture is fully open-source and 100% transparent at the data source level. All data is aggregated directly from first-party exchanges (DEXs and CEXs) using open scrapers and transparent methodologies, ensuring developers and users can audit every feed. This commitment to verifiability and openness ensures the highest levels of trust and accountability.
Relevant Resources and Links to Shipped Products GithHub Repositories:
Integration Repositories on Non-EVM Chains:
Post-Delivery Plan
DIA will operate, monitor, and maintain the oracle feeds on LEZ for two years from the start of the operating period, under the SLA targets proposed in this submission. A service agreement will be available to continue operations beyond the initial two-year term.
Protocols building on Logos that require custom oracle feeds can contact DIA directly through its existing support channels, including Discord, Telegram, and direct Telegram or Slack groups with the DIA team.
DIA will also establish a dedicated support channel with the Logos team, through Slack or Telegram, to manage:
Primary Points of Contact
Samuel Brack — Cofounder and CTO
Primary point of contact during the technical integration for architecture, implementation, and specification-related questions.
David D'Amario — QA Lead
Primary operational contact for feed monitoring, alert management, incident triage, and coordinating response and remediation in accordance with the committed SLA thresholds.
Dillon Hanson — Head of Business Development
Primary contact for additional asset and oracle requests.
Josh Bellerive — Business Development Manager
Secondary contact for additional asset and oracle requests.
DIA is open to establishing additional ecosystem support channels as needed, including a dedicated support channel in the Logos Discord for DIA Oracle inquiries or participation in Logos ecosystem Telegram groups, to provide superior support for the Logos team and its ecosystem builders.
On behalf of DIA, we are committed to the Logos Ecosystem for the long term, and very much keen to play a supporting role in the growth of the ecosystem for all years to come.
Permissions and Consent
Program Requirements