Skip to content

Weekly development report as of 2023-10-06

Weekly development report as of 2023-10-06


This week, the ledger team achieved several milestones in Conway-related development. They fully implemented the constitutional committee, addressed governance actions related to treasury withdrawals, ensuring they now operate as expected, and enforced compliance with transaction rules by verifying the current treasury amount. They also implemented a mechanism to delay the expiration of delegate representative (DRep) positions when no proposals are available for voting, and changed the semantics of how CostModels are updated with protocol parameters to allow for individual Plutus language version updates, rather than requiring a complete replacement of all CostModels. They also made a range of performance and testing improvements.

The consensus team confirmed that the value-only workload benchmarks showed that the mempool forging regression observed in the UTXO-HD branch was fixed by the latest patch. Despite the increased resource requirements, key metrics like forging, peer-propagation, and end-to-end propagation show no regression when utilizing the UTXO-HD version of the Cardano node with the in-memory backend.

On the Genesis development, researchers continued their review of various design aspects, with particular attention to the Genesis rule's selection of the Cardano historical chain.

Finally, the consensus team merged a fix for the Babbage to Conway transition and released a new version of consensus.

As always, see this technical development report for more details from different teams.


This week, the Lace team worked on the upcoming Lace v.1.6 release running tests against the new Cardano services, which will include portfolio persistence. They fixed some bugs related to portfolio and stake management, finalized implementing basic Trezor support, and started the internal security audit. 


This week, the Plutus tools team continued working on exposing the queries of the new Marconi API via a JSON-RPC server. Additionally, they conducted tests using the new cardano-node-emulator within the Marconi environment for integration purposes, and implemented a strategy of deferring the creation of SQL indices in Marconi, aimed at enhancing synchronization times. Finally, the team conducted experiments involving the transition of Marconi to function as a Cardano node, simultaneously managing indexing tasks.

The Plutus Core team released version, introducing two static binaries – pir and uplc, tailored for x86-64 Linux. The pir binary encompasses functionalities like pretty-printing, optimizing PIR programs, and compiling PIR programs to UPLC. The uplc binary handles tasks such as pretty-printing, optimization, and evaluation of UPLC programs. This marks the initial publication of these binaries, and moving forward, each release will include an updated version.

The Marlowe team created Docker images for marlowe-withdrawals and Marlowe Runner, re-benchmarked Runtime resources and syncing on mainnet, preview, and pre-production networks, and made changes to the API to support open roles. They also fixed some Marlowe Runtime issues and released Marlowe Runtime version 0.0.5. The team updated marlowe-cli run initialize not to write open roles validator to the Marlowe file, improved the OpenAPI document to be friendlier to ecosystem tooling, and updated marlowe-payouts with the ts-sdk 0.0.2-alpha-0 version. 

Finally, the team continued working on Marlowe Runner, making functionality and design improvements.


This week, the Hydra team primarily focused on developing a reliable new network layer and outlined its anticipated behavior in a new architectural decision record. They also released Hydra version 0.13.0, which fixes a few security vulnerabilities.

Additionally, the team reviewed the security policy and vulnerability disclosure policy for handling security vulnerabilities within Hydra, specifically addressing ‘silent fixes’, leading to the publication and fixing of three new security advisories.

The September development report is now published on the Hydra website.

The Mithril team updated a proposal for implementing Mithril in a light wallet and created a relevant discussion to receive feedback and contributions from the community.

They also completed a proof of concept to run a Mithril client in a browser with WASM and worked on enhancing the explorer UI with SPO tickers displayed next to the pool IDs. Additionally, the team finalized a tool for benchmarking aggregator performance over a range of signer and client loads and for visualizing the results of these benchmarks.

Finally, they added a root page to the aggregator endpoint, created a status page for the Mithril networks, and added a section about KES key rotation in the signer documentation for SPOs.


In case you missed it, learn more about the GovTool, which was presented previously to test the governance features on SanchoNet. This tool allows ada holders to register on SanchoNet to become a delegate representative (DRep) and delegate voting power to other DReps. 

Community ownership is integral to governance tooling. Intersect, aided by its committees and working groups, will assume a significant role in hosting and maintaining these tools, subject to community approval. Together with various community builders, the goal is to establish the initial foundation layer, supporting essential off-chain governance processes for complete on-chain voting via CIP-1694. Once this foundation is set, the community can continue enhancing these tools by maintaining existing features, introducing new ones, or exploring entirely new areas. This can be done independently or with support from awards and grants administered by Intersect.

To find out about the progress made on CIP-1694 development, read this blog post about the advancement of CIP-1694 to a ballot.

To get involved in shaping the future of Cardano governance, make sure to join Intersect, visit the SanchoNet website, and join the conversations on Discord


