forked from cheng/wallet
still pondering cold start
This commit is contained in:
parent
ab0b426bb8
commit
c1e5d47ae9
@ -945,6 +945,10 @@ Then take over Monero's niche by being a better Monero.
|
|||||||
Then take over Bitcoin and Nostr's niche by being a better Bitcoin and a better Nostr,
|
Then take over Bitcoin and Nostr's niche by being a better Bitcoin and a better Nostr,
|
||||||
because recursive snarks can do lots of things, such as smart contracts, better than they can.
|
because recursive snarks can do lots of things, such as smart contracts, better than they can.
|
||||||
|
|
||||||
|
This is the tactic that keet, holepunch, pear, and Particl are attempting to deploy, but
|
||||||
|
their software is so far unusable. The niche is still effectively vacant and open
|
||||||
|
for the taking.
|
||||||
|
|
||||||
## failure of previous altcoins to solve Cold Start.
|
## failure of previous altcoins to solve Cold Start.
|
||||||
|
|
||||||
During the last decade, numberless altcoins have attempted to compete with
|
During the last decade, numberless altcoins have attempted to compete with
|
||||||
@ -976,9 +980,10 @@ network, and without the rest of the network needing to know what that there was
|
|||||||
a contract, what that contract is nor to be able to evaluate it.
|
a contract, what that contract is nor to be able to evaluate it.
|
||||||
Because of its privacy mechanism,
|
Because of its privacy mechanism,
|
||||||
|
|
||||||
Monero cannot do contracts, which prevents atomic exchange between Monero
|
Monero cannot do contracts, which renders atomic exchange between Monero
|
||||||
and Bitcoin, and prevents Monero from doing a lightning network that would
|
and Bitcoin difficult and unduly complicated, and prevents Monero from
|
||||||
enable fast atomic exchange between itself and Bitcoin lightning.
|
doing a lightning network that would enable fast atomic exchange between
|
||||||
|
itself and Bitcoin lightning.
|
||||||
|
|
||||||
In order to do atomic exchanges between two blockchains, which is to say,
|
In order to do atomic exchanges between two blockchains, which is to say,
|
||||||
to enable people to move value between one blockchain and another without
|
to enable people to move value between one blockchain and another without
|
||||||
@ -1004,7 +1009,7 @@ being, unlike Monero, a better Bitcoin.
|
|||||||
### Bitmessage
|
### Bitmessage
|
||||||
|
|
||||||
The lowest hanging fruit of all, (because, unfortunately, there is
|
The lowest hanging fruit of all, (because, unfortunately, there is
|
||||||
no money or prospect for money in it) is to replace Bitmessage.
|
no money or prospect for money in it) is to replace Bitmessage,
|
||||||
Which is currently abandonware, which has ceased working on most platforms,
|
Which is currently abandonware, which has ceased working on most platforms,
|
||||||
has never supported humanly intelligible names, and lacks the
|
has never supported humanly intelligible names, and lacks the
|
||||||
moderation capability to grey list, blacklist, and whitelist names
|
moderation capability to grey list, blacklist, and whitelist names
|
||||||
@ -1016,6 +1021,11 @@ So next step, after capturing its abandoned market niche,
|
|||||||
is to integrate payment mechanisms, in particular to integrate
|
is to integrate payment mechanisms, in particular to integrate
|
||||||
core lightning, which brings us a little closer to the faint smell of money.
|
core lightning, which brings us a little closer to the faint smell of money.
|
||||||
|
|
||||||
|
Bitmessage is long overdue to be replaced, and Keef and Particl attempted
|
||||||
|
to replace it, as a starting point to get their respective crypto currencies of the ground
|
||||||
|
so far without success, for their software is so far even less usable and more broken
|
||||||
|
than Bitmessage.
|
||||||
|
|
||||||
### Integrating money
|
### Integrating money
|
||||||
|
|
||||||
So we create our own currency. But because it will be created on sovcorp model
|
So we create our own currency. But because it will be created on sovcorp model
|
||||||
|
@ -251,6 +251,12 @@ ssh-keygen -t ed25519 -f /etc/ssh/ssh_host_ed25519_key
|
|||||||
Note that visual studio remote compile requires an `ecdsa-sha2-nistp256` key on the host machine that it is remote compiling for. If it is nist, it is
|
Note that visual studio remote compile requires an `ecdsa-sha2-nistp256` key on the host machine that it is remote compiling for. If it is nist, it is
|
||||||
backdoored
|
backdoored
|
||||||
|
|
||||||
|
To change the snake oil certificate:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
make-ssl-cert generate-default-snakeoil --force-overwrite
|
||||||
|
```
|
||||||
|
|
||||||
### .bashrc
|
### .bashrc
|
||||||
|
|
||||||
If the host has a domain name, the default in `/etc/bash.bashrc` will not display it in full at the prompt, which can lead to you being confused about which host on the internet you are commanding.
|
If the host has a domain name, the default in `/etc/bash.bashrc` will not display it in full at the prompt, which can lead to you being confused about which host on the internet you are commanding.
|
||||||
|
Loading…
Reference in New Issue
Block a user