Home
Notification
Profile
Trending Articles
News
Bookmarked and Liked
History
Creator Center
Settings
gakonst
--
Follow
Who has the best express / 1click checkout for stablecoins?
Disclaimer: Includes third-party opinions. No financial advice. May include sponsored content.
See T&Cs.
0
0
Explore the latest crypto news
⚡️ Be a part of the latests discussions in crypto
💬 Interact with your favorite creators
👍 Enjoy content that interests you
Email / Phone number
Sign Up
Login
Relevant Creator
gakonst
@gakonst
Follow
Explore More From Creator
What I think is important for Ethereum to win while maintaining a global node set: 1. decouple validation from block building throughout with zk. this needs making zk proving blocks in real time easier: ePBS or Delayed Execution, I don't care which. trie migrations help but imo not needed, whereas ensuring you don't prove at the end of the slot but at the start really matters. 2. decouple censorship resistance from weakest node. If you do the above, introducing low-ETH staked nodes w FOCIL who are responsible just for CR but not for the hot path block building and validation liberates us from raspberry pis for scaling but let's us continue using raspberry pis for CR
--
What I think is important for Ethereum to win while maintaining a global node set: 1. decouple validation from block building throughout with zk. this needs making zk proving blocks in real time easier: ePBS or Delayed Execution, I don't care which. trie migrations help but imo not needed, whereas ensuring you don't prove at the end of the slot but at the start really matters. 2. decouple censorship resistance from weakest node. If you do the above, introducing low-ETH staked nodes who are responsible just for CR but not for the hot path block building and validation liberates us from raspberry pis for scaling but let's us continue using raspberry pis for CR
--
I'm still baffled that the Ethereum Core Dev community does not prioritize fixing the 2 most cited problem of EVM developers per the Solidity Lang survey despite our repeated efforts: 1. Stack too Deep: yes this is a Solidity skill issue a little bit but just add a SWAP/DUP17-32 opcode range and call it a day. You will burn some opcodes. It's fine, they are meant to be used. You're gonna have another PUSH0-style mismatch, this is also fine, it's not perfect but it's fine. 2. Lift the 24KB limit. I don't really care what you do, make it 32KB, 48KB, 128KB, 256KB, 512KB, do it all at once, incrementally, price it or not but do something! Now, not next year! If you are scaling the L1, ensuring people can write contracts without stupid errors is P0. If the system cannot handle an extra 8KB per bytecode which is a param that was set 10yrs ago literally then there's no chance you will be able to actually scale the L1. Fix stack too deep and bytecode size limit! For the devs!
--
I'm still baffled that the Ethereum Core Dev community does not prioritize fixing the 2 most cited problem of EVM developers per the Solidity Lang survey: 1. Stack too Deep: yes this is a Solidity skill issue a little bit but just add a SWAP/DUP17-32 opcode range and call it a day. You will burn some opcodes. It's fine, they are meant to be used. You're gonna have another PUSH0-style mismatch, this is also fine, it's not perfect but it's fine. 2. Lift the 24KB limit. I don't really care what you do, make it 32KB, 48KB, 128KB, 256KB, 512KB, do it all at once, incrementally, price it or not but do something! Now, not next year! If you are scaling the L1, ensuring people can write contracts without stupid errors is P0. If the system cannot handle an extra 8KB per bytecode which is a param that was set 10yrs ago literally then there's no chance you will be able to actually scale the L1. Fix stack too deep and bytecode size limit! For the devs!
--
I'm still baffled that the Ethereum Core Dev community does not prioritize fixing the most cited problem of EVM developers per the Solidity Lang survey 1. Stack too Deep: yes this is a Solidity skill issue a little bit but just add a SWAP/DUP17-32 opcode range and call it a day. You will burn some opcodes. It's fine, they are meant to be used. You're gonna have another PUSH0-style mismatch, this is also fine, it's not perfect but it's fine. 2. Lift the 24KB limit. I don't really care what you do, make it 32KB, 48KB, 128KB, 256KB, 512KB, do it all at once, incrementally, price it or not but do something! Now, not next year! If you are scaling the L1, ensuring people can write contracts without stupid errors is P0. If the system cannot handle an extra 8KB per bytecode which is a param that was set 10yrs ago literally then there's no chance you will be able to actually scale the L1. Fix stack too deep and bytecode size limit! For the devs!
--
Latest News
Arizona Senate Passes Bitcoin Reserve Bill HB 2324
--
Trump Extends TikTok Sale Deadline by 90 Days
--
Abstract Chain's Official Account Compromised in Solana Scam
--
Elon Musk's Vision for X: A Comprehensive Super App
--
Trump's Company Reduces Stake in WLFI, Potentially Earning Significant Profits
--
View More
Sitemap
Cookie Preferences
Platform T&Cs
