Go-ethereum: Increase geth's mining rate to >= 2 blocks/second for private chains

[satoshi101]

Feature request

When used in private chains, there's a need to demonstrate ether in lower-latency settings. The main requirement for the ~17second mining time seem to be connected to the fact that "12.6 seconds is the time it takes for a new block to propagate to 95% of nodes" [1, 2].

In a small e.g. 10 node network, with small latency (e.g. lower than 100ms) there's no reason to not mine more frequently. There's a proposed solution here about freezing the difficulty to the one in Genesis Block. This would likely translate to nop'ing the calcDifficultyHomestead() method here. Another alternative might be to change parameters here and especially DifficultyBoundDivisor.

I would like, if possible, some discussion on the subject, someone trying a proposed solution and demonstrating it with - for example - a small 5-node docker-compose - based cluster. The solution should be proved to be reasonably stable i.e. able to run successfully for e.g. a few hours.

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__This issue now has a funding of 0.2 ETH (161.09 USD @ $805.44/ETH) attached to it.__

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $10,087.68 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

__The funding of 0.2 ETH (161.09 USD @ $805.44/ETH) attached to this issue has been cancelled by the bounty submitter__

• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $9,926.59 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__This issue now has a funding of 0.2 ETH (161.09 USD @ $805.44/ETH) attached to it.__

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $10,087.68 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

__The funding of 0.2 ETH (161.09 USD @ $805.44/ETH) attached to this issue has been cancelled by the bounty submitter__

• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $9,926.59 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__This issue now has a funding of 0.2 ETH (163.96 USD @ $819.79/ETH) attached to it.__

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $10,206.07 more funded OSS Work available on the Gitcoin Issue Explorer

[ghost]

I want to work on this issue, still dump on git technology, already
started, thx
On 6 May 2018 07:10, "Gitcoin.co Bot" [e-mail] wrote:

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 0.2 ETH (163.96 USD @ $819.79/ETH)
attached to it.

• If you would like to work on this issue you can 'start work' on the
  Gitcoin Issue Details page
  https://gitcoin.co/issue/ethereum/go-ethereum/16688/372.
• Questions? Checkout Gitcoin Help https://gitcoin.co/help or the Gitcoin
  Slack https://gitcoin.co/slack
• $10,206.07 more funded OSS Work available on the Gitcoin Issue Explorer
  https://gitcoin.co/explorer

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ethereum/go-ethereum/issues/16688#issuecomment-386846151,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac3rNROCbk_1oXF7Re-mfhvNhWNJ7jpJks5tvk1vgaJpZM4Tz0II
.

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

__The funding of 0.2 ETH (163.96 USD @ $819.79/ETH) attached to this issue has been cancelled by the bounty submitter__

• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $10,042.11 more funded OSS Work available on the Gitcoin Issue Explorer

[satoshi101]

@intizarabe - sorry - I had some problems with gitcoin's project. Let me try one more time.

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__This issue now has a funding of 0.2 ETH (166.27 USD @ $831.33/ETH) attached to it.__

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $10,301.33 more funded OSS Work available on the Gitcoin Issue Explorer

[abitrolly]

@satoshi101 maybe open an issue describing the problems here - https://github.com/gitcoinco/web/issues

[satoshi101]

Thanks @abitrolly - here it is.

[pfilippi24]

@intizarabe You still working on this? If not, I would give it a shot

[ghost]

@satoshi101 yes, i am working on it. Sorry for later replies, having
hardwares issues unsolved yet.

On Mon, 7 May 2018 21:30 Pascal [e-mail] wrote:

@intizarabe https://github.com/intizarabe You still working on this? If
not, I would give it a shot

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ethereum/go-ethereum/issues/16688#issuecomment-387103238,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac3rNckv4tC_zDdPLC1XhyW7gcdn6FGpks5twGicgaJpZM4Tz0II
.

[vs77bb]

Hi @intizarabe can you please click 'Start Work' on Gitcoin (here) to state your intent to work this bounty?

[ghost]

Hello, i can not proceed with job till i fix my OS bugs, it is not workable
since out of my control. I try to fix it for more than 60 hours. Awfull

On Tue, 8 May 2018 10:02 Vivek Singh [e-mail] wrote:

