Bitmessage : Différence entre versions
De WikiOpenTruc
m (→Concurrents) |
m (→Points communs avec bisq bitsquare) |
||
| Ligne 13 : | Ligne 13 : | ||
==Points communs avec bisq bitsquare== | ==Points communs avec bisq bitsquare== | ||
| + | * https://bisq.network/blog/new-p2p-network/ | ||
Additionally to the publicly readable data like the offers there are data stored which need to remain private. There are trade process messages which are stored in a kind of mailbox in case the peer is offline. Those data are encrypted and signed and also sent to every node for storage. Only the receiver (who has the private key) can decrypt the data. A similar approach is used in Bitmessage. | Additionally to the publicly readable data like the offers there are data stored which need to remain private. There are trade process messages which are stored in a kind of mailbox in case the peer is offline. Those data are encrypted and signed and also sent to every node for storage. Only the receiver (who has the private key) can decrypt the data. A similar approach is used in Bitmessage. | ||
Version du 22 décembre 2017 à 06:59
P2P, décentralisé, chiffré
Top language : python
- https://github.com/Bitmessage/PyBitmessage sur github, projet actif en 2017
Points communs avec bisq bitsquare
Additionally to the publicly readable data like the offers there are data stored which need to remain private. There are trade process messages which are stored in a kind of mailbox in case the peer is offline. Those data are encrypted and signed and also sent to every node for storage. Only the receiver (who has the private key) can decrypt the data. A similar approach is used in Bitmessage.
Concurrents
- https://crypviser.network/ pour le 20 août 2018 ... site souvent inaccessible ?
- https://www.coingecko.com/en/coins/cvcoin
- https://www.coingecko.com/en/price_charts/cvcoin/usd#panel chart date du 30/10/2017
