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.
Heya Gitcoiners & Gitcoinerettes! They say that July is the warmest month of the year (location depending), and we’re definitely getting ready fo…
Howdy, Gitcoiners! This month we’re running hackathons, we launched Grants Round 6 (which we just tweaked big time btw), we’re building, we’re improv…
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.
If a contract message that creates another contract is reverted, that byte code is displayed in the interface. At that moment there's no byte code associated with that contract. The contract effectively does not exist.
Because the contract message reverts, the contract's nonce is not incremented.
When a second contract message is generated and it does not revert the newly generated byte code that deploys to the same address is not displayed on the web page.
Because the first contract message was reverted, the second contract message will deploy to the same address.
### Steps to reproduce
The contract with the incorrect byte code is
The contract message that reverted is
The second contract message that does not revert but deploys a different byte code is
### Expected behaviour
Should display byte code
### Actual behaviour
Displays byte code