Since yesterday and throughout today, instead of tweaking code, I took a deep dive into thinking through the…

Since yesterday and throughout today, instead of tweaking code, I took a deep dive into thinking through the fundamental architecture of the protocol. One interesting thing I realized is that I originally assumed every part of Ethereum and Web3 guaranteed end-to-end "integrity" purely through the system itself. However, as multiple layers and diverse entities get involved, I discovered that far more components than expected actually operate on "trust." It’s almost like how we all agree not to cross on a red light and only walk on green. That said, this isn't an issue for my ongoing project, nor does the project require that extreme level of integrity. Below is a list of core conceptual keywords that will be applied to the protocol. If I had already known all of this beforehand, it wouldn't have taken so long. But learning each concept along the way and evaluating the rationale behind every single one definitely slowed down the process. Among these, I highlighted "No per-edit approval or gas" in green because it is a principle I really want to protect. Given the nature of the protocol, it needs to capture granular user actions. If a wallet approval popup appeared every single time an action is recorded, the UX would be unbearable, and gas fees would become a major barrier to entry. Moreover, in the long run, I felt this could foster a bad habit of users mindlessly clicking "Approve." Another key insight was that not every raw action from users needs to be stored directly on-chain. No one should be able to tamper with the user's records. The records must be permanently stored. Anyone should be able to view the original source. As long as these three conditions are met, the original data doesn't necessarily have to live on-chain. Therefore, I shifted the approach to anchoring only the hashes of the raw data on-chain. Since handling "currency-grade" integrity isn't the primary goal of this protocol, I decided to aim for an architecture that practically approaches that standard, rather than obsessing over absolute 100% tamper resistance. Through this process, I also came to truly appreciate just how thoughtfully designed the Lens Protocol is. Using Hey naturally piqued my interest in its underlying design. In any case, starting tomorrow, I plan to flesh out and specify the details based on this foundational architecture. It's shaping up to be an exciting journey! ⛵