ADA Unleashed: Trustless Gateway to Multi-Chain Power

[Proposal setup] Proposal title

Please provide your proposal title

ADA Unleashed: Trustless Gateway to Multi-Chain Power

[Proposal Summary] Budget Information

Enter the amount of funding you are requesting in ADA

183000

[Proposal Summary] Time

Please specify how many months you expect your project to last

10

[Proposal Summary] Problem Statement

What is the problem you want to solve?

ADA liquidity remains mostly locked on Cardano, complex dApps face scaling limits, and cross-chain use is minimal—creating barriers to broader utility, developer growth, and ecosystem adoption.

[Proposal Summary] Supporting Documentation

Supporting links

• https://docs.google.com/document/d/1OXT-OWHNqlsEpi9wvLKNGy45WGBFYKhvTR8gZtgeD20/edit?usp=sharing
,
• https://docs.google.com/document/d/1vFoqYB3Ix1gJYHesvgHGFTf_Wi7nlH_asrysz7GsTI8/edit?usp=sharing

[Proposal Summary] Project Dependencies

Does your project have any dependencies on other organizations, technical or otherwise?

Yes

Describe any dependencies or write 'No dependencies'

ICP Chain Fusion Technology

[Proposal Summary] Project Open Source

Will your project's outputs be fully open source?

Yes

Please provide details on the intellectual property (IP) status of your project outputs, including whether they will be released as open source or retained under another licence.

The project outputs (software and documentation) will be released as open source under the MIT License. All new IP generated will be owned by our organization but will be publicly available via a GitHub repository.

[Theme Selection] Theme

Please choose the most relevant theme and tag related to the outcomes of your proposal

Cross-chain

[Campaign Category] Category Questions

Describe what makes your idea innovative compared to what has been previously launched in the market (whether by you or others).

Our Cardano RPC Canister pioneers a trustless, Cardano-initiated cross-chain execution layer that extends ADA’s utility without moving, wrapping, or custodizing assets. Unlike existing bridges and oracle networks—which often force users to exit Cardano, rely on trusted intermediaries, or transfer value off-chain—this architecture is entirely new to the Cardano ecosystem.

Key Differentiators:

1. Trustless Execution, Not Asset Bridging: Custodial bridges (e.g., Wanchain) and ZK systems (e.g., BitcoinOS) move assets. We enable Plutus scripts to trigger heavy computation, real-time data, or cross-chain actions while ADA remains fully on Cardano. Prior ICP experiments were ICP-led; ours is Cardano-triggered, Plutus-validated, and Cardano-sovereign.
2. Cardano-First Satellite Compute: Most interoperability tools (e.g., Chainlink committees) center external chains or introduce centralization. We position ICP as a fully Cardano-controlled compute satellite—users need zero ICP tokens or knowledge—delivering seamless alignment with Cardano’s ethos, unlike custody-heavy models (e.g., eBTC).
3. Decentralized Web-Speed Compute Without Oracles: Solutions like Orcfax rely on node committees. Our WASM-based ICP canisters deliver replicated, tamper-proof execution at web speed with no operators, uniquely extending Cardano’s eUTXO model across chains.
4. Zero Protocol Changes – Live Today: No forks or custom middleware required. It works with existing CIP-30, on-chain metadata, Koios/Blockfrost APIs, and standard Plutus tooling—dramatically lowering risk and enabling immediate adoption of bridgeless DeFi, PRISM integrations, and cross-chain oracles.

Why This Is Truly Novel

We shift the paradigm from cross-chain custody to cross-chain compute, transforming Cardano into a trustless multi-chain hub without exposing ADA to wrap risk, bridge custodians, or added trust assumptions.

Describe what your prototype or MVP will demonstrate, and where it can be accessed.

The MVP delivers a complete end-to-end, Cardano-initiated cross-chain round trip using a real Plutus script and live ICP canister on Cardano Preprod Testnet.

What It Demonstrates

• A CIP-30 wallet signs an ADA transaction → triggers the Cardano RPC Canister on ICP → the canister performs real-time computation (e.g., price fetch, API call, or EVM interaction) → verified result returns to Cardano as metadata or validator response.
• ADA never leaves Cardano—no bridging, wrapping, or custody.

Core Proof Points

• Full Cardano → ICP → Cardano execution triggered solely by an ADA transaction
• Real-time off-chain capabilities while preserving Cardano-first principles
• Verifiable on-chain results and reusable developer primitive

Public Access

