BigUP Wallet
C++ Python Assembly HTML C QMake Other
Switch branches/tags
Nothing to show
Clone or download
BigUps Update main.h
Significant inflation rate reduction added to base source code. Stake rate from 100%/year to 5%/year

It is up to the community to update their wallets, compile new binaries, etc. Then, if everyone (or the majority) switches to the new version, the supply will become more manageable

This is the first of a few actions that should hopefully motivate people to do things differently
Latest commit 308f8b3 Apr 19, 2017
Permalink
Failed to load latest commit information.
contrib First commit Feb 19, 2016
doc First commit Feb 19, 2016
share First commit Feb 19, 2016
src Update main.h Apr 19, 2017
Bigup-qt.pro First commit Feb 19, 2016
COPYING First commit Feb 19, 2016
INSTALL First commit Feb 19, 2016
README First commit Feb 19, 2016
README.md First commit Feb 19, 2016

README.md

Bigup development tree

Bigup 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 Bigup.

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'.