YieldBay recently submitted Referenda 97 to the treasury, requesting payment for the development of polkadot's yield farming dashboard.
&nbsp;
For details please <a href="https://docs.google.com/document/d/106gnRv8uxJyyU4xbwHNPFc6c97UR1qqYk5FE5tf6XQU/edit">see our delivery report</a>.
&nbsp;
This work was approved by the council as motion #355 under gov1, but the proposal is currently failing with only 29% in favor.
&nbsp;
The changes introduced with OpenGov left a few proposals like our own in the shadow realm.
&nbsp;
The reason I'm writing this post is because some of these proposal including our own were passed under Gov1 by the council.
&nbsp;
And there was a social contract to pay for the final milestones AFTER delivery.
&nbsp;
Now we've delivered the promised work, but proposals like ours are currently being denied the payment for the same under OpenGov.
&nbsp;
Since info for reimbursement wasn't stored on-chain, there aren't any special provisions for proposals like ours under the new OpenGov system&hellip; this means if the proposal doesn't pass, we need to pay the development cost out of our pockets.
&nbsp;
I believe we should respect everyone's right to vote as they please and feel that they do not owe any explanation for their voting decision.
&nbsp;
However, if builders acting in good faith are left at loss due to the recent change without a notice period, I believe it sets a bad precedent.
&nbsp;
I personally believe it's IMPERATIVE to attract and retain teams that act in good faith and try to contribute to a flourishing DOT economy.
&nbsp;
And an event like this can be discouraging, even severely damaging for builders.
&nbsp;
Link to our proposal: <a href="../referenda/97">https://polkadot.polkassembly.io/referenda/97</a>
&nbsp;
A proposed solution:
<img src="https://i.ibb.co/bJFp7Bb/Screenshot-2023-08-22-at-10-59-18-AM.png" alt="" width="640" height="446" />
<a href="https://forum.polkadot.network/t/gov1-social-contracts-opengov-transition-should-there-be-a-system/3751/2?u=batman">Source</a>

YieldBay recently submitted Referenda 97 to the treasury, requesting payment for the development of polkadot's yield farming dashboard.
&nbsp;
For details please <a href="https://docs.google.com/document/d/106gnRv8uxJyyU4xbwHNPFc6c97UR1qqYk5FE5tf6XQU/edit">see our delivery report</a>.
&nbsp;
This work was approved by the council as motion #355 under gov1, but the proposal is currently failing with only 29% in favor.
&nbsp;
The changes introduced with OpenGov left a few proposals like our own in the shadow realm.
&nbsp;
The reason I'm writing this post is because some of these proposal including our own were passed under Gov1 by the council.
&nbsp;
And there was a social contract to pay for the final milestones AFTER delivery.
&nbsp;
Now we've delivered the promised work, but proposals like ours are currently being denied the payment for the same under OpenGov.
&nbsp;
Since info for reimbursement wasn't stored on-chain, there aren't any special provisions for proposals like ours under the new OpenGov system&hellip; this means if the proposal doesn't pass, we need to pay the development cost out of our pockets.
&nbsp;
I believe we should respect everyone's right to vote as they please and feel that they do not owe any explanation for their voting decision.
&nbsp;
However, if builders acting in good faith are left at loss due to the recent change without a notice period, I believe it sets a bad precedent.
&nbsp;
I personally believe it's IMPERATIVE to attract and retain teams that act in good faith and try to contribute to a flourishing DOT economy.
&nbsp;
And an event like this can be discouraging, even severely damaging for builders.
&nbsp;
Link to our proposal: <a href="../referenda/97">https://polkadot.polkassembly.io/referenda/97</a>

Gov1 Social Contracts -> OpenGov Transition - Should there be a system?

