Sabitlenmiş Tweet
Ready to take @pintocommunity to the next level. The world needs low volatility, leviathan free monies, and we aim to deliver hard.
Expect big things 2025 🌱
English
Frijo (1≈1)
230 posts
Frijo (1≈1)
@Fr1j00
In all things of nature there is something of the marvelous. Lead developer and co-creator of @pintodotmoney, the next iteration of money.
Katılım Kasım 2024
109 Takip Edilen121 Takipçiler
Proud to achieve first place on the @InverseFinance competition in @sherlockdefi. Pushed super hard on this one and sometimes things just click.
Turns out stablecoins is my favorite thing to audit after working on one for 2+ years!
Excited for the next steps coming soon 👀
SHERLOCK@sherlockdefi
Here are the results of the @InverseFinance Audit Contest! 1. @0xdmanwalking - $1,833 🥇 2. bughuntoor - $8,312 🥈 3. @ValvesSec - $1,691 🥉 $35,500 in rewards, bringing Sherlock's total researcher payouts to $19.6M+. Link below for the full results 👇
English
🫣 Calldata encoder has been achieved internally @swissknifexyz
Frijo (1≈1)@Fr1j00
@apoorveth wen calldata encoder, it would truly make this site a one stop shop
English
... after three long days with claude code, i have this to share:
→ SlotScan.info a human readable web ui for evm storage visualization (supports Solidity + Vyper)
→ Blog post documenting my learnings: wavey.info/posts/2025/rev…
English
the value of one unchanged standard greatly outweighs the benefits imo. It would be hard for me to see us upgrading the diamond off of pure syntax changes. What about immutable diamonds? Will they be non standard now?
5 mins of googling nonstandard terms is way more favorable than new devs having to understand why there are two sets of diamond functions.
I think you should reach out to projects that use the diamond standard in prof and get their opinions, but imo it will be met with indifference/hesitation
English
Guess what? I want to change the ERC-2535 Diamonds standard.
Yes — the Final Ethereum standard that’s been around for 5 years.
Why? Because it can be better.
Most people don’t realize this, but “Final” EIPs can still be updated. EIP-1 says Final EIPs may be changed to add non-normative clarifications — meaning improvements that don’t alter the rules or behavior of the standard, but make it clearer and easier to understand.
The biggest complaint over the years has been the extra terminology I introduced — I took the diamond metaphor too far. Too many diamond-industry words. Too much cognitive overhead.
You’re right. I did. And now I want to fix it.
I’m proposing simpler, clearer terminology that keeps Diamonds powerful but removes the unnecessary baggage.
Details here:
🔗 ethereum-magicians.org/t/revising-erc…
English
@jarrodwatts blobscan.com/stats
easy link for those who want to view (7 day view)
English
Blob fees are already up 1500x since the Fusaka upgrade has gone live!
Up from 1 wei -> 1500 wei and climbing quickly
English
i hear this thrown around all the time, it’s misleading and honestly a little disingenuous to say “if blob demand was constant w/7918, all ETH would be burnt”
L2s would generally post less blobs to compensate until there is natural equilibrium. 7918 would make the system reach equilibrium faster, and perhaps increase that equilibrium, but it’s nowhere near the level of the level stated here.
English
In anticipation of Fusaka and EIP-7918, I built a little somETHing.
I present to you: blobs.money
This website simulates the fees and the resulting burn from EIP-7918 as if it were live already.
Yes, (theoretically) today all existing ETH would have been burned many times over under EIP-7918.
Wait... but why? When blob fees basically burned nothing consistently for the last months, how would that change so drastically now?
Isn't this absurd?
Well, no, because in the past it took ~50 minutes of nearly full blobs to even come close to a fee range that would have a measurable impact in $ terms.
EIP-7918 in Fusaka now introduces a moving fee floor for blobs via a reserve fee, which is derived from the execution gas fee.
This fee floor is many “million” times higher than the current floor of 1 wei right now.
That means tiny, but finally noticeable, amounts of ETH are now being burned regularly from blobs, even at times of lower blob congestion. At the same time, we'll enter price discovery much (much) sooner compared to before.
This leads to the absurd amount of ~5.1M ETH (theoretically) burned during the last hour.
While under the old regime that wouldn’t even have made an impact on fees, under the new reserve fee, having even smaller periods of blob congestion will let the blob market enter price discovery.
Obviously, the result will not be 5.1M ETH burned, it will be rollups adjusting to a new reality... The reality of having to pay an actual market price for the resources they use.
This project is still in a very early stage, but I definitely wanted to launch this before Fusaka, so here it is!
A fun little blob explorer 🔥
(Follow @blobs_money for updates and some interesting blob burn stats later this week.)
English
As a diamond lover, it would require an opcode repricing and huge ecosystem support in order for devs to use - reducing gas to delegatecall would get us a decent way there.
What would help imo is an on chain registry of facets. there should be a facet deployer that assigns a unique id/hash as a function of bytecode (or could be on the facet itself) upon deployment.
anyone can query and thus make it easier for people to compose
English
Nick Mudge 💎@mudgen
We have an opportunity to create something new and valuable for Solidity developers. The Solidity team has said they plan to remove inheritance and Solidity libraries from the language. That’s a drastic shift — but in my opinion, it’s the right direction. What most people don’t realize is this: 👉 You can already build great smart contract systems TODAY without inheritance and without Solidity libraries. How? By writing your Solidity code outside of contracts and libraries, and importing those files — essentially using them as modules. Solidity has the term “free functions,” but that only covers the functions themselves. You can also define structs, enums, constants, errors, events, comments and more. …all at the top level, outside any contract or library. These files behave exactly like modules in other languages — but Solidity never gave them a name. To avoid confusion with “Solidity libraries,” I propose calling them Solidity modules. I’ve already refactored Compose (compose.diamonds) to use Solidity modules. Designing Compose for the future means aligning with where Solidity is heading — and modules are a big part of that future. The idea to use free functions instead of libraries was suggested to me by Cameel, from the Solidity Compiler Team. What do you think?
English
Super proud to have cracked the Top20 at my first audit competition with 4M issues. Going all in now with no turning back.
Big thanks to @sherlockdefi for hosting and wishing the @Convergence_fi team a smooth launch for USG.
Still a lot to learn. Onwards!
English
@gakonst agreed, its unclear who is going to use this in the first place, and when there's clearly higher prio things to be fixing
English
Maybe unpopular opinion, I think Solidity as-is is mostly fine, and the highest priority thing to fix is _not_ new syntax / language features but the complier:
- make compilation 100x faster
- make gas optimization 100x better
- solving stack too deep
- making the compiler easier to extend & experiment so that EVM devs can propose new EIPs that improve the EVM
All for generics & better syntax, just doesn't feel like high priority. I fear a python2 to python3 moment.
Solidity@solidity_lang
Presenting 'The Road to Core Solidity', a series of blog posts through which we will share where we are headed with the language. Let's take a look at the overview!
English
@jessepollak @base does the creation a fully endogenous, censorship-resistant, network-native money count here?
The die-hard farmers at @pintodotmoney believe a more fair form of money is needed to usher in the new economy, and we need everyone that’s willing to lend a hand in this endeavor 🌱
English
If you want to get followed by me or @base:
- build an app that onboards new users
- create content that onboards new users
- grow a community that onboards new users
- deploy your capital into the base economy
if you do any of those, we will see you and follow you.
English
Ill never forgive the Eth devs for removing EIP7907 in the Fusaka upgrade- Pinto is at the point where we require multiple library links in order to get the contracts down to 24kb 🙃
Time spent on dealing with this is time not spent on writing good code
English
@yq_acc in the “supposed capital efficiency” section, is the leverage supposed to be 10x? else the math is very unclear to me
English
people are jaded because a significant amount of economic activity on ethereum uses value that doesn’t adhere to the ethos of ethereum.
there is a huge disconnect where the value proposition of ethereum (or any L1 computational network) is derived from said activity on the network, but the value itself is censorable and centralized.
it’s no wonder why great people are moving on. the money problem is the root of all this, and only a censorship resistant, network native money can solve this.
English
I guess I’ll say it.
This is not great for Ethereum. 🫠
Losing key talent to alt L1s now.
Tempo is built on Ethereum tech and now stacked with former Ethereum OGs - people who loved Ethereum but became somewhat jaded for one reason or another.
Dankrad Feist@dankrad
I am excited to announce that I will be joining Tempo. This last year has been a turning point for crypto, where we have finally seen the outlines of our vision being materialized. While payments used to be front and center in the early days of crypto, I see a special opportunity to finally achieve this ambitious goal with relentless execution on both the technical and distribution fronts. I believe that the real world moment is now, and I want to make sure we do not miss this window to touch normal people’s lives everywhere in the world. I have dedicated the past several years to architecting and scaling blockchains, and I’m excited to leverage my learnings together with the very strong team being assembled at Tempo. My journey in Ethereum first started when I began working with the EF research team in 2018, and later joining full time in 2019. The project has greatly matured since then and with the soon coming Fusaka upgrade will implement PeerDAS, a significant scaling milestone I am proud to have contributed to. I am very happy to have played a role in leading to more people being able to use Ethereum and I look forward to continuing being able to do that. Over the last year, I have been involved in advancing Ethereum Foundation’s strategy and roadmap and I will remain a research advisor to the three strategic initiatives (Scale L1, Scale Blobs, Improve UX) at the Protocol Cluster at the EF. Ethereum has a strong set of values and technical choices that make it unique in the world. And Tempo will be a great complement, built using similar technology and values, whilst being able to push the boundaries on scale and speed. I believe that this will be of great benefit to Ethereum. Tempo’s open-source technology can easily integrate back into Ethereum, benefiting the entire ecosystem. Ethereum and Tempo are strongly aligned, as they are built with the same permissionless ideals in mind. I am looking forward to staying involved with the community and continuing to push Ethereum forward!
English
printer gone rouge, couldn’t be @pintodotmoney
zoomer@zoomerfied
[ ZOOMER ] PAYPAL'S PYUSD MINTS $300T ON ETHEREUM
English
1) Various pain points in developing in the EVM including but not limited to: stack too deep, contract size limits, gas costs incentivizes one off deployments rather than composable infrastructure
2) Lack of infra for ERC-1155. Most of DeFi is limited to only ERC-20s.
3) lack of economic innovation. Most value on eth are exogenous and not network native. From a technical perspective, the network is censorship resistant, but certainly not from an economic perspective.
English
dear ethereum power users, what would you say are your biggest frustrations with DeFi?
English
Love to hear it! We are actually discussing internally about creating an EIP that will extend the diamond functionality, which standardizes forking between Diamonds.
This EIP would create the first smart contract governance mechanism that is arguably better than network level governance.
Would love to talk more about it 🙂
English
@Fr1j00 Wow! I am really glad you are forking Beanstalk. I like that technology. I am glad to know about your project!
English
If you are a Solidity developer, then I want to follow you.
English
@zerosnacks the feature for impersonating signatures is awesome! well needed, ty for your work 🐐🐐
English
Foundry has a new release candidate: v1.4.0-rc3!
Highlights include: backtraces, configuration inheritance & multi-chain configuration, forge fmt powered by Solar🌞, enhanced coverage guided fuzzing, custom precompiles & many performance improvements!
$ foundryup -i v1.4.0-rc3
English