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.
In partnership with Protocol Labs, we’re excited to welcome builders from everywhere to APOLLO, your mission control to engage with the builder…
We’re excited to publically announce that Matic Network is partnering with Gitcoin to launch the Build-n-Earn Program – assisting dApps t…
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.
`JUMP` and `JUMPI` opcode work well but do not seem to work well under one exception. For example, if the current pc is 100(JUMP), JUMP works well with 150(JUMPDEST), but not with 50(JUMPDEST).
I'm testing here.
2047 has JUMP opcode so we expect to jump to 0x69c(1692).
When the pcCount is 2048, it should go to 0x69c(1692), but it does not go.
It's good to jump to a bigger pc(JUMPDEST) than current pc(JUMP), but it doesn't seem to work well when jumping to a smaller pc(JUMPDEST) than current pc(JUMP). Do you happen to know why?