Skip to content

wbubblerteam/bubcoin

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Bubcoin Core integration/staging tree

http://bit.do/wbubblercore-org

What is Bubcoin?

Bubcoin is

For an immediately usable, binary version of the Bubcoin Core software, see https://github.com/wbubblerteam/bubcoin/releases, or read the original whitepaper.

Disclaimer

Cyrptocurrency sucks ass!!
This is a joke
It's worthless and low power consumption because it's got low proof of work difficulty
Praise be to bub

What

What is Bubcoin?

Bubcoin is a joke cryptocurrency for trading with your friends, and some scripts for automatically creating your own version with your own name, logo recolour, and genesis block message.

Forked from the bitcoin core software https://github.com/bitcoin/bitcoin/

NAME: Bubcoin
CODE: BUB
CODE ISO4217: XUB

How to use Bubcoin?

Bubcoin is just bitcoin but renamed and restarted. This software is bubcoin core. You can use other software designed for bitcoin with this, by running it with custom parameters.

More info:

How-To.mp4

License

Bubcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

Bubcoin core is a bitcoin core knockoff. The latest stable release tag is cloned from the upstream repo to a branch like upstream-release-0.21.1](https://github.com/wbubblerteam/bubcoin/tree/upstream-release-0.21.1). This is then merged into upstream-release-latest.

From here the branching is a little convoluted:

Scripts

  • Scripts are written on the scripts-latest. The reason is that I originally worked off the upstream master branch - see scripts-master - before realising I needed to work off a stable release, and rebasing.

Manual modifications

  • Manual icon changes are made on the manual-icons branch. These include the .icns file and the bitmap with altered text.
  • Manual parameter changes are made on the manual-chainparams branch. These include the proof of work difficulty and coin limit.
  • Manual changes to information is made on the manual-readme branch. Like this here.
  • The backporting branch is used for fixes to the release tag to make it buildable, like dead dependency download links.

Automatic modifications

On these branches changes are made automatically using the scripts.

Finally, all of these branches are merged into staging, and when staging is stable it's merged into the main branch.

In other words: branching

Scripts:

The contribution workflow is described in CONTRIBUTING.md and useful hints for developers can be found in doc/developer-notes.md.