Bitgesell (BGL) is an experimental digital currency
Explore more about project »
English
·
Chinese
Table of Contents
BGL is an experimental digital currency that enables instant payments to anyone, anywhere in the world. BGL uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. BGL Core is the name of open source software which enables the use of this currency.
Bitgesell is a fork of bitcoin with the following changes:
- Block Reward [Burn rate is 90% of tx fees]
nFees*0.1 + GetBlockSubsidy()
- Block Weight [10 times smaller than Bitcoin]
<= 400,000 - 100% Segwit
Eliminates problems with legacy type of transactions - Halving Interval [Halving cycle of bitgetsell is 1yr while that of bitcoin is 4yr]
210000 blocks/4
- Block Subsidy [Max coins = 21,000,000]
210000 blocks/4
Hashing algorithm for blocks is Keccak (sha-3).
The master branch is regularly built (seedoc/build-*.mdfor instructions) and tested, but is not guaranteed to be completely stable.
tagsare created regularly to indicate new official, stable release versions of BGL Core.
Visit official website: click here
The https://github.com/BGL-core/gui repository is used exclusively for the development of the GUI. Its master branch is identical in all monotree repositories. Release branches and tags do not exist, so please do not fork that repository unless it is for development reasons.
Official thread: click here
Developers are strongly encouraged to write unit tests for new code, and to
submit new unit tests for old code. Unit tests can be compiled and run
(assuming they weren't disabled in configure) with: make check. Further details on running
and extending unit tests can be found in src/test/README.md.
There are also regression and integration tests, written
in Python.
These tests can be run (if the test dependencies with: test/functional/test_runner.py
The CI (Continuous Integration) systems make sure that every pull request is built for Windows, Linux, and macOS,
and that unit/sanity tests are run automatically.
Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.
See the open issues for a list of proposed features (and known issues).
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.
- Fork the Project
- Create your Feature Branch
- Commit your Changes
- Push to the Branch
- Open a Pull Request
Distributed under the MIT License. See LICENSE for more information.
Discord - Bitgesell
Twitter: Bitgesell
Medium: Bitgesell
Facebook: Bitgesell
Changes to translations as well as new translations can be submitted to BGL Core's Transifex page.
Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.
Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.