Go implementation of the Ethereum protocol
Find a file
2023-09-11 12:00:01 +05:30
.circleci chg: Update README 2020-11-14 14:30:47 +05:30
.github Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
accounts Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
build Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
builder/files Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
cmd Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
common Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
consensus Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
console Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
contracts/checkpointoracle Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
core Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
crypto Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
docs Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
eth Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
ethclient Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
ethdb Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
ethstats Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
event Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
graphql Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
integration-tests mardizzone/merge-qa-to-master (#856) 2023-05-10 22:52:14 +02:00
internal Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
les Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
light Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
log Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
metrics Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
miner Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
mobile Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
node Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
p2p Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
packaging Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
params Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
rlp Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
rpc Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
scripts Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
signer Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
swarm Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
tests Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
trie Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +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 mardizzone/merge-qa-to-master (#856) 2023-05-10 22:52:14 +02:00
.gitmodules new: dev: pos-398 remove duplicate git submodule 2022-07-12 17:37:44 +02:00
.golangci.yml Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
.goreleaser.yml Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
.mailmap Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
.snyk mardizzone/merge-qa-to-master (#856) 2023-05-10 22:52:14 +02:00
.travis.yml Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
appveyor.yml Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
AUTHORS Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +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 rollback bor user and use root 2022-11-23 14:16:36 -07:00
Dockerfile.alltools Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
Dockerfile.release rollback bor user and use root 2022-11-23 14:16:36 -07:00
fuzzbuzz.yaml fuzzers: removed fuzzbuzz configuration (#21813) 2020-11-10 21:54:59 +02:00
go.mod Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
go.sum Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
interfaces.go Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
Makefile Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
oss-fuzz.sh V0.2.16 candidate (#373) 2022-05-06 12:31:48 +02:00
README.md Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
RETESTBOR.md Revert "Merge v0.5.0 into master (#982)" 2023-09-11 11:58:40 +05:30
SECURITY.md mardizzone/merge-qa-to-master (#856) 2023-05-10 22:52:14 +02:00
sonar-project.properties mardizzone/merge-qa-to-master (#856) 2023-05-10 22:52:14 +02: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 commited 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) 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.