Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Learn about Web3 & earn rewards
Show appreciation for each other
Meet fellow developers, designers, futurists and more. Collaborate and BUIDL awesome projects together.
Discover great web3 organizations, work on meaningful projects and build relationships with like minded people. Browse Tribes
Meet the top hunters and contributors from our community.
Hello, Gitcoiners & Gitcoinerettes! It’s happening again – happy blockchain times are coming to San Francisco 🎉, as the San Francisco…
Heya Gitcoiners & Gitcoinerettes! They say that July is the warmest month of the year (location depending), and we’re definitely getting ready fo…
Gitcoin is GDPR complaint. Learn more in
Gitcoin's Terms & Conditions.
Check out the Issue Explorer
Looking to fund some work? You can submit a new Funded Issue here.
Following the Ethereum 2.0 Serenity [specification](https://github.com/ethereum/eth2.0-specs/blob/master/specs/core/0_beacon-chain.md), the BLS12-381 signature scheme desires having signatures live as points in G2 while public keys can live in G1. This was originally referenced in https://github.com/herumi/bls/issues/21 and was merged in by Herumi in the https://github.com/herumi/mcl repo, which would allow to build the project with `make BLS_SWAP_G=1`. However, we have to update our Go wrapper as well to support this functionality.
A PR would build MCL in bazel with the BLS_SWAP_G flag enabled and would modify this repo's go wrappers to support the G1 vs. G2 swap and allow tests to pass. Additionally, it would run benchmarks for the passing tests with the swapped groups.
Edit: see https://github.com/ethereum/eth2.0-specs/issues/605