CORE TECHNOLOGY

Last week, the networking team released node v.1.35.6, which brings Dynamic P2P networking to mainnet. Dynamic P2P enables SPO relays to automatically connect to each other, replacing the current manual configuration process. See this blog post for more details.

The ledger team made progress on the Conway era implementation by expanding the ledger API and including multiple governance features. They also kept working on the specification and Haskell implementation, continued integrating ledger packages into cardano-node, and addressed technical debt.

The consensus team continued working on the UTXO-HD prototype refactoring and Genesis design and testing. They also extracted the fs-sim package, which provides a file-system abstraction layer that can be used for testing and simulation. This makes the consensus code base smaller while providing a package that the community can reuse and contribute to. 

Finally, they fixed a failing property test related to iterators and continued working on mempool and VRF improvements.

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

WALLETS AND SERVICES 

This week, the Daedalus team worked on the application’s starting screen improvements to show a more precise sync progress with decimals. 

Work is ongoing on the Lace desktop development. The team improved the DApp Connector’s browser navigation and transaction drawer logic and fixed minor UI issues to improve the overall user experience. 

Finally, they finalized and implemented a simple onboarding mechanism for the local node feature.

The Adrestia team worked on extending the multi-signature feature with delegation functionality in cardano-wallet. They also worked on extracting the transaction balancing library and did some refactoring of the DBLayer to improve performance and memory usage. 

Finally, they continued working on performance optimization of cardano-services in cardano-js-sdk.

SMART CONTRACTS

The Marlowe team fixed the inclusion of the stake address in the Marlowe address, removed trace statements from the Marlowe validator, and assessed options for preventing double satisfaction. The team also assessed various conditions in the Marlowe semantics validator: adding a check for the positivity of accounts for the output state, guarding against duplicate accounts, guarding balance postcondition, and guarding against negative deposits in the validator. They also documented the rationale for allowing multiple outputs to an address, fixed Eq instance for ReduceWarning, added missing specification tests for validator semantics, and addressed minor issues related to the validator and its spec.

Finally, they implemented a transaction detail view for Marlowe Explorer, displayed ada amounts in a more readable way, and implemented a paginated index of all Marlowe contracts.

BASHO (SCALING)

The Hydra team continued working on hydra-node mainnet compatibility, added a golden test suite for Hydra Plutus scripts and some detection of hydra-node misconfiguration, established a mainnet limit of 100 ada per commit (for now), and addressed smaller tasks in preparation for the mainnet beta release. 

The Mithril team continued implementing the migration of the aggregator stores to a relational design and completed the adaptation and migration of the stake pool store. They also worked on refactoring the multi-signer to enable it to sign multiple concurrent messages. Additionally, they finished implementing the automatic handling of API versions switch at era transition.

Finally, the team successfully completed the tests to create certificates and snapshots on a network running on the Cardano mainnet and fixed issues related to deadlocks on the SQLite connections. 

GOVERNANCE 

If you haven’t had a chance to review the updates to CIP-1694, IOG encourages you to! You can contribute directly to GitHub and continue the conversation on various community channels.

Following on from the earlier CIP-1694 workshop in Colorado, IOG would like to invite all community members to a Zoom conversation on March 30. It will be an opportunity to recap the workshop with attendees, hear more about CIP-1694, as well as discuss future workshops and the next steps towards the age of Voltaire. RSVP here if you’d like to join. 

This week in Project Catalyst, the team introduced a proposed iteration for the community assessment stage coming into Fund10. You can rewatch the segment from the main town hall here. There will be more information shared in the coming weeks, make sure to stay tuned and register your attendance for the upcoming town hall.

Also, the Special Voting Event introduced during this week’s 360 segment is coming soon. More details will be announced soon, but you can register via the usual voter registration in Catalyst to participate in the upcoming voting event.

Lastly, if you’re trying to stay up to date with everything that's happening in Project Catalyst, bookmark the past issues of the weekly newsletter. Check it out here.



コアテクノロジー

ネットワーキングチームは、ダイナミックP2Pネットワーキングをメインネットにもたらすノードv. 1.35.6をリリースしました。ダイナミックP2Pを使用すると、SPOリレーが自動的に相互接続され、現在の手動設定プロセスが置き換えられます。詳しくはこちらのブログ記事をご覧ください。

台帳チームは、台帳APIを拡張し、複数のガバナンス機能を含めるなど、Conway期の実装を進めました。仕様とHaskell実装に関する作業、Cardanoノードへ台帳パッケージを統合する作業を続け、技術債務に対処しました。

コンセンサスチームは、UTXO-HDプロトタイプのリファクタリング、およびGenesisの設計とテストに引き続き取り組みました。テストやシミュレーションに使用できるファイルシステム抽象化レイヤーを提供するfs-simパッケージの抽出も行いました。これによりコンセンサスコードベースが小さくなり、コミュニティが再利用して貢献できるパッケージが提供されます。 

失敗したイテレーター関連のプロパティテストを修正し、メモリープールとVRFの改善への取り組みを続けました。

通常通り、チーム別の詳細はこちらの技術開発レポートをご覧ください。

ウォレットとサービス 

Daedalusチームは、小数を使用して同期の進行状況表示の正確性を高めるという、アプリケーション起動画面の改良に取り組みました。 

Laceデスクトップの開発作業は進行中です。DAppコネクターのブラウザーナビゲーションとトランザクションドロワーロジックを改善し、ユーザーエクスペリエンス全体を向上させるために、UIの軽微な不具合を修正しました。 

ローカルノード機能の簡単なオンボーディングメカニズムを完成させて実装しました。

Adrestiaチームは、cardano-walletのマルチシグ機能を委任機能で拡張する作業に取り組みました。トランザクション残高ライブラリーの抽出作業、パフォーマンスとメモリー使用量を改善するためのDBLayerのリファクタリングも行いました。 

cardano-js-sdkにおけるcardano-servicesのパフォーマンス最適化作業を続けました。

スマートコントラクト

Marloweチームは、Marloweアドレスにステークアドレスが含まれていることを修正し、Marloweバリデーターからトレースステートメントを削除し、二重満足を防ぐためのオプションを評価しました。アウトプットステータスに対するアカウントのポジティブ性のチェックの追加、重複アカウントに対する保護、残高事後条件の保護、バリデーターの負のデポジットに対する保護など、Marloweセマンティクスバリデーターのさまざまな条件を評価しました。1つのアドレスへ複数のアウトプットを許可する論理的根拠を文書化し、ReduceWarningのEqインスタンスを修正し、バリデーターセマンティクスの不足している仕様テストを追加し、バリデーターとその仕様に関する軽微な問題を解決しました。

Marloweエクスプローラーにトランザクション詳細ビューを実装し、ADAの金額表示を読みやすくし、すべてのMarloweコントラクトのページ分割インデックスを実装しました。

Basho( スケーリング)

Hydraチームは、引き続きhydra-nodeのメインネット互換性に取り組み、Hydra Plutusスクリプトのゴールデンテストスイートとhydra-nodeの設定ミス検出を追加し、コミットごとの100ADAのメインネット制限を確立し（暫定）、メインネットベータリリースに向けて小規模なタスクに対処しました。 

Mithrilチームは、アグリゲーターストアのリレーショナル設計への移行の実装を続け、ステークプールストアの適応と移行を完了しました。複数の同時メッセージに署名できるように、マルチ署名者のリファクタリングにも取り組みました。開発期移行時のAPIバージョン切り替えの自動処理の実装も完了しました。

Cardanoメインネットで実行されているネットワーク上で証明書とスナップショットの作成テストを完了し、SQLite接続のデッドロックに関する不具合を修正しました。 

ガバナンス 

CIP-1694の更新を未確認の場合は、ぜひ実行してください。GitHubに直接貢献し、さまざまなコミュニティチャネルで会話を続けることができます。

コロラド州で開催されたCIP-1694ワークショップに続き、IOGでは3月30日のZoomミーティングにコミュニティメンバー全員の参加を希望しています。参加者とともにワークショップを振り返り、CIP-1694についての詳細を聞き、ヴォルテール期に向け今後のワークショップと次のステップについて話し合う機会となります。参加をご希望の場合は、こちらからお申込みください。 

今週のProject Catalystでは、Fund10に導入されるコミュニティ評価段階のイテレーション案が紹介されました。ここで、メインタウンホールからセグメントを再視聴できます。今後数週間のうちに、さらに情報が更新される予定です。今後のタウンホールへの参加登録をしてください。

今週の360セグメントで紹介されたスペシャル投票イベント（SVE）も近日中に開催されます。詳細は近日中に発表されますが、Catalystの通常の有権者登録から登録し、次の投票イベントに参加することができます。

週刊ニュースレターの過去の号をブックマークに登録して、Project Catalystの最新情報を入手してください。詳しくは、こちらをご覧ください。


Weekly development report as of 2023-03-24

The whole Cardano community will be rallying around Voltaire this year. The age of Voltaire is all about governance, fully unlocking the community’s contributions to create an autonomous system.

CIP-1694 is a Cardano Improvement proposal, named after the birth year of the French enlightenment thinker. And it’s a key component of Cardano's next generation of governance, now being designed and community-co-created to deliver the on-chain mechanisms which will further empower democratic decision-making across the ecosystem.

