Proposal “dash-incubator-rion-2025“ (Active)Back

Title:Dash Incubator Rion 2025
Owner:rion
Monthly amount: 300 DASH (10625 USD)
Completed payments: no payments occurred yet (12 month remaining)
Payment start/end: 2025-01-07 / 2025-12-31 (added on 2025-01-08)
Final voting deadline: in 26 days
Votes: 359 Yes / 92 No / 54 Abstain
Will be funded: No. This proposal needs additional 41 Yes votes to become funded.
Manually vote on this proposal (DashCore - Tools - Debugconsole):
gobject vote-many c24be3cbc6581372c788527c2071f6a5177581cee6087e214dcb9cc3a997de2e funding yes

Please login or create a new DashCentral account for comfortable one button voting!

Proposal description

Dash Incubator Rion 2025

Proposal to fund the Dash Incubator reserve administered by Rion Gull, Dash Incubator Lead Strategist.

I'm requesting 300 DASH/month (down from 450 DASH/month). Like last quarter, this will be Incubator's only proposal.  Unlike last quarter which had a 3-month proposal duration, this proposal has a 12-month duration.  The rationale for this change is explained below.

Incubator Updates

In my last proposal I provided an important update regarding our Incubator strategy (see my 2024 Q4 proposal for details).  In summary, starting last quarter, each strategist would continue in their roles until their reserves were used and if they wished to continue working for Dash they would submit their own proposals independent from the Incubator.  Up until now, only Mikhail/pshenmic has done this; no others have submitted independent proposals so far.  

