AURORA Seeks 940,000 ADA for Cardano Credit Infrastructure

Fairway submitted a request on October 18 for 940,000 ADA from the Cardano Treasury to develop AURORA, open infrastructure for credit markets. The project would help applications and capital providers find, filter, and compare individual credit opportunities across compatible lending protocols.

What AURORA Would Build on Cardano

AURORA would standardize credit information that applications otherwise have to collect and process separately. Its Discovery Engine would index compatible loan requests, making them searchable by attributes such as duration, asset, amount, jurisdiction, and verification requirements.

Open APIs would let wallets, lending applications, and analytics services access those records. Developers could integrate the shared infrastructure while retaining their own lending systems and application designs.

The architecture uses Cardano’s UTxO model, allowing individual financial agreements to retain their own terms and state. Loan origination, lending decisions, funding, and settlement would remain with the underlying protocols and participants.

Fairway would lead implementation, with technical contributions from Sundial and architectural advice from Fallen Icarus. Four milestones cover specifications, development, integration, and independent review. Delivery culminates in an end-to-end testnet demonstration and public release of Treasury-funded software, standards, and reference implementations under Apache License 2.0.

Fairway’s Fee and Treasury Payment Controls

The budget initially allocates ₳800,000 as a fixed implementation fee payable to Fairway for the agreed public outputs. Fairway would determine staffing, contributor compensation, and subcontracting. Payments would be assessed against deliverables rather than reimbursed against actual internal costs.

The remaining ₳140,000 would cover independent security and legal reviews, Treasury-use audits, hosting, and technical contingency. Administrators could approve reallocations within the total budget, including additional implementation payments, while preserving funding for required reviews and existing commitments.

If approved and enacted, the full allocation would first enter a dedicated multisignature wallet controlled by five independent administrators. Transactions would require at least three signatures. Fairway, Sundial, and Fallen Icarus would hold no signing keys to that wallet.

The first installment would fund the start of development. Subsequent releases would follow acceptance of the preceding milestone. Funds transferred to Fairway’s implementation wallet would leave the administrators’ custody, while undisbursed balances would remain under their control.

Administrators could suspend further payments over material delivery problems. If the project terminates, the proposal requires funds remaining in their custody to be returned to the Cardano Treasury.

AURORA Voting and Document Immutability

Koios data checked at approximately 9:47 p.m. CEST on October 19 recorded three DRep votes in favor of AURORA and five against. Those votes represented approximately ₳15.29 million and ₳571.89 million in active voting power, respectively.

The submitted action also raises a documentation question. Its on-chain anchor points to a metadata file on the main branch of Fairway’s GitHub repository, where content can be replaced through a new commit.

The retrieved file’s hash matched the value recorded on-chain during the check. That establishes correspondence with the submitted version. Article II.6.1 of the Cardano Constitution separately requires the document at the supplied URL to be immutable after submission.

Fairway has published a separate proposal snapshot, but the action’s anchor points to the main-branch metadata file. Toto Finance’s ₳22 million copper-reserve request similarly references a file hosted on its own website, whose hash also matched its on-chain record.

DReps decide whether to support the proposed spending, while the Constitutional Committee assesses compliance with the Constitution. Neither action had received a recorded committee vote at the time of the check, leaving the documentation issue without an on-chain constitutional determination.