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.
**Describe the bug**
Adding in any node moves all others of the same type to that location.
This is a slightly more precise description of the bug as pointed out by @agni21 in #44.
1. Drag any node into the /porcupine editor
2. And another one of the same type.
3. The first one seems to disappear, but in reality is moved to the location of the second one.
The existing nodes should stay in place
Provided by @agni21 in #44
A fix was suggested in #43, but this does not solve the problem. In fact, making the node unselectable might have consequences for #35, although that doesn't seem to be the case yet.