Moved the abstract to the yaml to allow more freedom to globally manipulate
doc format, and to reduced boilerplate repetition in each web page in accordance with the dry principle modified: docs/manifesto/crypto_currency_as_a_wide_area_distributed.md modified: docs/manifesto/lightning.md modified: docs/manifesto/motivation.md modified: docs/manifesto/scalability.md modified: docs/manifesto/social_networking.md modified: docs/pandoc_templates/pandoc.template
This commit is contained in:
parent
a10790026a
commit
ce79e3515d
@ -1,13 +1,19 @@
|
||||
---
|
||||
lang: en
|
||||
title: Crypto Currency as a wide area distributed database
|
||||
abstract: >-
|
||||
In <a href="scalability.html" target="_blank">Scalable and private blockchain</a>
|
||||
I note that the proposed blockchain structure maps directly to sql,
|
||||
and is often easiest to design if one thinks about it as if an sql database.
|
||||
Eventually we want everything in the world that relates to property ownership,
|
||||
contracts, agreements, financial relationships, and ongoing disputes,
|
||||
that Ann chooses to make accessible to Bob, accessible through sql code running on Bob's computer,
|
||||
and included in the pre-image of the blockchain root hash,
|
||||
so that Ann can prove to Bob that she is showing the same thing to Bob as to everyone else,
|
||||
and is not re-inventing the past, it is the same thing, or validly derived from,
|
||||
what she always showed.
|
||||
---
|
||||
|
||||
::: myabstract
|
||||
[abstract:]{.bigbold}
|
||||
In [Scalable and private blockchain](scalability.html){target="_blank"} I note that the proposed blockchain structure maps directly to sql, and is often easiest to design if one thinks about it as if an sql database. Eventually we want everything in the world that relates to property ownership, contracts, agreements, financial relationships, and ongoing disputes, that Ann chooses to make accessible to Bob, accessible through sql code running on Bob's computer, and included in the pre-image of the blockchain root hash, so that Ann can prove to Bob that she is showing the same thing to Bob as to everyone else, and is not re-inventing the past, it is the same thing, or validly derived from, what she always showed.
|
||||
:::
|
||||
|
||||
Much of this material is shamelessly plaigarized without [attribution.](http://docplayer.net/14501083-Blockchain-throughput-and-big-data-trent-mcconaghy.html)
|
||||
|
||||
Bitcoin has dangerously few miners, subject to dangerously few political authorities, and miner interests are insufficiently aligned to currency user interests.
|
||||
|
@ -4,13 +4,15 @@ title: >-
|
||||
How to do lightning right
|
||||
sidebar: false
|
||||
notmine: false
|
||||
abstract: >-
|
||||
Lightning is about to replace SWIFT for international transactions,
|
||||
due to high SWIFT fees, slow transactions,
|
||||
and the disruptive weaponization of SWIFT in imperial wars.
|
||||
It is already taking a significant bite out of SWIFT,
|
||||
which is likely to very soon become an enormous bite.
|
||||
This will immensely increase the value of Bitcoin. But lightning is very hard to use.
|
||||
---
|
||||
|
||||
::: myabstract
|
||||
[abstract:]{.bigbold}
|
||||
Lightning is about to replace SWIFT for international transactions, due to high SWIFT fees, slow transactions, and the disruptive weaponization of SWIFT in imperial wars. It is already taking a significant bite out of SWIFT, which is likely to very soon become an enormous bite. This will immensely increase the value of Bitcoin. But lightning is very hard to use.
|
||||
:::
|
||||
|
||||
Lightning software still sucks appallingly. Nice solutions are centralized and custodial. Mutiny wallet and electrum is non custodial, but their profit model that made it possible to pay people to produce nice software relies on rather more quiet centralization that is admitted.
|
||||
|
||||
Someone who owns a lot more bitcoin than I do should fund development of a lightning wallet done right in order to increase the value of Bitcoin.
|
||||
|
@ -1,15 +1,12 @@
|
||||
---
|
||||
lang: en
|
||||
title: Why we need a better crypto currency
|
||||
abstract: >-
|
||||
Why we need to build internet protocols that rest on
|
||||
the consensus of the blockchain, rather than the authority
|
||||
of giant organizations
|
||||
---
|
||||
|
||||
::: myabstract
|
||||
[abstract:]{.bigbold}
|
||||
Why we need to build internet protocols that rest on
|
||||
the consensus of the blockchain, rather than the authority
|
||||
of giant organizations
|
||||
:::
|
||||
|
||||
To secure a crypto currency against hostile forces, we
|
||||
need to secure people's ability to hold conversations,
|
||||
including conversations about payment, contracts, and
|
||||
|
@ -4,13 +4,18 @@ title: >-
|
||||
Scalable and private blockchain
|
||||
sidebar: true
|
||||
notmine: false
|
||||
abstract: >-
|
||||
Bitcoin does not scale to the required size.
|
||||
The Bitcoin reliable broadcast channel is a massively replicated public ledger of every transaction that ever there was,
|
||||
each of which has to be evaluated for correctness by every full peer.
|
||||
With recursive snarks, we can now instead have a massively replicated public SQL index of private ledgers.
|
||||
Such a blockchain with as many transactions as bitcoin, will, after running for as long as Bitcoin,
|
||||
only occupy a few dozen megabytes of disk storage, rather than near a terabyte,
|
||||
and each peer and client wallet only has to evaluate the root recursive snark
|
||||
to prove the validity of every transaction that ever there was,
|
||||
including all those lost in the mists of time.
|
||||
...
|
||||
|
||||
::: myabstract
|
||||
[abstract:]{.bigbold}
|
||||
Bitcoin does not scale to the required size. The Bitcoin reliable broadcast channel is a massively replicated public ledger of every transaction that ever there was, each of which has to be evaluated for correctness by every full peer. With recursive snarks, we can now instead have a massively replicated public SQL index of private ledgers. Such a blockchain with as many transactions as bitcoin, will, after running for as long as Bitcoin, only occupy a few dozen megabytes of disk storage, rather than near a terabyte, and each peer and client wallet only has to evaluate the root recursive snark to prove the validity of every transaction that ever there was, including all those lost in the mists of time.
|
||||
:::
|
||||
|
||||
# Scaling, privacy, and recursive snarks
|
||||
|
||||
Bitcoin does not not scale because it is a massively replicated public ledger.
|
||||
|
@ -4,12 +4,12 @@ title: >-
|
||||
Social networking
|
||||
sidebar: true
|
||||
notmine: false
|
||||
abstract: >-
|
||||
Speech is suppressed by censorship, and on "free speech" platforms by state sponsored shill spam.
|
||||
Crypto currency transaction metadata goes over insecure networks, so we need a secure, uncensorable, and spam resistent
|
||||
Web 3.0 both for freedom of speech and economic freedom.
|
||||
...
|
||||
|
||||
::: myabstract
|
||||
[abstract:]{.bigbold}
|
||||
Speech is suppressed by censorship, and on "free speech" platforms by state sponsored shill spam. Crypto currency transaction metadata goes over insecure networks, so we need a secure, uncensorable, and spam resistent Web 3.0 both for freedom of speech and economic freedom.
|
||||
:::
|
||||
# the crisis of censorship
|
||||
|
||||
If we have a mechanism capable of securely handling arbitrary free form
|
||||
|
@ -93,6 +93,12 @@ $table-of-contents$
|
||||
</nav>
|
||||
$endif$
|
||||
$endif$
|
||||
$if(abstract)$
|
||||
<div class="myabstract">
|
||||
<p><span class="bigbold">abstract:</span>
|
||||
$abstract$
|
||||
</div>
|
||||
$endif$
|
||||
$body$
|
||||
$if(sidebar)$
|
||||
</div>
|
||||
|
Loading…
Reference in New Issue
Block a user