🪐 Current Milestone

⏱ Milestone 3

Time: 2 months ($100k)

• Load and security testing of validator DDOS protection and successful propagation of submitted transaction, protecting Juno validators from black-swan crashes caused by massive congestion
  • This has been completed over a period of 5 months!
• Commitment of 30+ validator design partners in test environments
  • We beat this milestone by 100%, and on mainnet, not just Testnet!
• Initial mainnet launch on our own validator and with a select group of 5+ early adopters, to scale to full set each week given load testing and live monitoring
  • We beat this milestone by 1,200% on mainnet

✅ What’s been completed

• Mainnet-adoption of Skip and mev-tendermint on over 60 validators (~70% of stake!)

  • This is more than we ever hoped, and the success of Skip on Juno has been a surprise for our entire team

• Recently: over 200 JUNO in MEV recaptured for the community per day!

  • This has led to meaningful value recapture, volume, and balancing on the two new DEXes that have launched (WYNDEX and Hopers) - with much more to come

  

• New validator dashboard, everything fully public for the community (skip.money/validators) - average of 75% of MEV reshared to stakers!

  

• New activity dashboard, everything fully public (skip.money/activity)

  

♻️ Changes to the Final Distribution

• Given a number of unfortunate narratives and perceptions regarding the handling of project’s grant funds, we propose that the final $100k allocation in JUNO tokens is vested over one year, i.e. on DAODAO V2
• Skip has never sold any substantial portion of it’s grant (we still hold and stake 99% of our original grant funds!) and we hope the community has acknowledged this, and is continually excited by the value that Skip has brought to Juno in the form of MEV recapture (and future projects it has been launching like Skip Secure)
• Skip uses its grant funding to take a long-term bet on Juno, and to support validators testing and using mev-tendermint with delegations. Nothing has made us less bullish, and we hope our own efforts contribute to making Juno more exciting and widely adopted.

🕊 Next Focus

• The final frontier: making mev-tendermint a viable (and perhaps alternative) dependency for Juno!
  • Although we have deployed docker containers, ansible playbooks, precompiled binaries, and alternate git repos to make building with mev-tendermint as easy as possible, and increasing number of validators have asked if mev-tendermint could be offered
    • At a minimum as a alternative dependency within the core Juno binary repo
    • At a maximum, as the core tendermint dependency
  • Although mev-tendermint is now the majority-used active version of Tendermint by stake weight on Juno, and has been without flaw for many months, we would still like to complete a formal audit with Informal (mid process here)
    • We’re happy to take any additional steps