Developer Office Hours #60 - Ecosystem Engineering Feature Showcase

:rocket: Ecosystem Engineering Feature Showcase

Join the Cardano Foundation Ecosystem Engineering team for a special session highlighting some of the projects we’re currently building.

Get a behind-the-scenes look at ongoing work, explore new ideas, and see how these initiatives are shaping the Cardano developer ecosystem.

Come discover what we’ve been cooking on and join the conversation.

:date: Friday, 8 May

:eight_o_clock: 08:00 – 09:00 UTC

Stay updated with our events!

You can subscribe directly to the calendar here: Cardano Developers | AddEvent

Join the discussion below! We’ll update this thread with the recording link as soon as it’s live.

2 Likes

Thanks see you on 8 may

Summary: Cardano Ecosystem Engineering Showcase

In the 60th edition of the Developer Office Hours, host Darlisa Consoni from the Cardano Foundation, alongside the ecosystem engineering team, provides an exclusive look behind the scenes. The session introduces active projects, tools, and standards being developed to significantly improve the developer experience on Cardano.

Interoperability and Standards (Kuribic & x402)
Fabian Bormann presented updates on two important projects. “Kuribic” is a tool from the IBC incubator designed to make it easier for developers to locally manage components for the IBC bridge to the Cosmos ecosystem and test cross-network token swaps. Additionally, an update on the x402 standard (a Web3 extension of the HTTP 402 “Payment Required” protocol) was shared. The integration is now complete, and the standard can be used immediately in programming languages like Python, TypeScript, Go, and Java to require cryptocurrency payments for API calls.

CIP-113: Regulation and Institutional Tokens
Because traditional native assets on Cardano do not have built-in transfer restrictions (such as KYC or anti-money laundering regulations), institutions require extended functionalities. Thomas and Giovanni introduced the CIP-113 standard for programmable tokens. Thomas provided a live demonstration of how a KYC token is minted and transferred using Vidian credentials (based on CIP-170). The CIP-113 standard is currently undergoing an audit by Witness Lab and is already being integrated into platforms by several partners, including Fluid Tokens, Zeta, and Liberatum.

Infrastructure: Rosetta and Yaci DevKit
Maciej gave an update on Rosetta and the preparations for the upcoming hard fork. The team is integrating CIP-113 into the Token Metadata Registry and building an “asset store” to simplify infrastructure management for cryptocurrency exchanges, as they often have to run their own registry nodes.
In the realm of big data, a massive update for Yaci (version 2.1.0) was introduced. A new exporter uses DuckDB to convert Cardano blockchain data into highly compressed Parquet files. This drastically reduces storage requirements (from around 900 GB to just 13 GB) and makes the data directly compatible with analytics platforms like Apache Spark or Kafka.

Yano: The Specialized DevNet Node
Another major highlight was the introduction of “Yano”, a custom-built Cardano node designed exclusively for development networks (DevNets). Yano solves the problem where traditional nodes require long wait times for parameter updates when testing protocol upgrades (such as new Plutus versions). With Yano, developers can perform “time travel” on the blockchain and reuse database snapshots at will, which extremely shortens feedback loops during development. Additionally, there was a brief preview of “Juci”, an experimental, AI-powered Java-to-UPLC compiler for smart contracts.


Top Five Q&A (FAQ) about the Ecosystem Engineering Showcase

Question 1: What is Kuribic and what is it used for?
Answer: Kuribic is a tool from the ecosystem engineering team designed to manage the infrastructure for the IBC bridge between Cardano and the Cosmos ecosystem. It bundles the necessary processes, allowing developers to quickly spin up the required components and test cross-network token transfers.

Question 2: Why does the ecosystem need the CIP-113 standard?
Answer: Normal native assets on Cardano can be transferred completely freely. However, institutions and banks require tokens where regulatory transfer restrictions (such as KYC or anti-money laundering regulations) can be strictly enforced. CIP-113 provides exactly these control mechanisms, enabling so-called “programmable tokens.”

Question 3: What is “Yano”, and what advantage does it offer developers?
Answer: Yano is a newly developed, custom-tailored Cardano node designed exclusively for local DevNets (development networks). It allows developers to reuse database snapshots and “time travel” into the blockchain’s past or future. This eliminates the sometimes minute-long waiting periods that usually occur during protocol upgrades on the network.

Question 4: How does the Yaci DevKit facilitate big data analytics now?
Answer: With the release of Yaci 2.1.0, a new tool was introduced that exports Cardano data into highly compressed Parquet files. This massively shrinks storage requirements. These files are an open standard and can be seamlessly utilized by big data tools like Apache Spark, Kafka, or Superset for complex analytics and dashboards.

Question 5: What is the current status of the x402 standard on Cardano?
Answer: The x402 standard, which automatically ties API access to cryptocurrency payments, has reached the implementation phase. The developers at the Cardano Foundation have provided ready-to-use code packages for programming languages like Python, TypeScript, Go, and Java, meaning projects can start using the standard in their own web applications right away.

1 Like