AURORA: Open infrastructure for bringing real credit markets to Cardano.
Treasury withdrawal: Pays ADA out of the Cardano treasury.
- Status
- Active: Open for voting.
- Proposed
- 18 Oct 2026, in epoch 662
- Voting closes
- At the end of epoch 669, 25 Nov 2026
- Amount
- ₳940,000
- Action ID
- gov_action1znt2fr0chyye50nj0cdld2dvdjg3xsdfvq0fr37n43uehlvfkqdsqjnuq3n
Votes
- DReps: 0.2% yes, 67% needed, threshold not reached, 2 Yes · 0 No · 0 Abstain.
- Stake pools: do not vote on this action.
- Constitutional Committee: no votes counted yet.
Abstract
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.