Not shared an update on rindexer latest development in a while, so here it is:- rindexer now supports reth ExEx out of the box, run the node and get rindexer to handle the indexing for you https://rindexer.xyz/docs/start-building/create-new-project/reth-mode
- stream all the data to redis streams (you can already do webhooks, kafka, rabbitmq and sns/sqs) https://rindexer.xyz/docs/start-building/streams/redis
- native transfer indexing https://rindexer.xyz/docs/start-building/yaml-config/native-transfers
- factory contract indexing https://rindexer.xyz/docs/start-building/yaml-config/contracts#factory
- More optimisations for speed, rindexer is even faster - rindexer migrated from ethers to alloy
- Running in production for lens, family and aave, we use the rindexer rust project to build more advanced indexing systems, which have worked out incredibly for usNext on the cards:- No code upserts, so you never have to write indexer code again (for tracking stuff like balances, etc)
- Generate indexing from a foundry project: rindexer new no-code --foundry
- Integrate Metabase so you can do graphs and reports with the data
- reorg handling out of the box
- more storage providers like clickhouse, BigQuery, mysql, etc
- anything else anyone wants raise and issue we will support it if it makes sensebig up to Skanda Jack @pawel and others who have been contributinghttps://github.com/joshstevens19/rindexer
Since its launch, I’ve noticed a wide range of lens noise, both positive and negative. I want to share some historical context and my thoughts on this.Lens began as an R&D project at Polygon before any L2s existed. It was built through a trial-and-error approach, resulting in numerous mistakes we learned from. Lens V2 was primarily a tech debt fix. Building something in R&D at the outset significantly impacted what was possible. We had to address numerous issues and add logic where feasible.Over the past few years, Lens has consistently paid for all the gas used by every app. Polygon’s costs were unstable, ranging from $10,000 to $20,000 per day in some peaks, especially during Ethereum’s volatile price fluctuations. Even the slightest increase in the number of unrelated NFTs being minted outside of Lens could drive costs up and potentially break Lens activity. To address this issue, we had to abandon our vision of pure composable core data ownership and create Momoka (which was still great). We were aware that the Polygon network wouldn’t be able to handle social mainstream usage and adoption and was essentially a temporary fix.Lens chain and Lens V3 were ways to eliminate all the tech debt and build something we truly believed in, leveraging the knowledge gained over the years. We developed a new protocol, storage solution, network, onboarding tools, developer dashboard, backend, SDKs, and documentation from scratch. Our goal was to create a flexible protocol with a set of primitives that could be used in an unlimited amount of various ways. We recognised that this build would primarily benefit developers. These foundational changes enables Lens for future possibilities of what can be built on it, what developers can create, and how they can extend it. The primitives can be used together or independently on a cheap and scalable chain.The easy option would have been to stay on Polygon and give up. However, this didn’t make sense to anyone who saw Lens potentially transforming the social landscape.Migrating the data was crucial because we understood that users had invested time and effort in building content, connections, and relationships. We wanted to honour their contributions by dedicating significant engineering resources to ensure a smooth migration process. This allowed users to log in and access their new accounts, connections and posts without doing anything. No other chain has managed to migrate such a substantial amount of data, which is a significant achievement. As a result, users can now utilise Lens on LC.While the apps had time to migrate, these processes were time-consuming due to the complete protocol change. Consequently, we all endured the challenges, even though some aspects of the apps were still imperfect. Throughout this process, the apps remained engaged and enthusiastic about the potential of Lens V3, which you’ll all see soon. The apps have put tremendous effort into this migration; it’s not an easy task, and we will carry out continuous fixes as they arise.Moving forward, we are now equipped to address the significant issues we encountered during Lens V1 and V2. We have established the necessary infrastructure and foundations to empower the apps to create incredible experiences. We have prioritised developers by providing a developer portal and easy-to-use no-code options, which we continue to enhance. We believe that without excellent developer tooling, amazing apps would not exist.Let’s acknowledge that building foundations and core infrastructure takes time. The networking foundation was established in the 1960s, and the Internet emerged from those foundations in 1989. However, mainstream adoption didn’t occur until ten years after the Internet’s founding. While the Internet itself was a significant milestone, it was the underlying foundations that paved the way for its potential. The core foundations may appear insignificant, but they serve as the stepping stones for future advancements.We fully understand that simply building and letting them come is ineffective. If it hasn’t proven successful for the internet, it won’t work for Lens either. With our initial build of the developer portal and family account onboarding, we will dedicate time to the application layer to demonstrate the incredible experience that can be achieved when building on Lens, both ourselves and with the apps that build on Lens. Without applications and experiences, the protocol becomes meaningless, just like the internet, and we aim to push that boundary.While some users may have anticipated substantial user announcements at the launch, our focus is on building a protocol that inherits core traits for the users we believe in—an open and decentralised social protocol that allows for various forms and the free exchange of information.As a company, we recognise the importance of effective communication and want to facilitate open discussions and community decision-making. While LIPs attempted to achieve this, its implementation on GitHub posed significant challenges. The social community discussion experience should be integrated into the protocol itself. We can for sure do a lot better at this and we will.We aim to empower users to earn rewards and create a protocol that enables apps and users to earn organic funds.Lens is for the people, and it is the driving force behind the efforts of all the core team members. We firmly believe in core ownership and recognise that a centralised network can only perpetuate stagnation. A full-fledged onchain social network is a highly challenging technological task. Still, we have laid the groundwork to enable innovation at scale while maintaining cost-effectiveness and speed without compromising ownership.For one, I want to start seeing new app experiments which are only possible with blockchain technology, we should be building web3 social to do stuff web2 can not do, and with the new protocol, it is even more flexible to create mindblowing apps.2025 is the year of the apps now the foundational core is complete, in turn, the users will thrive when apps thrive.
Lens Chain transactions are up
today is a good day to post on Lens
I know it may not seem like much but migrating data from one chain to another has been one of the most complex tasks of my life that i have been involved in - glad we are here and glad we can now grow. As my handle says WAGMI baby!! We most likely will have some issues throughout but we will fix it fast if anything comes up - glad to see you on LC ❤️
gm
If you are in a very senior tech role (VP/CTO) you need to still be in the trenches with the engineering team building the core code and you should be one of the top contributors to the codebase, know it inside out and leading the engineering team from the front, hands-on.
Special People Special Places - Milady 5891 - thanks @stani
bull market comes bull market gas costs 🙂
