* merge geth v1.10.15 * fix: Removed FastSync from cli server * fix: TestHeadersRLPStorage * Added t.skip(ETH2 in bor) * fix: flow in create consensus engine * bumped version * Fix typo * increase block time * remove file * bumped version * merge gethv1.10.17 * bumped version * fix failing tests * Bump Go version to v1.18 (#368) * Bump Go version to v1.18.1 * Build using netgo tag This will create a static build using Go native networking stack. Checked and it works stable for all archs and distros. * Fix meta * initial implementation for common ancestor approach * extract whitelist interface * fix types * fix tests and format * add unit tests for IsValidChain function * more tests * wip * test ErrCheckpointMismatch * minor fixes * fix test * dont panic * fmt * Limit state sync by gas * Added logging for state-sync total gas usage * Added number of event-records in log * Minor Changes * Minor Fix * Adding individual gasUsed * Minor Fix * fix: return value for no remote block * handle all errors * modularise fake chain validator in downloader * add more tests * fix tests * Modifying miner.recommit flag and its adjustment function. (#370) * changed min/max/current recommit values * Remove Hardcoded min/max * Code Sanitization * Skipping tests for constant recommit interval * Adding default miner.recommit value * Minor Change * Increased default value of rpc.txfeecap to 5 * add debug rpc endpoints for checkpoint whitelist service * minor fixes and enhancements * avoid capping warnings for gas set by internal system transactions * use typed mocks * fix * fix * fix * fix close * fix * Create stale.yml * Fix bor consensus checkpoint bug Co-authored-by: Arpit Temani <temaniarpit27@gmail.com> Co-authored-by: Shivam Sharma <shivam691999@gmail.com> Co-authored-by: Manav Darji <manavdarji.india@gmail.com> Co-authored-by: Sandeep Sreenath <sandeep.sreenath@gmail.com> Co-authored-by: Victor Castell <victor@victorcastell.com> Co-authored-by: Ferran <ferranbt@protonmail.com> Co-authored-by: Krishna Upadhyaya <krishnau1604@gmail.com> Co-authored-by: Karlo <karlonovak@gmail.com> Co-authored-by: Sandeep Sreenath <ssandeep@users.noreply.github.com> Co-authored-by: Jerry <jerrycgh@gmail.com> |
||
|---|---|---|
| .circleci | ||
| .github | ||
| accounts | ||
| build | ||
| builder/files | ||
| cmd | ||
| common | ||
| consensus | ||
| console | ||
| contracts/checkpointoracle | ||
| core | ||
| crypto | ||
| docs | ||
| eth | ||
| ethclient | ||
| ethdb | ||
| ethstats | ||
| event | ||
| graphql | ||
| internal | ||
| les | ||
| light | ||
| log | ||
| metrics | ||
| miner | ||
| mobile | ||
| node | ||
| p2p | ||
| params | ||
| rlp | ||
| rpc | ||
| scripts | ||
| signer | ||
| swarm | ||
| tests | ||
| trie | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .golangci.yml | ||
| .goreleaser.yml | ||
| .mailmap | ||
| .travis.yml | ||
| appveyor.yml | ||
| AUTHORS | ||
| circle.yml | ||
| COPYING | ||
| COPYING.LESSER | ||
| Dockerfile | ||
| Dockerfile.alltools | ||
| Dockerfile.release | ||
| fuzzbuzz.yaml | ||
| go.mod | ||
| go.sum | ||
| interfaces.go | ||
| Makefile | ||
| oss-fuzz.sh | ||
| README.md | ||
| SECURITY.md | ||
Bor Overview
Bor is the Official Golang implementation of the Matic protocol. It is a fork of Go Ethereum - https://github.com/ethereum/go-ethereum and EVM compabile.
How to contribute
Contribution Guidelines
We believe one of the things that makes Polygon special is its coherent design and we seek to retain this defining characteristic. From the outset we defined some guidelines to ensure new contributions only ever enhance the project:
- Quality: Code in the Polygon project should meet the style guidelines, with sufficient test-cases, descriptive commit messages, evidence that the contribution does not break any compatibility commitments or cause adverse feature interactions, and evidence of high-quality peer-review
- Size: The Polygon project’s culture is one of small pull-requests, regularly submitted. The larger a pull-request, the more likely it is that you will be asked to resubmit as a series of self-contained and individually reviewable smaller PRs
- Maintainability: If the feature will require ongoing maintenance (eg support for a particular brand of database), we may ask you to accept responsibility for maintaining this feature
Submit an issue
- Create a new issue
- Comment on the issue (if you'd like to be assigned to it) - that way our team can assign the issue to you.
- If you do not have a specific contribution in mind, you can also browse the issues labelled as
help wanted - Issues that additionally have the
good first issuelabel are considered ideal for first-timers
Fork the repository (repo)
-
If you're not sure, here's how to fork the repo
-
If this is your first time forking our repo, this is all you need to do for this step:
$ git clone git@github.com:[your_github_handle]/bor -
If you've already forked the repo, you'll want to ensure your fork is configured and that it's up to date. This will save you the headache of potential merge conflicts.
-
$ git remote add upstream https://github.com/maticnetwork/bor -
To sync your fork with the latest changes:
$ git checkout master $ git fetch upstream $ git merge upstream/master
Building the source
-
Building
borrequires both a Go (version 1.14 or later) and a C compiler. You can install them using your favourite package manager. Once the dependencies are installed, run$ make bor
Make awesome changes!
-
Create new branch for your changes
$ git checkout -b new_branch_name -
Commit and prepare for pull request (PR). In your PR commit message, reference the issue it resolves (see how to link a commit message to an issue using a keyword.
Checkout our Git-Rules
$ git commit -m "brief description of changes [Fixes #1234]" -
Push to your GitHub account
$ git push
Submit your PR
- After your changes are commited to your GitHub fork, submit a pull request (PR) to the
masterbranch of thematicnetwork/borrepo - In your PR description, reference the issue it resolves (see linking a pull request to an issue using a keyword)
- ex.
Updates out of date content [Fixes #1234]
- ex.
- Why not say hi and draw attention to your PR in our discord server?
Wait for review
- The team reviews every PR
- Acceptable PRs will be approved & merged into the
masterbranch
Release
- You can view the history of releases, which include PR highlights
License
The go-ethereum library (i.e. all code outside of the cmd directory) is licensed under the
GNU Lesser General Public License v3.0,
also included in our repository in the COPYING.LESSER file.
The go-ethereum binaries (i.e. all code inside of the cmd directory) is licensed under the
GNU General Public License v3.0, also
included in our repository in the COPYING file.
Join our Discord server
Join Polygon community – share your ideas or just say hi over on Discord.