Blockless is ready to reinvent the blockchain industry with its groundbreaking modular application framework, which allows developers to choose the consensus algorithms and verification tools that are best suited to their individual workflows. With a strong emphasis on simplifying both user and operator experiences, Blockless is preparing for its testnet launch, targeting a diverse range of potential operators to assure network growth.

The latest AMA session shed insight on Blockless' novel approach to decentralized applications, which prioritizes developer autonomy and operational ease. Explore the core of Blockless's vision to transform the blockchain ecosystem, making it more accessible and efficient for all:

• X Spaces: AVS Deep Dive with Blockless
• YouTube: AVS Deep Dive with Blockless
• Spotify: AVS Deep Dive with Blockless

Speakers:

• Alan (X Profile): CMO @ Blockless (X Profile)
• Liam Zhang (X Profile): Engineering and Design @ Blockless (X Profile)

Index:

1. Blockless Framework
2. Blockless vs Other AVSs
3. Product and Performance Targets
4. Connection to EigenLayer
5. Modular Network Nodes
6. Fault Tolerance and Security
7. Distributed Orchestration
8. Blockless Technology and Adoption
9. User and Operator Focus
10. Technical Capabilities and Developer Experience

1. Blockless Framework

• Blockless is the first modular application framework and network, offering what Celestia did for blockchain networks by breaking down applications into individual workloads:

“So Blockless is the first modular application framework and network doing for applications what Celestia did for blockchain networks. (...) What we do is break the application layer down into individual workloads. So instead of processing an application as a whole, you break down those individual workloads”

• It enables users to power applications by selecting the best-suited node group or operator set for specific workloads, thus creating fully distributed, decentralized off-chain networks:

“And you're then able to actually enable users themselves to power the applications that they use, kind of creating fully distributed, decentralized off-chain networks that use the best-suited nodes for each individual workload”

2. Blockless vs Other AVSs

• Blockless stands out as the first modular application framework that provides different consensus and verification tools for distinct workloads:

“It is the first modular application framework. So for us, we see ourselves as quite different because we enable those different consensus and verification tools for different workloads. We enable people to... power applications by using them.”

• It focuses on empowering users and developers by allowing them to power applications they use and make choices about the rule sets and resources used for their workloads:

“The idea is that when you break an application down into its workloads, you liberate the developer and the users from having to adhere to one set of rules on one network. And so ultimately, what that means is that the application becomes network neutral”

3. Product and Performance Targets

• Blockless is nearing readiness for its testnet launch, which is expected in the next 6-8 weeks, with the mainnet launch anticipated to follow soon after:

”And so we are planning on launching a testnet very soon. um you can expect that um kind of in the next six to eight weeks and then also a mainnet um shortly after”

• The focus is on expanding their potential operator pool, targeting every consumer desktop device:

”Our main focus right now is really on expanding and growing our potential operator pool. And for us, our potential operator pool equates to every consumer desktop device out there.”

• The intent is to release performance metrics around the time of the testnet launch rather than engaging in theoretical performance claims:

“ In terms of the performance metrics and what we're what our goals are I think we're going to be releasing some more information around that when it comes to the uh launch of the testnet”

4. Connection to EigenLayer

• Blockless’s connection to EigenLayer is framed as a means of securing their network to enable mainstream adoption, with the relationship being viewed as dual-faceted:

“ For a lot of crypto native people, what EigenLayer is doing, they are quite familiar with. um but actually when it comes to mainstream adoption I think it's somewhat you know mainstream adoption doesn't occur um in a vacuum”

• EigenLayer provides the possibility for security while Blockless commits to simplicity, allowing users to make choices about Ethereum security:

“ I think that the relationship to mainstream adoption is a dual one i think that ultimately you know Eigen layer and restaking is somewhat complicated for your average person. However, you know, the idea of powering an application by using it is very simple”

5. Modular Network Nodes

• Blockless uses both its own network nodes and nodes from EigenLayer to provide diversity and robust support for applications:

“ It's really important to have the optionality there as well as the diversity for both the application developers, but also the end users when it comes to rock time.”

• Developers can choose off-chain processing or EigenLayer support based on their workload specifics, offering choices:

“People who want specific workloads on an off-chain through off-chain computation, and some people will want to use EigenLayer for other particular workloads. So it's ultimately, yes, it's all about providing the optionality”

6. Fault Tolerance and Security

• Blockless uses secure runtime with automatic failover for nodes that go offline, with additional nodes on standby for backup support:

“So ultimately we use a secure runtime and so the fault tolerance is pretty much we have an automatic failover. And so what that means is if any node goes offline when we run the initial check of who is online, a roll call, so to speak”

• Their system is viewed as secure by significant figures in the EigenLayer ecosystem after thorough strategy talks:

“And in the discussions that we've had with some of the big players in the EigenLayer ecosystem, especially around things like the security strategy and how safe an AVS is, they're pretty happy with us.”

7. Distributed Orchestration

• Blockless utilizes dynamic resource matching to optimize node selection, taking into account factors like geolocation and historic performance:

“It doesn't make sense if we're not looking at things like the geolocation of those operators. How far are they coming from the initial request and how far are they from the endpoint? How do we reduce latency?”

• It orchestrates efficient matching of workloads to nodes, benefiting users and application developers by offering choices between different verification tools and consensus algorithms per workload:

“So our orchestration is key. And when it comes as well to, you know, how these things are secured and the verification tools that we use or the consensus algorithms, this is also, you know, a key part of benefiting the retail users, but also the developers themselves. It's... primarily about ensuring that developers have the choice for each workload.”

8. Blockless Technology and Adoption

• Alan talked about AI networks using Blockless tech for inference. Additionally, mentioned the progress that has been made in both the Deepin and GameFi space:

“ We're already working with some AI networks that are leveraging Blockless and our technology for inference. We also have some other progress on both Deepin and the GameFi space.”

• The importance of showing how easy it will be to run a Blockless node and how intuitive it is for network-neutral apps to use their users' compute resources was explained:

“What's key is to promote the widespread adoption is ultimately explaining to people how simple it is going to be to run a node and how intuitive it is for network neutral applications to leverage their own users' compute resource.”

• Exciting partnerships to be announced soon, but details are kept under wraps pre-testnet and pre-mainnet:

“So we have some very exciting partnerships uh that we'll be announcing soon but yeah we're keeping our lips tightly sealed pre-testnet and pre-mainnet but yeah we'll we'll be announcing some fun things soon “

9. User and Operator Focus

• Alan stated they are prioritizing operator needs before bringing in applications because having no operators would be a big mistake:

“Adoption for us what's key is we're prioritizing the operator side first because if you prioritize getting all of the applications onboarded and there aren't any operators then it's a big oopsie”

• They need many people running nodes because it is effortless, which sets high goals for operator adoption on their network:

“For us, the metric really that we're looking at is, well, if it's so easy to run a node, then everyone should be running a node. So we have some pretty significant standards to meet when it comes to how many people will be running nodes on our network.”

10. Technical Capabilities and Developer Experience

• Liam mentioned that Wasm and Wasi allow running diverse programming languages in a web browser without needing different translators:

“It's a very small form factor runtime built tailored for the web browser. So it is designed to be running within the web browser. And... If anyone doesn't know about this, you have to download a specific kind of software or translator”

• Work is ongoing to integrate JavaScript and Node.js support using technical methods, even though native Wasm doesn't support them yet:

“For example, native wasm doesn't support JavaScript, but using some tricks under the hood and with the help of our very talented engineering team, we're able to. allow people to use vanilla JavaScript and Node.js for development.”