DeFi By Design EP#117: Why Data Availability Is The Missing Piece To The Modular Scaling Puzzle

Name: DeFi By Design EP#117: Why Data Availability Is The Missing Piece To The Modular Scaling Puzzle
Uploaded: 2023-12-28T18:06:31.000Z
Duration: 2 h 16 min 47 s

Introduction and Disclaimer

The hosts welcome the viewers back to the podcast and emphasize that nothing discussed should be considered financial advice. They encourage viewers to like, share, and subscribe to support their educational content in the DeFi space.

Purpose of the Podcast

The hosts explain that the podcast aims to educate, empower, and enrich viewers by discussing blockchain and cryptocurrency topics. They introduce episode 117 of the podcast.

Lowering Transaction Costs on Rollup

The hosts express excitement about reducing transaction costs on rollups. They mention meeting someone named pbal in Istanbul and discuss their positive experiences at a conference.

Settling In After Conferences

The hosts talk about settling in after attending conferences, mentioning how it can be a whirlwind experience. They express enthusiasm for learning about modularity and pushing forward on various fronts.

Understanding Modularity in Blockchain

The hosts discuss the concept of modularity in blockchain technology. They explain that different technologies are stacked on top of each other, with data flowing down to the base level. Modularity allows for flexibility in connecting different components for various applications or blockchains.

Unpacking Components with Modularity

The hosts elaborate on how modularity breaks down components and distributes them throughout space. This approach enables customization and optimization of individual pieces within an application-specific rollup or blockchain.

Challenges with Monolithic Layers

Section Overview (in the language of the transcript): The hosts discuss the limitations of a monolithic layer where all activities are consolidated. They explain that making changes to one part affects the entire layer, making it difficult to optimize specific aspects without impacting everything else.

Shifting Mental Model with Rollups

The hosts introduce the rollup-centric roadmap, which allows for implementing components in a modular manner. They explain that this shift in mental model enables efficient execution and ordering on-chain while minimizing on-chain demands.

Minimal On-Chain Demands with Rollups

The hosts highlight how rollups reduce on-chain demands by handling most execution and ordering off-chain. They mention that the base layer primarily focuses on providing security and minimal functions like data availability.

Customization and Optimization with Rollups

The hosts emphasize that rollups enable customization and optimization of different components based on specific requirements. This includes custom states, transaction structures, storage layouts, and more.

Evolution from Monolithic to Modular Approach

Section Overview (in the language of the transcript): The hosts compare the shift towards modularity in blockchain technology to starting with a single codebase and gradually optimizing it by breaking it into functions. They highlight how this approach leads to overall better code quality and efficiency.

Increasing Interest in Modularity

The hosts reflect on their initial confusion about modularity but acknowledge its growing importance in the crypto world. They mention receiving many questions about what modularity means.

Timestamps have been associated with relevant sections as per the provided transcript.

# The Modular Future of Blockchain

In this section, the speaker discusses the future of blockchain technology and how it will evolve in the next six, twelve, and eighteen months. They also highlight the differences between the current state of blockchain technology and what it will look like in the modular future.

The Unsustainability of High Transaction Fees

As more use cases and applications emerge, it becomes unsustainable to have high transaction fees on a specific blockchain.

The Ethereum ecosystem experiences extensive price activity that makes it difficult to use the chain when there is a lot of activity.

Transaction fees can spike up to hundreds of dollars, which is not sustainable for widespread adoption.

Rollup Centric Future

To make blockchains mainstream, execution needs to be taken off-chain through rollups.

Users will receive sub-confirmations of acceptance for their transactions.

Batches of transactions will be sent to settlement layers while proofs hit the settlement layers.

Amortization of Costs and Improved User Experience

Different layers have different block times and finalities, affecting user experience.

Users can choose different levels of guarantees depending on their needs.

Some rollup solutions offer millisecond transaction confirmations for better user experience.

For large fund transfers, subjective or objective finality may be required.

Customized Experiences Based on Use Cases

The roadmap aims to provide different experiences based on specific use cases.

Developers can optimize and customize applications based on different layer constructions.

# Lower Transaction Costs with Layer 2 Solutions

This section focuses on layer 2 solutions that aim to reduce transaction costs significantly compared to current blockchain networks. The speaker mentions a conversation with Neil founder at Epic e INF and discusses the potential impact of layer 2 solutions on transaction costs.