IOG, the Cardano Foundation, and EMURGO recently hosted a community workshop to capture input and take full advantage of the Cardano community’s incredible hive mind as we collaborate on moving the CIP toward community validation and implementation.

The event was just the kickoff to a broader program of community governance events planned for the next few months, we had representation from across the community - from educators to developers, SPOs to academics. We covered topics such as enhancing participation, DReps, voting thresholds, community tooling, and much more, drilling down into the current CIP and capturing all the feedback.

Find out more here:

https://forum.cardano.org/t/cip-1694-...

Thanks to all the attendees:

Matthias Benkort (Cardano Foundation)

Markus Guffler (Cardano Foundation)

Tsz Wai Wu (EMURGO)

Sergio Sanchez Ferreros (EMURGO)

Juana Attieh

Kenric Nelson

Andrew Westberg

Pi Lanningham

Patrick Tobler

Eystein Hansen

Marek Mahut

Rick McCracken

James Dunseith

Adam Rusch

Michael Dogali

Lloyd F Duhon II

Darlington Wleh

Mercy A Fordwoo


CIP-1694 Community Workshop

There are a a few reasons you may want to split your ada delegation between multiple stake pools. For example, to participate in multiple ISPOs, or you feel ethically aligned with more than one stake pool.

Currently there are two ways you can split your delegation.

Create new wallets
This option is pretty straightforward and you will be familiar with this from when you set up your first wallet. You can simply create extra wallets which will have their own seed phrase, transfer funds between these wallets and delegate each wallet to a different stake pool.

Add additional accounts under the same wallet
It is possible to add multiple additional accounts to your existing wallet. From a user perspective accounts act like separate wallets but they are recoverable using the same seed phrase or hardware wallet. Each account has its own receive address, transaction history, delegation history and stake key. Once you have set up an additional account you can send ada between accounts and delegate each account to a different Stake Pool if you wish. The multiple account feature is currently available in Eternl, Flint and some other wallets but not currently available in Daedalus or Yoroi.

How to set up and access additional accounts in Eternl
Open the wallet for which you would like to add additional accounts. On the main account screen select ‘account list’ then ‘add accounts’ and select which accounts you would like to add. To switch between accounts select ‘account list’ then select ‘activate’ underneath the account you would like to access.

How to set up and access additional accounts in Flint
Select the ‘wallets’ icon in the top right corner then select ‘add account’ under the wallet for which you would like to add an account and follow the on-screen instructions. To switch accounts select the ‘wallet’ icon in the top right then select the account you would like to access.

For instructions on how to set up additional accounts in other wallet interfaces please see their documentation.

It’s important to note that when restoring your wallet you will have to remember to add the accounts you want to access.


How can I delegate to more than one Stake Pool?

CORE TECHNOLOGY

This week, the core technology teams continued working on node, ledger, and networking improvements.

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

WALLETS AND SERVICES 

Work is ongoing on the Lace desktop development. The team improved the error handling of CIP-30 DApps operations, fixed issues with signing CIP-30 transactions using hardware wallets, and added a friendly onboarding screen for users who want to use the local node to send transactions.

The Adrestia team worked on extending the multi-signature feature with delegation functionality in cardano-wallet. They also worked on extracting the transaction balancing library and did some refactoring of the DBLayer to improve performance and memory usage.

The team is currently working on performance optimization of cardano-services in cardano-js-sdk.

SMART CONTRACTS

This week, the Plutus team continued working on the Marconi MVP development. They created a dedicated repository for it and evaluated and implemented Marconi notifications. They also added test performance optimizations for cardano-api and Plutus end-to-end testing, and evaluated the need for building a standalone emulator that doesn’t require a contract monad. 

Work is ongoing on the Plutus debugger, script capacity increase, and documentation improvements. 

The Marlowe team made significant improvements to the golden tests for the Marlowe validator to make them more comprehensive and fixed an issue with incorrect build instructions for the Marlowe Playground. They also rewrote a theorem to support multiple token asset preservation, resolved a discrepancy with division rounding between the Isabelle specification and PureScript, and updated content for the Getting Started pages. 

Finally, the team added the escrow contract to the examples suite in the specification and set up the end-to-end CLI tests infrastructure. 

BASHO (SCALING)

The Hydra team addressed issues with committing complex UTXOs into a Hydra head, prepared the Hydra node to support mainnet, and improved the test suite of the Hydra Plutus scripts. Also, work is ongoing on the Hydra V1 specification, the team improved the specification on the reviewers' feedback, and refined the graphical notation to be more transaction focused.

The Mithril team are running the last milestones to make the Mithril beta version available on mainnet. The signer and aggregator parts of the system are thoroughly tested thanks to the enthusiastic participation of the SPO community, and a security audit will soon be undertaken on the more sensitive parts of the system. 

The team released a new 2310.0 distribution that activates the era switch mechanism. They also started implementing the migration of the aggregator stores to a relational design with the first adaptation of the stake pool store. Additionally, they worked on automatically handling the network API version from the Open API specifications, optimized the stake distribution computation that now happens only once per epoch, and also enhanced the client multi-platform workflow to test the Docker images.

The team is now seeking more feedback and testing from a client perspective.

If you are used to spinning up Cardano nodes on preview and pre-production testing environments and would like to significantly reduce the sync time, you can benefit from using a Mithril Client to download a certified snapshot of the node DB:

Clients are available for Linux, OS X, Windows, and as Docker images

Documentation is available on the Mithril website

Share your feedback in Discord or GitHub discussions

GOVERNANCE 

The publication of CIP-1694, describing Cardano’s future on-chain governance system, has been received with anticipation and excitement. In February 2023, IOG, the Cardano Foundation, and Emurgo hosted a community workshop at IOG’s offices in Longmont, Colorado. The workshop sparked deep engagement and insight gathering, which captured inputs from a broad spectrum of community interests and experiences.  

This week a large update to CIP-1694 was pushed on GitHub. CIP-1694 continues to spark conversations and thoughts across the community and we encourage you to engage and comment directly in GitHub.



コアテクノロジー

コアテクノロジーチームは、ノード、台帳、ネットワークの改良への取り組みを続けました。

通常通り、チーム別の詳細はこちらの技術開発レポートをご覧ください。

ウォレットとサービス 

Laceデスクトップの開発作業は進行中です。CIP-30 DApp操作のエラー処理を改善し、ハードウェアウォレットを使用してCIP-30トランザクションに署名する際の問題を修正し、ローカルノードを使用してトランザクションを送信したいユーザーのための使いやすいオンボーディング画面を追加しました。

Adrestiaチームは、cardano-walletのマルチシグ機能を委任機能で拡張する作業に取り組みました。トランザクション残高ライブラリーの抽出作業、パフォーマンスとメモリー使用量を改善するためのDBLayerのリファクタリングも行いました。

現在、Cardano-js-sdkにおけるcardano-servicesのパフォーマンス最適化に取り組んでいます。

スマートコントラクト

PlutusチームはMarconi MVPの開発作業を続けました。専用リポジトリを作成し、Marconi通知を評価して実装しました。ｃardano-apiとPlutusのエンドツーエンドテストテストのテストパフォーマンスの最適化を追加し、Contractモナドを必要としないスタンドアロンエミュレーターの構築の必要性を評価しました。 

Plutusデバッガー、スクリプト容量の増加、ドキュメントの改善の各作業は進行中です。 

MarloweチームはMarloweバリデーターのゴールデンテストを大幅に改良して包括性を高め、Marlowe Playgroundのビルド手順が不正確だった問題を修正しました。複数のトークン資産の保存をサポートするように定理を書き直し、Isabelle仕様とPureScriptの除算丸めの不一致を解決し、Getting Startedページの内容を更新しました。 

仕様のサンプルスイートにエスクロー契約を追加し、エンドツーエンドのCLIテストインフラをセットアップしました。 

Basho( スケーリング)

Hydraチームは、複雑なUTXOをHydra Headにコミットする際の不具合に対処し、Hydraノードのメインネットサポート準備を進め、Hydra Plutusスクリプトのテストスイートを改良しました。Hydra V1仕様の作業も進行中です。レビュワーからのフィードバックに関する仕様を改善し、トランザクションに焦点を当てるようにグラフィック表記を改良しました。

Mithrilチームは、Mithrilベータ版のメインネットリリースに向け、最後のマイルストンを実行しています。SPOコミュニティの熱心な参加のおかげで、システムの署名者とアグリゲーターの部分は徹底的にテストされ、システムの機密性の高い部分についてセキュリティ監査がまもなく実施されます。 

開発期スイッチメカニズムを有効にする新しい2310.0ディストリビューションをリリースしました。アグリゲーターストアのリレーショナル設計への移行の実装も開始し、ステークプールストアの初回適応を実施しました。Open API仕様からのネットワークAPIバージョンの自動処理に取り組み、現在エポックごとに1回しか発生しないステーク分布計算を最適化し、Dockerイメージをテストするためのクライアントマルチプラットフォームワークフローを強化しました。

現在、クライアントの観点から、より多くのフィードバックとテストを求めています。

