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.
We are proud to announce that we have teamed up with Chainlink to launch a new bug bounty program to secure the Chainlink protocol. Chainlink is the …
In partnership with Protocol Labs, we’re excited to welcome builders from everywhere to APOLLO, your mission control to engage with the builder…
Gitcoin is GDPR compliant. 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.
**What's the problem? (required)**
We just deployed a new protocol change that prohibits active transcoders from bonding to another transcoder.
**What's the current behavior? (required)**
Currently active transcoders can bond to another transcoder in the explorer. After the protocol upgrade, transactions like this will fail.
We should disallow transcoders from bonding to another transcoder by disabling the "bond" button if the current address is an active transcoder. (They should still be able to bond to themselves)
There are 2 places in the explorer where the "bond" button exists.
1) In the [`/transcoders` page](https://github.com/livepeer/livepeerjs/blob/75317611839382c771d70c6828c48ab6f93a5cc5/packages/explorer/src/views/Account/enhance.js#L14).
2) In the [`/account` page](https://github.com/livepeer/livepeerjs/blob/75317611839382c771d70c6828c48ab6f93a5cc5/packages/explorer/src/views/Transcoders/enhance.js#L9).
We need to add the `Transcoder` fragment in both graphql queries to access whether the authenticated user is an active user.
If the authenticated user is a transcoder AND we are on a different transcoder's page (or tab), we should hide the `bond` button. Otherwise (if the authenticated user is a transcoder and we are on her page / tab), we don't hide the `bond` button.
If you need help join our Discord chat and post your question in the #dev or #js channel: https://discord.gg/7wRSUGX