Docs: dev blog posts for 2437 distribution

docs/website/blog/2024-07-30-cardano-transaction-certification/index.md

@@ -7,16 +7,24 @@ tags: [certification, cardano transaction]
 
 ### Certification of Cardano transactions
 
+:::info
+
+A threshold of at least **75%** of the stake running version `0.2.182` (within **10** days after the distribution `2437` is released) is mandatory in order to activate the certification of the Cardano transactions on the `release-mainnet` network.
+
+The [Mithril Protocol Insights](https://lookerstudio.google.com/u/0/reporting/8b05ea4b-6a43-45ea-aef2-237906ec7a42?s=oi6CR5eZrnQ) dashboard displays the adoption rate of the different signer versions on the `release-mainnet` network.
+
+:::
+
 With the release of the new distribution [2430](https://github.com/input-output-hk/mithril/releases/tag/2430.0), we have started to roll-out the certification of the **Cardano transactions** in the Mithril networks.
 
 ![](img/cardano-transaction-rollout-plan.png)
 
 The roll-out plan of the feature is the following:
 
-- [x] Distribution `2430` (before the **Chang** hardfork):
+- [x] Distribution [2430](https://github.com/input-output-hk/mithril/releases/tag/2430.0) (before the **Chang** hardfork):
   - [x] Activation of the certification of **Cardano transactions** in the `pre-release-preview` network.
   - [x] Activation of the certification of **Cardano transactions** in the `release-preprod` network.
-- [ ] Distribution `2434` (after the **Chang** hardfork):
+- [x] Distribution [2437](https://github.com/input-output-hk/mithril/releases/tag/2437.1) (after the **Chang** hardfork):
   - [ ] Activation of the certification of **Cardano transactions** in the `release-mainnet` network.
 
 For any inquiries or assistance, don't hesitate to reach out to the team on the [Discord channel](https://discord.gg/5kaErDKDRq).

docs/website/blog/2024-09-24-client-wasm-unstable-breaking-change.md

@@ -0,0 +1,44 @@
+---
+title: Mithril client WASM breaking change
+authors:
+  - name: Mithril Team
+tags: [mithril client, cli, breaking-change]
+---
+
+### Breaking change introduced in the unstable features of the Mithril client WASM
+
+With the release of the new distribution [2437](https://github.com/input-output-hk/mithril/releases/tag/2437.1), we have introduced a breaking change to the **Mithril client WASM** version `0.4.1`: the activation of the unstable features is now done with a **configuration option of the client** instead of using the special `.unstable` property of the client.
+
+This means that when a new `unstable` feature is switched to `stable`, there will be no breaking change in the developers code using the Mithril client WASM, thus providing a seamless transition and a better developer experience.
+
+Here is the code used to activate the `unstable` features with the client options:
+
+```js
+let client = new MithrilClient(aggregator_endpoint, genesis_verification_key, {
+  // The following option activates the unstable features of the client.
+  // Unstable features will trigger an error if this option is not set.
+  unstable: true,
+});
+```
+
+The previous `client.unstable` implementation is not supported anymore and must be replaced with `client`:
+
+```js
+// Before
+let mithril_stake_distributions_message =
+  await client.unstable.compute_mithril_stake_distribution_message(
+    last_stake_distribution,
+  );
+```
+
+```js
+// After
+let mithril_stake_distributions_message =
+  await client.compute_mithril_stake_distribution_message(
+    last_stake_distribution,
+  );
+```
+
+The Mithril client WASM documentation is available [here](https://mithril.network/doc/manual/developer-docs/nodes/mithril-client-library-wasm).
+
+For any inquiries or assistance, don't hesitate to reach out to the team on the [Discord channel](https://discord.gg/5kaErDKDRq).