diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 67e22e8c71f..5e694e7113a 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -356,7 +356,7 @@ jobs: cardano_node_version: "10.6.2" hard_fork_latest_era_at_epoch: 0 run_id: "#1" - extra_args: "--skip-signature-delayer --number-of-aggregators=2 --use-relays --relay-signer-registration-mode=passthrough --relay-signature-registration-mode=p2p --aggregate-signature-type=Concatenation --use-dmq --dmq-node-flavor=haskell --dmq-node-version 0.6.0.0" + extra_args: "--skip-signature-delayer --number-of-aggregators=2 --use-relays --relay-signer-registration-mode=passthrough --relay-signature-registration-mode=p2p --aggregate-signature-type=Concatenation --use-dmq --dmq-node-flavor=haskell --dmq-node-version 0.7.0.0" # Include a test for partial decentralization with leader/follower signer registration and P2P signature registration with Haskell DMQ node (with fallback signature delayer) - mode: "leader-follower-dmq-haskell-with-delayer" era: ${{ fromJSON(needs.build-ubuntu.outputs.eras)[0] }} @@ -364,7 +364,7 @@ jobs: cardano_node_version: "10.6.2" hard_fork_latest_era_at_epoch: 0 run_id: "#1" - extra_args: "--number-of-aggregators=2 --use-relays --relay-signer-registration-mode=passthrough --relay-signature-registration-mode=p2p --aggregate-signature-type=Concatenation --use-dmq --dmq-node-flavor=haskell --dmq-node-version 0.6.0.0" + extra_args: "--number-of-aggregators=2 --use-relays --relay-signer-registration-mode=passthrough --relay-signature-registration-mode=p2p --aggregate-signature-type=Concatenation --use-dmq --dmq-node-flavor=haskell --dmq-node-version 0.7.0.0" # Include a test for partial decentralization with leader/follower signer registration and P2P signature registration with fake DMQ node - mode: "leader-follower-dmq-fake" era: ${{ fromJSON(needs.build-ubuntu.outputs.eras)[0] }} diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 8bb3e2e6b0a..082d825f207 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -107,10 +107,10 @@ jobs: - environment: release-preprod environment_prefix: release cardano_network: preprod - mithril_use_p2p_network: false - mithril_p2p_use_dmq_protocol: false - mithril_p2p_use_real_dmq_node: false - mithril_p2p_dmq_use_ledger_peers: false + mithril_use_p2p_network: true + mithril_p2p_use_dmq_protocol: true + mithril_p2p_use_real_dmq_node: true + mithril_p2p_dmq_use_ledger_peers: true mithril_api_domain: api.mithril.network mithril_protocol_parameters: | { @@ -136,10 +136,10 @@ jobs: - environment: release-mainnet environment_prefix: release cardano_network: mainnet - mithril_use_p2p_network: false - mithril_p2p_use_dmq_protocol: false - mithril_p2p_use_real_dmq_node: false - mithril_p2p_dmq_use_ledger_peers: false + mithril_use_p2p_network: true + mithril_p2p_use_dmq_protocol: true + mithril_p2p_use_real_dmq_node: true + mithril_p2p_dmq_use_ledger_peers: true mithril_api_domain: api.mithril.network mithril_protocol_parameters: | { diff --git a/CHANGELOG.md b/CHANGELOG.md index 3d979ca9cd4..acf53ffb5cc 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -35,7 +35,8 @@ As a minor extension, we have adopted a slightly different versioning convention - DMQ node: - Implemented new message id format for the DMQ message to follow specification of the [CIP-0137](https://cips.cardano.org/cip/CIP-0137). - - Added support for the DMQ node `0.6.0.0` stable version. + - Added support for the DMQ node `0.7.0.0` stable version. + - Promoted the DMQ node as stable (beta) on `release-mainnet` and `release-preprod` networks. - Added optional support for ledger peers declared with `SRV` records ([CIP-155](https://cips.cardano.org/cip/CIP-0155)). - Gracefully handle unknown signed entity types across Mithril nodes for improved forward compatibility. diff --git a/docs/website/blog/2026-01-06-dmq-testing-program.md b/docs/website/blog/2026-01-06-dmq-testing-program.md index caf34612a9e..840e72ba36e 100644 --- a/docs/website/blog/2026-01-06-dmq-testing-program.md +++ b/docs/website/blog/2026-01-06-dmq-testing-program.md @@ -7,6 +7,12 @@ tags: [DMQ, decentralization, testing program] ### DMQ testing program with SPOs +:::info[Update 2026/08/04] + +With the release of the [`2630.0`](https://github.com/input-output-hk/mithril/releases/tag/2630.0) distribution, the DMQ node has been upgraded to its first **stable beta release** version `0.7.0.0` on the `release-mainnet` and `release-preprod` networks. + +::: + :::info[Update 2026/04/28] With the release of the [`2617.0`](https://github.com/input-output-hk/mithril/releases/tag/2617.0) distribution, the DMQ node has been upgraded to version `0.4.2.0` on the `pre-release-preview` network. The testing program with SPOs is extended to keep gathering feedback before the stable release on `release-preprod` and `release-mainnet` networks. @@ -47,14 +53,14 @@ The rollout plan of the DMQ network is the following: - [x] DMQ activation on the `pre-release-preview` network - [x] Released a [guide](https://mithril.network/doc/manual/operate/run-signer-node/#set-up-the-dmq-node-unstable) for setting up a DMQ node in the SPO infrastructure - [x] 4-6 weeks testing program with selected SPOs -- [ ] **Distribution [2617](https://github.com/input-output-hk/mithril/releases/tag/2617.0)**: `unstable` on the `pre-release-preview` network (extended testing) +- [x] **Distribution [2617](https://github.com/input-output-hk/mithril/releases/tag/2617.0)**: `unstable` on the `pre-release-preview` network (extended testing) - [x] Upgraded the DMQ node to version `0.4.2.0` on the `pre-release-preview` network - - [ ] 4-6 weeks extended testing program with selected SPOs -- [ ] **Distribution +3**: `stable` on the `release-preprod` and `release-mainnet` networks with fallback - - [ ] DMQ activation on the `release-preprod` and `release-mainnet` networks - - [ ] Activation of the fallback to the legacy signature registration mechanism for all SPOs - - [ ] Release of an updated guide for setting up a DMQ node in the SPO infrastructure - - [ ] Monitoring and support for SPOs running DMQ nodes + - [x] 4-6 weeks extended testing program with selected SPOs +- [x] **Distribution [2630](https://github.com/input-output-hk/mithril/releases/tag/2630.0)**: `stable` on the `release-preprod` and `release-mainnet` networks with fallback + - [x] DMQ activation on the `release-preprod` and `release-mainnet` networks + - [x] Activation of the fallback to the legacy signature registration mechanism for all SPOs + - [x] Release of an updated guide for setting up a DMQ node in the SPO infrastructure + - [x] Monitoring and support for SPOs running DMQ nodes - [ ] **Distribution +4**: `stable` on the `release-preprod` and `release-mainnet` networks - [ ] Deactivation of the fallback to the legacy signature registration mechanism for all SPOs - [ ] Monitoring and support for SPOs running DMQ nodes. diff --git a/docs/website/blog/2026-01-06-multiple-aggregators-testing-program.md b/docs/website/blog/2026-01-06-multiple-aggregators-testing-program.md index 42fb0c327a4..6089dc5bcbc 100644 --- a/docs/website/blog/2026-01-06-multiple-aggregators-testing-program.md +++ b/docs/website/blog/2026-01-06-multiple-aggregators-testing-program.md @@ -67,8 +67,8 @@ The rollout plan of the DMQ network is the following: - [x] Released a [guide](https://mithril.network/doc/manual/operate/run-aggregator-node) for setting up a follower aggregator - [x] Wait for the DMQ adoption to reach the required threshold until aggregators can produce valid certificates - [x] 4-6 weeks testing program with selected participants -- [ ] **Distribution [2617](https://github.com/input-output-hk/mithril/releases/tag/2617.0)**: `unstable` on the `pre-release-preview` network (extended testing) - - [ ] 4-6 weeks extended testing program with selected SPOs +- [x] **Distribution [2617](https://github.com/input-output-hk/mithril/releases/tag/2617.0)**: `unstable` on the `pre-release-preview` network (extended testing) + - [x] 4-6 weeks extended testing program with selected SPOs - [ ] **Distribution +3**: `stable` on the `release-preprod` and `release-mainnet` networks - [ ] Activation of the feature on the `release-preprod` and `release-mainnet` networks - [ ] Release of an updated guide for setting up a follower aggregator diff --git a/docs/website/root/manual/operate/run-aggregator-node.md b/docs/website/root/manual/operate/run-aggregator-node.md index de391d32813..4a1faf0a2b5 100644 --- a/docs/website/root/manual/operate/run-aggregator-node.md +++ b/docs/website/root/manual/operate/run-aggregator-node.md @@ -961,7 +961,7 @@ As we are still in a testing stage, we only support the `pre-release-preview` ne You can use these parameters for the **pre-release-preview** network: -- **DMQ_RELEASE_URL**: `https://github.com/IntersectMBO/dmq-node/releases/download/0.6.0.0/dmq-node-linux.tar.gz` +- **DMQ_RELEASE_URL**: `https://github.com/IntersectMBO/dmq-node/releases/download/0.7.0.0/dmq-node-linux.tar.gz` _These URLs may change in the future; please refer to this page for the latest released version of the DMQ node binary._ diff --git a/docs/website/root/manual/operate/run-signer-node.md b/docs/website/root/manual/operate/run-signer-node.md index d9f65b7e114..fcc71d6bfbc 100644 --- a/docs/website/root/manual/operate/run-signer-node.md +++ b/docs/website/root/manual/operate/run-signer-node.md @@ -981,7 +981,7 @@ As we are still in a testing stage, we only support the `pre-release-preview` ne You can use these parameters for the **pre-release-preview** network: -- **DMQ_RELEASE_URL**: `https://github.com/IntersectMBO/dmq-node/releases/download/0.6.0.0/dmq-node-linux.tar.gz` +- **DMQ_RELEASE_URL**: `https://github.com/IntersectMBO/dmq-node/releases/download/0.7.0.0/dmq-node-linux.tar.gz` _These URLs may change in the future; please refer to this page for the latest released version of the DMQ node binary._ diff --git a/docs/website/root/networks-matrix.md b/docs/website/root/networks-matrix.md index de49f0d18df..8dc99a52994 100644 --- a/docs/website/root/networks-matrix.md +++ b/docs/website/root/networks-matrix.md @@ -24,7 +24,7 @@ Here is an updated list of all **Mithril networks**, including their configurati | **Cardano node versions** | `10.7`, `11.0` | | **Mithril status** | Stable (signer) 🟒 / Beta (aggregator/client) 🟒 | | **DMQ magic Id** | `2912307721` | -| **DMQ node versions** | `0.6.0.0` | +| **DMQ node versions** | `0.7.0.0` | | **DMQ bootstrap peers** | `35.233.75.24:6161` | | **DMQ status** | Beta 🟒 | | **Aggregator endpoint** | `https://aggregator.release-mainnet.api.mithril.network/aggregator` [:arrow_upper_right:](https://aggregator.release-mainnet.api.mithril.network/aggregator) | @@ -48,7 +48,7 @@ Here is an updated list of all **Mithril networks**, including their configurati | **Cardano node versions** | `10.7`, `11.0` | | **Mithril status** | Stable 🟒 | | **DMQ magic Id** | `2147483649` | -| **DMQ node versions** | `0.6.0.0` | +| **DMQ node versions** | `0.7.0.0` | | **DMQ bootstrap peers** | `34.79.19.73:6161`,`34.79.19.73:11002` | | **DMQ status** | Beta 🟒 | | **Aggregator endpoint** | `https://aggregator.release-preprod.api.mithril.network/aggregator` [:arrow_upper_right:](https://aggregator.release-preprod.api.mithril.network/aggregator) | @@ -72,7 +72,7 @@ Here is an updated list of all **Mithril networks**, including their configurati | **Cardano node versions** | `10.7`, `11.0` | | **Mithril status** | Pre-release 🟠 | | **DMQ magic Id** | `2147483650` | -| **DMQ node versions** | `0.6.0.0` | +| **DMQ node versions** | `0.7.0.0` | | **DMQ bootstrap peers** | `34.76.22.193:6161`,`34.76.22.193:11002` | | **DMQ status** | Beta 🟒 | | **Aggregator endpoint** | `https://aggregator.pre-release-preview.api.mithril.network/aggregator` [:arrow_upper_right:](https://aggregator.pre-release-preview.api.mithril.network/aggregator) | @@ -101,7 +101,7 @@ This network is only for the developers of the Mithril Core team. | **Cardano node versions** | `10.7`, `11.0` | | **Mithril status** | Unstable πŸ”΄ | | **DMQ magic Id** | `2147483650` | -| **DMQ node versions** | `0.6.0.0` | +| **DMQ node versions** | `0.7.0.0` | | **DMQ bootstrap peers** | `34.38.152.55:6161`,`34.38.152.55:11001`,`34.38.152.55:11002`,`34.38.152.55:11003` | | **DMQ status** | Unstable πŸ”΄ | | **Aggregator endpoint** | `https://aggregator.testing-preview.api.mithril.network/aggregator` [:arrow_upper_right:](https://aggregator.testing-preview.api.mithril.network/aggregator) | diff --git a/docs/website/versioned_docs/version-maintained/manual/develop/nodes/mithril-client-library-wasm.md b/docs/website/versioned_docs/version-maintained/manual/develop/nodes/mithril-client-library-wasm.md index a09aea1b093..8715b88963e 100644 --- a/docs/website/versioned_docs/version-maintained/manual/develop/nodes/mithril-client-library-wasm.md +++ b/docs/website/versioned_docs/version-maintained/manual/develop/nodes/mithril-client-library-wasm.md @@ -144,7 +144,7 @@ console.log( ); ``` -:::tip[Adding Custom HTTP Headers] +:::tip Adding Custom HTTP Headers You can customize the HTTP headers sent by the Mithril client. This is particularly useful in scenarios where the Mithril client is used with a proxy, as it allows you to include headers like **Authorization** or custom headers for specific use cases. Below is an example of how to set custom headers: diff --git a/docs/website/versioned_docs/version-maintained/manual/operate/run-aggregator-node.md b/docs/website/versioned_docs/version-maintained/manual/operate/run-aggregator-node.md index addac9e616e..4a1faf0a2b5 100644 --- a/docs/website/versioned_docs/version-maintained/manual/operate/run-aggregator-node.md +++ b/docs/website/versioned_docs/version-maintained/manual/operate/run-aggregator-node.md @@ -912,16 +912,11 @@ Make sure your domain name points to your server's public IP address and that po ::: -## Set up the DMQ node (unstable) +## Set up the DMQ node (beta) -:::danger - -The DMQ node setup is currently **unstable** and not suitable for production use. - -During the stabilization and ramp-up phase of the DMQ network: +:::info -- Signatures are still sent to the central aggregator (using the DMQ node is harmless) -- This section is subject to frequent changes. +The DMQ node setup is currently **beta**. During the stabilization and ramp-up phase of the DMQ network, signatures received through it may not be enough to reach the quorum and thus produce valid certificates. ::: @@ -966,7 +961,7 @@ As we are still in a testing stage, we only support the `pre-release-preview` ne You can use these parameters for the **pre-release-preview** network: -- **DMQ_RELEASE_URL**: `https://github.com/IntersectMBO/dmq-node/releases/download/0.6.0.0/dmq-node-linux.tar.gz` +- **DMQ_RELEASE_URL**: `https://github.com/IntersectMBO/dmq-node/releases/download/0.7.0.0/dmq-node-linux.tar.gz` _These URLs may change in the future; please refer to this page for the latest released version of the DMQ node binary._ diff --git a/docs/website/versioned_docs/version-maintained/manual/operate/run-signer-node.md b/docs/website/versioned_docs/version-maintained/manual/operate/run-signer-node.md index 6c634aceb90..fcc71d6bfbc 100644 --- a/docs/website/versioned_docs/version-maintained/manual/operate/run-signer-node.md +++ b/docs/website/versioned_docs/version-maintained/manual/operate/run-signer-node.md @@ -896,16 +896,13 @@ sudo service netfilter-persistent save ::: -## Set up the DMQ node (unstable) +## Set up the DMQ node (beta) -:::danger - -The DMQ node setup is currently **unstable** and not suitable for production use. +:::info -During the stabilization and ramp-up phase of the DMQ network: +The DMQ node setup is currently **beta** and suitable for production use by SPOs. -- Signatures are still sent to the central aggregator (using the DMQ node is harmless) -- This section is subject to frequent changes. +During the stabilization and ramp-up phase of the DMQ network, signatures are still sent to the leader aggregator (using the DMQ node is harmless). ::: @@ -984,7 +981,7 @@ As we are still in a testing stage, we only support the `pre-release-preview` ne You can use these parameters for the **pre-release-preview** network: -- **DMQ_RELEASE_URL**: `https://github.com/IntersectMBO/dmq-node/releases/download/0.6.0.0/dmq-node-linux.tar.gz` +- **DMQ_RELEASE_URL**: `https://github.com/IntersectMBO/dmq-node/releases/download/0.7.0.0/dmq-node-linux.tar.gz` _These URLs may change in the future; please refer to this page for the latest released version of the DMQ node binary._ diff --git a/docs/website/versioned_docs/version-maintained/mithril/advanced/mithril-protocol/protocol.md b/docs/website/versioned_docs/version-maintained/mithril/advanced/mithril-protocol/protocol.md index 2c1e5b892d3..b898f4254f5 100644 --- a/docs/website/versioned_docs/version-maintained/mithril/advanced/mithril-protocol/protocol.md +++ b/docs/website/versioned_docs/version-maintained/mithril/advanced/mithril-protocol/protocol.md @@ -44,7 +44,7 @@ The protocol has three phases: 2. **Initialization phase** during which Mithril nodes generate and exchange keys 3. **Operations phase** during which nodes sign and aggregate signatures of messages to produce certificates. -:::note[Note] +:::note Note Note that all three phases require a set of parties (`P` in the paper) to be fixed. During the protocol establishment phase three important parameters are generated: @@ -118,7 +118,7 @@ a quorum of `k` valid signatures must be submitted. - Each certificate `Ο„` can be verified as valid for some message, using the known setup parameters to verify the certificate’s proof and then verifying the aggregate signatures and verification keys. -:::note[Note] +:::note Note Note that if the individual signatures are broadcast to all parties, then each party can independently produce the certificates. In particular, the party that performs aggregation is not required to have any specific knowledge, nor it is assumed to be honest. This means that _any_ third party that has access to the individual signatures can perform the signature aggregation. diff --git a/docs/website/versioned_docs/version-maintained/mithril/advanced/threat-model.md b/docs/website/versioned_docs/version-maintained/mithril/advanced/threat-model.md index 5a2885df241..aaa29044b97 100644 --- a/docs/website/versioned_docs/version-maintained/mithril/advanced/threat-model.md +++ b/docs/website/versioned_docs/version-maintained/mithril/advanced/threat-model.md @@ -22,7 +22,7 @@ The threat model is a living document, updated to reflect the [latest Mithril ve ### System description -:::info[To do] +:::info To do - Consider reducing these details and moving them into the [architecture page](https://mithril.network/doc/mithril/mithril-network/architecture). - Also consider updating the [protocol page](https://mithril.network/doc/mithril/mithril-protocol/protocol). @@ -35,7 +35,7 @@ The system consists of three main components: signers, aggregators, and clients. - **Mithril signing keys** are rotated every epoch and require certification by the Cardano KES key. Therefore, Mithril signers must have access to the KES key to register a signing key for each epoch. - **Cardano KES keys** are also used by the block-producing `cardano-node` and are typically located on the same machine that produces blocks. These keys must be evolved every 36 hours, although they can be rotated from a root key when needed. For more details, see [KES period documentation](https://github.com/IntersectMBO/cardano-node-wiki/blob/main/docs/stake-pool-operations/7_KES_period.md). -:::info[To do] +:::info To do Is there a Cardano threat model available for this? @@ -55,7 +55,7 @@ Mithril clients do connect to an aggregator using HTTP over TLS to query Mithril A Mithril client can verify the received Mithril certificate is linked to other certificates up to the genesis certificate and can be verified using the Mithril genesis verification key (see [details](https://mithril.network/doc/mithril/mithril-protocol/certificates/)). -:::info[To do] +:::info To do Missing: the currently recommended relay (reverse proxy) diff --git a/docs/website/versioned_docs/version-maintained/networks-matrix.md b/docs/website/versioned_docs/version-maintained/networks-matrix.md index de49f0d18df..8dc99a52994 100644 --- a/docs/website/versioned_docs/version-maintained/networks-matrix.md +++ b/docs/website/versioned_docs/version-maintained/networks-matrix.md @@ -24,7 +24,7 @@ Here is an updated list of all **Mithril networks**, including their configurati | **Cardano node versions** | `10.7`, `11.0` | | **Mithril status** | Stable (signer) 🟒 / Beta (aggregator/client) 🟒 | | **DMQ magic Id** | `2912307721` | -| **DMQ node versions** | `0.6.0.0` | +| **DMQ node versions** | `0.7.0.0` | | **DMQ bootstrap peers** | `35.233.75.24:6161` | | **DMQ status** | Beta 🟒 | | **Aggregator endpoint** | `https://aggregator.release-mainnet.api.mithril.network/aggregator` [:arrow_upper_right:](https://aggregator.release-mainnet.api.mithril.network/aggregator) | @@ -48,7 +48,7 @@ Here is an updated list of all **Mithril networks**, including their configurati | **Cardano node versions** | `10.7`, `11.0` | | **Mithril status** | Stable 🟒 | | **DMQ magic Id** | `2147483649` | -| **DMQ node versions** | `0.6.0.0` | +| **DMQ node versions** | `0.7.0.0` | | **DMQ bootstrap peers** | `34.79.19.73:6161`,`34.79.19.73:11002` | | **DMQ status** | Beta 🟒 | | **Aggregator endpoint** | `https://aggregator.release-preprod.api.mithril.network/aggregator` [:arrow_upper_right:](https://aggregator.release-preprod.api.mithril.network/aggregator) | @@ -72,7 +72,7 @@ Here is an updated list of all **Mithril networks**, including their configurati | **Cardano node versions** | `10.7`, `11.0` | | **Mithril status** | Pre-release 🟠 | | **DMQ magic Id** | `2147483650` | -| **DMQ node versions** | `0.6.0.0` | +| **DMQ node versions** | `0.7.0.0` | | **DMQ bootstrap peers** | `34.76.22.193:6161`,`34.76.22.193:11002` | | **DMQ status** | Beta 🟒 | | **Aggregator endpoint** | `https://aggregator.pre-release-preview.api.mithril.network/aggregator` [:arrow_upper_right:](https://aggregator.pre-release-preview.api.mithril.network/aggregator) | @@ -101,7 +101,7 @@ This network is only for the developers of the Mithril Core team. | **Cardano node versions** | `10.7`, `11.0` | | **Mithril status** | Unstable πŸ”΄ | | **DMQ magic Id** | `2147483650` | -| **DMQ node versions** | `0.6.0.0` | +| **DMQ node versions** | `0.7.0.0` | | **DMQ bootstrap peers** | `34.38.152.55:6161`,`34.38.152.55:11001`,`34.38.152.55:11002`,`34.38.152.55:11003` | | **DMQ status** | Unstable πŸ”΄ | | **Aggregator endpoint** | `https://aggregator.testing-preview.api.mithril.network/aggregator` [:arrow_upper_right:](https://aggregator.testing-preview.api.mithril.network/aggregator) | diff --git a/mithril-infra/assets/infra.version b/mithril-infra/assets/infra.version index 17f210d5490..44bee585828 100644 --- a/mithril-infra/assets/infra.version +++ b/mithril-infra/assets/infra.version @@ -1,2 +1,2 @@ -0.5.19 +0.5.20 diff --git a/mithril-infra/variables.tf b/mithril-infra/variables.tf index d962b26e0c6..3d124a164cb 100644 --- a/mithril-infra/variables.tf +++ b/mithril-infra/variables.tf @@ -243,7 +243,7 @@ variable "mithril_p2p_dmq_use_ledger_peers" { variable "dmq_image_id" { type = string description = "The DMQ image tag of service to deploy" - default = "0.6.0.0" + default = "0.7.0.0" } variable "dmq_image_registry" { diff --git a/mithril-test-lab/cardano-devnet/VERSION b/mithril-test-lab/cardano-devnet/VERSION index 64d201bd51e..ce4cc376c3e 100644 --- a/mithril-test-lab/cardano-devnet/VERSION +++ b/mithril-test-lab/cardano-devnet/VERSION @@ -1,2 +1,2 @@ -0.4.38 +0.4.39 diff --git a/mithril-test-lab/cardano-devnet/mkfiles/mkfiles-init.sh b/mithril-test-lab/cardano-devnet/mkfiles/mkfiles-init.sh index 5ceb7941ced..b769e453a2f 100644 --- a/mithril-test-lab/cardano-devnet/mkfiles/mkfiles-init.sh +++ b/mithril-test-lab/cardano-devnet/mkfiles/mkfiles-init.sh @@ -49,7 +49,7 @@ if [ -z "${NETWORK_MAGIC}" ]; then NETWORK_MAGIC=42 fi if [ -z "${DMQ_NODE_VERSION}" ]; then - DMQ_NODE_VERSION="0.6.0.0" + DMQ_NODE_VERSION="0.7.0.0" fi if [ -z "${DMQ_NODE_BINARY_URL}" ]; then DMQ_NODE_BINARY_URL="https://github.com/IntersectMBO/dmq-node/releases/download/${DMQ_NODE_VERSION}/dmq-node-linux.tar.gz" diff --git a/mithril-test-lab/cardano-devnet/mkfiles/mkfiles-start.sh b/mithril-test-lab/cardano-devnet/mkfiles/mkfiles-start.sh index 76d0f1878b7..37d5961b94b 100644 --- a/mithril-test-lab/cardano-devnet/mkfiles/mkfiles-start.sh +++ b/mithril-test-lab/cardano-devnet/mkfiles/mkfiles-start.sh @@ -133,6 +133,7 @@ $DMQ_NODE \\ --local-socket ${NODE}/ipc/dmq.node.sock \\ --host-addr $(cat ${NODE}/host) \\ --port $(cat ${NODE}/port.dmq) \\ + --min-sig-delay 0.01s \\ > ${NODE}/dmq.node.log EOF chmod u+x ${NODE}/start-dmq.sh diff --git a/networks.json b/networks.json index 8081383642f..74ae10fc841 100644 --- a/networks.json +++ b/networks.json @@ -4,6 +4,7 @@ "mithril-signer": "10.7.1", "mithril-aggregator": "10.7.1" }, + "dmq-minimum-version": "0.7.0.0", "mithril-networks": [ { "release-mainnet": { @@ -40,6 +41,7 @@ "mithril-signer": "10.7.1", "mithril-aggregator": "10.7.1" }, + "dmq-minimum-version": "0.7.0.0", "mithril-networks": [ { "release-preprod": { @@ -76,7 +78,7 @@ "mithril-signer": "10.7.1", "mithril-aggregator": "10.7.1" }, - "dmq-minimum-version": "0.6.0.0", + "dmq-minimum-version": "0.7.0.0", "mithril-networks": [ { "pre-release-preview": {