Jebinraj

One thing that gets tricky when building onchain apps: The application may need the data to do its job, but that doesn't mean everyone else should be able to see it Think API credentials, private inputs, user-specific information or business logic Making something verifiable shouldn't mean making every detail public That's an interesting part of what @RialoHQ is exploring with confidential execution The goal isn't just to run code onchain It's to make the result verifiable while keeping sensitive information protected Feels like an important piece if we want onchain apps to handle more than simple transactions

Yeah!!

dk it's still continuing

This cute duck

Downtober 🤝 Downvember Different month, same pain!

Processing 1,000 transactions at once sounds impressive But what if 100 of them are trying to update the same account? That's where things get interesting Parallel execution can make a blockchain faster, but handling conflicts without messing up the final state is a whole different challenge This is something I find interesting about @RialoHQ It's not just about running transactions in parallel. It's also about making sure they produce the right result Because speed means very little if correctness gets lost along the way

Intern Wah braining

@bluvv_xo @duel_duck