WingRiders Dey Expand Cardano Infrastructure for AI Agents

WingRiders don expand Cardano support for Open Wallet Standard (OWS), as dem merge im Blockfrost integration enter di project main development branch on October 14. Di update build on top of di team original implementation, wey bring Cardano wallet operations inside di same interface wey Ethereum, Solana, and Bitcoin dey use.

Di first Cardano integration ship inside OWS v1.4.3 on September 29. Input Output Group present am on October 8, give WingRiders credit for di implementation and talk say IOG and di Midnight Foundation provide coordination and technical review. Blockfrost support na next addition for di development branch.

WingRiders Dey Contribute to Shared Cardano Infrastructure

WingRiders dey run decentralized exchange for Cardano, where users fit trade tokens, provide liquidity, and join yield farms. Di OWS contributions extend di team engineering work enter open-source project wey other applications and developer tools fit use.

Di Cardano implementation cover key and address derivation, transaction and message signing, wallet balance queries, and transaction data for policy evaluation. OWS maintainers review di contribution through multiple rounds before dem merge am inside di repository.

OWS dey standardize local wallet storage and access to signing through software development kits and command-line interface. Wallet secrets still remain encrypted at rest. As WingRiders implement Cardano inside dat framework, dem make wallet functions dey accessible through toolkit wey dem don design already to support multiple blockchain

Cardano Signing and AI Agent Controls

To support Cardano, dem need change how OWS dey derive and handle keys. Cardano base address dey combine payment key, wey control funds, with stake key wey dem dey use for delegation and rewards. WingRiders extend di signer to derive di two separately under CIP-1852.

Transactions dey receive payment-key signature, and dem go add stake signature when e needed and di relevant key dey available. Message signing dey support base, enterprise, and reward addresses, to fit different Cardano account functions.

For AI agents, OWS dey provide individual access tokens wey dem scope to specified wallets and policies. Any request wey dem make with agent token go undergo policy evaluation before key decryption. Built-in controls include permitted networks and access expiration, while spending limits and recipient restrictions go need custom executable policies.

WingRiders Cardano implementation dey supply those checks with calculated changes in ADA and native tokens for each address. Dem dey report potential collateral consumption separately, make custom policy fit account for funds wey fit dey at risk if script execution fail.

Di documentation include one custom policy example wey dey limit outflow to 5 ADA per transaction, including potential collateral loss. Developers fit adjust di amount and di wallet addresses wey di rule cover.

Blockfrost and Initial Midnight Support

Di latest accepted contribution add Blockfrost join Koios through one shared Cardano provider interface. Di two dey support balance queries, retrieval of source transactions wey needed to resolve inputs, and submission of signed transactions. Developers go select di provider through their network configuration.

Koios still remain di default option if separate API credential no dey. Blockfrost require project identifier for authentication. Di integration dey validate where dem dey send dat credential and e dey restrict agent requests from redirecting am go arbitrary services through custom-provider prefix. Wallet keys and signing still remain local inside OWS.

WingRiders still implement initial Midnight support, wey dem merge on October 12. Dat contribution register di network and derive im three address types from recovery phrase. Balance retrieval, transaction signing, and submission still dey under development through separate contributions.

For Cardano applications wey dey use di development branch, WingRiders latest work don add choice of network infrastructure to di existing wallet workflow. Applications fit use either Koios or Blockfrost for transaction data and submission while dem retain OWS local signing and individually configured agent access.