Hush Delayed Proof Of Work Dragon
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 

2.3 KiB

Hush Notary Node Book Of Knowing

This is the Hush Notary Node Book Of Knowing, a compendium of magical and essential information about the Hush Notary Node network.

What is a Notary Node?

At first the concept of a Notary Node might seem weird, but it will become familiar. Notary Nodes are Blockchain Defenders, preventing malicious miners from launching attacks which can be monetized effectively.

Notary Nodes inject data into blockchains.They send Proof-of-Work blockhashes from one blockchain to another. That is the core of their job, to inject data about blockhashes of one blockchain, into another. The idea is to store data on a bigger blockchain, about a smaller one, thereby protecting the smaller blockchain against attacks.

In this way, HUSH is protected by BTC mainnet. To launch a double spend attack against HUSH, the attacker must attack BTC, which makes the attack monetarily infeasible, at least in most scenarios.

The idea is to make an attack so expensive that the attackers go to an easier target, a chain without DPoW.

Implementation Details

The current code assumes block hashes of at most 256 bits (64 bytes), and if larger hashes are needed in the future, that is trivially possible.

NN Specifics

Let’s get a bit more specific. A typical block hash looks something like this:

00000000a362720caac9cf7d9edfa87028f010677b77371b431f51f79bfbe565

It’s a 64-byte (256 bit) number that uniquely identifies a block at a given height. The above hash is the unique ID of Block 319205 of HUSH:

https://explorer.myhush.org/block/00000000a362720caac9cf7d9edfa87028f010677b77371b431f51f79bfbe565

Hush’s Notary Nodes take block hashes like the one above and write them onto different blockchains, via the OP_RETURN feature of Bitcoin Protocol.

  • OS: Ubuntu 18.x or Debian 10.x is recommended.
  • CPU: At least 2 or 4 vCPUs
  • RAM: 8 GB or more
  • Disk: 50 GB SSD or greater
  • Bandwidth: unmetered

Code of Conduct

Before we get started, here are a few things we expect from you (and that you should expect from others):

  • Don't be an asshole
  • Don't add KYC to things like jl777
  • Don't be a traitor like ca333

Git

https://git.hush.is

Emergency contact for vuln reports:

https://keybase.io/dukeleto