• Open-source GitHub repo (Plutus contracts, Rust canisters, integration scripts, full docs)
• Live ICP canister endpoint for direct testing
• Browser-based Preprod dApp compatible with any CIP-30 wallet (Eternl, Lace, etc.)
• Step-by-step demo video of the entire flow

Describe realistic measures of success, ideally with on-chain metrics.

Metrics are phased and verifiable via Cardano explorers, with targets benchmarked against early Cardano tools (e.g., Orcfax ~1,000 daily queries post-launch).

Primary On-Chain KPIs

• Transactions triggering RPC calls: ≥100 (testnet Phase 1) → 500–3,000 in first 90 days of mainnet beta
• Unique interacting addresses: ≥50 (testnet) → ≥200 (mainnet)
• Integrating Plutus scripts/dApps: ≥1 (testnet) → ≥3 (mainnet)
• Successful round-trip result transactions: ≥40 (testnet) → ≥200 (mainnet)
• ADA locked in using scripts (TVL signal): 5,000–20,000 ADA

Performance Targets

• Full round-trip latency: ≤10 seconds
• Request success rate: ≥98 %

Even 50–70 % of targets under bearish conditions still validates a functional, adopted prototype.

[Your Project and Solution] Solution

Please describe your proposed solution and how it addresses the problem

The Cardano RPC Canister is a trustless execution layer on ICP that extends Cardano’s capabilities while keeping users and ADA entirely within the ecosystem.

How It Works

A Cardano transaction or Plutus script sends a request (via CIP-30/metadata). The ICP canister performs off-chain tasks—real-time data, heavy compute, or cross-chain calls—and returns cryptographically verified results. No assets ever leave Cardano; the canister never holds funds.

Problems Solved

• Unlocks dormant ADA liquidity for multi-chain yields without custodial risk
• Enables complex, high-frequency dApps by offloading compute to ICP’s web-speed layer
• Breaks cross-chain silos while users stay in Cardano wallets and pay only ADA fees
• Fully aligns with Cardano’s decentralization and research-driven principles

One-Sentence Summary

A Cardano-initiated, trustless gateway that delivers cross-chain functionality and advanced computation without compromising security, custody, or sovereignty.

[Your Project and Solution] Impact

Please define the positive impact your project will have on the wider Cardano community

• Drives on-chain transaction volume and fee revenue (benefiting SPOs)
• Increases ADA utility and TVL by enabling safe multi-chain DeFi and RWAs
• Unlocks new dApp categories (hybrid oracles, PRISM integrations, cross-ledger governance)
• Eliminates bridge hacks and custody risk—strengthening Cardano’s security reputation
• Positions Cardano as the secure hub asset in a multi-chain world
• Provides open, auditable tools that strengthen Catalyst and community governance

[Your Project and Solution] Capabilities & Feasibility

What is your capability to deliver your project with high levels of trust and accountability? How do you intend to validate if your approach is feasible?

Proven Cardano Plutus Pioneers + ICP canister engineers with shipped, audited contracts across Cardano, Ethereum, ICP, and Move chains.

Trust & Accountability

• 100 % open-source from day one with community audits
• No custody of ADA → minimized risk surface
• Monthly Catalyst milestones, videos, and public test endpoints

Phased Validation

• 1–3 months: Live testnet POC with <10 s round trips
• 4–6 months: Restricted mainnet beta + >98 % success rate
• Pre-full launch: Professional audit + community governance handover

We deliver with transparency, proven execution, and direct alignment to Cardano’s ethos.

[Milestones] Project Milestones

Milestone Title

Research, Architecture Design & Foundational Prototype Development

Milestone Outputs

During this phase, we complete all foundational research required to build a robust, production-ready Cardano–ICP integration layer. This includes validating ICP’s newly introduced Ed25519 threshold signing API, determining the appropriate Cardano data providers, and designing the transaction-composition strategy for the RPC canister.

We will experiment on an ICP development subnet to retrieve the canister’s Ed25519 public key, generate signatures, and verify them off-chain to confirm correct behavior and latency.

In parallel, we explore Cardano testnet connectivity by running a local node and testing REST endpoints such as fetching UTXOs, latest blocks, and submitting trial transactions. We compare Koios and alternative APIs for reliability and data completeness and select one as the primary development provider.

Finally, we design the transaction-composition workflow and prototype a minimal Rust script capable of producing a valid unsigned Cardano transaction. This establishes the architecture and serialization format needed for full canister-side implementation.

