The ₳940K AURORA treasury withdrawal
AURORA: Open infrastructure for bringing real credit markets to Cardano.
gov_action1znt2fr0chyye50nj0cdld2dvdjg3xsdfvq0fr37n43uehlvfkqdsqjnuq3nLast votes count before start of epoch 669: Nov 20, 2026, 21:44 UTC
Nov 20, 2026, 21:44 UTC
In plain English
Fairway is asking the Cardano treasury for ₳940,000 to build AURORA: shared, open infrastructure for finding, comparing and verifying individual credit opportunities (loan requests that each sit in their own on-chain UTxO) across compatible Cardano lending implementations. The proposal says loan origination, lending logic and settlement stay with those underlying lending systems.
The funded deliverables are a Metadata Standard, a Verification Framework, the AURORA Discovery Engine (an open-source indexer), open APIs, filtering and query tooling, a Capital Provider Profile Standard with a Reference Query Library, developer tooling, a reference implementation, documentation, and independent security and legal review. Delivery culminates in an end-to-end testnet demonstration, and all Treasury-funded software and standards are to be released under the Apache License 2.0.
Fairway leads delivery, with technical contributions from Sundial and architectural advice from Fallen Icarus (Rusty). The work runs about five months across four milestones. The withdrawal goes into an independent 3-of-5 AURORA Treasury multisig; the proposal says no implementation contributor holds a signing key.
According to the full proposal, ₳800,000 is a fixed implementation fee payable to Fairway, and ₳140,000 covers about ₳60,000 of security and legal review, ₳20,000 of Treasury-use audit and oversight, ₳30,000 of hosting and ₳30,000 of contingency. Funding is released in advance for each stage: up to ₳140,000 at commencement, rising to ₳460,000 after M1, ₳750,000 after M2 and ₳940,000 after M3. If the project terminates, ADA still held by the administrators returns to the treasury.
Who it affects
- The Cardano treasury: ₳940,000 would leave it and go into the 3-of-5 AURORA Treasury multisig, which pays it out to Fairway in instalments.
- Fairway, which receives the instalments and leads delivery, plus Sundial and Fallen Icarus as contributors.
- Cardano lending protocols, wallets, apps and capital providers, which could use the open standards and tools. The proposal describes adoption as optional.
- DReps and the Constitutional Committee, who decide it. SPOs do not vote on treasury withdrawals.
Where the vote stands
Snapshot: Koios, Oct 26, 2026, 13:01 UTC, epoch 663, block 14,118,605
| Voting body | Yes | No | Abstain | Yes % of stake |
|---|---|---|---|---|
| DReps | 10 | 28 | 6 | 1.6% |
| SPOs | Not applicable SPOs do not vote on treasury withdrawals. | |||
| Constitutional Committee | 0 / 7 | 2 / 7 | 0 / 7 | — |
Yes is 1.6% of DRep voting stake when delegated stake that hasn't voted counts as No (the CIP-1694 rule). Among DReps who voted Yes or No, Yes is about 6.6% of stake (₳80.20M yes vs ₳1,140.44M no).
2 of 7 Constitutional Committee members (Ace Alliance and Tingvard) have voted No, judging the action unconstitutional. Ace Alliance cites Article II.6.1 (the proposal document and its hash); Tingvard notes the full proposal is referenced without a hash.
Counts are votes cast; percentages are stake-weighted, per CIP-1694.
What it needs to pass
- DReps: Yes must reach at least 67% of active DRep voting stake. Delegated stake whose DRep hasn't voted counts as No; Abstain votes and the Always Abstain option are left out.
- Constitutional Committee: at least two-thirds of the voting committee members must vote Yes (the committee currently has 7 members).
- SPOs: no vote on this action type.
- The withdrawal must also fit the Cardano Constitution's treasury guardrails, such as the net change limit.
- If it reaches both thresholds at an epoch boundary, it is ratified and paid out at the next boundary. If it hasn't by the start of epoch 669 (Nov 20, 2026, 21:44 UTC), it expires and the ₳100,000 deposit is returned.
Arguments for / against
We don't take sides. These are verbatim excerpts from published vote rationales and the proposal document. Follow the links to read them in full.
The case for
“Yes: open, milestone-paid infrastructure via an independent multisig; good to have it ready before credit markets grow.”
“Despite the risks of development failure and limited adoption, I support this investment based on the team’s track record, open-source commitments, and milestone-based funding structure.”
“This is a small, five-month project to build free, open tools that help people find and compare lending opportunities on Cardano. The money is held by independent people, it’s paid out only as each stage is delivered, and it’s checked by outside auditors along the way. I support it, and I’ll be watching to see whether real lenders start using it.”
“Instead of each wallet, lending application or capital provider building its own indexer and reconstructing the same market information independently, they can build against common open infrastructure.”
“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.”
The case against
“AURORA asks 940,000 ada to index a credit market that does not exist on mainnet. The lending model it builds on has never been used there, no lender or protocol has committed to it, delivery ends on testnet, and most of the money is a fixed fee paid in advance.”
“The proposal identifies a potentially useful infrastructure concept, but it does not demonstrate that there is a market ready to use it. … there are no adoption or mainnet KPIs.”
“What I want to point out is that the biggest hurdle for this proposal is not technical implementation but adoption: getting people to use it.”
“After the third milestone is accepted, the cumulative ceiling reaches the full ₳940,000, so that Fairway's whole fee can be released before the fourth milestone begins. … Each is repairable by the proposer in days rather than months, and the proposal's history shows a team that revises when asked.”
Excerpts are taken verbatim from rationales attached to on-chain votes; follow the links to read them in full. Not every Yes vote has a published rationale, so the case for also quotes the proposal document. Most No rationales say the idea has merit in principle; their objections centre on demand, adoption and the payment schedule. Two Constitutional Committee members have also voted No. If more rationales are published, we'll add them.