YieldBay recently submitted Referenda 97 to the treasury, requesting payment for the development of polkadot's yield farming dashboard.&nbsp;For details please <a href="https://polkadot.polkassembly.io/referenda/97">see the full proposal</a>.&nbsp;&nbsp;This work was approved by the council as motion #355 under gov1, but the proposal is currently failing with only 29% in favor.&nbsp;I'm NOT asking you to vote in favor of the proposal, though I would be very grateful if you do.&nbsp;I just wish to share my honest thoughts with you and ask the same of you i.e. to share your honest feedback with me.&nbsp;As a builder who has been in the ecosystem since the time Kusama was still considered a test net&hellip;&nbsp;Polkadot has a special place in my heart.&nbsp;&nbsp;However, the changes introduced with OpenGov left a few proposals like our own in the shadow realm.&nbsp;The reason I'm writing this post is because some of these proposal including our own were passed under Gov1 by the council.&nbsp;And there was a social contract to pay for the final milestones AFTER delivery.&nbsp;Now we've delivered the promised work, but we're currently being denied the payment for the same under OpenGov.&nbsp;Since info for reimbursement wasn't stored on-chain, there aren't any special provisions for proposals like ours under the new OpenGov system&hellip; this means if the proposal doesn't pass, we need to pay the development cost out of our pockets.&nbsp;Now, for you $80,000 may or may not seem like a lot of money, but for a small bootstrapped team like our own, it is a life or death situation.&nbsp;We respect everyone's right to vote as they please and feel that they do not owe any explanation for their voting decision.&nbsp;&nbsp;However, if you are a fellow DOT holder that cares about the growth and well-being of this ecosystem, I just want you to ask yourself:&nbsp;"Is it fair to pull support from those acting in good faith without sharing any feedback or thoughts behind the decision?"&nbsp;&nbsp;I personally believe it's IMPERATIVE to attract and retain teams that act in good faith and try to contribute to a flourishing DOT economy.&nbsp;And an event like this can be discouraging, even severely damaging for builders like myself.&nbsp;&nbsp;I'll just leave you with these thoughts and the link to the proposal for you to share your honest feedback: <a href="https://polkadot.polkassembly.io/referenda/97">https://polkadot.polkassembly.io/referenda/97</a>&nbsp;UPDATE:I saw that some of the voters have flipped their vote in favor since I last checked and at the time of writing this, the proposal is at 54% in favor.&nbsp;I am deeply grateful for every single voter who is supporting us. It means the world! ❤️

Have you considered 'AYE'? Calling for your vote on Referenda 97: Proposal requests retroactive payment for work APPROVED by the Council under Gov1 and is currently FAILING

YieldBay recently submitted Referenda 97 to the treasury, requesting payment for the development of polkadot's yield farming dashboard.
&nbsp;
For details please <a href="97">see the full proposal</a>.
&nbsp;
&nbsp;
This work was approved by the council as motion #355 under gov1, but the proposal is currently failing with only 29% in favor.
&nbsp;
I'm NOT asking you to vote in favor of the proposal, though I would be very grateful if you do.
&nbsp;
I just wish to share my honest thoughts with you and ask the same of you i.e. to share your honest feedback with me.
&nbsp;
As a builder who has been in the ecosystem since the time Kusama was still considered a test net&hellip;
&nbsp;
Polkadot has a special place in my heart.
&nbsp;
&nbsp;
However, the changes introduced with OpenGov left a few proposals like our own in the shadow realm.
&nbsp;
The reason I'm writing this post is because some of these proposal including our own were passed under Gov1 by the council.
&nbsp;
And there was a social contract to pay for the final milestones AFTER delivery.
&nbsp;
Now we've delivered the promised work, but we're currently being denied the payment for the same under OpenGov.
&nbsp;
Since info for reimbursement wasn't stored on-chain, there aren't any special provisions for proposals like ours under the new OpenGov system&hellip; this means if the proposal doesn't pass, we need to pay the development cost out of our pockets.
&nbsp;
Now, for you $80,000 may or may not seem like a lot of money, but for a small bootstrapped team like our own, it is a life or death situation.
&nbsp;
We respect everyone's right to vote as they please and feel that they do not owe any explanation for their voting decision.
&nbsp;
&nbsp;
However, if you are a fellow DOT holder that cares about the growth and well-being of this ecosystem, I just want you to ask yourself:
&nbsp;
"Is it fair to pull support from those acting in good faith without sharing any feedback or thoughts behind the decision?"
&nbsp;
&nbsp;
I personally believe it's IMPERATIVE to attract and retain teams that act in good faith and try to contribute to a flourishing DOT economy.
&nbsp;
And an event like this can be discouraging, even severely damaging for builders like myself.
&nbsp;
&nbsp;
I'll just leave you with these thoughts and the link to the proposal for you to share your honest feedback: <a href="97">https://polkadot.polkassembly.io/referenda/97</a>

