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.
### User Story
[comment]: # (As a , I want to so that .)
as a user, i want standard bounty tx's to be processed instantly by gitcoin, so i know my tx went through
### Why Is this Needed?
[comment]: # (Describe the problem and why this task is needed. Provide description of the current state, what you would like to happen, and what actually happen)
so that any new transaction to standardbounties on the mainnet will instantly show up on the site.
d372815fe36dc5d5b8d02de98222c5ca69e8e485 is my attempt at starting to do this. i stopped when i had trouble decoding the tx input args to extract the standard bounty id
the goal for this request is listed in 'expected behaviour' below.
[comment]: # (Feature or Bug? i.e Type: Bug)
### Current Behavior
[comment]: # (Describe what actually happened.)
if user doesnt close their browser window after submitting the tx, the tx will proces instantly (usually, unless there is a race condition with the browser / infura)
if user DOES close their browser window after submitting the tx, the tx will be picked up by `sync_geth` management command and processed within the hour.
### Expected Behavior
[comment]: # (Describe what you expected to happen.)
a management command `sync_listener`, which is scheduled to always run in the background, which listens for new blocks that contain transactions to standard bounties, and processes those bounties instantly with `dashboard.utils.web3_process_bounty()`