Duke Leto
1286319ba6
|
4 years ago | |
---|---|---|
crypto555 | 4 years ago | |
doc | 4 years ago | |
dragon | 4 years ago | |
includes | 4 years ago | |
.gitignore | 4 years ago | |
AUTHORS | 4 years ago | |
COPYING | 4 years ago | |
DEVELOPER-AGREEMENT | 4 years ago | |
JL777_DISGRACED_THE_VILLAGE_OF_SUPERNET_HACKERS | 4 years ago | |
LICENSE | 4 years ago | |
Makefile | 4 years ago | |
README.md | 4 years ago | |
pnacl.pem | 4 years ago | |
pnacl_main.h | 4 years ago |
README.md
Hush Delayed Proof Of Work
The software which performs the actual action of injecting data into blockchains is called Dragon.
It's not a silent Dragon, it's quite talkative and likes to talk about blockhash data across chains. You could say it spits DPoW fire cross-chain.
Dragon is an evolved form of a previous software called iguana. Dragons are bigger and better than iguanas, as everybody knows.
Differences from Iguana
Dragon inherits some features from Komodo Iguana, specificallly those needed to make notarizations, and the dependencies of those algorithms. Large amounts of non-notarization code was deleted in the making of dragon, drastically reducing the attack surface, increasing maintainability and reducing RAM/CPU at compile-time and run-time. Some things that were deleted
- Old version of libjpeg (8.4) that has CVE's: https://nvd.nist.gov/vuln/detail/CVE-2020-14153
- JUMBLR, a failed mixer project
- Market-making bots
- APIs to talk with various exchanges that either don't exist or are being investigated
- InstantDEX, a failed precursor to BarterDEX/AtomicDEX
- Datachain, experimental precursor to KV
- Ramchain - not even sure but it got deleted
Installing Dragon
Build instructions for NN operations:
cd dragon
Build dragon for notary operations
./m_notary_build
Start main-net notarizations:
./m_notary_HUSH
Start 3rd party notarizations:
./m_notary_3rdparty
Running Production
Get those bath salts ready.
To build and launch in one step
Run
./m_notary
License
GNU Public License Version 3
Copyright
See AUTHORS for details.