Significant Reduction in Transaction Costs

Layer 2 solutions can make transactions up to 100 times cheaper compared to current costs.

The founder of Neil confirms that layer 2 solutions will significantly lower transaction costs.

Pre-Confirmation Speed with Layer 2 Solutions

Layer 2 solutions can potentially speed up pre-confirmations of transactions.

The time for pre-confirmations may vary depending on the type of confirmation mechanism used.

# Impact of Layer 2 Solutions on Confirmation Times

This section explores how layer 2 solutions can affect confirmation times for transactions. The speaker explains that the confirmation time depends on various factors, such as using a centralized sequencer or a decentralized network aggregator (DNA).

Confirmation Time with Centralized Sequencer

If a centralized sequencer is used, the confirmation time remains unchanged.

Transactions are confirmed by the sequencer, maintaining the same user experience.

Confirmation Time with Decentralized Network Aggregator (DNA)

Using a DNA for subjective finality may result in shorter or longer confirmation times.

Shorter times may occur when smaller batches are sent to Ethereum due to limited block capacity.

Longer times may occur when using base rup constructions without a sequence, relying solely on DNA processing.

Potential for Faster Confirmations with Shared Sequences

Shared sequences offer faster confirmations for cross-rollup interactions compared to other configurations.

Supplementary constructions may further enhance this capability.

The transcript provided does not include timestamps beyond this point.

The Upside of Using Data Availability Layers

This section discusses the benefits of using data availability (DA) layers in blockchain systems, such as abstracting away edge cases, improving security and decentralization, and reducing costs.

Benefits of DA Layers

DA layers abstract away edge cases and allow users to focus on the main functionalities.

DA layers help find a balance between security and decentralization while lowering costs.

Modular rollups like Solana offer faster confirmation times (e.g., 200 milliseconds), providing a great user experience.

Every construction has trade-offs, so if users are satisfied with a certain experience, it should be appreciated.

More use cases are needed in the blockchain ecosystem, and if platforms like Solana can bring new use cases, they should be embraced.

User Verifiability and Data Sampling

This section focuses on user verifiability in blockchain transactions and the importance of data availability for end users. It also mentions efforts towards achieving verifiability in the Ethereum community.

Importance of User Verifiability

End users should be able to verify whether their transactions were done correctly.

Data sampling allows users to verify transaction validity themselves instead of relying solely on the blockchain.

Users can receive proofs of execution and perform sampling to ensure transaction accuracy.

Achieving end user verifiability is a key goal in building decentralized applications (DApps).

Trade-offs: Verifiability vs. Faster Confirmation Times

This section discusses the trade-offs between verifiability and faster confirmation times in blockchain systems. It also mentions the potential for smaller block confirmation times in the future.

Verifiability vs. Faster Confirmation Times

Builders make trade-offs between verifiability and faster confirmation times.

Sequencers can provide very fast confirmations, making it feel like a web API call.

The sustainability of growing a chain while maintaining faster confirmation times is a consideration.

EVM-centric rollups with complex state transitions may have longer processing times.

Custom state transitions with lightweight app rops can offer faster processing times.

Builders prioritize different aspects based on their specific rollup designs.

User Verifiability and Data Availability

This section explores the importance of user verifiability and data availability from a first principles perspective, drawing parallels to Satoshi's white paper.

Importance of User Verifiability and Data Availability

User verifiability is crucial, as seen in the phrase "not your keys, not your coins."

Each user processes their own data, contributing to the native experience of running a node.

Enabling user verifiability allows users to trust their own transactions' data integrity.

Conclusion

The transcript covers various topics related to using data availability layers in blockchain systems, including the benefits of abstraction, trade-offs between security and decentralization, user verifiability, and the importance of data availability. It emphasizes finding a balance between security and efficiency while ensuring end users can verify their transactions accurately.

Verifiability and Data Availability in Blockchain

In this section, the speaker discusses the importance of verifiability and data availability in blockchain systems. They explain how running a full node allows users to verify if their transactions were processed correctly. They also highlight the concept of social consensus and how light clients can verify data availability without relying solely on validators.

Importance of Verifiability

Running a full node is necessary to know if transactions were processed correctly.

Social consensus ensures that even if a wrong transaction is processed, a full node will reject it.

Data Availability for Light Clients

The focus of execution-based chains like Ethereum is data availability.

