morgoth (@morgoth) • Hey

Publications

Continuing visiting the most interesting places in Europe
Momoka, the new infrastructure powering @lensprotocol, just hit 500,000 transactions at a total cost of ~ $173 With these updates our infrastructure is now ~250x less expensive while being ~165x more scalable than in the past. 🤯 Momoka Stats 💰 Cost of 100,000 transactions: Old infrastructure ~ $10,000.00 Momoka ~$40.00 Difference ~250,000% less expensive ⚡️ 📈 Scalability of 100,000 transactions Old infrastructure (~30 TPS) 55 minutes Momoka (~50,000 TPS) 2 seconds Difference ~ 165,000% more scalable ⚡️ Here’s how it works 🌫️ Blockchains today cannot scale to social TPS. Traditional databases scale to up to millions of operations per second while most blockchains max out at a few hundred. This is mainly because blockchain storage is an expensive bottleneck in terms of both cost and scalability. Blockchain storage is more than just storage - it also enables composability, allowing your state to also be executed with other smart contracts and programs. But with most social use cases, especially non-financial, that power and composability is not needed, so why would we continue to use it in this way? For decentralized social applications, two of the main characteristics needed are permanent and immutable storage tied to a user’s identity. What if those characteristics could be derived from another infrastructure layer, but at a much lower cost and with more scalability? In the past, all Lens transactions were processed on the EVM via Polygon network. What is the EVM at its root? It is a big state machine, holding the entire history of state changes of what has happened in what are known as archive nodes. The expensive part of using EVM networks is performing these state updates. BUT! The EVM only forces cost when you want to change the state in the next block. The EVM does **not** charge anything to simulate if something could of happened on a certain block. This means that you can leverage this to check that a transaction has been signed by the correct access control and would of passed for free *without any gas needed*. When you do an EVM contract call, you are signing the transaction with your private key. The EVM verifies this and injects key helpers like msg.sender which is your public key to allow contracts to know it was you who did that. Since transactions can be run for free to prove something has the correct access control conditions to run it, what if we swapped the storage updates to a place that can handle high TPS, cheap, immutable, one time payments and will be guaranteed for at least 100 years? Momoka is an optimistic hybrid layer 3 solution from Lens Protocol that uses data availability storage on Arweave/Bundlr along with transaction proofs on Polygon to enable highly scalable and low-cost social graph data storage and verification. It allows proving social graph transactions would be valid on-chain without actually submitting them, enabling greater scalability while maintaining verifiability and user ownership. Arweave is a decentralized blockchain-like infrastructure protocol, built specifically for storing data forever for a one off cost, and was launched over 6 years ago. Bundlr Network is an Arweave scaling solution built to handle 50,000+ TPS. It functions similarly to a rollup in that it batches multiple transactions together and posts them to the underlying network. An important characteristic of Bundlr is that it supports EVM addresses, allowing you to build EVM tech state on Arweave ⚡️. They also allow you to pay fees in any EVM native token you wish! To enable this new functionality on Lens, Momoka introduces two new pieces of architecture - the Submitter and the Verifier. Submitters are responsible for validating and constructing the metadata and submitting it to Arweave, providing proofs that anyone can contest. The Verifier software listens for publications sent from whitelisted submitter addresses and verifies their validity. Anyone can run a verifier using open-source software with a few commands. https://github.com/lens-protocol/momoka Momoka is not limited to blocks and max limits as the restriction has been removed due to storage on Bundlr/Arweave. Momoka gets timestamp proofs from Bundlr to be able to keep chain and off-chain actions in ordering and also to have a third party timestamp to avoid trust assumptions on Momoka. With Momoka, users still own their content as it’s not possible to action a Momoka transaction if you do not pass the access control on-chain. Momoka is fully trustless – anyone can check proofs with their own Polygon archive node! We believe Momoka is core to the future of web3 social, enabling applications to scale to tens of thousands of operations per second while still enabling the differentiating features that make web3 social unique and special. To learn more about Momoka, check out the following resources: Announcement post https://mirror.xyz/lensprotocol.eth/3Hcl0dGE8AOYmnFolzqO6hJuueDHdsaCs3ols2ruc9E Momoka Explorer https://momoka.lens.xyz/ Momoka Verifier software https://github.com/lens-protocol/momoka
Spain is definitely different Monday morning and here I am having tapas for dinner on a busy af street Which street though?
Vibes check: on https://orb.ac/post/0x05-0x1f16-DA-afd4efca
Impressive
Vibing
What is dead can never die Maison Carrée, Nîmes, France. Monument dedicated to Julius Caesar, 2AD… Aprox 46 years after his death.
Gm fam What are you guys up to over the weekend?
Take **your** followers with **you.**
You don't need to collect anything onchain in order to take someone's data and train AI on it. In fact I could already take all your posts and make train AI on it without interacting with you once. Also I don't really understand the concept of becoming a "user" of someone. It sounds like an euphemism for stealing someones data and replicating it. Where is the benefit for the creator?
Muahahahaha I am alive, I am Morgoth, I destroy Middle Earth
Beware for I am Morgoth