プレビューおよびプリプロテスト環境でCardanoノードをスピンアップすることに慣れており、同期時間を大幅に短縮したい場合は、Mithril Clientを使用してノードDBの認定スナップショットをダウンロードすることをお勧めします。

クライアントは、Linux、OS X、Windows、およびDockerイメージとして使用できます

ドキュメントはMithrilのウェブサイトで入手できます

DiscordまたはGitHubディスカッションでフィードバックをお寄せください

ガバナンス 

Cardanoの将来のオンチェーンガバナンスシステムを説明するCIP-1694の公開は、期待と興奮を持って受け入れられました。2023年2月、IOG、Cardano財団、Emurgoは、コロラド州ロングモントにあるIOGのオフィスでコミュニティワークショップを開催しました。ワークショップは、コミュニティの幅広い関心や経験からのインプットを捉え、深いエンゲージメントと洞察の収集を促しました。  

今週、CIP-1694の大規模な更新がGitHubにプッシュされました。CIP-1694はコミュニティ全体で会話や考えを巻き起こし続けています。ぜひGitHubで直接コメントしてください。


Weekly development report as of 2023-03-17

Dynamic peer-to-peer (P2P) networking comes with the release of node v.1.35.6. Network participants can now test automatic node communication without a need for static configurations.

Dynamic P2P networking is an important evolution for Cardano and a further boost to the network's performance, resilience, and decentralization. By automating the peer selection process, Dynamic P2P enables enhanced communication between distributed nodes and simplifies the process of running a relay or a block-producing node. This eliminates the need for static configurations and manual stake pool operators’ (SPO) input.

Dynamic P2P comes as a built-in functionality with node v.1.35.6 release today. The SPO community is now encouraged to test P2P functionality by updating one of their relays to use the P2P topology mode. Over the next few weeks, IOG and CF teams together with the SPO community will be assessing network connectivity to ensure a smooth rollout of Dynamic P2P functionality.

Here’s more about the evolution of the Cardano network and the features that Dynamic P2P brings.

Connectivity

Cardano's networking protocols combine nodes and their interactions into a unified system using standard communication infrastructure. The network distributes information about transactions and blocks to all active nodes.

There are two ways to configure a Cardano node:

As a block-producing node responsible for producing blocks on the Cardano blockchain. SPOs run block-producing nodes that require incoming connections to receive block information and outgoing connections to propagate generated blocks. P2P will enable bi-directional usage of each connection, so the order of connections will not matter.

As a relay node, responsible for communicating with other relays in the network and broadcasting blocks from block-producing nodes. Relay nodes also act as a ‘defense layer’ for block producers to ensure that block producers are not directly exposed to the whole internet.

Ensuring minimum communication delays and maximum resilience

The network’s design aims to minimize communication delays and maximize network resilience against failures, capacity constraints, or malicious behavior.

IOG has always recommended that SPOs deploy at least two relay nodes for each block-producing node to ensure that the system adds blocks and verifies transactions effectively. This strengthens security and deters denial of service (DoS) attacks.

As mentioned in a previous post, Cardano's networking evolved from its initial federated structure to hybrid and the current P2P model. Networking will keep evolving with future additions such as Ouroboros Genesis and peer-sharing:

Federated: introduced in the Byron development phase in 2017, IOG core and relay nodes maintained the network and connected users, wallets, and exchanges.

Hybrid: since the Shelley development phase in 2020, block-producing nodes send and receive communications through trusted relays and/or a manual community-developed and managed tool called the topology updater.

Dynamic P2P: currently being released, Dynamic P2P provides automation and resilience to optimize network performance. SPO relays can automatically connect to each other through self-discovery and optimization.

Ouroboros Genesis: in development. Anyone running their own node or Daedalus wallet will connect to a fully decentralized and self-organized network.

Peer sharing: in development. Peer sharing will facilitate the discovery of potential peers that are not registered on the chain within the overall Cardano node network. This phase will also allow anyone to contribute to running the network, rather than just using resources from SPOs.

The current network state: hybrid mode

Currently, block-producing nodes require both incoming and outgoing connections to receive and propagate blocks. However, the selection (in the configuration) of these connections is a manual task done with the topology updater tool. This tool helps SPOs to configure their nodes to connect to other nodes in the network and also receive updates about network changes (eg, stake, performance, or availability).

SPOs need to spend time and effort running the tool manually. When updating their relays, SPOs also need to ensure that their block-producing nodes are connected to the network, otherwise, they may miss a block-producing slot and any rewards.

Dynamic P2P automates connectivity

Dynamic P2P enables automated connection of SPO relays to each other through self discovery and optimization, thus removing the need for static configuration and the manual SPO maintenance required by the hybrid setup. P2P makes the network more performant and resilient to changes such as node or routing failures, and also streamlines the flow of information between the thousands of distributed nodes.

How does Dynamic P2P work?

P2P doesn’t just automate the selection of the static configuration, it is more dynamic than that. Currently, SPOs might configure a node to connect to, for example, 50 other SPO nodes. This is a pretty large number, since many nodes can be offline, change their addresses, etc. While 20 connections are enough for efficient communication, SPOs may have to over-provision because of the static configuration.

In a Dynamic P2P setup, SPOs can target to configure 20 connections, which can be picked from thousands of SPO relays, not just 50. And if any are offline, or go offline, the setup will automatically pick new ones, to meet the set target. This means that the configuration is no longer limited to a static pool of 50 peers.

P2P also allows for more sophisticated configurations for direct peering arrangements between SPOs. For example, if two SPOs want to maintain a connection between their relays, and each has two relays, they can configure a group of peers that lists the other SPOs’ two relays but with a target that there should be at least one connection. This means that there is no need for over-provisioning, and SPOs still get automatic failover if one relay goes down. With static configuration, one had to choose between listing only one and thus not getting resilience, or listing both and over-provisioning (using more resources).

Finally, P2P optimizes the selection of peers to minimize the overall diffusion time in the whole network. It does this continuously and automatically. Internal IOG research shows that a policy based purely on local information can achieve a global outcome close to optimal. It measures the frequency with which peers are the first to provide a block header that later ends up in the chain. Peers that are least useful by this metric are periodically ‘churned out’ and replaced by other randomly selected peers. Simulation results show that this simple optimization procedure method reaches a near optimal global outcome within a relatively small number of iterations, on the order of 24 hours.

See this technical specification for more details.

We’re continuing to share further updates with the SPO community and invite everyone to join the SPO Telegram group and Discord channel for technical discussions.


Dynamic P2P is available on mainnet

A Cardano ecosystem interface map showing all projects and DApps on the Cardano blockchain accessible at DCOne Crypto. Explore the latest projects in the Cardano ecosystem and discover the potential of blockchain innovation.


DCOne Crypto

DCOne Crypto allows connecting webhook api for developers to receive information on changing stake balance on Cardano blockchain

Notification of stake addresses tracking via Webhook, API (Announcement of webhook activity payment stake addresses)

Read more: https://docs.dconecrypto.finance/notify/webhooks

Document Github: https://github.com/DCOneCrypto/StakeAddress-Tracking-Webhook-API

Note: Create an account before using the APIs

Create an account: Mainnet https://dconecrypto.finance

Note: Website direct menu (please login before):

Live: Mainnet https://dconecrypto.finance/DC\_WebhookWallets

REST API

Network: Mainnet Endpoint: https://dconecrypto-mainnet.dconecrypto.finance/

Credentials when using API



Authenticate

Example api request:

Required field: userNameOrEmailAddress , password



Example api Authenticate responses



Create a new webhook (CreateOrEdit)

Once a payment is detected in the stake address, it will be activated and the webhook call will work

Example api request:



List of webhook connections (GetAll)

Get a list of all webhooks connected to the system

Example api request:



Example api response:



Get detailed information of a webhook (GetDC\_WebhookWalletForEdit)

Get a list of all webhooks connected to the system

Example api request:



Remove webhooks (Delete)

Remove 1 webhook information and don't trigger notification when stake address payment

Example api request:



Get userId by token (GetAllUserForTableDropdown)

Get the userId variable and put in the userId input parameter in the "CreateOrEdit" api



Example success response:



Example error response:



Trigger webhook callback and return data results

Note: Trigger webhook callback (result webhookUrl in CreateOrEdit api) and data result returned



Application GUI Screenshots\_1

Application GUI Screenshots\_2

Application GUI Screenshots\_3
Application GUI Screenshots\_4

Application GUI Screenshots\_5


How to listen to the balance of the blockchain Stake Key address in real time on Cardano using DCOne Crypto Webhook

CORE TECHNOLOGY

Over the last two weeks, the ledger team focused on CIP-1694 making a major update to the Conway era to ensure that the implementation follows the specification for the ratification and enactment logic. They also integrated ledger updates into consensus and node and worked on the Conway infrastructure testing. 

The networking team ​​focused on bug fixing, the implementation of Eclipse Evasion, simulation testing improvements, and mini-protocol extensions. They also published ouroboros-network-0.4.0.1 and ouroboros-network-protocols-0.3.0.0 to CHaP, and fixed a bug in cardano-node (failure to configure inbound connection limits). 

