Skip to content


Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Bitgesell (BGL)

Bitgesell (BGL) is an experimental digital currency
Explore more about project »

English · Chinese

Table of Contents
  1. About The Project
  2. Getting Started
  3. Roadmap
  4. Contributing
  5. License
  6. Contact
  7. Translations

About The Project

Product Name Screen Shot


  • secp256k1 ECDSA signing/verification and key generation.
  • Additive and multiplicative tweaking of secret/public keys.
  • Serialization/parsing of secret keys, public keys, signatures.
  • Constant time, constant memory access signing and public key generation.
  • Derandomized ECDSA (via RFC6979 or with a caller provided function.)
  • Very efficient implementation.
  • Suitable for embedded systems.
  • Optional module for public key recovery.
  • Optional module for ECDH key exchange.
  • Optional module for Schnorr signatures according to BIP-340 (experimental).

Bitgesell is a fork of BGL 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 BGL 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 (see doc/build-*.md for instructions) and tested, but is not guaranteed to be completely stable.

    tags are created regularly to indicate new official, stable release versions of BGL Core.

Built With

Getting Started

Visit official website: click here

The 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

Automated Testing

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/

There are also regression and integration tests, written in Python.
These tests can be run (if the test dependencies with: test/functional/

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.

Manual Quality Assurance (QA) Testing

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

$ mkdir -p coverage
$ gcovr --exclude 'src/bench*' --html --html-details -o coverage/coverage.html

If you don't mind more setup in return for more speed, replace autocomplete-clang and linter-clang with you-complete-me. This requires setting up ycmd.

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.

  1. Fork the Project
  2. Create your Feature Branch
  3. Commit your Changes
  4. Push to the Branch
  5. 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.