This article may rely excessively on sources too closely associated with the subject, potentially preventing the article from being verifiable and neutral. (June 2014) |
Namecoin (Abbreviation: NMC; sign: ) is a cryptocurrency originally forked from bitcoin software. It uses proof-of-work algorithm. Like bitcoin, it is limited to 21 million coins.[5]
Denominations | |
---|---|
Plural | namecoins |
Symbol | [citation needed] |
Code | NMC |
Subunits | |
1⁄1000 | millinamecoin |
1⁄1000000 | micronamecoin |
1⁄100000000 | swartz |
Development | |
Original author(s) | Vincent Durham |
Initial release | 18 April 2011[1] |
Latest release | 0.21.0[2] / 29 January 2021 |
Code repository | https://github.com/namecoin/namecoin-core |
Development status | Active |
Project fork of | Bitcoin |
Ledger | |
Ledger start | 17 April 2011[3] |
Timestamping scheme | Proof-of-work (merged mining)[4] |
Hash function | SHA-256 |
Block time | 10 minutes[5] |
Block explorer | bitinfocharts nmc |
Supply limit | 21,000,000[5] |
Website | |
Website | www.namecoin.org |
Namecoin can store data within its own blockchain transaction database. The original proposal for Namecoin called for Namecoin to insert data into bitcoin's blockchain directly. Anticipating scaling difficulties with this approach, a shared proof-of-work system was proposed to secure new cryptocurrencies with different use cases.
Namecoin's flagship use case is the censorship-resistant top level domain .bit
, which is functionally similar to .com
or .net
domains but is independent of the Internet Corporation for Assigned Names and Numbers, the main governing body for domain names.[6] In practice, the top level domain is used by a handful of functional websites. As of 2019, OpenNIC no longer supports the .bit domain.
Transactions
A peer-to-peer network similar to handles Namecoin's transactions, balances and issuance through a based proof-of-work scheme (they are issued when a small enough hash value is found, at which point a block is created).[7]
Records
Each Namecoin record consists of a name and a value. Each name is actually a path, with the namespace preceding the name of the record. The key d/example
signifies a record stored in the DNS namespace d
with the name example
and corresponds to the record for the example.bit
website. The content of d/example
is expected to conform to the DNS namespace specification. As of 2015[update], the fee for a record was 0.01 NMC and records expired after 36000 blocks (~200 days) unless updated or renewed.[7]
Uses
.bit is a top-level domain, created outside the commonly used Domain Name System, and is not sanctioned by ICANN. The .bit domain is served via Namecoin infrastructure, which acts as a decentralized domain name system.[7]
Proposed potential uses for Namecoin besides domain name registration include notary/timestamp systems.[8]
History
In September 2010, a discussion was started[by whom?] in the BitcoinTalk forum about a hypothetical system called BitDNS and generalizing bitcoin. Gavin Andresen and Satoshi Nakamoto joined the discussion in the BitcoinTalk forum and supported the idea of BitDNS, and a reward for implementing BitDNS was announced on the forum in December 2010.[citation needed]
On block 19200 Namecoin activated the merged mining upgrade to allow mining of Bitcoin and Namecoin simultaneously, instead of having to choose between one or the other; this fixed the issue of miners jumping from one blockchain to another when the profitability becomes favorable in the former.[4]
Two years later, in June 2013, NameID was launched.[9] NameID allows to associate profile information with identities on the Namecoin blockchain, and an OpenID provider to allow logging into existing websites with Namecoin identities. The main site itself is accompanied by an open protocol for password-less authentication with Namecoin identities, a corresponding free-software implementation and a supporting extension for Firefox.[citation needed]
In October 2013, Michael Gronager, main developer of libcoin, found a security issue in the Namecoin protocol, which allowed modifying foreign names. It was successfully fixed in a short timeframe and was never exploited, except for bitcoin.bit as a proof-of-concept.[10][citation needed]
Namecoin was also mentioned by ICANN in a public report as the most well-known example of distributing control and privacy in DNS.[11]
A 2015 study found that of the 120,000 domain names registered on Namecoin, only 28 were in use.[7]
In December 2018, a proposal was tabled on the OpenNIC mailing list to drop support for Namecoin .bit domains.,[12] citing Spamhaus' (and by extension other antivirus software) blocking of several of their servers owing to spread of malware from some .bit domains, as well as concerns about potential child pornography. The vote did not reach a consensus.[13]
In the same month, OpenNIC was advised to drop support for .bit namespace owing to security concerns of Namecoin and PRISM Break developers.[14]
In July 2019, OpenNIC again voted on dropping the .bit namespace, citing "numerous problems with support of NameCoin domains" and recent animosity between the two projects. The vote passed.[15] Namecoin developer Jeremy Rand welcomed the move, thanking OpenNIC and describing it as the "right decision".[16][17][18]
See also
- Alternative DNS root
- Zooko's triangle
- Non-fungible token (a concept which Namecoin is sometimes considered a precursor of)
References
- ^ "[announce] Namecoin - a distributed naming system based on Bitcoin". bitcointalk.org.
- ^ "Releases - namecoin/namecoin-core". Archived from the original on 2020-11-09. Retrieved 2021-03-03 – via GitHub.
- ^ "Block #0". namebrow.se. Archived from the original on 2021-08-02. Retrieved 2021-03-03.
- ^ a b "Merged Mining: Analysis of Effects and Implications". repositum.tuwien.ac.at. Archived from the original on 2020-11-11. Retrieved 2018-12-24.
- ^ a b c Loibl, Andreas (2014-08-01). "Namecoin" (PDF). Archived (PDF) from the original on 2022-05-18. Retrieved 2020-11-26.
- ^ Dourado, Eli (2014-02-05). "Can Namecoin Obsolete ICANN (and More)?". Theumlaut. Archived from the original on 2020-11-12. Retrieved 2020-11-26.
- ^ a b c d Kalodner, Harry; Carlsten, Miles; Ellenbogen, Paul; Bonneau, Joseph; Narayanan, Arvind (2015). "An empirical study of Namecoin and lessons for decentralized namespace design" (PDF). Workshop on the Economics of Information Security. CiteSeerX 10.1.1.698.4605. Archived (PDF) from the original on 2022-11-10. Retrieved 2022-11-10.
- ^ Kirk, Jeremy (2013-05-24). "Could the Bitcoin network be used as an ultrasecure notary service?". Techworld. Archived from the original on 2014-10-12. Retrieved 2013-07-02.
- ^ Kraft, Daniel (2013-07-25). "NameID - Use namecoin id/ to log into OpenID sites". Namecoin Forum. Archived from the original on 2015-05-14. Retrieved 2015-10-14.
- ^ bitcoin.bit name operation is in tx-id 2f034f2499c136a2c5a922ca4be65c1292815c753bbb100a2a26d5ad532c3919
- ^ "The Internet Corporation for Assigned Names and Numbers Identifier Technology Innovation Report" (PDF). ICANN. 2014-05-15. Archived (PDF) from the original on 2021-12-19. Retrieved 2021-10-17.
- ^ "Should we have a vote on .bit ?". opennic-discuss. Archived from the original on 2021-01-27. Retrieved 2021-03-02.
- ^ "Vote to keep or drop peering with NameCoin". opennic-discuss. Archived from the original on 2022-04-16. Retrieved 2021-03-02.
- ^ "Drop OpenNIC (!2073) · Merge Requests · PRISM Break / PRISM Break". GitLab. 19 December 2018. Archived from the original on 2021-01-28. Retrieved 2021-01-23.
- ^ "Should OpenNIC drop support for NameCoin [OpenNIC Wiki]". wiki.opennic.org. Archived from the original on 2021-10-29. Retrieved 2021-01-23.
- ^ "OpenNIC does the right thing: listens to security concerns and shuts down its centralized Namecoin inproxy". namecoin.org. Archived from the original on 2022-03-24. Retrieved 2021-03-02.
- ^ "Namecoin : l'intégrité, mais à quel prix?". ZDNet France (in French). 2019-08-01. Archived from the original on 2021-11-23. Retrieved 2021-11-27.
- ^ "What is Namecoin's relationship to OpenNIC?". namecoin.org. Archived from the original on 2022-07-26. Retrieved 2021-03-02.