Finally, they implemented stricter validation of DNS names, IP addresses, and ports on cardano-cli to prevent common on-chain mistakes when registering a stake pool.

The consensus team continued working on refactoring and improving the UTXO-HD prototype, and introducing improvements to lmdb-related packages. In particular, they identified an opportunity to gain performance by handling locks more optimally.

On the Genesis front, the team sketched a mitigation for an issue caught by PNSol and researchers. They also came up with a roadmap for testing the Genesis prototypes and enriching the existing tests.

The team also addressed the technical debt, made some minor improvements, and created component-level micro-benchmarks for adding transactions to the mempool. The results of these benchmarks will be published in the ouroboros-consensus web page.

Finally, they finished moving the consensus documentation to the ouroboros-consensus repository, released ouroboros-consensus 0.3.0.0, and reduced the time GitHub actions take in ouroboros-network.

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

WALLETS AND SERVICES 

This week, the Daedalus team finished implementing support for Ledger v.6.0.3, and are now planning a regression test for next week.

Work is ongoing on the Lace desktop development. The team added collateral support for the CIP-30 implementation of the DApp browser and a grace waiting time for the cardano-node process to be shut down before closing Lace desktop. Finally, they solved incompatibility issues with some UI components shared with Lace browser extension.

The Lace team have been busy fixing bugs and adding new features before the browser extension release on mainnet. The new v.0.6.0 release brings CIP-30 implementation to Lace, which enables trying out the DApp connector and interacting with Cardano DApps. The team also fixed some bugs with Ledger hardware wallet support to connect Ledger with the DApp connector. The switch between the preview and pre-production networks is now ready too. Get the Lace extension at lace.io today and stay tuned for updates!

SMART CONTRACTS

This week, the Plutus team kept working on the Plutus debugger, script capacity increase, documentation improvements, and Marconi development. 

The Marlowe team addressed resource exhaustion in marlowe-chain-sync. They also updated multiple components to use the Marlowe Runtime protocol:  marlowe-apps, marlowe-integration, marlowe-web-server, and Marlowe CLI. The team implemented the Runtime proxy server, added four endpoints for withdrawals to REST API, and rewrote the withdrawal query to accept an optional set of role currencies to filter the results by different parameters. The team improved and automated different end-to-end tests, assessed options for replacing Plutus association map in validator, and added support for Merkleization of Marlowe contracts generated from ACTUS contract terms.

Finally, they fixed a discrepancy with division rounding between the Isabelle specification and PureScript.

BASHO (SCALING)

The Hydra team released hydra-node version 0.9.0, which includes fully specified behavior of on-chain scripts and off-chain head-logic, decreased costs for opening or closing a head, scalable contestation deadline semantics, and more. See the release notes for details.

They also published the February monthly report reflecting on the Hydra project development and further plans. The team is now planning to extend review meetings with a wider audience by inviting more participants through the new Hydra #announcements Discord channel. Stay tuned for updates!

The Mithril team finished deploying the era activation mechanism in the preview testing environment as well as preparing the upgrade procedure for the SPOs. They are actively working on deploying this mechanism on the pre-release-preview and release-preprod networks where signers are run by the SPOs. The team also completed the refactoring of the handling of critical errors in the signer and aggregator state machines. Additionally, they continued the deployment of a new test network that runs on Cardano mainnet and computes the stake distribution with the optimized unreleased Cardano CLI command.

Finally, they finished designing the certification of generic types of data by a Mithril network and started implementing its first phase.



コアテクノロジー

この2週間、台帳チームはCIP-1694に焦点を当て、Conway期を大幅に更新し、実装が承認および制定ロジックの仕様に準拠するようにしました。台帳の更新をコンセンサスとノードに統合し、Conwayインフラのテストに取り組みました。 

ネットワーキングチームは  バグの修正、Eclipse回避の実装、シミュレーションテストの改善、ミニプロトコルの拡張に焦点を当てました。ouroboros-network-0.4.0.1とouroboros-network-protocols-0.3.0.0をCHAPに公開し、cardano-nodeのバグ（着信接続制限の設定失敗）を修正しました。 

ステークプールを登録する際の一般的なオンチェーンミスを防止するために、cardano-cliでDNS名、IPアドレス、ポートの検証の厳密性を上げて実装しました。

コンセンサスチームは、UTXO-HDプロトタイプのリファクタリングと改良に引き続き取り組み、lmdb関連パッケージの改善を導入しました。特に、ロック処理の最適化を高めることでパフォーマンスを向上させる機会を特定しました。

Genesisに関しては、PNSolと研究者によって発見された問題の緩和策をスケッチしました。Genesisプロトタイプのテストと、既存のテストを充実させるためのロードマップも作成しました。

技術負債に対処し、軽微な改良を行い、メモリープールにトランザクションを追加するためのマイクロベンチマークをコンポーネントベルで作成しました。ベンチマークの結果は、ouroboros-consensusウェブページで公開されます。

コンセンサスドキュメントをouroboros-consensusリポジトリに移動し、ouroboros-consensus 0.3.0.0をリリースし、ouroboros-networkでのGitHubアクションの実行時間を短縮しました。

通常通り、チーム別の詳細はこちらの技術開発レポートをご覧ください。

ウォレットとサービス 

DaedalusチームはLedger v. 6.0.3のサポートの実装を完了しました。現在来週の回帰テストを計画しています。

Laceデスクトップの開発作業は進行中です。DAppブラウザーのCIP-30実装のための付随的なサポートと、Laceデスクトップを閉じる前にcardano-nodeプロセスがシャットダウンされるまでの猶予待機時間を追加しました。Laceブラウザー拡張機能で共有されている一部のUIコンポーネントの非互換性の問題を解決しました。

Laceチームは、ブラウザー拡張機能のメインネットリリース前に、バグの修正と新機能の追加に追われました。新しいv.0.6.0リリースでは、LaceにCIP-30が実装され、DAppコネクターの試用やCardano DAppsとのインタラクションが可能になりました。LedgerをDAppコネクターに接続するために、Ledgerハードウェアウォレットサポートのバグを修正しました。プレビューネットワークとプリプロネットワークの切り替えも可能になりました。lace.ioでLace拡張機能を今すぐ入手して、更新情報をお楽しみください。

スマートコントラクト

Plutusチームは、Plutusデバッガー、スクリプト容量増加、ドキュメントの改良、Marconi開発への取り組みを続けました。 

Marloweチームは、Marlowe-chain-syncのリソースの枯渇に対処しました。また、Marlowe Runtimeプロトコルを使用するために、marlowe-apps、marlowe-integration、marlowe-web-server、Marlowe CLIの各コンポーネントを更新しました。Runtimeプロキシサーバーを実装し、REST APIに引き出し用の4つのエンドポイントを追加し、引き出しクエリを書き直して、さまざまなパラメーターで結果をフィルタリングする機能を持つオプションの通貨セットを受け入れるようにしました。さまざまなエンドツーエンドテストを改良および自動化し、バリデーターでPlutusアソシエーションマップを置き換えるためのオプションを評価し、ACTUSコントラクト条件から生成されたMarloweコントラクトのマークル化サポートを追加しました。

Isabelle仕様とPureScript間の除算の丸めに関する不一致を修正しました。

Basho( スケーリング)

Hydraチームは、hydra-node 0.9.0をリリースしました。このバージョンには、オンチェーンスクリプトとオフチェーンヘッドロジックの動作の完全指定、ヘッドの開閉にかかるコストの削減、スケーラブルな競合デッドラインセマンティクスなどが含まれています。詳細はリリースノートをご覧ください。

Hydraプロジェクトの開発と今後の計画を反映した2月の月次報告書を公開しました。現在、新しいHydra #announcements Discordチャネルを使ってより多くの参加者を招待することで、レビューミーティングをより多くのユーザーに拡大することを計画しています。更新情報をお見逃しなく。

Mithrilチームは、プレビューテスト環境に開発期アクティベーションメカニズムを導入し、SPOの更新手順の準備を完了しました。SPOによって署名者が実行される「プレリリースプレビュー」および「リリースプリプロ」ネットワークにこのメカニズムを導入することに積極的に取り組んでいます。署名者ステートマシンとアグリゲーターステートマシンのクリティカルエラー処理のリファクタリングも完了しました。Cardanoメインネット上で動作し、最適化された未リリースのCardano CLIコマンドを使用してステーク分布を計算する新しいテストネットワークのデプロイを継続しました。

Mithrilネットワークによる汎用型データ認証の設計を完了し、実装の第1段階を開始しました。


Weekly development report as of 2023-03-10

This is a common question from people who are new to Cardano, who are familiar with staking on other blockchains, or who are moving their funds from an exchange to a self-custodial wallet such as Daedalus, Eternl, Flint, Typhon, Yoroi, and others.

As Cardano is a proof of stake (PoS) blockchain, it relies on holders  delegating their ada to stake pools to secure the blockchain. In return they delegators are rewarded with ada. As Cardano relies on delegators taking part in this process it has been designed to be very secure.

When a delegator stakes their ada on Cardano their funds do not leave their wallet, the staking mechanism therefore does not put the delegator's ada at risk.

