namecoin-canaries's Introduction

Namecoin

Namecoin is a decentralized key/value registration and transfer system based on Bitcoin technology (a decentralized cryptocurrency).

It can be used for multiple purposes, for example a secure and censorship resistant replacement for DNS.

Ownership of a name is based on ownership of a coin, which is in turn based on public key cryptography. The namecoin network reaches consensus every few minutes as to which names have been reserved or updated.

There is a FAQ.md to answer some general questions.

See http://namecoin.info or http://dot-bit.org for more information.

Technical

The Bitcoin protocol is augmented with namecoin operations, to reserve, register and update names. In addition to DNS like entries, arbitrary name/value pairs are allowed and multiple namespaces will be available. This will include a personal handle namespace mapping handles to public keys and personal address data.

The protocol differences from bitcoin include:

Different blockchain, port, IRC bootstrap and message header
New transaction types: new, first-update, update
Validation on the new transaction types
RPC calls for managing names
Network fees to slow down the initial rush

Please read DESIGN-namecoind.md for details.

BUILDING

Building is supported on Linux, Windows and Mac. For building on windows you can use the scripts in ./contrib/easywinbuilder. Find build instructions on https://wiki.namecoin.info/index.php?title=Build_Namecoin_From_Source.

namecoin-canaries's People

Contributors

Stargazers

Watchers

namecoin-canaries's Issues

Cross-checking with blockchain data

Due to my pretty limited pgp skills I can think of only this method of cross-checking the signature verification with uncensorable information on the Namecoin blockchain:

./namecoin-cli name_show id/domob
---> d•domob.eu, fpr:1142850E6DFF65BA63D688A8B2492AC4A7330737
curl 'https://sks-keyservers.net/pks/lookup?op=get&options=mr&search=0x1142850E6DFF65BA63D688A8B2492AC4A7330737' | gpg --import
---> ... "Daniel Kraft <d•domob.eu>" ...
gpg --verify  canary-001-2017.md.sig.domob  canary-001-2017.md
---> gpg: Good signature from "Daniel Kraft <d•domob.eu>"
---> Primary key fingerprint: 1142 850E 6DFF 65BA 63D6  88A8 B249 2AC4 A733 0737

./namecoin-cli name_show id/hlandau
---> hlandau•devever.net, fpr:95A9908DDFA16830BE9FB9003D30A3A9FF1360DC
curl 'https://sks-keyservers.net/pks/lookup?op=get&options=mr&search=0x95A9908DDFA16830BE9FB9003D30A3A9FF1360DC' | gpg --import
---> "Hugo Landau (2013 Principal) <hlandau•devever.net>"
gpg --verify  canary-001-2017.md.sig.hlandau  canary-001-2017.md
---> Good signature from "Hugo Landau (2013 Principal) <hlandau•devever.net>"
---> Primary key fingerprint: 95A9 908D DFA1 6830 BE9F  B900 3D30 A3A9 FF13 60DC

Both Daniel's and Hugo's data look consistent. When I try verifying @JeremyRand's signature I run into issues:

./namecoin-cli name_show id/jeremy
---> jeremy•veclabs.net, fpr:9B0FCA28C8A773B514B4775801CDFC46D9D72D3A
curl 'https://sks-keyservers.net/pks/lookup?op=get&options=mr&search=0x9B0FCA28C8A773B514B4775801CDFC46D9D72D3A' | gpg --import
---> "Jeremy Rand <jeremy•veclabs.net>"
gpg --verify  canary-001-2017.md.sig.jeremy  canary-001-2017.md
---> "jeremyrand•airmail.cc"
---> Can't check signature: No public key

How can I tell (or anybody else trying to monitor the canary's health) that jeremy•veclabs.net and jeremyrand•airmail.cc are identical?

Recommend Projects

namecoin / namecoin-canaries Goto Github PK

namecoin-canaries's Introduction

Namecoin

Technical

BUILDING

namecoin-canaries's People

Contributors

Stargazers

Watchers

Forkers

namecoin-canaries's Issues

Cross-checking with blockchain data

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent