AURORA: Open infrastructure for bringing real credit markets to Cardano.

On-chain governance action (Treasury Withdrawals).

AURORA will give Cardano builders shared infrastructure for finding, comparing and verifying individual credit opportunities across compatible lending implementations. Today, each application must build much of this infrastructure separately, increasing integration costs and fragmenting market information.

AURORA provides that shared market layer. Treasury funding will deliver the Metadata Standard, Verification Framework, AURORA Discovery Engine, open APIs, filtering and query tooling, Capital Provider Profile Standard, developer tooling and reference implementation. Together, these components allow independent credit opportunities to expose standardized market information, become discoverable through common interfaces, and be evaluated according to different application and capital-provider requirements.

The infrastructure operates around compatible lending implementations while leaving loan origination, lending logic and settlement to those underlying systems. This allows different protocols and applications to share common market infrastructure without requiring adoption of a single lending protocol, verification system or commercial model.

The Treasury request is 940,000 ADA for approximately five months of delivery across four milestones. Fairway is responsible for delivery, with technical contributions from Sundial and architectural advice from Fallen Icarus. Treasury-funded implementation will begin following approval and enactment of the Treasury Withdrawal and receipt of funds. Treasury funds are initially received into an independent 3-of-5 AURORA Treasury multisignature, and all Treasury-funded software, standards and reference implementations will be released under Apache License 2.0 with public documentation and operating guidance.

Implementation contributors hold no signing keys to the administrator-controlled Treasury multisignature. Implementation installments are paid to Fairway, beginning at project commencement, with subsequent releases based on acceptance of the preceding milestone. Fairway manages implementation resources. Administrators may approve budget reallocations within the approved scope and total request. Independent Treasury-use audits take place following publication of the M2 technical outputs and during M4 before project closure, covering the funding arrangement and records defined in Section 11 of the full proposal.

• Proposer return address: stake1uyj67ee245gdks6swa8syq2u7glywh2pwh6tnwlxehk233clnk4zk
• Deposit: 100,000 ₳
• Submitted: epoch 662
• Expires: epoch 669

View in explorer

As a DRep, I decided to vote NO on the proposal: AURORA: Open infrastructure for bringing real credit markets to Cardano.

My rationale:

The proposal identifies a potentially useful infrastructure concept, but it does not demonstrate that there is a market ready to use it. The proposed software can be built, but we must demand more than that.

First, the product may be technically complete but economically dead. A discovery engine cannot create loan supply, credible originators, or capital providers. The central challenge is not building an indexer, metadata schema, or API. It is bringing real credit opportunities and capital to the market. The proposal does not provide sufficient evidence that this demand exists.

Second, there are no adoption or mainnet KPIs. Delivery is measured through specifications, testnet functionality, open-source code, documentation, and a technical demonstration. These are useful outputs, but they do not demonstrate that the infrastructure has been integrated, used, or validated by real market participants.

Third, there is a serious risk of creating a "standard without an ecosystem." A shared standard becomes valuable only when multiple independent lending implementations, originators, applications, and capital providers actually adopt it. No concrete integration commitments or credible adoption pathway are presented. Without them, AURORA risks becoming a well-documented reference implementation rather than a shared Cardano market infrastructure.

Fourth, the milestones pay for technical artifacts rather than demonstrated utility. Significant funds can be released after publication of specifications and testnet components, while there is still no requirement for a mainnet integration, a real credit opportunity, a committed capital provider, or measurable usage.

For comparison, the Catalyst process has set a very high bar for funding. Teams requesting up to 200,000 ADA are expected to demonstrate quality of the team, adoption potential, technical feasibility, marketing and go-to-market thinking, realistic milestones, and value for money. This proposal requests 940,000 ADA, yet it does not provide comparable evidence in the areas that matter most for its success.

As a DRep, I want funding rules to become stricter and to be applied consistently. I am not saying on-chain governance must copy the Catalyst standard exactly. However, I would like on-chain governance to move in the same direction: stronger evidence, clearer accountability, and a higher burden of proof for large Treasury withdrawals.

If you'd like to support my work, consider delegating to the MANDA pool and backing me as a DRep. Your support is the only way I can get time for governance.

MANDA Pool ID:
pool1c3fjkls7d2aujud8y5xy5e0azu0ueatwn34u7jy3ql85ze3xya8

My DRep ID:
drep1y2m0g4r66...skqwqp

Buy me a beer:
https://pay.cexplorer.io/pay/c0410d5b237b6ec0

Voting NO on AURORA: Open infrastructure for bringing real credit markets to Cardano (₳940,000).

As an elected Cardano Civics Committee member, Unified Cardano Student Club President in Nigeria, and a DRep focused on transparency and sustainable treasury use, I recognise the potential value of shared credit-market infrastructure that could reduce duplication and help builders.

However, I cannot support this withdrawal. There is no clear proven track record or sufficient evidence of previous work from the team that gives me confidence in delivery at this stage. With the treasury under pressure and remaining withdrawal capacity limited, I prioritise proposals with demonstrated capability, stronger accountability signals, and clearer sustainability before committing funds.

I remain open to future versions that show concrete prior results, tighter evidence of execution capacity, and stronger transparency around past delivery. For now, fiscal discipline and the need for proven performance lead me to vote No.