Skip to content

chore: remove trailing whitespaces in release notes #6154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PastaPastaPasta merged 1 commit into from
Jul 24, 2024
Merged

chore: remove trailing whitespaces in release notes #6154

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions doc/release-notes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ Once the EHF signed message is mined and a cycle ends, the hard fork status will
miners on v20 and v21 will begin to signal for activation of MN_RR. As such, nearly 100% of miners will
likely be signalling. If a sufficient number of mined blocks signal support for activation (starting at 80% and gradually decreasing to 60%)
by the end of a cycle, the hard fork will change status from `started` to `locked_in`. At this point, hard fork activation
will occur at the end of the next cycle.
will occur at the end of the next cycle.

Now that the hard fork is active, the new rules will be in effect.

Expand Down Expand Up @@ -339,7 +339,7 @@ dash-tx Changes
- When creating a hex-encoded Dash transaction using the `dash-tx` utility
with the `-json` option set, the following fields: `addresses`, `reqSigs` are no longer
returned in the tx output of the response.

dash-cli Changes
----------------

Expand Down Expand Up @@ -376,7 +376,7 @@ user-friendly for managing Dash wallets.
- new commands `dump` and `createfromdump` have been added, enhancing the wallet's storage migration capabilities. The
`dump` command allows for exporting every key-value pair from the wallet as comma-separated hex values, facilitating a
storage agnostic dump. Meanwhile, the `createfromdump` command enables the creation of a new wallet file using the
records specified in a dump file. These commands are similar to BDB's `db_dump` and `db_load` tools and are useful
records specified in a dump file. These commands are similar to BDB's `db_dump` and `db_load` tools and are useful
for manual wallet file construction for testing or migration purposes.


Expand Down