Light clients should be able to verify data availability without relying solely on validators.

Light clients can perform cheap data sampling to check for correctness and ensure data availability.

Power of Cryptographically Driven Chains

Cryptographically driven chains shift from relying on crypto-economics to cryptographic verification.

Users can now verify both execution correctness and data availability quickly using ZK proofs.

Quick Verification with ZK Proofs

This section focuses on the efficiency of verifying ZK proofs in blockchain systems. The speaker explains that while creating the proof itself may be difficult, verifying it is quick and easy.

Efficiency of ZK Proofs

ZK proofs are difficult to create but easy to verify, making them ideal for quick verification processes.

Verifying a ZK proof takes milliseconds, providing assurance about correct execution and data availability.

Creating Proofs of Correct Execution

The speaker discusses the process of creating proofs of correct execution in blockchain systems. They explain that after executing a task, a proof is generated and provided to the verifier for verification.

Creating Proofs

After executing a task, a proof of correct execution is created using circuits or representations.

The verifier can use the succinct proof to verify the complete execution.

Data Availability Sampling

This section explores the concept of data availability sampling in blockchain systems. The speaker explains how data can be efficiently sampled and encoded to prevent hiding parts of it.

Efficiency of Data Availability Sampling

Data availability sampling allows efficient sampling and encoding of data.

Redundancy in encoded data makes it difficult to hide parts, ensuring data availability.

Conclusion

Blockchain systems require verifiability and data availability for secure and reliable operations. Running full nodes enables users to verify transaction correctness, while light clients can independently verify data availability through cheap sampling methods. Cryptographically driven chains shift focus from relying on crypto-economics to cryptographic verification using ZK proofs, which are efficient to verify. Proofs of correct execution are created after tasks are executed, allowing verifiers to ensure complete execution accuracy. Data availability sampling ensures efficient sampling and encoding, preventing the hiding of crucial information within the blockchain system.

Timestamps may vary slightly due to differences in transcription speed or video editing cuts

One-dimensional vs Two-dimensional Data Availability

The discussion focuses on the construction of data availability blocks and the tradeoffs involved in ensuring data security. Different constructions, such as commitment-based schemes, are mentioned.

Construction Tradeoffs

In commitment-based schemes, tradeoffs include the time taken to create a commitment, generate an opening, and verify an opening.

Openings refer to cryptographic proofs that a small section of data belongs to a previously given commitment.

Tradeoffs also involve determining how many samples are needed to verify if the original data was available.

Other constructions like fraud-proof secured systems have tradeoffs related to the efficiency of verifying fraud proofs.

Verifiability and Design Choices

The level of verifiability and proof sizes are important design choices in constructing data availability blocks.

The balance between offloading verification to end users and the block production engine is crucial.

Different use cases may require different levels of security and sophistication in their data availability systems.

Designing Data Availability for Efficiency

The discussion explores how the size, type, and modularity of data affect cost reduction and scalability. It emphasizes the importance of finding a balance between security and cost-effectiveness.

Cost Reduction Factors

The amount of data should be manageable for light clients to operate efficiently.

Cryptographic proofs help reduce economic costs by providing evidence that a blob of data is accurate without extensive verification.

Modular blockchain approaches aim to mitigate traditional trade-offs by using cryptographic proofs and reducing costs.

Reshaping Trade-offs

The goal is to find the right formula that combines security and cost-effectiveness.

Ethereum's shift towards a data-centric roadmap reflects the need for scalability in handling data availability.

Many base layers are transitioning to become data availability networks (DANs) to scale effectively.

Compute does not scale similarly to data availability, making DANs more efficient for handling large-scale computations.

Optimizing Systems for Specific Jobs

The discussion clarifies that cost optimizations come from creating systems optimized for specific tasks rather than simply cloning existing platforms. It emphasizes the importance of understanding the differences between various blockchain roadmaps.

Cost Optimization Factors

Optimized systems designed for specific jobs tend to be more performant and cost-effective.

Ethereum initially focused on computation but is now shifting towards a data-centric roadmap due to inefficiencies in handling data availability.

Comparing costs between different systems should consider their optimization for specific tasks, not just activity levels.

Ethereum's Transition Towards Data Availability Networks (DAN)

The discussion highlights how Ethereum aims to become a DNA and how other base layers are also moving towards becoming DANs. It explains why scalability requires a focus on data availability.