Staking is liquid, which means ada is not locked up for any period, delegators can move or spend their ada whenever they like.

The worst thing that could happen is that a stake pool underperforms, in which case a delegator may not receive all of the staking rewards. Even if this happens, the ada in the delegator's wallet is not at risk of being slashed or penalized in any way.

In line with the ethos of cryptocurrency and blockchain technology, staking is completely trustless and staking rewards are distributed automatically by the protocol.

A delegator can move to a new stake pool whenever they wish.

You can stake while using a hardware wallet and it is advisable to use one for extra security. See 'Should I get a hardware wallet?'


Is my ada safe when staking?

Staking rewards left in the rewards section of your wallet count towards your total balance staked. They therefore automatically compound without the need to withdraw them to the main part of your wallet. Each time you withdraw your staking rewards you will pay a transaction fee, which at the time of writing this is around 0.17 ada. This might not seem like a lot but it could add up over time. So it's best to leave your rewards in your rewards address until you need them.

As your staking rewards are held in the rewards address of your wallet, and not by the stake pool, you do not need to withdraw your staking rewards when delegating from one stake pool to another. You also do not need to withdraw your rewards when switching to a new wallet interface.

Some wallets offer an option to withdraw rewards at the same time as making a transaction. This reduces the withdrawal fee to a fraction of what you would normally pay to withdraw your rewards.


When should I withdraw my staking rewards?

Depegging: The stablecoin kryptonite

Stablecoins are cryptocurrencies designed to maintain price stability and are pegged to an external asset. These assets are viewed as one of the backbones of cryptocurrency and DeFi but can face the risk of depegging if not properly managed. Depegging refers to the phenomenon of a stablecoin deviating from its intended peg. We saw a hallmark example of a catastrophic depegging with Terra and its algorithmic stablecoin LUNA’s UST. This was a result of a concentrated selling of UST combined with a lack of reserves and liquidity that disabled the issuer from being able to maintain its peg. 

USDA, Cardano’s native stablecoin, is fully backed 1:1 to USD. The difference between algorithmic stablecoin UST and fiat-backed USDA is that a fiat-backed stablecoin losing its peg has a much higher probability of returning 1:1 to its paired asset because it’s entirely backed by cash or cash-like reserves. An algorithmic design, which relies on math and code to balance stablecoin issuance against tokenized collateral, may not be as reliable as USDA to regain its peg. Because USDA is fully backed 1:1 to deposits, the USDA stablecoin has been designed to maintain stability, even in the face of market fluctuations. That design is on purpose and is the key to the stablecoin’s stability – the antidote to the kryptonite in this analogy. 

USDA’s stablecoin design mitigates risk

A major depegging event could result from a large-scale cash-out where a plurality of USDA holders “rush” to cash out their assets to a different currency (fiat or another asset). The supply and demand dynamics are the same as any other cryptocurrency, thus creating prices higher or less than $1 at any given time. But any depegging on USDA should be temporary, in the event it takes place. The USDA stablecoin is designed to operate by minting or burning USDA coins at a fixed exchange rate of 1 USDA to 1 USD based on user demand, ensuring that each USDA coin is backed by a corresponding US dollar held by our regulated US banking partner.

Fundamentally, all stabilization techniques are based on the elementary economic model of supply and demand. The key to avoiding depegging is understanding how reserves are managed to ensure 1:1 backing. Asset liquidity becomes key here. The pegged USD is custodied by a regulated US banking partner who keeps proper accounting of the cash reserves, making funds available at a moment’s notice. In the event of market volatility causing our stablecoin to depeg below a dollar, EMURGO or any other party would be in a position to purchase USDA on the market and sell it on Anzens, presenting a low-risk arbitrage opportunity.  We will provide further information on our reserves in the coming months, including monthly attestation reports – which are reports that are used to provide a snapshot of the reserves and assets that back USDA – and a technical whitepaper. 

Mitigating risk as it relates to USDA is critical to not only the health of the Cardano ecosystem, but also to its utility in achieving the vision of EMURGO Fintech’s Anzens platform, which includes a suite of Web3 enterprise and individual financial services applications. 

Read more: How fiat-backed stablecoins like USDA benefit the Cardano blockchain ecosystem

There is no one-size-fits-all. But USDA fits most.

It is unlikely that a single design is optimal for all use cases. Which stablecoin is best depends upon a wide variety of competing factors, including intended use, degree of desired trust minimization and decentralization, regulatory jurisdictional compliance, and scalability. The Cardano ecosystem supports a number of stablecoin designs for this very reason.

EMURGO Fintech’s USDA provides Web3 organizations and individuals with a viable option to shelter from market volatility and will usher in more opportunities for real-world use cases. And with the Anzens platform and product suite, USDA will be the stable asset that provides interoperability between traditional finance and decentralized finance.

About USDA, Cardano’s Native Fiat-Backed Stablecoin

