Kenneth Smith

Porto is now production-ready & fully open source! Porto’s north star is to enable secure and programmable web-native crypto payments & finance without passwords, or browser extensions. Integrate now in 2 lines of code and in less than 1 minute: `pnpm i porto`.

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!

Porto is gonna 100x app UX. Bring your own auth like Privy, or use Passkey-based authentication, we provide best in class support for both. Gas optimal, 1-click, nextgen onboarding, cross chain, apps pay onchain "server" fees, users pay apps fixed fees, and so much more.