Scalability through Data Availability

Base layers need to transition into DANs to achieve scalability since compute does not scale as efficiently as data availability.

The trend of base layers becoming DANs is driven by the need for scalable computation and efficient handling of data.

Cost Reduction and Efficiency in Data Availability

The discussion emphasizes that cost reduction and efficiency in data availability come from optimized systems designed for specific tasks. It clarifies the relationship between activity levels, costs, and optimization.

Optimized Systems for Cost Reduction

Optimized systems designed for specific tasks are more efficient at handling data availability.

Comparing costs between different systems should consider their optimization for specific tasks rather than just activity levels.

The transcript provided does not include any timestamps beyond this point.

Scaling Challenges and Validator Resources

The speaker discusses the challenges of scaling blockchain networks, particularly in relation to the resources required by validators.

Glocks and Computational Resources

Validators require significant computational resources to handle increased transaction processing.

Doubling the space for computation would require double the amount of resources for validators.

Some chains have highly resource-intensive validators to achieve high TPS (transactions per second).

Increasing Block Size without Doubling Validator Cost

DApps can increase block size without doubling the cost for validators.

Verifiability depends on the number of light clients and utility.

As more people use a chain, more light clients run, allowing for larger blocks.

This is a novel approach not seen in monolithic chains.

Transitioning to Data-Focused Chains

The speaker explains how data-focused chains can scale effectively without incurring excessive costs on validators.

Utility and Light Clients

The scalability of data-focused chains relies on increasing utility and attracting more users.

More utility leads to more light clients running, enabling larger blocks.

This approach differs from computational-focused chains like Ethereum.

Transitioning from Computational Focus to Data Focus

The speaker discusses the transition from Ethereum's computational-heavy roadmap to a data-focused roadmap and potential implications.

Understanding the Transition

Ethereum is transitioning from a computational-heavy roadmap to a data-focused roadmap.

This shift may be driven by fear or concerns about competition from modular solutions.

Ethereum's role as a settlement layer is hard to dispute, but alternative VMs and DApps may pose challenges.

Potential Risks for Ethereum's Value Proposition

The speaker explores potential risks associated with Ethereum's value proposition amidst the rise of modular solutions.

Modular Solutions and Ethereum's Dominance

The dominance of Ethereum's EVM (Ethereum Virtual Machine) is currently strong.

However, there are emerging use cases that require functionalities beyond what the EVM can offer.

Alternative VMs and DApps are gaining traction, potentially challenging Ethereum's dominance.

Evaluating the Future of Ethereum

The speaker presents two perspectives on the future of Ethereum in light of modular solutions.

Two Perspectives

One perspective suggests that Ethereum's dominance will be broken as new solutions emerge.

The other perspective emphasizes Ethereum's role as a settlement layer and its potential to become ultrasound money.

While there may be risks to Ethereum's execution layer, innovation and competition are positive factors for the ecosystem.

Ethereum's Position in the Future

The speaker discusses how Ethereum is positioned in terms of being a dominant settlement layer and adapting to a data-centric roadmap.

Settlement Layer Dominance

Despite the transition to a data-centric roadmap, Ethereum is expected to remain a dominant settlement layer.

Upcoming proposals like Eth2.0 and sharding support this roadmap.

While there may be challenges at the execution layer, it does not jeopardize Ethereum's position as a value-based platform.

Embracing Innovation and New Solutions

The speaker highlights the importance of embracing innovation and new solutions within the blockchain ecosystem.

Benefits of Innovation

Innovations bring new possibilities and advancements to the blockchain space.

Different VMs, DApps, and approaches contribute to overall progress.

While there may be risks associated with change, they also present opportunities for growth.

Bitcoin and Ethereum: Understanding the Value Proposition

In this section, the speaker discusses the value proposition of Bitcoin and Ethereum, highlighting their distinctiveness and novel features. They also emphasize the importance of understanding the evolving technological landscape and the impact of corruption on different blockchain constructions.

The Significance of Bitcoin and Ethereum

Bitcoin's paper introduced a distinctive and novel approach to utilizing blockchain technology.

Ethereum demonstrated that blockchain can be used for much more than just cryptocurrencies.

Understanding Technological Changes

Corruption has a significant impact on Bitcoin and Ethereum.

Not all blockchain constructions are equally affected by corruption.

Ensuring protocol guarantees are incentive-compatible is crucial for maintaining a secure system.

