@@ -51,7 +51,7 @@ Once the EHF signed message is mined and a cycle ends, the hard fork status will
5151miners on v20 and v21 will begin to signal for activation of MN_RR. As such, nearly 100% of miners will
5252likely be signalling. If a sufficient number of mined blocks signal support for activation (starting at 80% and gradually decreasing to 60%)
5353by the end of a cycle, the hard fork will change status from ` started ` to ` locked_in ` . At this point, hard fork activation
54- will occur at the end of the next cycle.
54+ will occur at the end of the next cycle.
5555
5656Now that the hard fork is active, the new rules will be in effect.
5757
@@ -339,7 +339,7 @@ dash-tx Changes
339339- When creating a hex-encoded Dash transaction using the ` dash-tx ` utility
340340 with the ` -json ` option set, the following fields: ` addresses ` , ` reqSigs ` are no longer
341341 returned in the tx output of the response.
342-
342+
343343dash-cli Changes
344344----------------
345345
@@ -376,7 +376,7 @@ user-friendly for managing Dash wallets.
376376- new commands ` dump ` and ` createfromdump ` have been added, enhancing the wallet's storage migration capabilities. The
377377 ` dump ` command allows for exporting every key-value pair from the wallet as comma-separated hex values, facilitating a
378378 storage agnostic dump. Meanwhile, the ` createfromdump ` command enables the creation of a new wallet file using the
379- records specified in a dump file. These commands are similar to BDB's ` db_dump ` and ` db_load ` tools and are useful
379+ records specified in a dump file. These commands are similar to BDB's ` db_dump ` and ` db_load ` tools and are useful
380380 for manual wallet file construction for testing or migration purposes.
381381
382382
0 commit comments