ed0e2dd075
cb3511b9d Add release notes for importing key origin info change (Andrew Chow) 4c75a69f3 Test importing descriptors with key origin information (Andrew Chow) 02d6586d7 Import KeyOriginData when importing descriptors (Andrew Chow) 3d235dff5 Implement a function to add KeyOriginInfo to a wallet (Andrew Chow) eab63bc26 Store key origin info in key metadata (Andrew Chow) 345bff601 Remove hdmasterkeyid (Andrew Chow) bac8c676a Add a method to CWallet to write just CKeyMetadata (Andrew Chow) e7652d3f6 Add WriteHDKeypath function and move *HDKeypath to util/bip32.{h,cpp} (Andrew Chow) c45415f73 Refactor keymetadata writing to a separate method (Andrew Chow) Pull request description: This PR allows for key origin data as defined by the descriptors document to be imported to the wallet when importing a descriptor using `importmulti`. This allows the `walletprocesspsbt` to include the BIP 32 derivation paths for keys that it is watching that are from a different HD wallet. In order to make this easier to use, a new field `hdmasterkeyfingerprint` has been added to `getaddressinfo`. Additionally I have removed `hdmasterkeyid` as was planned. I think that this API change is fine since it was going to be removed in 0.18 anyways. `CKeyMetadata` has also been extended to store key origin info to facilitate this. Tree-SHA512: 9c7794f3c793da57e23c5abbdc3d58779ee9dea3d53168bb86c0643a4ad5a11a446264961e2f772f35eea645048cb60954ed58050002caee4e43cd9f51215097 |
||
---|---|---|
.. | ||
gitian-building | ||
man | ||
release-notes/dash | ||
.gitignore | ||
assets-attribution.md | ||
benchmarking.md | ||
bips.md | ||
bitcoin_logo_doxygen.png | ||
build-cross.md | ||
build-generic.md | ||
build-netbsd.md | ||
build-osx.md | ||
build-unix.md | ||
build-windows.md | ||
dash-conf.md | ||
descriptors.md | ||
developer-notes.md | ||
dnsseed-policy.md | ||
Doxyfile.in | ||
files.md | ||
fuzzing.md | ||
gitian-building.md | ||
init.md | ||
instantsend.md | ||
JSON-RPC-interface.md | ||
masternode-budget.md | ||
productivity.md | ||
psbt.md | ||
README_doxygen.md | ||
README_windows.txt | ||
README.md | ||
reduce-memory.md | ||
reduce-traffic.md | ||
release-notes-13152.md | ||
release-notes-14021.md | ||
release-notes-14023.md | ||
release-notes-14941.md | ||
release-notes-14954.md | ||
release-notes-14982.md | ||
release-notes-15006.md | ||
release-notes-15226.md | ||
release-notes-15566.md | ||
release-notes-15637.md | ||
release-notes-16512.md | ||
release-notes-17410.md | ||
release-notes-pr12255.md | ||
release-notes.md | ||
release-process.md | ||
REST-interface.md | ||
shared-libraries.md | ||
tor.md | ||
translation_process.md | ||
translation_strings_policy.md | ||
travis-ci.md | ||
zmq.md |
Dash Core
This is the official reference wallet for Dash digital currency and comprises the backbone of the Dash peer-to-peer network. You can download Dash Core or build it yourself using the guides below.
Running
The following are some helpful notes on how to run Dash Core on your native platform.
Unix
Unpack the files into a directory and run:
bin/dash-qt
(GUI) orbin/dashd
(headless)
Windows
Unpack the files into a directory, and then run dash-qt.exe.
macOS
Drag Dash Core to your applications folder, and then run Dash Core.
Need Help?
- See the Dash documentation for help and more information.
- Ask for help on Dash Discord
- Ask for help on the Dash Forum
Building
The following are developer notes on how to build Dash Core on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.
- macOS Build Notes
- Unix Build Notes
- Windows Build Notes
- OpenBSD Build Notes
- NetBSD Build Notes
- Gitian Building Guide
Development
The Dash Core repo's root README contains relevant information on the development process and automated testing.
- Developer Notes
- Productivity Notes
- Release Notes
- Release Process
- Source Code Documentation TODO
- Translation Process
- Translation Strings Policy
- Travis CI
- JSON-RPC Interface
- Unauthenticated REST Interface
- Shared Libraries
- BIPS
- Dnsseed Policy
- Benchmarking
Resources
- See the Dash Developer Documentation for technical specifications and implementation details.
- Discuss on the Dash Forum, in the Development & Technical Discussion board.
- Discuss on Dash Discord
- Discuss on Dash Developers Discord
Miscellaneous
- Assets Attribution
- dash.conf Configuration File
- Files
- Fuzz-testing
- Reduce Memory
- Reduce Traffic
- Tor Support
- Init Scripts (systemd/upstart/openrc)
- ZMQ
- PSBT support
License
Distributed under the MIT software license. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com), and UPnP software written by Thomas Bernard.