Genesis Block Time (GBT) is time in blocks accepted on upon the Bitcoin blockchain. There is no better, true or secure way to tell time than Genesis Block Time (GBT).
Slack: genesisblocktime.slack.com
Have a bug or a feature request? Please first read the issues and search for existing and closed issues. If your problem or idea is not addressed yet, please open a new issue.
Looking to contribute something to Genesis Block Time? Here's how you can help.
Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
The issue tracker is the preferred channel for bug reports, features requests and submitting pull requests, but please respect the following restrictions:
Please do not use the issue tracker for personal support requests. Stack Overflow or Slack are better places to get help.
Please do not derail or troll issues. Keep the discussion on topic and respect the opinions of others.
Please do not post comments consisting solely of "+1" or ":thumbsup:". Use GitHub's "reactions" feature instead. We reserve the right to delete comments which violate this rule.
Feature requests are welcome, but before opening a feature request, please take a moment to find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Please provide as much detail and context as possible.
Good pull requests—patches, improvements, new features—are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.
Please ask first before embarking on any significant pull request (e.g. implementing features, refactoring code, porting to a different language), otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project.
Fork the project, clone your fork, and configure the remotes:
# Clone your fork of the repo into the current directory
git clone https://github.com/<your-username>/genesis.git
# Navigate to the newly cloned directory
cd genesis
# Assign the original repo to a remote called "upstream"
git remote add upstream https://github.com/jrschupak/genesis.gitIf you cloned a while ago, get the latest changes from upstream:
git checkout master
git pull upstream masterCreate a new topic branch (off the main project development branch) to contain your feature, change, or fix:
git checkout -b <topic-branch-name>Commit your changes in logical chunks. Please adhere to these git commit message guidelines or your code is unlikely to be merged into the main project. Use Git's interactive rebase feature to tidy up your commits before making them public.
Locally merge (or rebase) the upstream development branch into your topic branch:
git pull [--rebase] upstream masterPush your topic branch up to your fork:
git push origin <topic-branch-name>Open a Pull Request
with a clear title and description against the master branch.
IMPORTANT: By submitting a patch, you agree to allow the project owners to license your work under the terms of the MIT License (if it includes code changes) and under the terms of the Creative Commons Attribution 3.0 Unported License (if it includes documentation changes).
Get updates on Bootstrap's development and chat with the project maintainers and community members.