(E)mail Client for Limited or Blocked Internet
There are two motivations for this idea.
Some countries, such as China and Belarus, are already blocking Tor. We can expect that some countries will try to block cryptocurrency protocols similarly in the future.
Governments often shut down the Internet during civil unrest. Previously there were partial or complete shutdowns in Egypt, Ethiopia, Sudan, Iran and Turkey.
However, people have the right to store their available value, whether the value is under threat from monetary policies, political instability, or war.
With digital communications and digital gold, we can solve this problem.
As a possible solution for Bitcoin, Blockstream satellite network could be used; however, the satellite signal could be jammed. Another option is email (usually last to be blocked ) or other uninteractive low-bandwidth means of communication (fax, modem call over a landline to a bulletin board system, mail).
So assume Alice is willing to buy X ERGs from Bob (paying with cash), but the Internet is limited or does not work in their area. Bob owns a box protected by a public key (stored locally). Then the protocol could be as follows.
- Bob creates a transaction from his box, creating a new box where X ERG are locked by the condition
Before deadline: Bob's signature and spending transaction have an output of *X* ergs which belongs to Alice's public key; After deadline: Bob's signature. We will refer to the new box as the "deal box".
Please note that outputs with respective identifiers are known for a signed transaction.
Bob sends the transaction over (e)mail to a gateway. The gateway sends an efficient NiPoPoW proof for a header having enough confirmations + proof of box membership against state digest from the header. This proof is small, tens of kilobytes. For better security, Bob may also ask another gateway for header proof.
Bob shows the proof to Alice. Alice checks proofs and ensures that the deadline will not likely be met when a new transaction with their deal reaches the Ergo blockchain. Bob signs the new transaction: spending the deal box created in step 1 and creating the output box for Alice.
Now, Alice sends the transaction signed by Bob to the gateway and gets the proof of inclusion from it.
With such small proofs (tens of kilobytes), email/fax/ADSL modem or even paperwork is acceptable for communication between the users and gateways.