WingRiders Expands Cardano Infrastructure for AI Agents

WingRiders has expanded Cardano support in Open Wallet Standard (OWS), with its Blockfrost integration merged into the project’s main development branch on October 14. The update builds on the team’s original implementation, which brought Cardano wallet operations into the same interface used for Ethereum, Solana, and Bitcoin.

The initial Cardano integration shipped in OWS v1.4.3 on September 29. Input Output Group presented it on October 8, crediting WingRiders with the implementation and identifying IOG and the Midnight Foundation as providing coordination and technical review. Blockfrost support is a subsequent development-branch addition.

WingRiders Contributes to Shared Cardano Infrastructure

WingRiders operates a decentralized exchange on Cardano, where users can trade tokens, provide liquidity, and participate in yield farms. Its OWS contributions extend the team’s engineering work into an open-source project that other applications and developer tools can use.

The Cardano implementation covers key and address derivation, transaction and message signing, wallet balance queries, and transaction data for policy evaluation. OWS maintainers reviewed the contribution through multiple rounds before merging it into the repository.

OWS standardizes local wallet storage and access to signing through software development kits and a command-line interface. Wallet secrets remain encrypted at rest. By implementing Cardano within that framework, WingRiders made its wallet functions accessible through a toolkit already designed to support multiple blockchain

Cardano Signing and AI Agent Controls

Supporting Cardano required changes to how OWS derives and handles keys. A Cardano base address combines a payment key, which controls funds, with a stake key used for delegation and rewards. WingRiders extended the signer to derive both separately under CIP-1852.

Transactions receive a payment-key signature, with a stake signature added when required and the relevant key is available. Message signing supports base, enterprise, and reward addresses, accommodating different Cardano account functions.

For AI agents, OWS provides individual access tokens scoped to specified wallets and policies. Requests made with an agent token undergo policy evaluation before key decryption. Built-in controls include permitted networks and access expiration, while spending limits and recipient restrictions require custom executable policies.

WingRiders’ Cardano implementation supplies those checks with calculated changes in ADA and native tokens for each address. Potential collateral consumption is reported separately, allowing a custom policy to account for funds at risk if script execution fails.

The documentation includes a custom policy example limiting outflow to 5 ADA per transaction, including potential collateral loss. Developers can adjust the amount and the wallet addresses covered by the rule.

Blockfrost and Initial Midnight Support

The latest accepted contribution adds Blockfrost alongside Koios through a shared Cardano provider interface. Both support balance queries, retrieval of source transactions needed to resolve inputs, and submission of signed transactions. Developers select the provider through their network configuration.

Koios remains the default option without a separate API credential. Blockfrost requires a project identifier for authentication. The integration validates where that credential is sent and restricts agent requests from redirecting it to arbitrary services through a custom-provider prefix. Wallet keys and signing remain local within OWS.

WingRiders also implemented initial Midnight support, merged on October 12. That contribution registers the network and derives its three address types from a recovery phrase. Balance retrieval, transaction signing, and submission are being developed through separate contributions.

For Cardano applications using the development branch, WingRiders’ latest work adds a choice of network infrastructure to the existing wallet workflow. Applications can use either Koios or Blockfrost for transaction data and submission while retaining OWS’s local signing and individually configured agent access.