Go implementation of the Ethereum protocol
Find a file
2023-08-24 11:51:10 +05:30
.circleci chg: Update README 2020-11-14 14:30:47 +05:30
.github exempt draft PRs (#962) 2023-08-15 11:25:56 +05:30
accounts Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
beacon/engine Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
build Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
builder/files rename db.engine key for config files (#969) 2023-08-22 21:11:43 +05:30
cmd Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
common Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
consensus remove indore hf logs 2023-08-24 11:51:10 +05:30
console Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
contracts/checkpointoracle Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
core core/txpool: convert lock acquire log to debug 2023-08-24 11:42:05 +05:30
crypto Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
docs Update docs and add default config 2023-08-17 11:38:21 +05:30
eth Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
ethclient ethclient: use bor_getRootHash instead of eth (#967) 2023-08-18 14:39:05 +05:30
ethdb Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
ethstats Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
event Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
graphql graphql: dev: chg: avoid greedy allocation on graphql blocks call (#958) 2023-08-11 14:37:11 +02:00
integration-tests minor chg: add new line 2022-11-25 17:50:58 +05:30
internal rename db.engine key for config files (#969) 2023-08-22 21:11:43 +05:30
les Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
light Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
log Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
metrics Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
miner Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
node Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
p2p Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
packaging Adding fix for postrm removing the config.toml and service file (#951) 2023-08-23 14:43:22 -07:00
params Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
rlp Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
rpc Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
scripts Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
signer Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
swarm Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
tests Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
trie Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
.dockerignore cmd, internal/build, docker: advertise commit date in unstable build versions (#19522) 2019-05-08 16:44:28 +03:00
.gitattributes .gitattributes: enable solidity highlighting on github (#16425) 2018-04-03 15:21:24 +02:00
.gitignore dev: add: pos-944: snyk and govuln integration (#578) 2022-12-06 10:53:55 +01:00
.gitmodules new: dev: pos-398 remove duplicate git submodule 2022-07-12 17:37:44 +02:00
.golangci.yml Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
.goreleaser.yml Merge branch 'qa' and 'master' into develop (#663) 2023-01-13 14:47:14 +05:30
.mailmap Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
.snyk add ignore rule for net/http2 2022-12-12 12:26:12 +05:30
.travis.yml Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
appveyor.yml Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
AUTHORS Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
circle.yml use go-ethereum for better forked-bor release 2020-11-13 09:21:48 +05:30
COPYING use go-ethereum for better forked-bor release 2020-11-13 09:21:48 +05:30
COPYING.LESSER all: update license information 2015-07-07 14:12:44 +02:00
Dockerfile Merge branch 'qa' and 'master' into develop (#663) 2023-01-13 14:47:14 +05:30
Dockerfile.alltools Merge branch 'develop' into mardizzone/upstream-merge 2023-07-24 14:19:30 +05:30
Dockerfile.release Merge branch 'qa' and 'master' into develop (#663) 2023-01-13 14:47:14 +05:30
fuzzbuzz.yaml Update Bor to geth-v1.9.16 (#78) 2020-07-24 19:01:41 +05:30
go.mod Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
go.sum Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
interfaces.go Revert "Upstream merge from go-ethereum/v1.11.6 (#901)" 2023-08-03 14:42:09 +05:30
Makefile Disable shuffling in unit test (#954) 2023-08-17 10:54:09 +05:30
oss-fuzz.sh V0.2.16 candidate (#373) 2022-05-06 12:31:48 +02:00
README.md Merge pull request #949 from maticnetwork/mardizzone/upstream-merge 2023-08-03 14:48:53 +05:30
RETESTBOR.md Additional reformatting and cleanup of RETESTBOR document 2023-08-13 15:21:21 -04:00
SECURITY.md dev: add: pos-944: snyk and govuln integration (#578) 2022-12-06 10:53:55 +01:00
sonar-project.properties sonarqube integration (#658) 2023-01-11 17:33:53 +01:00

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

Forks Stars Languages Issues PRs MIT License contributors size lines Discord Twitter Follow

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 projects 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 issue label 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.

  • To configure your fork:

    $ 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 bor requires both a Go (version 1.19 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!

  1. Create new branch for your changes

    $ git checkout -b new_branch_name
    
  2. 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]"
    
  3. Push to your GitHub account

    $ git push
    

Submit your PR

  • After your changes are committed to your GitHub fork, submit a pull request (PR) to the master branch of the maticnetwork/bor repo
  • 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]
  • 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 master branch

Release


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