Current strategist reserves are as follows:
  • Rion: 678 DASH 
  • Ash: 387 DASH
  • Tim: 6 DASH
  • Mikhail: 3 DASH
  • Jojobyte: 0 DASH

  • Last quarter work was done and funds were allocated to projects by Ash, Mikhail, Jojobyte, and me.  Although Ash still has a substantial reserve, and Mikhail and Tim have token amounts, I am effectively the only active strategist in the Incubator right now.  Jojobyte has depleted his reserve and may submit his own independent proposal to continue work (not this month, but potentially later).

    Personally, other than developer relations, research, Incubator Weekly, general strategy, org management, and various smaller projects (Spritz expenses, Dash Core contributions, the Distributed Thumbnail Image service, and the Confidential Transactions DIP), I allocated time and funds to the platform application I discussed in my last proposal - a web app for creating Dash superblock proposals with proposal content and metadata hosted on Dash Platform.  I had hoped to get further on it, but after a modest start I decided to postpone work until there was more clarity on the evolving plans related to the JS SDKs, both from DCG and AJ.  More about that below.

    Future Plans

    It appears now that DCG's existing SDK will receive a major re-design and re-implementation.  AJ's prior proposal to add platform support to our/his Dash tooling didn't pass, but it was very close, even reaching the 10% passing criteria just after the voting deadline.  Because it received significant community support he has put up another proposal to give MNOs another opportunity to fund it (or not).  

    As stated last quarter, my main goal with Incubator moving forward (if funded) is to focus on outreach, primarily to developers, but also to a wider audience.  I will introduce developers, entrepreneurs, and small business owners to Dash and Dash Platform and help them submit independent proposals if they need funding for development or integration. 

    We now have a web application that simplifies this process by allowing people to submit new proposals from a website rather than needing to sync a full node and deal with tricky console commands.  We need to simplify the proposal creation process further by adding support for in-app proposal content, hosted on Dash Platform and using DashPay usernames for auth.

    I'm convinced that Dash will be better off if we can increase the number of people and orgs creating independent proposals and competing to add value in the Dash economy.  I'd like to focus exclusively on achieving that goal throughout this year.  Rather than scaling up internally in the Incubator, it's now clear to me that it's better to help people become independent and fully accountable directly to the MNOs. That maximizes the value they deliver and experience they get.  I'm also convinced that without help from someone with experience in Dash, we will miss out on what might be our most valuable contributors.  So that's my focus now - find people and give them the initial help they need to navigate all things Dash, including initial funding, experience using Dash tech, introductions to people in the Dash community, help with proposal creation, etc.

    With this 12-month proposal I'm committing to a modest budget that's enough to work with, has some upside for scaling if and only if Dash's purchasing power increases, and is predictable for the DAO over a longer term.  MNOs can always fund or defund any given month of the 12-month duration.  Of course I hope to earn your support each month.  

    Feel free to ask any questions you might have.  I'm happy to answer and expound on anything.

    Thank you for your support!

    Rion

    Show full description ...

    Discussion: Should we fund this proposal?

    Submit comment
     
    3 points,2 days ago
    Really unhappy about the outcome of this voting.
    Reply
    1 point,11 hours ago
    The outcome of this proposal is SUCCESS!!!

    https://mnowatch.org/votethenumbers/votethenumbers3/calc3.php?proposals%5B%5D=dash-incubator-rion-2025

    70.74 % votes YES for this proposal
    16.23 % was the participation.

    But still the proposal fails because the polarized Net votes system of Dash, requires 8.49 % of the eletorate while it should require only 0.0001% (more yes than no, this applies to all election systems !!!!)
    Reply
    1 point,11 hours ago
    https://www.youtube.com/watch?v=Gv7FagDCkuw&t=238s

    Watch this video, look at the curve, and stop beeing stupid!
    Reply
    1 point,10 hours ago
    https://book.encointer.org/protocol-democracy.html

    Adaptive Quorum Biasing (AQB) and Minimum Approval

    In order to determine if a proposal is passing, we use positive turnout bias. The approval threshold follows the formula:
    thrs=1/(1+√turnout) where turnout∈[0,1] and thrs∈[0,1]

    In addition we enforce a minimum turnout of 5%.

    The goal of AQB is to ensure proposals can be approved even if turnout is low. Especially noncontroversial proposals may suffer from low turnout as they fail to mobilize the crowd. However, low turnout should require a higher approval rate to pass.

    AQB

    The blue trace depicts a possible turnout over time. It can be expected that the initiators of a proposal will immediately vote Aye, leading to very high approval at start. Nevertheless, as long as less than 5% of the elecorate have cast their vote, the proposal is in failing state. Over time, more people will make up their mind and the proposal may flip between passing and failing state several times before eventually staying in the passing state for the confirmation period. The end of the confirmation period is depicted by the blue dot.

    Tutorial
    Reply
    1 point,11 hours ago
    In what kind of logic, the 18% of the NO voters impose their opinion to the 70% of the YES voters?

    HEY, DASH COMMUNITY, ARE YOU NUTS?

    (answer: yes we are....)
    Reply
    1 point,11 hours ago
    To any rational person here, can you argue with reasonable arguments why the correct thershold of the NET votes is 10% and not 8% ?

    Any logical person around?
    Reply
    1 point,7 hours ago
    Ok...let me tell you this.

    100% net votes leads to 100% required YES to approve, if all the electorate votes.
    75% net votes leads to 87.5% required YES to approve, if all the electorate votes.
    50% net votes leads to 75% required YES to approve, if all the electorate votes.
    20% net votes leads to 60% required YES to approve, if all the electorate votes.
    10% net votes leads to 55% required YES to approve, if all the electorate votes.
    7.5% net votes leads to 53% required YES to approve, if all the electorate votes.
    5% net votes leads to 52.5% required YES to approve, if all the electorate votes.
    0% net votes leads to 50% required YES to approve, if all the electorate votes.
    Reply
    1 point,7 hours ago
    What % of net votes do you chose?

    In Encointer, we selected 5%.
    Reply
    1 point,7 hours ago
    https://www.dash.org/forum/threads/pre-proposal-put-the-unvoted-10-net-votes-threshold-of-the-dash-budget-system-into-vote.54042/
    Reply
    1 point,7 hours ago
    https://www.dash.org/forum/attachments/10-net-png.12825/
    Reply
    3 points,5 days ago
    Yes from me.
    Reply
    3 points,4 days ago
    Thanks for your support, qwizzie!
    Reply
    3 points,8 days ago
    > my main goal with Incubator moving forward (if funded) is to focus on outreach, primarily to developers, but also to a wider audience. I will introduce developers, entrepreneurs, and small business owners to Dash and Dash Platform and help them submit independent proposals

    Yes, we need this, it would definitely be beneficial for Dash! I support the idea.

    What I'm having difficulties with is the amount asked. You call it a modest budget. At today's price (~$36) it's over 10,000 USD per month. You need that much money to do outreach?
    Reply
    4 points,6 days ago
    Thanks for your comment and question, MasterNoodle.

    Outreach is most effective when I can offer money (Dash) for doing work. We have stiff competition for developer attention with VCs throwing money at companies which throw money at devs. The best devs rarely work for free, and our Dash products simply aren't mature enough for entrepreneurs (who do work "for free" in a sense) to gamble their ventures on Dash tech without some kind of additional financial incentive.
    Reply
    1 point,4 days ago
    This ^^^
    Reply
    3 points,11 days ago
    Although AJ's proposal for the JS SDK rewrite did not pass, it did have the effect of bringing it to the attention of DCG and according to the most recent Development Review, they are making great progress with it now. So, that is a win you and he helped create. The web based proposal generator (e2e) is cool, but note that from v23 of Core, it will be possible to sync a node completely just from a checkpoint near the tip with the AssumeUTXO feature. This will be a massive win for those wishing the skip the overnight sync and get straight to work.

    Overall, I think you do good work in promoting Dash and platforming community members on your youtube show, the most recent example with August helped get across his ideas and that was useful, so I like that. I like the focus on bringing in new devs to the Dash ecosystem, but certainly that has been the focus for the past 12 months and while we did see some new faces, few stuck around. I think we need to address that and find out what happened to them? Were they not a good fit? Not enough work? Names that come to mind are, Anthony and Niles, but there were many others.

    I think this proposal asks for a lot for what I think you do, but I assume you save most of it until you find a new dev to incubate, in that case I am voting YES. However, since the proposal is for 12 months, I may in the future change that vote and will comment again if I decide to do that.
    Reply
    3 points,6 days ago
    Thanks for your support and feedback. That's a very fair comment.

    As Dash's purchasing power rises, this proposal's funds and the treasury in general will be able to support more work from the devs I've found (and will find). Anthony, Niles, and others would love to continue working with Dash, but they will be more cost effective with better SDKs (from AJ, DCG, or ideally both).
    Reply
    3 points,11 days ago
    yes
    Reply
    3 points,6 days ago
    Thanks for your support, Agnew!
    Reply