!\[$USDA-Cardano-Blockchain-Stablecoin]\(https://emurgo.io/wp-content/uploads/2022/12/USDA-1024x218.png "Maintaining Stability: How Cardano's Fiat-Backed USDA Stablecoin Handles Depegging 1")

USDA – Cardano’s regulatory-compliant USD-backed stablecoin for the ecosystem – is scheduled to launch in early 2023 and bring value to Cardano’s Web3 ecosystem of decentralized applications. USDA will be a native token to the Cardano blockchain that is backed 1:1 by real-world reserves. It’s meant to be a stable asset that can unlock fast global transactions without legacy banking and payment infrastructure delays. USDA is the key that will unlock all the future use cases and applications that will be available on Anzens.

Join the waitlist now at Anzens to be ready for USDA.

\_This article originally appears here.

About USDA

Official Homepage: anzens.com

Twitter: @AnzensOfficial

About EMURGO

Official Homepage: EMURGO.io

Twitter (Global): @EMURGO\_io

YouTube: EMURGO channel

Discord: EMURGO Community

Facebook: @EMURGO.io

Instagram: @EMURGO\_io

LinkedIn: @EMURGO\_io

\*\*

Manteniendo la estabilidad: cómo la moneda estable USDA de Cardano, respaldada por Fiat, maneja la desvinculación\*\*

Una imagen sobre la moneda estable USDA de Cardano, en espanol

Índice

Desvinculación: La criptonita de las monedas estables

El diseño de la moneda estable USDA minimiza el riesgo

No existe una talla única. Pero USDA se adapta a la mayoría.

Sobre USDA, la moneda estable nativa de Cardano respaldada por fiat

Desvinculación: La criptonita de las monedas estables

Las stablecoins \[o monedas estables en español] son criptomonedas diseñadas para mantener la estabilidad de precios y están vinculadas a un activo externo. Se considera que estos activos son una de las columnas vertebrales de las criptomonedas y la financiación descentraliza (DeFi), pero pueden enfrentarse al riesgo de desvinculación si no se gestionan adecuadamente.

Depegging \[“despegarse” o “desvincularse” en español] se refiere al fenómeno de que una moneda estable se desvíe de su vinculación.

Hemos presenciado un ejemplo emblemático de desvinculación catastrófica con Terra y UST de su moneda estable algorítmica LUNA, a consecuencia de una venta concentrada de UST combinada con una falta de reservas y liquidez que impidió al emisor poder mantener su paridad.

USDA, la moneda estable nativa de Cardano, cuenta con un respaldo total 1:1 a USD. A diferencia de la moneda estable UST algorítmica y la USDA respaldada por fiat, una moneda estable respaldada por fiat que pierde su paridad tiene una probabilidad mucho mayor de volver 1:1 a su activo emparejado porque está totalmente respaldada por efectivo o reservas similares al efectivo. Es posible que un diseño algorítmico, que se basa en las matemáticas y el código para equilibrar la emisión de moneda estable frente a la garantía tokenizada, no sea tan fiable como la USDA para recuperar su paridad. Dado que la USDA está totalmente respaldada 1:1 por los depósitos, la moneda estable USDA ha sido diseñada para mantener la estabilidad, incluso frente a las fluctuaciones del mercado. Ese diseño es a propósito y es la clave de la estabilidad de la moneda - el antídoto contra la criptonita en esta analogía.

El diseño de la moneda estable USDA minimiza el riesgo

Podría producirse un acontecimiento de desvinculación \[perder la paridad] importante como consecuencia de una retirada de efectivo a gran escala en la que una pluralidad de titulares de USDA se “apresurara” a cambiar sus activos a una divisa diferente (fiat u otro activo). La dinámica de la oferta y la demanda es la misma que la de cualquier otra criptomoneda, creando así precios superiores o inferiores a 1$ en un momento dado. Pero cualquier desvinculación de la USDA debería ser temporal, en el caso de que se produzca. USDA está diseñada para funcionar acuñando o quemando monedas USDA a un tipo de cambio fijo de 1 USDA por 1 USD en función de la demanda de los usuarios, garantizando que cada moneda USDA esté respaldada por un dólar estadounidense correspondiente en poder de nuestro socio bancario estadounidense regulado.

En esencia, toda técnica de estabilización se basa en el modelo económico de la oferta y la demanda. La clave para evitar la depreciación es comprender cómo se gestionan las reservas para garantizar un respaldo 1:1. La liquidez de los activos se convierte aquí en la clave. El dólar vinculado está custodiado por un socio bancario estadounidense regulado que lleva una contabilidad adecuada de las reservas en efectivo, lo que permite disponer de los fondos en cualquier momento. En caso de que la volatilidad del mercado hiciera que nuestra moneda estable descendiera por debajo de un dólar, EMURGO o cualquier otra parte estaría en posición de comprar USDA en el mercado y venderla en Anzens, presentando una oportunidad de arbitraje de bajo riesgo. En los próximos meses, ofreceremos más información sobre nuestras reservas, incluidos los informes mensuales de atestación - que son informes que se utilizan para ofrecer una instantánea de las reservas y los activos que respaldan al USDA - y un informe técnico.

Atenuar el riesgo en lo que respecta a la USDA es fundamental no solo para la salud del ecosistema Cardano, sino también para su utilidad en la consecución de la visión de la plataforma Anzens de EMURGO Fintech, que incluye un conjunto de aplicaciones Web3 empresariales y de servicios financieros individuales.

Si desea consultar más información, considere leer el siguiente artículo:

:es: Qué ventajas aportan a Cardano las monedas estables algorítmicas y respaldadas por fiat como USDA y DJED .

No existe una talla única. Pero USDA se adapta a la mayoría.

Resulta improbable que un único diseño sea óptimo para todos los casos de uso. Qué moneda estable es mejor depende de una amplia variedad de factores que compiten entre sí, como el uso previsto, el grado de minimización de la confianza y descentralización deseado, el cumplimiento de las jurisdicciones reguladoras, y la escalabilidad. El ecosistema Cardano admite varios diseños de stablecoin por esta misma razón.

La moneda estable USDA de EMURGO Fintech ofrece a las organizaciones Web3 y a los particulares una opción viable para refugiarse de la volatilidad del mercado y dará paso a más oportunidades para casos de uso en el mundo real. Y con la plataforma y el conjunto de productos de Anzens, la USDA será el activo estable que ofrezca interoperabilidad entre las finanzas tradicionales y las descentralizadas.

Sobre USDA, la moneda estable nativa de Cardano respaldada por fiat

$USDA-Cardano-Blockchain-Stablecoin

USDA -moneda estable de Cardano respaldada por USD que cumple con la normativa para el ecosistema- se lanzará a principios de 2023 y aportará valor al ecosistema Web3 de Cardano de aplicaciones descentralizadas. USDA será un token nativo de la cadena de bloques de Cardano que estará respaldado 1:1 por reservas del mundo real. Se pretende que sea un activo estable que pueda desbloquear transacciones globales rápidas sin los retrasos de las infraestructuras bancarias y de pago tradicionales. La USDA es la llave que desbloqueará todos los futuros casos de uso y aplicaciones que estarán disponibles en Anzens.

Únase desde ahora a la lista de espera en https://www.anzens.com 2 para estar preparado para la USDA.

Sobre USDA

Sitio Web Oficial: anzens.com 2

Twitter: @AnzensOfficial

Sobre EMURGO

Sitio Web Oficial: EMURGO.io

Twitter (Global): @EMURGO\_io

YouTube: EMURGO channel

Discord: EMURGO Community

Facebook: @EMURGO.io

Instagram: @EMURGO\_io

LinkedIn: @EMURGO\_io

Traducción al español de “Maintaining Stability: How Cardano’s Fiat-Backed USDA Stablecoin Handles Depegging” 1, escrito por @EMURGO\_io, en marzo 6 de 2023.


Maintaining Stability: How Cardano’s Fiat-Backed USDA Stablecoin Handles Depegging

ISPO is an acronym for Initial Stake Pool Offering. There are two main types but in both cases they enable projects that are building on Cardano to distribute their tokens to stake pool delegators. The tokens that are distributed generally have some sort of utility such as governance privileges in the project. The tokens can be held by the delegator for the utility or, if listed on one, can be traded on an exchange.

Community building ISPO

This type of ISPO uses the existing stake pool operator community to help raise awareness of and build a community around a project. A number of stake pools are selected to partner with the project and delegators of the partnered stake pools receive, or are able to claim, the project's token and also receive their regular staking rewards in ada. Stake pools are able to attract new delegators by being able to offer this extra incentive to join them. In an attempt to attract delegators, the stake pool operators would promote the project that they are partnered with, which would raise the profile of the project.

Fundraising ISPO

This type of ISPO is used to raise funds to finance the build and development of a project. In a fundraising ISPO, the project would run their own stake pools and set a high margin fee, sometimes 100%. The delegators would forfeit some or all of their normal staking rewards in ada in return for the promise of some of the project's tokens at a later date.


What is an ISPO & what are the different types of ISPO?

CORE TECHNOLOGY

This week, the core technology teams continued working on ledger, consensus, and networking improvements. 

The benchmarking team finalized benchmarking runs and analyses for the new SECP primitives and for the upcoming node v.1.35.6 release. The team also performed their first benchmarking runs for UTXO-HD and are currently refining the setup. To improve accessibility, they added introspective capabilities to the new tracing system. More work is ongoing on infrastructure and tooling improvements.

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

WALLETS AND SERVICES 

This week, the Daedalus team worked on adding support for Ledger v.6.0.3.

Work is ongoing on the Lace desktop development. The team continued polishing the DApp browser, which follows the newest v.0.2.0 of CIP-30, and added a banner to display various Cardano node statuses. They also reduced the app's memory consumption, reorganized the translation files' structure, and made significant progress on CI infrastructure issue resolutions. 

The Adrestia team are still working on extending the multi-signature feature with delegation functionality in cardano-wallet. They're also working on extracting the transaction balancing library, and on DBLayer refactoring to improve performance and memory usage.

Finally, the team is preparing cardano-js-sdk for production release.

SMART CONTRACTS

This week, the Plutus team kept enhancing the Plutus debugger and worked on script capacity increase by adding sums and products and incorporating Plutonomy optimizations. The Plutus tools team worked on building indexers for the sidechains team using Marconi. Additionally, they worked on reducing technical debt by providing support for cardano-api in the emulator.

This week, the Marlowe team fixed the traversal of parties to extract roles and public keys and some incorrect asset records for marlowe-chain-indexer. They also handled the epoch-boundary block in chain-indexer tests, ensured that coin selection respects collateral rules, and defined the Marlowe Runtime scaling strategy. The team worked on the creation of a first draft of the Marlowe Starter Kit for demeter.run, added unit tests for buildApplyInputConstraintsV1, and made some table modifications in Marlowe Explorer.

Finally, they introduced basic error reporting to the REST API and fixed db-comparison for the illegal Shelley address.    

BASHO (SCALING)

This week, the Hydra team continued closing various gaps and aligning the implementation of the Hydra Head protocol logic with the specification. They also completed the minting policy implementation, clarified message authentication with researchers, and planned further work for mainnet compatibility. 

Finally, the team progressed on the internal audit and published some auditing guidelines to receive community contributions.

The Mithril team worked on deploying the era activation mechanism to their test networks and preparing the upgrade procedure to be implemented on the signer nodes run by the SPOs. They also refactored the state machines of the aggregator and signer nodes so that they can better handle critical errors, which lead to node panic, from recoverable errors. Additionally, the team started working on the design that will allow a Mithril network to certify generic types of data with a minimum customization effort and only soft updates.

Finally, they started working on a test network running a mainnet Cardano network and fixed a bug that made the client Docker image crash at startup.



コアテクノロジー

コアテクノロジーチームは、台帳、コンセンサス、ネットワークの改良への取り組みを続けました。 

ベンチマークチームは、新しいSECPプリミティブと予定されているノードv.1.35.6リリースのベンチマーク実行と分析を完了しました。UTXO-HDの最初のベンチマークランを実行し、現在セットアップを改良しています。アクセシビリティを向上させるために、新しい追跡システムにイントロスペクティブ機能を追加しました。インフラとツールの改良に向けて、さらに多くの作業が進行中です。

通常通り、チーム別の詳細はこちらの技術開発レポートをご覧ください。

ウォレットとサービス 

Daedalusチームは、Ledger v. 6.0.3のサポートの追加に取り組みました。

Laceデスクトップの開発作業は進行中です。CIP-30の最新バージョン0.2.0に続くDAppブラウザーの改良を続け、さまざまなCardanoノードのステータスを表示するバナーを追加しました。アプリのメモリ消費量を削減し、翻訳ファイルの構造を再編成し、CIインフラの問題解決に大きな進展をもたらしました。 

Adrestiaチームは、cardano-walletのマルチシグ機能を委任機能で拡張する作業を続けています。トランザクション残高ライブラリーの抽出作業、パフォーマンスとメモリー使用量を改善するためのDBLayerのリファクタリングに取り組んでいます。

cardano-js-sdkの本番リリースを準備しています。

スマートコントラクト

Plutusチームは、Plutusデバッガーの機能強化を続け、SUMと製品を追加し、Plutonomy最適化を組み込むことでスクリプト容量を増やす作業に取り組みました。Plutusツールチームは、Marconiを使用してサイドチェーンチームのインデクサー構築に取り組みました。エミュレーターでcardano-apiのサポートを提供することで、技術負債の削減に取り組みました。

Marloweチームは、Marlowe-chain-indexerの役割と公開鍵、およびいくつかの誤った資産レコードを抽出するために、当事者のトラバーサルを修正しました。chain-indexerテストのエポック境界ブロックを処理し、コイン選定が担保ルールを遵守するようにし、Marlowe Runtimeスケーリング戦略を定義しました。demeter.run用のMarlowe Starter Kit初回ドラフトを作成し、buildApplyInputConstraintsV1のユニットテストを追加し、Marloweエクスプローラーに変更を加えました。

REST APIに基本的なエラー報告を導入し、不正なShelleyアドレス用のdb-comparisonを修正しました。    

Basho( スケーリング)

Hydraチームは、Hydra Headプロトコルロジックの実装と仕様のさまざまなギャップを埋め、調整する作業を続けました。ミントポリシーの実装を仕上げ、研究者とメッセージ認証を明確にし、メインネットの互換性に関する今後の作業を計画しました。 

内部監査を進め、コミュニティの貢献を受けるための監査ガイドラインをいくつか公開しました。

Mithrilチームは、ERAアクティベーションメカニズムをテストネットワークにデプロイし、SPOが実行する署名者ノードに実装するアップグレード手順を準備しました。アグリゲーターノードと署名者ノードのステートマシンをリファクタリングして、回復可能なエラーからノードパニックを引き起こす重要なエラーをより適切に処理できるようにしました。Mithrilネットワークが最小限のカスタマイズ労力とソフトアップデートだけで汎用タイプのデータを認証できるようにする設計に取り組み始めました。

Cardanoのmainnetネットワークを実行しているテストネットワークの作業を開始し、起動時にクライアントDockerイメージがクラッシュするバグを修正しました。


Weekly development report as of 2023-03-03

If you're wondering whether you need a hardware wallet, the answer is probably yes. If you have an amount of cryptocurrency that you worry about losing, you should probably get one.

Using a Cardano wallet interface such as Yoroi, Daedalus, Flint, Eternl, etc. without a hardware wallet means that the cryptographic keys to your on-chain wallet are stored on your computer or mobile phone. The only thing protecting your wallet keys in this scenario is your spending password, and as the device is connected to the internet this leaves your wallet vulnerable to hacking attempts. A hacker could potentially decrypt your wallet keys and sign a transaction, sending all of your funds to themselves.

If you connect a hardware wallet such as a Ledger or Trezor device to one of the wallet interfaces mentioned above, the cryptographic keys to your wallet are stored on the hardware wallet itself. In this scenario, your cryptographic keys are never exposed to the internet-connected device and physical access to the device is required to sign a transaction. This makes your cryptocurrency wallet a lot more secure.

Hardware wallets also allow you to switch between wallet interfaces without having to type in your seed phrase. Every time you type your seed phrase into an internet-connected device, you are putting your wallet at risk. With a hardware wallet you can just pair it to the new wallet interface and you're good to go.


Should I get a hardware wallet?

Input Output Global (IOG) a réuni une équipe d'ingénieurs spécialisés pour utiliser la base solide de Cardano afin de créer une boîte à outils pour la construction de chaînes latérales (dites "sidechains") personnalisées. À l'aide de cette boîte à outils, ils ont construit un testnet public sidechain-compatible avec la machine virtuelle Ethereum (EVM) comme preuve de concept. Les sidechains rendent Cardano extensible et plus évolutif sans compromettre la stabilité ou la sécurité de la chaîne principale.

Extension de Cardano avec des sidechains

Cardano est une blockchain de troisième génération, basée sur des recherches universitaires et écrite en Haskell pour etablir une preuve mathématique d'exactitude.

La décentralisation, la sécurité et l'évolutivité du protocole de consensus Ouroboros ont été prouvées à grande échelle et en volume par des milliers Stake pools indépendants et des millions d'adresses de portefeuille pendant plus de cinq ans. Le réseau fonctionne sans défaillance depuis sa création en 2017.

La décentralisation et l'interopérabilité sont essentielles pour l'avenir de la blockchain. Ces fonctionnalités garantissent qu'aucune personne ou entité ne peut contrôler une blockchain ou être limitée à un seul écosystème. Pour se développer, d'un point de vue technique et social, la plupart des applications et des communautés doivent être dotées de leur propre souveraineté et de leurs propres choix de conception.

Pour permettre cet environnement interopérable, IOG a travaillé sur la création d'une boîte à outils pour construire une famille de sidechains. Avec cette boîte à outils, n'importe qui peut commencer à tirer parti de la sécurité et de l'infrastructure de Cardano pour créer des sidechains spécifiques à leurs missions. Les Chaîne latérale EVM prouve la faisabilité de ce concept. Tout ce travail est partagé avec la communauté Cardano et sera entièrement open source. La première étape a été la démonstration de l'application EVM à IO ScotFest à Edinburg fin novembre 2022. IOG a mis à disposition la première tranche de documentation formelle.

À propos de la boîte à outils

Une sidechain est simplement une blockchain qui dépend de sa chaîne principale et qui lui est connectée.

La boîte à outils permet à la sidechain d'avoir son propre algorithme de consensus et ses propres fonctionnalités. La sidechain est connectée à la chaîne principale via un pont qui permet le transfert d'atouts entre les chaînes. La finalité des blocs est déterminée par un mécanisme de consensus qui repose sur la sécurité de la chaîne principale.

La boîte à outils est composée de :

Scripts Plutus de la chaîne principale: Ces scripts s'exécutent sur la chaîne principale de Cardano, permettent des transactions inter-chaînes sécurisées et des mouvements de tokens, et utilisent les procédures de minting pour prendre en charge le token de la chaîne latérale.

Un suiveur de chaîne: Le suiveur de chaîne suit les données et les événements de la chaîne principale qui régissent la chaîne latérale. Dans la version v1 de la boîte à outils, il s'agit d'un Cardano instance de synchronisation de base de données.

Le module de chaîne latérale: Ce module fait partie du client sidechain. Il interprète les données de la chaîne principale et met en œuvre les adaptations nécessaires du grand livre.

La boîte à outils est également livrée avec un document de spécification technique contenant une introduction et un guide des sidechains Cardano. Les blocs de construction de la boîte à outils sont conçus pour donner des pouvoirs aux développeurs. Quelques exemples:

Déplacer des données et des atouts entre la chaîne principale et la chaîne latérale personnalisée.

Prendre en charge divers protocoles de consensus, règles du ledger et langues.

Sécuriser le lancement de sidechains.

Sécuriser les petites chaînes.

Permettre l'expérimentation, l'incubation et la recherche.

L'application sidechain EVM est disponible en tant que testnet publique. Les développeurs peuvent l'essayer en exécutant quelques applications Solidity pour avoir une idée de son potentiel. Les développeurs de DApp utilisant la sidechain EVM doivent noter que les données doivent être considérées comme finales sur la chaîne principale avant d'être déplacées vers la sidechain.

Utilisation des composants de la boîte à outils sidechain

Les développeurs de chaînes de blocs, les développeurs d'applications distribuées (DApp), les stake pool operators (SPO) et les utilisateurs de DApp peuvent tous bénéficier de sidechains personnalisées. Les développeurs peuvent utiliser la boîte à outils pour créer des blockchains pour des cas d'utilisation spécifiques basés sur la sécurité et la décentralisation de Cardano.

Les chaînes de blocs créées de cette manière peuvent tirer parti du soutien de la communauté SPO existante et bénéficier de la communauté enthousiaste des followers de Cardano.

Pour les développeurs  de DApps, les sidechains personnalisées offrent des avantages en termes d'interopérabilité, d'évolutivité, de testabilité et de compatibilité.

Interopérabilité

La forme de communication la plus basique entre une chaîne principale et une chaîne secondaire est l'échange d'atouts. Étant donné que les atouts conservent leur nature lorsqu'ils sont transférés vers la sidechain, ils peuvent être retransférés tout aussi facilement. Un mécanisme de pont permet cette communication. Tant que les deux chaînes sont sécurisées, cette sécurité est répercutée sur les transferts dans les deux sens.

La communication entre la chaîne principale et la chaîne latérale leur permet de conserver leurs propres protocoles de consensus (qu'ils soient modifiés) et leurs formats de bloc tout en continuant à travailler ensemble, donnant ainsi access à une plus large gamme d'applications.

Évolutivité

Tout comme un chef de projet a le choix entre bon, rapide ou bon marché (choisissez-en deux), une blockchain a le choix entre trois objectifs concurrents : la décentralisation, la sécurité et l'évolutivité.

Étant donné que les sidechains peuvent être spécifiques à un domaine d'application, les transactions peuvent être effectuées plus rapidement, soulageant la chaîne principale de cette charge. L’amélioration de l'évolutivité des sidechains ne compromet pas la sécurité et n'a pas besoin d'affecter la décentralisation.

Testabilité

Les développeurs peuvent tester des DApps pilotes sur des sidechains dédiées. S'il y a une panne nécessitant un redémarrage ou une modification de l'interface avec la chaîne, alors seule la chaîne latérale est affectée, pas la chaîne principale. Cette phase agit comme une étape intermédiaire entre le fonctionnement du testnet et la version complète du réseau principal pour les fonctionnalités expérimentales et les nouvelles applications.

Compatibilité

Les sidechains peuvent exposer la même interface de programme d'application (API) qu'une chaîne existante et utiliser la sécurité et l'efficacité des protocoles de consensus de Cardano. Par exemple, la chaîne latérale Cardano EVM fournit un environnement d'exécution Solidity qui ne nécessite pas de mineurs, mais qui sert toujours les méthodes Ethereum JSON RPC. Les smart contrats Ethereum peuvent fonctionner sans changement, à des frais de gaz considérablement inférieurs.

Pour les SPOs

Les sidechains offrent une opportunité aux SPOs en permettant à leurs pools d'attribuer plus de tokens que juste ada s'ils décident d'exécuter également un nœud de sidechain. Ces tokens spécifiques à la sidechain peuvent servir à différentes fins et à leur tour inciter les délégants à participer au réseau. Selon la façon dont les récompenses sont configurées sur la sidechain, les créateurs de blocs de sidechain peuvent être récompensés par de nouveaux tokens pour construire des blocs, les valider et contribuer à la sécurité du réseau. Tout Cardano SPO peut choisir de valider également les blocs sur la sidechain. S'ils le font, ils peuvent bénéficier de revenus supplémentaires pour fournir des services supplémentaires et utiliser plus de ressources.

Si un SPO choisit de valider les blocs sidechain, il devra fournir des ressources supplémentaires. Un peu d'espace disque est nécessaire pour stocker la sidechain, et ils doivent exécuter deux processus supplémentaires ; un suiveur de chaîne et un nœud de sidechain.

Pour les utilisateurs de DApp

Une plus grande interopérabilité entre les chaînes, des processus de développement simplifiés, plus de plateformes de développement et des frais de transaction réduits ont tendance à augmenter le nombre et la variété des DApp. Plus de sidechains Cardano signifie une plus grande variété de conceptions de chaînes de blocs innovantes, des cas d'utilisation et des récompenses de staking plus élevées, ce qui a tendance à attirer plus de SPO et de délégants, et garantit par conséquent une sécurité accrue et une plus grande décentralisation. Ceci est le potentiel de l'écosystème des sidechains.

Conclusion

La boîte à outils sidechain est la dernière livraison de la roadmap de Cardano au sein de Basho, la phase de mise à l'échelle, introduisant la programmabilité, l’interopérabilité et l’évolutivité plus élevées. Le développement des sidechains ouvre la voie à une adoption massive de Cardano en permettant un débit beaucoup plus élevé sans réduction de la décentralisation ou de la sécurité. Les développeurs de blockchain peuvent créer plus facilement des sidechains personnalisées. À terme, IOG espère voir émerger une famille de sidechains Cardano et de chaînes partenaires.

Le testnet public de la sidechain EVM a été publié, permettant à la communauté de déployer des DApps, de créer des smart contrats et de transférer des tokens entre les chaînes de test.

La boîte à outils publiée en janvier n'est pas une solution complète. Il existe des domaines d'amélioration connus, tels que l'expérience de pont, le mécanisme de récompenses SPO et le modèle de sécurité. Tous ces domaines seront améliorés avec la communauté au fur et à mesure - soigneusement et régulièrement - en collaborant pour obtenir des commentaires, des réflexions et des recommandations.

De nombreuses améliorations peuvent être apportées et il existe de nombreuses façons de gérer une sidechain. Cependant, IOG espére que ce qu'elle a développé en interne fournira un ensemble de capacités de base et posera des bases solides pour créer un ensemble d'outils et apporter de nouvelles améliorations en collaboration avec la communauté.

De la documentation supplémentaire et des didacticiels vidéo seront disponibles en temps voulu. Comme toujours, suivez Les réseaux sociaux d'IOG pour les dernières mises à jour.

Lisez les spécifications techniques de sidechains et la documentation de développement, et rejoignez la chaîne Discord de la communauté technique d'IOG pour de plus amples discussions. Pour les demandes commerciales et de partenariat, contactez IOG via le page de contact.


Toolkit for developing custom sidechains in Cardano (French)

Astarter ISPO Transition Reward Incentive

During the Astarter Ambassador Community Call series (AACC) in March 2022, we embarked on an exploration of ISPOs on Cardano and have since followed through, developing a plan to deliver a two-stage ISPO and Merge Staking Protocol.

We launched the first stage ISPO component (Launchpool) at the end of September 2022 (Epoch 366), enabling staking $ADA to Astarter AA1 stake pool to earn an assignment of $AA tokens.

AA1 stake pool quickly grew and produced the first three blocks in early October 2022 (Epoch 368). Soon after we announced the block genesis $ADA reward share because success is better when shared.

Launchpool has become an integral part of Astarter core product suite for enabling projects launching through Astarter to benefit from our research and development in this area.

We identified the potential for Merge Staking multi-token rewards when we first introduced Astarter ISPO and Merge Staking Protocol in May 2022 and introduced a Framework for Merge Staking Rewards Nov 2022. We look forward to delivering the first multi-token baskets as we transition to Merge Staking.



During the Transition to Merge Staking AA1 stake pool is increasing rewards with an incentive consisting of three incremental tiers to take us into the launch of the Merge Staking Protocol.

TRI 25, AA1 stake pool ISPO base reward increases by 25% and pool $ADA rewards of 25%

TRI 50, AA1 stake pool ISPO base reward increases by 50% and pool $ADA rewards of 50%

TRI 75, AA1 stake pool ISPO base rewards increases by 75% and pool $ADA rewards of 75%



You are probably wondering about the duration and when each tier begins and ends, however unlike stage 1 there is no set duration as the transition coincides closely with Astarter product launches. Methods of staking AA are required for Merge Staking as well as the Token Generation Event. Margin changes are on-chain and we will announce when a change is made and becomes active.

There is a final snapshot for stage 1 scheduled. Snapshots are used for tallying stage 1 bonus rewards and there will be another duration bonus, during the Transition Phase into MSP which will be announced soon for loyal Astartees to enjoy.



To earn AA and ADA during the transition phase simply stake Cardano ADA to AA1 stake pool and watch the rewards pile up!

In summary, the Transition to Merge Staking is an opportunity for ADA holders to earn AA and ADA from staking to AA1 stake pool. TRI is incremental to margin pool decreases giving delegators higher rewards at each tier and duration bonuses will also be applied in the future.

As a final note, there are 3 easy steps to transition into Merge Staking

Stake Cardano ADA to AA1 stake pool

Get AA + ADA rewards

Stake AA to Astarter DeFi and leverage on Merge Staking Rewards.

Thank you for reading and happy staking. 🙂

Astarter Social Links

Website | Twitter | Telegram | Medium | Youtube


Astarter ISPO Transition Reward Incentive

Anzens is a DeFi platform created & operated by EMURGO; one of Cardano's founding entities, that enables Cardano Community to tokenize real-world assets.

Launching in 2023, Anzens users will first be able to mint $USDA -- a Cardano-native, fully-regulated fiat-backed stablecoin that is pegged to the value of the US dollar.

Moving forward, Anzens will enable people to mint other currencies (e.g. EUR, JPY, GBP, etc.) as well as other real-world assets (e.g. gold, property, etc.)


Anzens

$USDA is a fully-regulated fiat-backed stablecoin that is pegged to US Dollars value, minted through Anzens.

Anzens is a DeFi platform created & operated by EMURGO, one of Cardano's founding entities that enable Cardano Community to tokenize real-world assets.


USDA

Topics mentioned in the video include:

CIPs, Constitutions, Contingent Staking, SpaceX, shades of right, wrong, sometimes in between without looking at the personality, without being absolutely categorical.


An Open Letter to Me (Charles Hoskinson)

Cardano light wallets such as Yoroi, Eternl, Flint, Typhon, and others rely on servers to keep the blockchain information up to date. If you notice incorrect balances in your wallets, if your wallet says you are not delegated to a stake pool, or if you have some other issue, it may just be that the servers behind the wallet are experiencing sync issues.

Think of the aforementioned wallets more as wallet interfaces. Your wallet is on the blockchain and Yoroi, Eternl, Flint, Typon, and others are just software applications you can use to view and interact with your on-chain wallet.

To view your actual balance, stake pool delegation, and more, you can enter your address (starting with 'addr1') or your stake key (starting with 'stake1') into cardanoscan.io. The 'Controlled Stake' section on the platform will show your whole balance including staking rewards.

To fix your wallet interface issues you could try resyncing. You can find a resync option in the settings of most light wallets. If this doesn't fix your issue and your wallet interface is still showing a different balance to cardanoscan.io, then you can use your seed phrase or hardware wallet to set up your wallet in a different wallet interface. You can have your wallet set up in multiple wallet interfaces at the same time, this also enables you to try the interfaces out and see which one is best for your needs.

Switching between wallet interfaces is a lot more secure when using a hardware wallet such as a Ledger or Trezor as you avoid the need to enter your seed phrase each time. See 'Should I get a hardware wallet?'.


Search Results