This week, Project Catalyst saw the start of the onboarding process for projects successfully selected in Fund10. You can review the stats for Fund10 and download a full copy of the results here.

Project onboarding consists of a number of critical steps that include a comprehensive guide on how to proceed for both challenge teams and funded projects, onboarding calls, proof of life statements, and milestone submissions to provide realistic expectations to the community about each team’s capacity to deliver. You can learn more about the onboarding process here.

During this onboarding phase, Project Catalyst enters the scheduled cooldown period before entering the next funding cycle. Stay tuned for news in the coming weeks. In case you missed it, you can check out the recording of the Catalyst town hall here.

On the technical side of Catalyst last week, the team:

  • finalized UX for ‘already voted’ and ‘themes’ filters

  • started implementing continuous snapshots in the mobile app, including updates to cat-data-service

  • started mobile app dry run to test the latest improvements on proposal loading times and max batch size

  • started work to implement the new load testing framework

  • continued automating artifact generation with GitHub actions and Earthly.

Finally, to stay updated with everything happening in Project Catalyst, join the Catalyst Telegram announcement channel. 


This week, the Education team continued delivering and supporting the Haskell course with ABC. They are also working with the Marlowe team to define learning assets.








Laceチームは、Lace v.1.6リリースに向け、ポートフォリオの永続性を含む新たなCardanoサービスに対するテストを実行しました。ポートフォリオ管理やステーク管理に関するバグを修正し、基本的なTrezorサポートの実装を仕上げ、内部セキュリティ監査を開始しました。 


Plutusツールチームは、JSON-RPCサーバーを介した新しいMarconi APIのクエリ公開への取り組みを継続しました。Marconi環境内で新しいCardanoノードエミュレーターを使用した統合テストを実施し、同期時間の向上を目的として、MarconiでSQLインデックスの作成を延期する戦略を実装しました。MarconiをCardanoノードとして機能するように遷移させ、インデックス作成タスクを同時に管理する実験を行いました。

Plutus Coreチームはバージョン1.14.0.0をリリースし、x86-64 Linux用に調整した2つの静的バイナリー、pirとUPLCを導入しました。pirバイナリーには、pretty-printing、PIRプログラムの最適化、PIRプログラムのUPLCへのコンパイルなどの機能が含まれています。uplcバイナリーは、pretty-printing、最適化、uplcプログラムの評価などのタスクを処理します。これは、これらのバイナリーの初回公開であり、今後、各リリースには更新されたバージョンが含まれることになります。

Marloweチームは、marlowe-withdrawalsMarlowe RunnerのDockerイメージを作成し、 メインネット、プレビュー、プリプロのネットワークでRuntimeリソースのベンチマークを再作成し、オープンロールをサポートするためにAPIに変更を加えました。Marlowe Runtimeの問題を修正し、Marlowe Runtimeバージョン0.0.5をリリースしました。オープンロールバリデーターをMarloweファイルに書き込まないようにmarlowe-cli run initializeを更新し、OpenAPIドキュメントをエコシステムツールで使いやすいものにし、marlowe-payoutsをts-sdk 0.0.2-alpha-0バージョンに更新しました。 

Marlowe Runnerの開発を続け、機能性と設計の改良に取り組みました。

Basho( スケーリング)








見逃した場合は、 SanchoNetのガバナンス機能をテストするために以前に紹介されたGovToolについてご覧ください。このツールを使用すると、ADA保有者はSanchoNetに登録してDRep(デリゲーター代表)になったり、投票権を他の代表者に委任したりすることができます。 


CIP-1694開発の進捗状況については、ブログ記事The Advancement of CIP-1694 to a Ballotを参照してください。



Project Catalystでは、Fund10で選ばれたプロジェクトのオンボーディングプロセスが開始されました。ここでFund10の統計を確認し、結果のフルコピーをダウンロードできます。


このオンボーディングの期間中、Project Catalystは次の資金調達サイクルに入る前の、既定のクールダウン期間に入っています。今後数週間のニュースをお楽しみください。見逃した場合は、ここでCatalystタウンホールの録画を視聴できます。


  • 「投票済み」フィルターと「テーマ」フィルターのUXを仕上げ

  • cat-data-serviceの更新を含む、モバイルアプリでの継続的スナップショットの実装を開始

  • モバイルアプリのドライランを開始し、提案されたロード時間と最大バッチサイズに関する最新の改良をテスト

  • 新しい負荷テストフレームワークの実装作業を開始

  • GitHubアクションとEarthlyを使用してアーティファクトの生成自動化作業を継続

Catalyst Telegram案内チャネルに登録して、Project Catalystの最新情報を入手してください。