Acceptance Criteria

• A functioning Rust canister that calls ICP Management APIs to retrieve the canister’s Ed25519 public key and produce a signature over a test message. The signature must verify correctly using known off-chain tools.

• Successful communication with the Cardano testnet using a locally hosted node or Koios API, with demonstrated ability to retrieve UTXOs, latest block data, and sample metadata.

• A documented decision on which Cardano data API (Koios or alternative) to adopt, with justification based on reliability and completeness.

• A prototype Rust test that constructs a syntactically valid unsigned Cardano transaction (hex-encoded) from dummy inputs, validated using an external serialization/inspection tool.

• All research findings and architectural decisions captured in a technical design document to support future milestones.

Evidence of Completion

• GitHub repository containing the canister prototype demonstrating Ed25519 key retrieval and message signing.

• Screenshots and logs of Cardano testnet queries showing UTXO retrieval and block data.

• A documented comparison of Cardano API providers with the selected option highlighted.

• Rust code and output confirming generation of a valid unsigned transaction verified via external Cardano tools.

• A finalized Research & Architecture Design document uploaded to the repository.

Delivery Month

2

Cost

36600

Progress

20 %

Milestone Title

Cardano RPC Canister: Read-Only Queries & Address Derivation

Milestone Outputs

In this phase, we implement the first functional version of the Cardano RPC canister focused on read-only operations and address generation. We initialize a Rust-based canister configured for HTTPS outcalls and verified to use ICP’s http_request API with appropriate cycle management.