Proponent: 16m9GvS9aYsepHTmZTMbJmc8Z5ZNGJ4D3ySqLE349Li7rKvY (YieldBay Treasury, Polkadot)
Requested Payment Amount: 15,375.745 DOT ($80,000 @ $5.203)
&nbsp;
<img src="https://i.ibb.co/gmSH3t7/image-7-720.png" alt="" />
&nbsp;
In March 2023, YieldBay proposed to create Polkadot's first central yield farming dashboard across 3 milestones, approved through Council Motion #355 under Gov1. This proposal seeks retroactive funding of the previously agreed-upon terms for milestones 2 &amp; 3.
<a href="https://docs.google.com/document/d/106gnRv8uxJyyU4xbwHNPFc6c97UR1qqYk5FE5tf6XQU/edit#heading=h.27my4qwymkc1">Detailed delivery report for milestones 2 &amp; 3</a>
&nbsp;
⭐ About YieldBay
&nbsp;
<img src="https://i.ibb.co/7nYLx7L/image-8-720.png" alt="" width="640" height="360" />
&nbsp;
YieldBay currently monitors 183 yield farms across 17 protocols tracking $33M, including collaborations with Interlay, Stellaswap, Arthswap, Mangata, and Zenlink among others.
&nbsp;
YieldBay also enables you to track and invest in your yield farming portfolio across 4 different parachains.
&nbsp;
YieldBay aims to unify the fragmented DeFi experience that exists currently throughout the ecosystem. Imagine being able to do DeFi on 10 different parachains and being able to track your portfolio &ndash; all through YieldBay.
&nbsp;
This is in line with Gavin&rsquo;s take on how crucial &ldquo;application-centricity&rdquo; &ndash; UIs must span across chains and provide comprehensive experiences.
&nbsp;
💪 Why support us?
YieldBay is strongly pledged to the Polkadot Ecosystem and it breaks our heart to see the lack of adoption. In the last quarter, Polkadot&rsquo;s active daily users took a dip by 16%.
&nbsp;
We as an ecosystem need to come together and do something about it.
&nbsp;
YieldBay is committed and we have a plan forward that will go hand in hand with the YieldBay List. Take a look at <a href="https://pitch.com/public/584e727e-7fb3-4e16-8ad3-0938f54cf456/2e8000e0-222b-44db-bcef-fcfc231da36a">our pitch deck</a>.
&nbsp;
Read more about our initial Treasury Proposal <a href="https://docs.google.com/document/d/1GQQOEZ3ZW3wQ9GH0fv7na8evmBcBc_Tamf2ulor2bqI/edit#heading=h.v6is2ta0txr1">here</a>.

Milestone 2 and 3 Payment Request – YieldBay: Polkadot’s yield farming dashboard

- YieldBay submitted a request for payment for developing a dashboard.
- The proposal is currently failing with only 29% in favor.
- Some proposals, including YieldBay's, were passed under Gov1 but are being denied payment under OpenGov.
- There were no special provisions for proposals like YieldBay's under the new OpenGov system.
- YieldBay believes it's important to attract and retain teams that act in good faith and contribute to the DOT economy.