Switch branches/tags
Nothing to show
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
..
Failed to load latest commit information.
build
contrib
doc
json
leveldb
obj-test
obj
qt
share
test
zerocoin
COPYING
INSTALL
Makefile
Novapoints-qt.pro
README
README.md
addrman.cpp
addrman.h
alert.cpp
alert.h
allocators.h
base58.h
bignum.h
bitcoinrpc.cpp
bitcoinrpc.h
checkpoints.cpp
checkpoints.h
clientversion.h
coincontrol.h
compat.h
crypter.cpp
crypter.h
db.cpp
db.h
init.cpp
init.h
irc.cpp
irc.h
kernel.cpp
kernel.h
key.cpp
key.h
keystore.cpp
keystore.h
main.cpp
main.h
makefile.bsd
makefile.linux-mingw
makefile.mingw
makefile.osx
makefile.unix
miner.cpp
miner.h
mruset.h
net.cpp
net.h
netbase.cpp
netbase.h
noui.cpp
pbkdf2.cpp
pbkdf2.h
protocol.cpp
protocol.h
rpcblockchain.cpp
rpcdump.cpp
rpcmining.cpp
rpcnet.cpp
rpcrawtransaction.cpp
rpcwallet.cpp
script.cpp
script.h
scrypt-arm.S
scrypt-x86.S
scrypt-x86_64.S
scrypt.cpp
scrypt.h
serialize.h
strlcpy.h
sync.cpp
sync.h
threadsafety.h
txdb-leveldb.cpp
txdb-leveldb.h
txdb.h
ui_interface.h
uint256.h
util.cpp
util.h
version.cpp
version.h
wallet.cpp
wallet.h
walletdb.cpp
walletdb.h

README.md

Novapoints development tree

Novapoints is a PoS-based cryptocurrency.

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don't match the project's coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new stable release versions of Novapoints.

Feature branches are created when there are major new features being worked on by several people.

From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'.