Using the canister’s Ed25519 public key (established in Milestone #1), we implement Cardano testnet address derivation following Cardano specs (Blake2b hashing, appropriate network tag, and Bech32 encoding). A getAddress() method exposes this functionality, and we validate the result against an external Cardano wallet generated from the same key.

We then implement core query methods, including getBalance and getUtxos, which call the selected Cardano API (e.g., Koios) over HTTPS, parse JSON responses, and return structured data. We handle pagination/large responses and typical error conditions.

This phase delivers a stable, read-only Cardano RPC canister running on ICP, capable of deriving a working Cardano address and reliably reading testnet state.

Acceptance Criteria

• Rust-based Cardano RPC canister deployed on an ICP environment with HTTPS outcalls enabled and tested via http_request.
• Implemented getAddress() method that derives a valid Cardano testnet address from the canister’s Ed25519 public key using Blake2b and Bech32 as per Cardano standards. The address must match an address generated by an external wallet using the same pubkey.
• Funding the derived address on Cardano testnet and successfully detecting those funds via the canister’s query methods.
• Implemented getBalance(address) and getUtxos(address) that call the chosen Cardano API endpoint(s), parse responses, and return normalized, typed data. Results must match those from a Cardano explorer for at least one funded address.
• Basic error handling in place for HTTP failures, invalid responses, and edge cases (no UTXOs, many UTXOs), validated through test scenarios.

Evidence of Completion

• GitHub repository with the Rust canister code, including getAddress, getBalance, and getUtxos methods, plus configuration for HTTPS outcalls.

• Test logs, screenshots & demo video showing:

• Derived Cardano testnet address from getAddress()
• Funding transaction to this address on testnet
• Matching balances and UTXO sets between getBalance/getUtxos and a Cardano explorer.

• Test cases or scripts (local replica / integration tests) covering no-UTXO and many-UTXO scenarios and demonstrating graceful error handling.

• Short technical note describing the address derivation process and API endpoints used.

Delivery Month

4

Cost

36600

Progress

40 %

Milestone Title

Full Transaction Lifecycle: Building, Signing, and Submitting Cardano Transactions

Milestone Outputs

In this phase, we implement complete transaction functionality within the Cardano RPC canister—covering raw transaction creation, threshold signing via ICP, and successful submission to the Cardano testnet. The canister will include a dedicated transaction builder module capable of selecting appropriate UTXOs, calculating fees, assembling inputs/outputs, and generating a valid unsigned transaction in hex format.

We leverage existing Cardano serialization libraries when possible to ensure strict adherence to Cardano’s transaction format.

Next, we integrate ICP’s Ed25519 threshold signing workflow using management canister APIs. The signTransaction function will produce a valid Cardano witness by signing the constructed transaction hash and attaching the appropriate public key. Once signing is integrated, we implement the submitTransaction function to POST the signed transaction to a Cardano node or API provider (Koios, Blockfrost, or a local testnet node).

To ensure secure operation, we incorporate basic access control—allowing read-only methods to remain public and restricting transaction-building and submission calls to authorized principals (e.g., a dapp controller canister). This phase culminates in a fully operational end-to-end transaction flow proven on Cardano testnet.

Acceptance Criteria

• Transaction Builder implemented with logic for UTXO selection, fee estimation, input/output construction, and serialization into a valid raw unsigned Cardano transaction (hex).

• A canister method that returns both the unsigned transaction and the exact UTXOs used. Output must be verifiable using external Cardano tools.

• Successful integration of ICP’s Ed25519 threshold signing APIs to sign the transaction hash and produce a valid Cardano witness. The signed transaction must pass external verification.

• A working submitTransaction method that sends a full signed transaction to the Cardano testnet and receives a valid TX hash response.

• End-to-end test: transferring ADA from the canister’s derived address to a second testnet address, with confirmation in a Cardano explorer.

• Basic access control implemented (e.g., authenticated caller checks) to prevent unauthorized spending actions.

Evidence of Completion

• GitHub repository containing the transaction builder, signing integration, and submission code, with detailed comments.

• Logs, screenshots, or explorer links and demo video showing:

• Construction of a raw unsigned transaction
• Valid witness/signature generation
• Successful submission and confirmation of a testnet transaction

• External verification output (from tools such as cardano-cli or serialization libraries) confirming correctness of the raw and signed transaction structures.

• Access control logic documented and demonstrated in tests.

Delivery Month

6

Cost

36600

Progress

60 %

Milestone Title

Testing, Optimization & Public Beta Deployment

Milestone Outputs

This phase focuses on validating reliability, optimizing performance and cycle efficiency, strengthening security, and deploying the Cardano RPC canister to the ICP mainnet for public beta use. We conduct extensive integration testing across diverse real-world scenarios: multi-output transactions, zero-change transactions, low-balance errors, invalid inputs, and simulated RPC provider failures.

We exercise the canister under repeated load—querying and submitting batches of transactions—to ensure deterministic, stable behavior on Cardano testnet.

Optimization efforts include reducing HTTP payload sizes, fine-tuning endpoint selection, minimizing unnecessary outcalls, and implementing selective caching for invariant data such as protocol parameters or frequently accessed UTXOs. We assess and document the cycle cost of core operations to guide dapp developers on expected resource usage.

A thorough internal security review is performed to check for logic errors, unsafe assumptions, improper signing flows, upgrade-safety, and potential vulnerabilities in the transaction, serialization, or caching components.

Finally, we deploy the canister to ICP mainnet (beta), connected to Cardano testnet (pre-prod), and publish its canister ID and Candid interface so external developers can freely test address derivation, balance queries, UTXO queries, and transaction submission.

Acceptance Criteria

• A comprehensive test suite covering >90% of code paths, including integration tests that execute at least 20 consecutive successful testnet transactions without failure.

• Demonstrated error handling for at least: insufficient balance, missing UTXOs, invalid transaction construction, RPC provider timeouts, and malformed data responses.

• Documented performance and cycle-cost benchmarks for key functions (getUtxos, getBalance, buildTransaction, submitTransaction), including caching or optimization techniques applied.

• Completed internal security audit with written findings and fixes addressing: fee calculation correctness, safe threshold-signing usage, absence of key leaks, and upgrade-safe state storage.

• Successful deployment of the Cardano RPC canister to ICP mainnet (beta) configured to interact with Cardano testnet.

• Publicly accessible canister ID and Candid interface enabling third-party developers to call read-only and transaction-related methods.

Evidence of Completion

• Test logs, CI outputs, or reports demonstrating >90% coverage and successful multi-transaction integration tests.

• Documentation showing cycle-cost analysis, optimization techniques, and before/after comparisons where applicable.

• Internal audit document summarizing vulnerabilities discovered and remediations applied.

• ICP mainnet canister ID, link to the Candid interface, and sample commands confirming successful Cardano testnet interactions.

• GitHub repository updates showing finalized, optimized, and reviewed code for beta release.

Delivery Month

8

Cost

36600

Progress

80 %

Milestone Title

Mainnet Enablement, Community Feedback & Documentation

Milestone Outputs

In this phase, we transition from a functioning beta canister to a production-ready service by enabling mainnet connectivity, gathering community feedback, and finalizing documentation. We open the Cardano RPC canister to the wider ICP and Cardano developer communities, encouraging real-world testing and providing demos that showcase end-to-end workflows (e.g., a simple cross-chain wallet or ADA-enabled dapp).

Feedback collection focuses on API usability, reliability, performance, and any edge-case failures not detected during earlier phases.

We then enable Cardano mainnet support by configuring the canister to reference mainnet endpoints and ensuring its Ed25519 public key is formatted correctly for mainnet addresses. After a small-scale mainnet test transaction, the canister will be able to query balances, UTXOs, and other chain data on Cardano’s main network.

To drive adoption, we publish comprehensive developer documentation (Candid interface, integration steps, examples) alongside an open-source example dapp demonstrating how to use the RPC canister from Rust.

Finally, we produce a roadmap for future enhancements—such as native token support, Plutus script integration, and decentralization improvements—positioning the canister for long-term community or DFINITY stewardship.

Acceptance Criteria

• Documented community testing process with feedback summaries from ICP and Cardano developers, including reports on API ergonomics, performance, and any detected bugs.

• Cardano mainnet mode enabled: the canister must successfully query real on-chain data (UTXOs, balances) from mainnet and demonstrate one small test transaction to confirm functionality.

• Comprehensive developer documentation published, including integration guides, example code snippets, data schemas, and usage patterns.

• Release of at least one example open-source dapp (Rust) that interacts with the RPC canister to showcase practical usage.

• A “Next Steps” proposal outlining additional features, architectural improvements, or potential adoption paths by the broader ecosystem.

Evidence of Completion

• Public documentation site or repository section containing full integration instructions and API reference.

• GitHub repository hosting the example dapp and all supporting code.

• Screenshots, logs, or explorer links showing successful mainnet data queries and at least one mainnet test transaction.

• Summary of developer testing feedback collected from Catalyst channels, forums, and GitHub issues.

• A published roadmap or proposal document outlining future enhancements.

Delivery Month

10

Cost

36600

Progress

100 %

[Final Pitch] Budget & Costs

Please provide a cost breakdown of the proposed work and resources

Our project is delivered across five milestones, each costing ADA 36,600, for a total budget of ADA 183,000. The breakdown reflects the effort of a 4-engineer full-stack blockchain team working across ICP, Cardano, Rust, cryptography, infrastructure, testing, and documentation. Costs include engineering time, development cycles, Cardano node infrastructure, testing resources, and public deployment.

1. Personnel Costs (80% of budget — ADA 146,400)

Four full-time engineers work throughout the project. Each milestone spans ~2 months of focused engineering effort.

Team Composition & Responsibilities

• Lead Rust Engineer (Architecture & Cryptography)
• Designs the canister architecture, Ed25519 threshold signing integration, and transaction lifecycle.
• Blockchain Engineer (Cardano Specialist)
• Implements Cardano UTXO logic, fee calculations, serialization, mainnet/testnet support.

ICP Systems Engineer

• Handles HTTPS outcalls, cycle optimization, deployment pipelines, and ICP security reviews.

Full-Stack / Tooling Engineer

• Builds example dapps, documentation, developer tooling, and community integrations.

What personnel costs cover

• 10 months of engineering work
• Rust canister development
• Cardano node setup & API integration
• Transaction builder, signing, and submission pipeline
• Testing, optimization, internal audits
• Documentation, example dapps, community onboarding

Subtotal: ADA 146,400

2. Infrastructure & Operational Costs (10% — ADA 18,300)

• ICP Cycles for HTTPS outcalls, signing tests, testnet deployments
• Cardano node hosting (testnet + optional mainnet)
• Cloud environment for CI/CD, integration tests, log aggregation
• Monitoring and automated test runners

Subtotal: ADA 18,300

3. Tooling, Libraries & External Services (5% — ADA 9,150)

• Cardano serialization libraries / build tooling
• Optional API access (Blockfrost, Koios enhanced tiers)
• Security analysis tools
• Automated testing frameworks

Subtotal: ADA 9,150

4. Documentation, Example Dapps & Community Support (5% — ADA 9,150)

• Developer documentation
• Example integration dapps (Rust/Motoko)
• Community testing sessions and demo materials
• Feedback integration and polish

Subtotal: ADA 9,150

[Final Pitch] Value for Money

How does the cost of the project represent value for the Cardano ecosystem?

The cost of this project represents exceptional value for the Cardano ecosystem because it delivers foundational cross-chain infrastructure, unlocks new ADA utility, and comes with guaranteed adoption from Helix Labs, which has already committed $200M in TVL to integrate with this trustless execution layer. This means the Catalyst investment does not fund a theoretical prototype—it funds infrastructure that will be used in production from day one.

1. High-Leverage Infrastructure for a Low Cost

For ADA 183,000, Catalyst receives a fully open-source, production-ready Cardano-sovereign RPC canister that enables:

Trustless Cardano ↔ ICP execution

Cross-chain compute without bridges or wrapped assets

Real-time oracles, DeFi interactions, and multi-chain triggers

Cardano-initiated signing and transaction submission

This infrastructure directly aligns with Catalyst’s priority of cross-chain prototypes that increase on-chain activity.

It is a fraction of what comparable interoperability projects cost, yet delivers multi-chain capabilities that Cardano does not have today.

2. The Project Immediately Increases On-Chain Activity

Every cross-chain action always begins with a Cardano transaction, increasing:

• L1 transaction volume
• Fees paid to SPOs (increasing economic security)
• Plutus script interactions
• ADA demand and contract usage

This directly supports Fund15’s intent to boost Cardano usage, liquidity, and transaction count.

3. $200M+ Guaranteed TVL Commitment — Massive ROI for Catalyst

Helix Labs’ commitment to onboard $200 million TVL into the infrastructure delivers:

• Immediate real-world usage
• Large early user base from existing vaults
• Guaranteed liquidity interacting with Cardano smart contracts
• Strong institutional narrative: “Cardano has trustless institutional-grade interoperability”

This level of pre-committed adoption makes the ROI for ADA holders extraordinarily high relative to the cost. Catalyst is not funding something hypothetical; it’s funding infrastructure with guaranteed economic activity.

No other Fund15 proposal includes anything close to this level of committed liquidity.

4. Avoids Custodial Bridges and Protects Cardano Users

Cardano has historically suffered from lack of safe interoperability. Existing solutions (Wanchain, CEX bridges, wrapped assets) carry:

• Custodial risk
• Smart contract exploit risk
• Governance attack surface

Your documents emphasize that this project provides trustless execution with zero custody, no wrapping, and no asset movement.

This dramatically reduces systemic and user-level risk—a core value for Cardano.

5. Multiplier Effect on Developer Productivity

For the cost of ~4 senior engineers for several months, Cardano developers gain:

• A free, open-source RPC gateway
• A decentralized oracle alternative
• A trustless off-chain compute engine
• Cross-chain dev primitives similar to Chainlink Functions or Axelar—at a fraction of the cost

This alone accelerates Cardano developer output significantly.

6. Institutional Onboarding & Canton Network Synergy (Zero Extra Cost to Catalyst)

The infrastructure becomes the foundation for:

• Institutional-grade cross-chain settlement
• Cardano participation in regulated DeFi
• Deep integration with the Canton Network, where Helix Labs is already an approved validator, giving us direct, credible access to institutional settlement rails from day one

Catalyst only funds Phase 1: the open-source Cardano–ICP execution layer.

The institutional integration layer (Phase 2+)—including Canton integration and institutional productization—is fully self-funded by Helix Labs, not by this proposal.

This means Cardano gains a powerful institutional gateway, backed by an existing Canton validator and a $200M TVL commitment from Helix Labs, without Catalyst needing to finance the entire institutional pipeline.

[Self-Assessment] Self-Assessment Checklist

I confirm that evidence of prior research, whitepaper, design, or proof-of-concept is provided.

Yes

I confirm that the proposal includes ecosystem research and uses the findings to either (a) justify its uniqueness over existing solutions or (b) demonstrate the value of its novel approach.

Yes

I confirm that the proposal demonstrates technical capability via verifiable in-house talent or a confirmed development partner (GitHub, LinkedIn, portfolio, etc.)

Yes

I confirm that the proposer and all team members are in good standing with prior Catalyst projects.

Yes

I confirm that the proposal clearly defines the problem and the value of the on-chain utility.

Yes

I confirm that the primary goal of the proposal is a working prototype deployed on at least a Cardano testnet.

Yes

I confirm that the proposal outlines a credible and clear technical plan and architecture.

Yes

I confirm that the budget and timeline (≤ 12 months) are realistic for the proposed work.

Yes

I confirm that the proposal includes a community engagement and feedback plan to amplify prototype adoption with the Cardano ecosystem.

Yes

I confirm that the budget is for future development only; excludes retroactive funding, incentives, giveaways, re-granting, or sub-treasuries.

Yes

[Required Acknowledgements] Consent & Confirmation

I Agree

Yes