Hi @intizarabe https://github.com/intizarabe can you please click
'Start Work' on Gitcoin (here
https://gitcoin.co/issue/ethereum/go-ethereum/16688/373) to state your
intent to work this bounty?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ethereum/go-ethereum/issues/16688#issuecomment-387277600,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac3rNQvxRez2im_zQy8gRXqw6VSMMj7fks5twRjggaJpZM4Tz0II
.

[ghost]

Sorry I really no understand if it is simulated networks how you plan to
get real output, using logs for that jobs, right?

On Tue, 8 May 2018 10:06 Inzo Abe [e-mail] wrote:

Hello, i can not proceed with job till i fix my OS bugs, it is not
workable since out of my control. I try to fix it for more than 60 hours.
Awfull

On Tue, 8 May 2018 10:02 Vivek Singh [e-mail] wrote:

Hi @intizarabe https://github.com/intizarabe can you please click
'Start Work' on Gitcoin (here
https://gitcoin.co/issue/ethereum/go-ethereum/16688/373) to state your
intent to work this bounty?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ethereum/go-ethereum/issues/16688#issuecomment-387277600,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac3rNQvxRez2im_zQy8gRXqw6VSMMj7fks5twRjggaJpZM4Tz0II
.

[ghost]

Hello, I have read a lot on blockchain implemantation, sorry I can not
support such a movement. I am supporting instead open society of happy
humanity, I am afraid of secret networks of vulnerable ppl, under script
managements. I am not going to be neither node nor peer, I am sick of
society organised into clusters, been tested non stop by machines. I am
angry with penetrating ppl privacy, violating boundaries. Manipulating ppl
using private info accessed via sick protocols as Whisper, attracting
vulnerable persons, than blackmailed with another FUNC. I
am got sick reading that codes for zombeing ppl, enslave them and
manipulate. You better solve issues of hunger or war with such interest. I
am trying to stand up, to become better, you with sadistic efforts creating
obstacles and registering metrocs. No , this is dead end of humanity. I am
giving up, enough i got knowleage to detect the beast. Sorry this is my
imho. I saw the ppl from you clusters, bmk, my beloved corp is zombi
village, others are psychiatric clinics pacienses. I do not care of your
threatenings, go ahead. I am not any block. I do not care of your building
evil ierarchies.

On Tue, 8 May 2018 11:36 Inzo Abe [e-mail] wrote:

Sorry I really no understand if it is simulated networks how you plan to
get real output, using logs for that jobs, right?

On Tue, 8 May 2018 10:06 Inzo Abe [e-mail] wrote:

Hello, i can not proceed with job till i fix my OS bugs, it is not
workable since out of my control. I try to fix it for more than 60 hours.
Awfull

On Tue, 8 May 2018 10:02 Vivek Singh [e-mail] wrote:

Hi @intizarabe https://github.com/intizarabe can you please click
'Start Work' on Gitcoin (here
https://gitcoin.co/issue/ethereum/go-ethereum/16688/373) to state
your intent to work this bounty?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ethereum/go-ethereum/issues/16688#issuecomment-387277600,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac3rNQvxRez2im_zQy8gRXqw6VSMMj7fks5twRjggaJpZM4Tz0II
.

[pfilippi24]

Guess that's a "no" from @intizarabe

[pfilippi24]

@satoshi101 Will be running my first tests with the modified geth tonight. You don't happen to have some scenarios in mind, I could try out?

[satoshi101]

@pfilippi24 That's great! :) The contract shouldn't really matter. One of the problems I've seen when I quickly tried something similar in the past was that it was slowing down as the time went by (i.e. difficulty raising) or periodical freezes. This was even when it was mining empty blocks. So overall if the network seems stable running any contract for sometime it should be fine. If you have anything in a shared repo, I could also try it/have a look.

[pfilippi24]

@satoshi101 No, didn't put it up on github yet. Simply playing with the suggestion, don't know yet, if something good will come out of it.
For how long will you be available today? Maybe we can keep in touch and test together?

[satoshi101]

Hello, I'm online now and for a while...

[ghost]

Hello, @satoshi, the work never stopped, i hope to give result soon, i
beleive this would be great to find solution. Sorry for spamming in repos.

On Thu, 10 May 2018 8:30 am satoshi101 [e-mail] wrote:

Hello, I'm online now and for a while...

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ethereum/go-ethereum/issues/16688#issuecomment-387933079,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac3rNdHB1z4Vy7wd8Ag53XJPFX9TIKguks5tw6ZVgaJpZM4Tz0II
.

[satoshi101]

@intizarabe - sure, but if you're interested in gitcoin's stuff, make sure you check the "Working Your First Issue" in the gitcoin developer guide.

[ghost]

@satoshi101 i can not make anythong, my harware is rooted from outside, i
cant control it istead it is control me. Embarasing trap.

On 10 May 2018 11:00 am, "satoshi101" [e-mail] wrote:

@intizarabe https://github.com/intizarabe - sure, but if you're
interested in gitcoin's stuff, make sure you check the "Working Your First
Issue" in the gitcoin developer guide
https://docs.google.com/document/d/1S8BLKJF7J5RbrfFw-mX0iYcy4VSc6-a1aQXtKT_ta0Y/edit#heading=h.mzjvbspfr2xt
.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/ethereum/go-ethereum/issues/16688#issuecomment-387952313,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac3rNdkldsVGBqRjukF405EZTuj0CIMZks5tw8lfgaJpZM4Tz0II
.

[ghost]

I also need understand who is manipulating my system and pushing me to
choices, by all means shrinking my freedom.
I will not take any move further till understand the processes and the
system(s) . The solution comes after clear vision, the latter is not
provided by defaults. The enviroment created is highly manipulative, anyway
i am working on issue, and seeking for any parter help if possible.

On 10 May 2018 11:12 am, "Inzo Abe" [e-mail] wrote:

@satoshi101 i can not make anythong, my harware is rooted from outside, i
cant control it istead it is control me. Embarasing trap.

On 10 May 2018 11:00 am, "satoshi101" [e-mail] wrote:

@intizarabe https://github.com/intizarabe - sure, but if you're
interested in gitcoin's stuff, make sure you check the "Working Your First
Issue" in the gitcoin developer guide
https://docs.google.com/document/d/1S8BLKJF7J5RbrfFw-mX0iYcy4VSc6-a1aQXtKT_ta0Y/edit#heading=h.mzjvbspfr2xt
.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/ethereum/go-ethereum/issues/16688#issuecomment-387952313,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac3rNdkldsVGBqRjukF405EZTuj0CIMZks5tw8lfgaJpZM4Tz0II
.

[ghost]

I also need understand who is manipulating my system and pushing me to
choices, and why.
I will not take any move till understand the processes and the system(s) .
The solution comes after clear vision, the latter is not provided vy
defauls anywau i am working on issue, and seeking for partners or help if
available

On 10 May 2018 11:12 am, "Inzo Abe" [e-mail] wrote:

@satoshi101 i can not make anythong, my harware is rooted from outside, i
cant control it istead it is control me. Embarasing trap.

On 10 May 2018 11:00 am, "satoshi101" [e-mail] wrote:

@intizarabe https://github.com/intizarabe - sure, but if you're
interested in gitcoin's stuff, make sure you check the "Working Your First
Issue" in the gitcoin developer guide
https://docs.google.com/document/d/1S8BLKJF7J5RbrfFw-mX0iYcy4VSc6-a1aQXtKT_ta0Y/edit#heading=h.mzjvbspfr2xt
.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/ethereum/go-ethereum/issues/16688#issuecomment-387952313,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac3rNdkldsVGBqRjukF405EZTuj0CIMZks5tw8lfgaJpZM4Tz0II
.

[satoshi101]

No clue about your freedom. My freedom is getting better.

[ghost]

Glad to hear that, and that was wrong statement logically since i am not
binded here and have the freedom to choose. Thank you for cooperation. Hope
to solve the issue for good.

On 10 May 2018 2:54 pm, "satoshi101" [e-mail] wrote:

No clue about your freedom. My freedom is getting better.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/ethereum/go-ethereum/issues/16688#issuecomment-387994990,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac3rNd837bf_IJVgmKYKHwRfYlDpHMHrks5txABTgaJpZM4Tz0II
.

[ghost]

On Thu, 10 May 2018 3:09 pm Inzo Abe [e-mail] wrote:

Glad to hear that, and that was wrong statement logically since i am not
binded here and have the freedom to choose. Thank you for cooperation. Hope
to solve the issue for good.

On 10 May 2018 2:54 pm, "satoshi101" [e-mail] wrote:

No clue about your freedom. My freedom is getting better.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/ethereum/go-ethereum/issues/16688#issuecomment-387994990,
or mute
https://github.com/notifications/unsubscribe-auth/Ac3rNd837bf_IJVgmKYKHwRfYlDpHMHrks5txABTgaJpZM4Tz0II

To upgrade block i guess need improvement solution to current
infrustrictures to cut costs ot increase volumes. I am working on that but
i qm new to industry.

>

[abitrolly]

Write code, not excuses. :)

[gitcoinbot]

@pfilippi24 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[vs77bb]

I'm not quite sure what to make of the conversation above, but from Gitcoin's side we see @pfilippi24 as the bounty hunter here. Are you able to update us on your progress? 😄

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

@pfilippi24 due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!

• [x] warning (3 days)
• [x] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@thjnhcolag Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@thjnhcolag Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

@thjnhcolag Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[ceresstation]

Hi @thjnhcolag unfortunately we have to give this issue back to the crowd as we haven't heard any updates from you. Please let us know if you think we've made a mistake!

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__Work has been started__.

These users each claimed they can complete the work by 2 months, 2 weeks ago.
Please review their action plans below:

1. cpurta has started work.

   Have started testing some of the proposed solutions and will update with the results of those.

Learn more on the Gitcoin Issue Details page.

[cpurta]

It seems like it would be better for private networks to have a frozen difficulty (set from the config). It would allow for them to mine at a consistent rate indefinitely. Adjusting the DifficultyBoundDivisor is just adjusting a scalar value in any of the Difficulty adjustment formula and will cause the difficulty to increase over time. One advantage to that is that it would mimic what the other networks do.

I am currently testing the stability of the frozen difficulty solution in a 5-node network for the next few hours.

[cpurta]

@satoshi101 I have tested freezing the difficulty in a private network and was able to have it run pretty successfully on a 5 node network. That solution showed that it was stable for at least 5 hours and was able to mine a new node every 1-2s. If you are curious on how I ran/setup that network you can find that at https://github.com/cpurta/ethereum-docker-network.

I opened a PR to which @karalabe made a good point in his comment about how those changes would affect the overall consensus engine (ethash). Also there is PoA which supports 1s block mining times which it roughly on par with the solution I had tested. Have yet to test setting up a PoA network.

[satoshi101]

@cpurta - Looks amazing! I will check it ASAP!

[gitcoinbot]

@cpurta Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[cpurta]

@gitcoinbot still working on the issue.

[motafa1320]

hi
can you help me about myself client balance.

davoud vakili

On Mon, 7/16/18, Christopher Purta [e-mail] wrote:

Subject: Re: [ethereum/go-ethereum] Increase geth's mining rate to >= 2 blocks/second for private chains (#16688)
To: "ethereum/go-ethereum" [e-mail]
Cc: "Subscribed" [e-mail]
Date: Monday, July 16, 2018, 3:04 PM

@gitcoinbot still
working on the issue.

—
You are receiving this because you are subscribed to this
thread.
Reply to this email directly, view
it on GitHub, or mute
the thread.

[gitcoinbot]

@cpurta Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[cpurta]

@satoshi101 have you had a chance to take a look at the test solution? I can run you through the steps needed to test if needed.

[vs77bb]

@cpurta Great work here and appreciate you sifting through the comment history as this one took some time to get to a serious developer. Open to any feedback you may have on how to make this better, and we're thinking about it at Gitcoin ourselves.

cc @PixelantDesign

[satoshi101]

Looks great to me. I can see the interesting issue/chat here. Would you like to 'complete work' on gitcoin?

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__Work for 0.2 ETH (92.4 USD @ $461.98/ETH) has been submitted by__:

1. @cpurta

@satoshi101 please take a look at the submitted work:

• PR by @cpurta

---

• Learn more on the Gitcoin Issue Details page
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
  $27,856.84 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

@cpurta Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[cpurta]

@satoshi101 work has been submitted on gitcoin. Mind reviewing?

[satoshi101]

I've accepted it a few times in gitcoin. The transaction doesn't go through because of too little gas. I will try again with more gas

[satoshi101]

Don't know what's going on :/ Is the system up? I keep getting transactions that don't even make it o to the chain eg. https://etherscan.io/tx/0x213e2323e527368dcaf2f24a0957874c7765af227086f364bdce2942a2e5872d

[cpurta]

@vs77bb any thoughts on what may be going on here ^^

[vs77bb]

@satoshi101 Gas prices are pretty low right now 🤔 is there a tx at a lower nonce which is still pending? It's likely this is holding up any other transactions you have posted.

Here's a tweet from @owocki about this... let me know on Slack if you keep having issues and want to troubleshoot!

[owocki]

we wrote up a little helpdesk article on this :) https://github.com/gitcoinco/gitcoinco/issues/50

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

__The funding of 0.2 ETH (90.46 USD @ $452.3/ETH) attached to this issue has been approved & issued to @cpurta.__

• Learn more on the Gitcoin Issue Details page
  
  
  
  • Questions? Checkout Gitcoin Help or the Gitcoin Slack
  
  
  • $28,701.66 more funded OSS Work available on the Gitcoin Issue Explorer
  
  

[satoshi101]

Congrats! Thanks a million!

[gitcoinbot]

@cpurta Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• [x] warning (3 days)
• [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

@cpurta due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!

• [x] warning (3 days)
• [x] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[cpurta]

@vs77bb @gitcoinbot work has already been submitted and I have been paid out for this task. Should the bounty be closed out in gitcoin to stop the bot from spamming this issue?