Exploring the Value Proposition in Blockchain Stack

The speaker shifts focus to examining the value of "crel" (possibly referring to "CRL," Certificate Revocation List) in the system.

The typical stack includes databases (daBMS), settlement layers, sequencers, etc.

Sequencers play a valuable role in capturing market energy but may not require bootstrapping.

Provers need incentives to ensure objective alignment within each module.

Clientside proving may become more prevalent in 2025, shifting user self-sustainability.

Transaction Costs and Revenue Streams

Sequencers capture significant revenue from the market but contribute back to the protocol.

DN (possibly referring to decentralized network or distributed ledger network?) involves transaction costs and provides security.

Users pay fees to operators and DN for security and transaction processing.

Provers can be incentivized directly by users or through operators, with various reward mechanisms.

Conclusion

The discussed components in the blockchain stack have well-defined values and revenue streams.

Understanding the value proposition of each module is crucial for their sustainability and success.

The Future of Web3 and Subsidized User Transactions

In this section, the speaker discusses different models for subsidizing user transactions in Web3. They mention the use of inferior RPCs and how some services may subsidize transaction costs to provide a better user experience.

Subsidizing User Transactions

Some models in Web3 involve subsidizing the cost of user transactions.

Inferior RPCs are being used, which means that the cost is being subsidized.

Services may choose to subsidize user transactions themselves instead of charging fees.

The goal is to provide a first-class web experience without requiring users to have wallets or pay transaction fees.

Implications of Subsidized Transactions

In this section, the speaker discusses the implications of subsidized transactions and mentions OP retracting grants from sequencer fee boys. They also confirm that when referring to operators, they mean the execution layer in the stack.

Implications of Subsidized Transactions

Users can enjoy subsidized transactions while they last.

OP retracting grants from sequencer fee boys will no longer be available if transactions are subsidized.

Operators refer to the execution layer in the stack where value is approved and revenue is generated.

Each part of the stack generates revenue based on user activity.

Solving the RPC Problem in Web3

In this section, there is a discussion about solving the RPC problem in Web3. The speaker mentions indexing 500 rollups and who would be responsible for paying for it.

Challenges with RPCs

There are challenges with indexing 500 rollups and keeping track of all PCS (Protocol Change Sets).

It's difficult for one entity to handle interactions with thousands of chains and keep track of their status.

The speaker questions who is solving the RPC problem for all these rollups and who is paying for it.

Efforts to Solve the RPC Problem

In this section, the speaker discusses their efforts to solve the RPC problem in Web3. They mention making light clients first-class citizens, reducing reliance on RPCs, and creating a network of light clients for security and availability.

Solving the RPC Problem

Efforts are being made to make light clients first-class citizens without relying heavily on RPCs.

The goal is to minimize reliance on RPCs by utilizing peer-to-peer layers and populating DHD (Decentralized Hash Database) with necessary proofs.

Plans include mitigating reliance on RPCs by using them as a backup only when necessary.

On the execution layer, efforts are focused on creating a composable ecosystem around DNA (Decentralized Network Architecture) for security.

Enhancing User Experience in Web3

In this section, the speaker discusses enhancing user experience in Web3 by minimizing user interactions with multiple applications. They use an example of how Amazon handles payment processing through intermediaries.

Enhancing User Experience

The goal is to ensure that users have a seamless experience with minimal interaction with various applications.

An example is given where Amazon uses payment aggregators and intermediaries like banks to handle payment processing without direct user involvement.

The focus is on keeping user interactions within a smaller fraction of the chain while maintaining security.

This summary covers key points from the transcript but may not include every detail mentioned in the video.

Chain-to-Chain Level Interactions and Application Specific Chains

The speaker discusses the concept of chain-to-chain level interactions and application-specific chains in the context of their world view.

Chain-to-Chain Level Interactions

Chain-to-chain level interactions refer to the communication and interaction between different blockchain networks.

These interactions can be specific to certain applications, such as payment chains or NFT chains.

In their world view, application-specific chains make indexing less challenging because they provide relevant information for specific use cases.

Indexing becomes necessary when filtering out irrelevant information from a shared team is required.

Application-Specific Chains

In a scenario where each chain serves only one application, indexing becomes less important.

The speaker mentions that they are working on features that allow users to interact with specific chains based on their needs (e.g., checking account balance on one chain and interacting with another chain for NFTs).

