Unless you have been living under a rock, you’re probably building your own L2 right now.

It’s easier than ever to launch your own chain, and doing so can scale your app while bringing new means of generating revenue though fees. We’ve recently seen web3 staples like Coinbase and Zora launch their own chain, and many more teams are preparing to follow suit.

By moving dapps on purpose-built chains while still keeping the interoperability, global namespace, and developer tools of the EVM, we can reach a scale ready to onboard the next billion users on web3.

To succeed, L2s need to embrace their developer community. Developers will have many chains to choose from, meaning a great developer experience can set you apart from the rest. Attracting developers allows your ecosystem to thrive, with essential tools like Wallets, Explorers and DeFi applications.

We’ve been building to support this future, and would love to share more about our upcoming feature, Basement Stack.

👀 Basement Stack is In Private Beta, reach out here to get access.

When Zora announced their L2’s testnet, we figured this was the perfect time to test Basement Stack in the wild. Overnight we had a SQL Playground and GraphQL API up and running, allowing developers to access any onchain event, NFT and transaction in realtime.

We’ve since been working on making Stack available to more developers, along with programmable streams, and any data-warehouse as a destination for your data.

Basement stack is a modular and programmable data processing pipeline for onchain data. Each part of a pipeline is designed to be interchangeable, meaning you can easily iterate and run the same stack on any chain.

For more than a year we have been working on making this feature a reality. Built on Elixir and the battle-tested BEAM Virtual Machine, Stack is fast, modular and fault-tolerant. We believe this tool is a key part to making L2 teams thrive.

First, we index primitives using our Adapters. Adapters extract onchain primitives from any RPC node, and store them in a database specifically optimized for reading large sets of onchain data. We take care of things like re-orgs, and ensures data gets delivered in realtime.

Thanks to this optimization we can later backfill in mere seconds rather than hours, depending on the size of your dataset.

We currently support EVM-based adapters, but are working with L1s to allow more types of chains.

These indexed events are read by hundreds of processes who transform and decode them at incredible speeds. We call these Streams.

You can run some custom code here to transform your events in any way you’d like, however most of the time an ABI and some filters is more than enough.

This data can be streamed to any destination you’d like. Need to make data searchable? Sync to ElasticSearch. Wanna ride the AI wave? Send it all to Snowflake. Analytics? Segment! We’re happy to help set up whatever data-warehouse best suits your needs.

Of course, running your own data-warehouse is not for everyone. This is why we have designed a general-purpose GraphQL API for the most common onchain interactions, and a fast and easy-to-use SQL playground to give you full creative freedom.

You can give these APIs a try for existing chains by signing up here:

https://dashboard.basement.dev

Over the coming weeks we’ll share more about Stack.

Later this year you’ll be able to add an RPC Endpoint in the dashboard, and spin up a public or private API without having to write any code. Once synced, data can be streamed to any destination you’d like with our no-code interface.

We are incredibly excited about this decentralized future, and aim to make Stack generally available as fast as possible, and are ready to onboard your chain in private beta.

We’re onboarding new chains in beta right now – if you’re interested, shoot us an email on stack@basement.dev, DM us on Twitter, or reach out here. The Basement team will get in touch to onboard you as soon as possible.

Unless you have been living under a rock, you’re probably building your own L2 right now.

It’s easier than ever to launch your own chain, and doing so can scale your app while bringing new means of generating revenue though fees. We’ve recently seen web3 staples like Coinbase and Zora launch their own chain, and many more teams are preparing to follow suit.

By moving dapps on purpose-built chains while still keeping the interoperability, global namespace, and developer tools of the EVM, we can reach a scale ready to onboard the next billion users on web3.

To succeed, L2s need to embrace their developer community. Developers will have many chains to choose from, meaning a great developer experience can set you apart from the rest. Attracting developers allows your ecosystem to thrive, with essential tools like Wallets, Explorers and DeFi applications.

We’ve been building to support this future, and would love to share more about our upcoming feature, Basement Stack.

👀 Basement Stack is In Private Beta, reach out here to get access.

When Zora announced their L2’s testnet, we figured this was the perfect time to test Basement Stack in the wild. Overnight we had a SQL Playground and GraphQL API up and running, allowing developers to access any onchain event, NFT and transaction in realtime.

We’ve since been working on making Stack available to more developers, along with programmable streams, and any data-warehouse as a destination for your data.

Basement stack is a modular and programmable data processing pipeline for onchain data. Each part of a pipeline is designed to be interchangeable, meaning you can easily iterate and run the same stack on any chain.

For more than a year we have been working on making this feature a reality. Built on Elixir and the battle-tested BEAM Virtual Machine, Stack is fast, modular and fault-tolerant. We believe this tool is a key part to making L2 teams thrive.

First, we index primitives using our Adapters. Adapters extract onchain primitives from any RPC node, and store them in a database specifically optimized for reading large sets of onchain data. We take care of things like re-orgs, and ensures data gets delivered in realtime.

Thanks to this optimization we can later backfill in mere seconds rather than hours, depending on the size of your dataset.

We currently support EVM-based adapters, but are working with L1s to allow more types of chains.

These indexed events are read by hundreds of processes who transform and decode them at incredible speeds. We call these Streams.

You can run some custom code here to transform your events in any way you’d like, however most of the time an ABI and some filters is more than enough.

This data can be streamed to any destination you’d like. Need to make data searchable? Sync to ElasticSearch. Wanna ride the AI wave? Send it all to Snowflake. Analytics? Segment! We’re happy to help set up whatever data-warehouse best suits your needs.

Of course, running your own data-warehouse is not for everyone. This is why we have designed a general-purpose GraphQL API for the most common onchain interactions, and a fast and easy-to-use SQL playground to give you full creative freedom.

You can give these APIs a try for existing chains by signing up here:

https://dashboard.basement.dev

Over the coming weeks we’ll share more about Stack.

Later this year you’ll be able to add an RPC Endpoint in the dashboard, and spin up a public or private API without having to write any code. Once synced, data can be streamed to any destination you’d like with our no-code interface.

We are incredibly excited about this decentralized future, and aim to make Stack generally available as fast as possible, and are ready to onboard your chain in private beta.

We’re onboarding new chains in beta right now – if you’re interested, shoot us an email on stack@basement.dev, DM us on Twitter, or reach out here. The Basement team will get in touch to onboard you as soon as possible.