DigitalNote Daemon/QT-Wallet
============================================

DigitalNote (XDN) Hybrid PoW/PoS blockchain with Masternode Support.
DigitalNote provides a lightweight blockchain with several avenues for passive income.
DigitalNote (SatoshiCore) is the core of the DigitalNote ecosystem and was been developed from a bitcore base and
since morphing into its own unique blockchain system.

![http://www.digitalnote.org](docs/digitalnote_logo.png)

Official website: [► Digitalnote.org](http://www.digitalnote.org)
White paper: [► WHITEPAPER](https://digitalnote.org/wp-content/uploads/2020/02/DigitalNote_Whitepaper.pdf).


Support Contact
-------------------
Twitter: [► digitalnotexdn](https://twitter.com/digitalnotexdn)
Telegram: [► invite link](https://t.me/XDNDN)
Discord: [► invite link](https://discord.gg/4dUquty)


Official download
-------------------
github releases: [► DigitalNoteXDN/DigitalNote-2](https://github.com/DigitalNoteXDN/DigitalNote-2/releases)


Build instructions:
-------------------
DigitalNote Builder project: [► DigitalNoteXDN/DigitalNote-Builder](https://github.com/DigitalNoteXDN/DigitalNote-Builder)


Specifications and General info
-------------------
DigitalNote uses 

	* Secp256k1
	* Leveldb
	* Boost 1.80  
	* Berkeley DB 6.2.32
	* GMP 6.2.1
	* libevent 2.1.12
	* miniupnpc 2.2.4
	* Openssl 1.1.1s
	* QRencode 4.1.1
	* QT 5.15.7

General Specs

	* Block Spacing: 2 Minutes
	* Stake Minimum Age: 15 Confirmations (PoS-v3) | 30 Minutes (PoS-v2)
	* Port: 18092
	* RPC Port: 18094


License
-------------------

DigitalNote [XDN] is released under the terms of the MIT license. See [COPYING](COPYING) for more
information or see https://opensource.org/licenses/MIT.


Development Process
-------------------

The `master` branch is regularly built and tested, but is not guaranteed to be
completely stable. [Tags](https://github.com/DigitalNoteXDN/DigitalNote-1) are created
regularly to indicate new official, stable release versions of DigitalNote [XDN].

The Developer Team [Discord](https://discord.gg/4dUquty) should be used to discuss complicated or controversial changes before working
on a patch set.


Testing
-------------------

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don't match the project's coding conventions (see docs/coding.txt) or are controversial.

Testing and code review is the bottleneck for development; we get more pull
requests than we can review and test on short notice. Please be patient and help out by testing
other people's pull requests, and remember this is a security-critical project where any mistake might cost people
lots of money.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new stable release versions of DigitalNote.

Manual Quality Assurance (QA) Testing
-------------------

Changes should be tested by somebody other than the developer who wrote the
code. This is especially important for large or high-risk changes. It is useful
to add a test plan to the pull request description if testing the changes is
not straightforward.