The goal is to create an ecosystem where users can focus on their intent (e.g., purchasing a product) while the system takes care of the necessary actions across multiple chains.

Asynchronous Message Passing and Indexing

The speaker explains how asynchronous message passing and indexing play a role in their rollup-centric ecosystem.

Indexing in Application-Specific Chains

In an ecosystem with application-specific chains, indexing becomes less crucial as it is focused on specific use cases rather than general information.

Filtering relevant information becomes easier due to the targeted nature of these chains.

Asynchronous Message Passing

Asynchronous message passing is a key component of their ecosystem.

It allows for efficient communication between different chains by passing messages asynchronously.

This approach enables users to specify their intent without needing to know all the details about how it will be executed across various chains.

Verifiability and Promises

The speaker mentions that the system they are building is based on verifiability.

Messages and promises play a crucial role in resolving actions across chains.

They draw inspiration from the web's asynchronous message request model, where promises and resolutions are used extensively.

Intent-Based Interactions and Chain Specialization

The speaker discusses intent-based interactions and chain specialization in their ecosystem.

Intent-Based Interactions

Users will only need to specify their intent, such as wanting to purchase an asset or make a payment.

The system will handle the necessary steps by finding the appropriate chains for each action (e.g., finding the chain with the lowest price for an asset).

Chain Specialization

Different chains can specialize in serving specific purposes or applications.

Users do not need to be aware of all the details about these specialized chains; they only need to know which chain serves their intended purpose.

Rollup-Centric Ecosystem and Interoperability

The speaker explains how their rollup-centric ecosystem aims to achieve interoperability through asynchronous message passing.

Rollup-Centric Ecosystem

The goal is to create a rollup-centric ecosystem that focuses on efficient communication between different chains.

Asynchronous message passing plays a vital role in achieving this goal.

Interoperability through Asynchronous Message Passing

Asynchronous message passing enables interoperability by allowing messages to pass between different chains.

Unlike value transfer, which is currently the primary use case for cross-chain communication, this approach allows for generic message passing across chains.

Lessons from Web2 and Trust Minimization

The speaker draws lessons from Web2 regarding asynchronous messaging and trust minimization.

Lessons from Web2

The speaker acknowledges that there are lessons to be learned from Web2, despite potential criticisms of its design decisions.

Asynchronous messaging and promises have been successfully implemented in Web2 applications, such as Amazon's order processing system.

Trust Minimization

The speaker emphasizes that their ecosystem aims to minimize the need for trust.

Verifiability is a key principle, allowing users to rely on cryptographic proofs rather than trusting centralized entities.

Unlike traditional systems where trust is placed in specific entities, their system focuses on verifiability and cryptographic guarantees.

Message Passing and Security Tradeoffs

The speaker discusses message passing and security tradeoffs when crossing boundaries within the ecosystem.

Message Passing and Solving

Message passing plays a crucial role in the ecosystem, allowing for communication between different chains.

Chains can solve specific tasks based on the messages they receive.

Security Tradeoffs

Crossing boundaries within the ecosystem introduces new security tradeoffs.

When crossing these boundaries, users must rely on the cryptoeconomic security provided by other chains.

While there are some similarities to bridges between chains, they aim for lower security assumptions compared to traditional bridges.

Sovereign Interoperability and Mainnet Plans

The speaker mentions sovereign interoperability and provides information about their mainnet plans.

Sovereign Interoperability

Sovereign interoperability is mentioned as a concept that will be discussed more in the future.

It likely refers to achieving interoperability while maintaining independence and control over individual chains or applications.

Mainnet Plans

The incentivized test net is currently running as a final round of stress testing before mainnet launch.

The mainnet launch is planned for Q1 next year (around the corner).

Users are invited to participate in challenges related to different components of the ecosystem, including balance transfers.

Launching Menet

In this section, the speaker discusses the upcoming launch of Menet and expresses gratitude for the time spent on the project.

Launching Menet

The toughest part of the project has been completed, and they are very close to launching Menet.

The target date for the launch is not mentioned explicitly but is referred to as "menet qy1."

They anticipate launching Menet unless any significant issues arise during testing.

The overall plan is progressing well, and they express gratitude for the time spent on development.

The speaker thanks Braal for their contribution to the project and mentions that working on modular weeds has been enjoyable.

Timestamps are not provided in this transcript.