web3 people! Happy new month!!!
we starting this month with a win 70$ playing @LootSurvivor opus yield dungeon @OpusMoney
initial investment 16$
The opus yield dungeon is the first implementation i have seen merging decentralized finance into web3 game.
Devs , players , community think about this.
A game makes a deposit and generates yield, that yield is then accumulated for a period then given to players as prize pool. This way the principal is intact and players can keep getting rewarded in battle for the yield.
@LootSurvivor has done this beautifully integrating @OpusMoney
More project should explore this its mind blowing
Happy new month and don't die in the dungeon
for all of these efforts i am very grateful. the only points of .. controversy, for lack of a better term, may be at the *amount* and *level* that the EF supports us. for example, it would be wonderful if they would publicly acknowledge our efforts on helping make the ecosystem more secure and user friendly, and for example for our efforts on formally verifying the compiler (first formally verified smart contract compiler!) and the @Verifereum's EVM (a current, and production-ready formal semantics for the EVM!) and perhaps put us in the spotlight or public discourse more.
it would also be wonderful if they funded us more sustainably than in the form of one-off grants, leaving us to wonder where we are going to get money from to keep the lights on in the next fiscal period. that is all! thanks again to the EF and thank you for reading.
i am happy to see people supporting @vyperlang but i want to make some important clarifying points, and i do not want to see this support be at the expense of @ethereumfndn, because --
- the EF *has* supported vyper to varying extents, particularly in the past couple of years
- for the first time ever, the EF gave us a grant in fiscal year 2025 to support work on the compiler
- they have kindly taken us on as a pilot project in project Odin (shout out to @nachortti !) to help us find sustainable revenue
- i have seen many EF members begin to acknowledge and include @vyperlang as a production-ready smart contract alternative to @solidity_lang
the _toy_ language Fe is the perfect example of ivory tower building. it's not only a misallocation of funds but a complete lack of vision for what actually matters in the real world. Vyper is the uncapturable, formally verified, cypherpunkish surviving smart contract language this space actually needs. not a circle-jerked theoretical language that still hasn't been prod ready after years. if you're bullish on Ethereum, you _must_ fund Vyper, there is no other choice.
btw very appreciative of the work @nachortti has been doing with us on project odin, but i do want to call out that on the grants side the EF is funding all kinds of formal verification and stack spilling projects.. when we have just kind of already done it? it almost feels like the EF is going to extra lengths *not* to fund us 🫠
"- from my seat at the EF, working on devex. A short-term fix for stack-too-deep is in sight, while solar, solx and the solidity team work on the real long-term solution"
?? vyper already has stack spilling algorithms and are even formally verifying the stack spiller and scheduler. why aren't we getting funded or even recognized for the novel work we are doing?
argot was spun out of ethereum foundation with a mandate to maintain ethereum's core programming languages and developer tooling.
then it immediately begins to launder research as if it was core infrastructure maintenance.
if you read their blog, they spend a lot of resources on fe, a language that has been "emerging" for over 5 years. they have long plans for fe, while the language itself has seen zero adoption and zero production use. their long term goal is "non-trivial contracts in production-like setting".
meanwhile vyper is actual production infrastructure. it secures real protocols, with real users and tvl, and real audit surface. curve, lido, yearn, frax, velodrome all use vyper.
yet vyper lives grant-to-grant, while argot started with a $16.6m check, about as much as ethereum started with.
argot doesn't disclose how much time and energy it spends on the fe fantasy versus solidity, sourcify, hevm, or other genuinely core tooling. but clearly this pet project abuses and stretches the mandate. even though it's a programming language, by no serious measure it's "core". it should spin out and try to survive and prove demand independently.
production compiler maintenance should get baseline funding before speculative language incubation gets considererd.
vyper is in good shape today despite the ecosystem, not because of it. and it still does not sit right with me that resources keep getting misallocated away from the compiler people actually use.
ethereum keeps saying "public goods", then funds the toy compiler like infrastructure and makes the production compiler pass the hat. that is not stewardship.
Vyper now has a public, machine-checked formal semantics 🔥
The first complete, precise, executable definition of what every Vyper program actually means, written in HOL4.
This builds on @Verifereum’s EVM semantics, which already comes with a growing library of proven properties about the EVM itself (gas monotonicity, storage isolation, etc.).
basically all of my code is _open-source_ and _free_ to use; in most cases it's licensed under AGPL-3.0 so everything stays open & accessible forever. a lot of my code is used to protect millions or even billions in funds (e.g. my `safe-tx-hashes-util`), yet many projects still don't donate because i don't go through some retarded kyc process (guys, fuck u!), even though i actively help secure their systems & money (yeah fml). the Ethereum Security QF round will hopefully change that tbh.
so i've submitted 2 applications:
- snekmate: i started snekmate in 2022 as its sole author and have poured thousands of hours into it over the past 3.5 years (1,200+ commits so far). its math functions are now even formally verified, it's used by Curve to help secure millions in funds, it's included in external integration tests in Foundry & Halmos (and has found various bugs already), and even used in the Vyper compiler itself (various bugs detected in the new venom IR because of this integration). it's essentially a one-person project that powers & ships essential Vyper modules to teams across the ecosystem.
- safe-tx-hashes-util: before the EF deploys capital into some defi protocols, the multisig txs are verified using my tool. before we deployed 69,420 ETH into staking at TheDAO, those multisig txs were verified with it. major protocols rely on it as a local-first verification layer for one of the most critical parts of any multisig: transaction correctness. i also recently shipped an easy-to-use Qubes template. so far i've received around ~$25k in donations, while this script alone has helped secure billions in funds.
pls donate:
- snekmate: https://t.co/0EsnTMgi10
- safe-tx-hashes-util: https://t.co/KgC2mG1yDK
1D remaining to:
🪙Support indie DeFi builders @OpusMoney
🎮Support indie onchain game builders @provablegames
📘 Have fun while learning how to access the equity of your tokens without selling them.
We deeply appreciate your support 🫶
How are you liking the @budokan_gg x @LootSurvivor campaign so far?
How’s your experience with CDP (Opus) DeFi been?
Have you tried LP staking yet? The yields are too good to ignore.
We’d love to hear your thoughts, feedback, or anything you’ve noticed along the way. Share it with us 👇
Day 6 of Opus X LS: Borrow & Survive 🥋
ICYMI: https://t.co/B1q4RJZeig
Yesterday: 3 axes of DeFi-in-gaming.
Today: one mechanism in detail — yield-funded tournaments 🧵
Day 5 of Opus X LS: Borrow & Survive 🥋
ICYMI: https://t.co/B1q4RJZeig
Borrow-to-enter is one design.
There's a whole space of DeFi-in-gaming patterns. Mapping it 🧵