Development resources at your finger tips
Build with the coolest Web3 projects
Recurring funding for Open Source
Ethical ads to power 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.
Aloha, Gitcoiners! How do you feel about Data Dignity, Quadratic Voting, Quadratic Finance and Decentralized Identity?
KERNEL is an 8-week, invite-only program for top tech talent looking to build relationships, products, and companies in blockchain and Web 3. 100 tal…
Type in [[ 2- term.length]] more characters to get results
[[ result.title ]]
[[ result.description | truncate(70) ]]
No matches found
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.
Currently the event system always send the event to relaying objects even if there is no callback at the end of the chain.
So if a chain of object forwards events originated in an object A but there is no callback registered to consume this events. The event is going to be passed through all the chain of objects with no particular reason to be discarded at the end.
The idea for this issue is to implement lazyness in the current system. The goal is that publishing an event which has no registered callback should be a no-op and super fast.
Perhaps patching `_publish` on certain objects depending on the callbacks that particular event has registered.