You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/website/root/manual/operate/run-aggregator-node.md
+3-8Lines changed: 3 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -906,16 +906,11 @@ Make sure your domain name points to your server's public IP address and that po
906
906
907
907
:::
908
908
909
-
## Set up the DMQ node (unstable)
909
+
## Set up the DMQ node (beta)
910
910
911
-
:::danger
912
-
913
-
The DMQ node setup is currently **unstable** and not suitable for production use.
914
-
915
-
During the stabilization and ramp-up phase of the DMQ network:
911
+
:::info
916
912
917
-
- Signatures are still sent to the central aggregator (using the DMQ node is harmless)
918
-
- This section is subject to frequent changes.
913
+
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.
Copy file name to clipboardExpand all lines: docs/website/root/manual/operate/run-signer-node.md
+67-7Lines changed: 67 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -893,16 +893,13 @@ sudo service netfilter-persistent save
893
893
894
894
:::
895
895
896
-
## Set up the DMQ node (unstable)
896
+
## Set up the DMQ node (beta)
897
897
898
-
:::danger
899
-
900
-
The DMQ node setup is currently **unstable** and not suitable for production use.
898
+
:::info
901
899
902
-
During the stabilization and ramp-up phase of the DMQ network:
900
+
The DMQ node setup is currently **beta**and suitable for production use by SPOs.
903
901
904
-
- Signatures are still sent to the central aggregator (using the DMQ node is harmless)
905
-
- This section is subject to frequent changes.
902
+
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).
906
903
907
904
:::
908
905
@@ -1486,6 +1483,69 @@ More information about the recommended firewall configuration of the Cardano nod
1486
1483
1487
1484
:::
1488
1485
1486
+
### Declare your DMQ node as a ledger peer (CIP-155)
1487
+
1488
+
:::info
1489
+
1490
+
This step is **optional** but **recommended**. It allows other DMQ nodes of the Mithril network to discover your relay automatically through the Cardano ledger, instead of relying solely on the bootstrap peer.
1491
+
1492
+
:::
1493
+
1494
+
[CIP-155](https://cips.cardano.org/cip/CIP-0155) defines a registry of `SRV` record prefixes that decentralized protocols can use to publish their service endpoints on the Cardano ledger. By declaring an `SRV` record with the `_mithril._tcp` prefix on your pool relay domain, your DMQ relay node becomes discoverable as a **ledger peer** by any DMQ node that uses ledger peers.
1495
+
1496
+
The declaration requires two steps:
1497
+
1498
+
1. Publish an `SRV` record for your **relay** DMQ node under the `_mithril._tcp` prefix of your pool domain.
1499
+
2. Register your pool domain as a multi-host relay in your stake pool registration certificate.
1500
+
1501
+
:::caution
1502
+
1503
+
Only the **relay** DMQ node must be published as a ledger peer. The **block producer** DMQ node must **never** be exposed.
1504
+
1505
+
Here is the needed information to declare your DMQ node as a ledger peer:
1506
+
1507
+
- `**YOUR_SPO_DOMAIN_NAME**`: replace with the domain name registered as a multi-host relay in your stake pool registration certificate (for example `example.com`)
1508
+
- `**YOUR_DMQ_NODE_RELAY_PUBLIC_HOSTNAME**`: replace with the public hostname (A or AAAA record) of your DMQ relay node
1509
+
- `**YOUR_DMQ_NODE_RELAY_PORT**`: replace with the listening port of your DMQ relay node.
1510
+
1511
+
:::
1512
+
1513
+
#### Publish the SRV record
1514
+
1515
+
Add an `SRV` record to the DNS zone of your pool domain so that `_mithril._tcp.**YOUR_SPO_DOMAIN_NAME**` points to your DMQ relay node:
1516
+
1517
+
```
1518
+
_mithril._tcp.**YOUR_SPO_DOMAIN_NAME**. 86400 IN SRV 10 5 **YOUR_DMQ_NODE_RELAY_PORT** **YOUR_DMQ_NODE_RELAY_PUBLIC_HOSTNAME**.
1519
+
```
1520
+
1521
+
:::tip
1522
+
1523
+
Here is an example for the pool domain `example.com`, with the DMQ relay node reachable at `cardano.example.com` on port `6161`:
1524
+
1525
+
```
1526
+
_mithril._tcp.example.com. 86400 IN SRV 10 5 6161 cardano.example.com.
1527
+
```
1528
+
1529
+
The values after `SRV` are the standard priority (`10`), weight (`5`), port (`6161`), and target hostname (`cardano.example.com`). More information is available in [RFC 2782](https://datatracker.ietf.org/doc/html/rfc2782).
1530
+
1531
+
:::
1532
+
1533
+
#### Register the pool domain as a multi-host relay
1534
+
1535
+
Register `**YOUR_SPO_DOMAIN_NAME**` as a multi-host relay of your stake pool so that it is published on the Cardano ledger:
The `_cardano._tcp` prefix is used by the Cardano node to discover Cardano relays on the same domain, while the `_mithril._tcp` prefix is used by the DMQ node to discover Mithril DMQ relays. Both prefixes can coexist on the same pool domain.
description="Use ledger peers declared with SRV records (CIP-155) for DMQ nodes. When true, the public facing DMQ nodes (aggregator and signer relays) discover peers from the Cardano ledger. Disabled by default to isolate Mithril networks sharing the same Cardano network. (experimental)"
240
+
default=false
241
+
}
242
+
237
243
variable"dmq_image_id" {
238
244
type=string
239
245
description="The DMQ image tag of service to deploy"
description="The dial to address of a bootstrap peer of the P2P network layer. Useful when setting-up a follower aggregator and signers in a different VM. (experimental, for test only)"
257
+
description="The dial to address of a bootstrap peer of the P2P network layer. Useful when setting-up a follower aggregator and signers in a different VM. (experimental)"
0 commit comments