• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

.github/H28-Jan-2021-17062

.tx/H28-Jan-2021-86

build-aux/m4/H28-Jan-2021-3,4052,976

build_msvc/H28-Jan-2021-2,2321,848

ci/H28-Jan-2021-1,161743

contrib/H28-Jan-2021-10,0097,731

depends/H28-Jan-2021-6,7545,747

doc/H03-May-2022-27,16922,427

share/H28-Jan-2021-627362

src/H03-May-2022-480,096410,713

test/H28-Jan-2021-54,22739,554

.appveyor.ymlH A D28-Jan-20213.4 KiB6463

.cirrus.ymlH A D28-Jan-20215.2 KiB145130

.fuzzbuzz.ymlH A D28-Jan-2021971 1716

.gitattributesH A D28-Jan-202135 21

.gitignoreH A D28-Jan-20211.9 KiB152126

.python-versionH A D28-Jan-20216 21

.style.yapfH A D28-Jan-20217.8 KiB262215

.travis.ymlH A D28-Jan-20213.2 KiB7771

CODEOWNERSH A D28-Jan-20214.6 KiB137107

CONTRIBUTING.mdH A D28-Jan-202120.9 KiB437330

COPYINGH A D28-Jan-20211.1 KiB2318

ChangesH A D28-Jan-20212.1 KiB4132

INSTALL.mdH A D28-Jan-2021161 64

Makefile.amH A D28-Jan-202112.7 KiB360284

README.mdH A D28-Jan-20214.3 KiB9967

SECURITY.mdH A D28-Jan-2021850 2113

TODOH A D28-Jan-2021750 2216

autogen.shH A D28-Jan-2021546 1711

configure.acH A D28-Jan-202167.6 KiB1,7801,560

libnamecoinconsensus.pc.inH A D28-Jan-2021268 119

README.md

1Namecoin Core integration/staging tree
2=====================================
3
4[![Build Status](https://travis-ci.org/namecoin/namecoin-core.svg?branch=master)](https://travis-ci.org/namecoin/namecoin-core)
5
6https://namecoin.org
7
8What is Namecoin?
9----------------
10
11Namecoin is a decentralized open source information registration and transfer system based on the Bitcoin cryptocurrency.
12
13What does it do?
14----------------
15
16* Securely record and transfer arbitrary names (keys).
17* Attach a value (data) to the names (up to 520 bytes, more in the future).
18* Transact namecoins, the digital currency (ℕ, NMC).
19
20Namecoin was the first fork of Bitcoin and still is one of the most innovative altcoins. It was first to implement merged mining and a decentralized DNS. Namecoin squares Zooko's Triangle!
21
22What can it be used for?
23----------------
24
25* Protect free-speech rights online by making the web more resistant to censorship.
26* Access websites using the .bit domain (with TLS/SSL).
27* Store identity information such as email, GPG key, BTC address, TLS fingerprints, Bitmessage address, etc.
28* Human readable Tor .onion names/domains.
29* File signatures, Voting, bonds/stocks,/shares, web of trust, escrow and notary services (to be implemented).
30
31For more information, as well as an immediately useable, binary version of
32the Namecoin Core software, see https://www.namecoin.org/download.
33
34License
35-------
36
37Namecoin Core is released under the terms of the MIT license. See [COPYING](COPYING) for more
38information or see https://opensource.org/licenses/MIT.
39
40Development Process
41-------------------
42
43The `master` branch is regularly built (see doc/build-*.md for instructions) and tested, but is not guaranteed to be
44completely stable. [Tags](https://github.com/namecoin/namecoin-core/tags) are created
45regularly to indicate new official, stable release versions of Namecoin Core.
46
47The contribution workflow is described in [CONTRIBUTING.md](CONTRIBUTING.md)
48and useful hints for developers can be found in [doc/developer-notes.md](doc/developer-notes.md).
49
50The developer [forum](https://forum.namecoin.info/viewforum.php?f=4)
51should be used to discuss complicated or controversial changes before working
52on a patch set.
53
54Developer IRC can be found on Freenode at #namecoin-dev.
55
56Testing
57-------
58
59Testing and code review is the bottleneck for development; we get more pull
60requests than we can review and test on short notice. Please be patient and help out by testing
61other people's pull requests, and remember this is a security-critical project where any mistake might cost people
62lots of money.
63
64### Automated Testing
65
66Developers are strongly encouraged to write [unit tests](src/test/README.md) for new code, and to
67submit new unit tests for old code. Unit tests can be compiled and run
68(assuming they weren't disabled in configure) with: `make check`. Further details on running
69and extending unit tests can be found in [/src/test/README.md](/src/test/README.md).
70
71There are also [regression and integration tests](/test), written
72in Python, that are run automatically on the build server.
73These tests can be run (if the [test dependencies](/test) are installed) with: `test/functional/test_runner.py`
74
75The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.
76
77### Manual Quality Assurance (QA) Testing
78
79Changes should be tested by somebody other than the developer who wrote the
80code. This is especially important for large or high-risk changes. It is useful
81to add a test plan to the pull request description if testing the changes is
82not straightforward.
83
84Translations
85------------
86
87**Translation workflow is not yet set up for Namecoin Core.  For strings which are common to Bitcoin Core, see below.**
88
89Changes to translations as well as new translations can be submitted to
90[Bitcoin Core's Transifex page](https://www.transifex.com/bitcoin/bitcoin/).
91
92Translations are periodically pulled from Transifex and merged into the git repository. See the
93[translation process](doc/translation_process.md) for details on how this works.
94
95**Important**: We do not accept translation changes as GitHub pull requests because the next
96pull from Transifex would automatically overwrite them again.
97
98Translators should also subscribe to the [mailing list](https://groups.google.com/forum/#!forum/bitcoin-translators).
99