module aptos::a_new_era { /// Built for the next billion users. /// Onboard the world, one transaction at a time. public fun onboard_next_billion(): bool { ... return true; } /// Rethink value. Rebuild trust. Rewrite the rules. /// A new era of Aptos starts here. public fun enable_new_era(): bool { ... return true; } /// What’s next moves here. /// No hype. Just real progress. public fun launch_next_phase(): bool { ... return true; }}module aptos::doers { /// You build fast. Aptos keeps up. /// No downtime. No forks. Just forward momentum. public fun deploy_with_speed(): bool { ... return true; } /// Get help, not hype. /// Grants, tools, and support for real builders. public fun access_builder_support(): bool { ... return true; } /// Tools that work. Docs you can trust. /// Build with clarity and confidence. public fun use_production_tooling(): bool { ... return true; } /// Push to mainnet. Trust the infrastructure. /// Aptos is made for developers who ship. public fun push_to_mainnet(): bool { ... return true; }}module aptos::quietly_excellent { /// Quiet execution. Reliable outcomes. /// Aptos stays out of the way, so you can move forward. public fun verify_infrastructure_integrity(): bool { ... return true; } /// Break ground. Not trust. /// Built-in performance you can validate. public fun ensure_audit_readiness(): bool { ... return true; } /// Built to work. Designed to last. /// Engineered for stability, not spectacle. public fun maintain_network_stability(): bool { ... return true; }}module aptos::performance_first { /// Sub-second finality. Scales to millions of users. /// Designed for performance at any load. public fun handle_high_throughput(): bool { ... return true; } /// Built for scale. Maintains performance under pressure. /// Modular beneath. Seamless above. public fun scale_modularly(): bool { ... return true; } /// Upgrade without disruption. /// Keep building, even while evolving. public fun upgrade_without_downtime(): bool { ... return true; }}module aptos::ecosystem_energy { /// Move what matters, together. /// A growing network of builders and believers. public fun grow_with_ecosystem(): bool { ... return true; } /// Real support. Real partners. Shared momentum. /// An ecosystem that grows with you. public fun launch_with_partners(): bool { ... return true; } /// Cross-chain. Cross-border. Cross-culture. /// Connect across Web3, securely and simply. public fun connect_across_networks(): bool { ... return true; }}
As 2024 unfolds, a transformative trend takes center stage – the adoption of parallelized execution layers. At the forefront of parallelism is Aptos Labs’ acclaimed Block-STM engine.
As the efficiency and speed gains from this technology become increasingly evident with respect to traditional serial execution engines like the Ethereum Virtual Machine (EVM), parallelism is rapidly transitioning from a strategic advantage to an industry standard.
The evolution towards parallelised execution layers is not a passing industry exploration; it's a response to a longstanding challenge in blockchain technology. Maintaining a correct, logical order for the execution of every transaction in a block is crucial. Without this order, consensus breaks, and logic fails. Validators, after proposing and agreeing on block orders, face the challenge of executing transactions in a way that ensures all arrive at the same final state. To address this challenge, block proposers and validators have traditionally verified transactions sequentially, ensuring there are no dependencies. This sequential verification contributes to a bottleneck, resulting in slow transaction times as ordering correctly takes time in traditional blockchain designs.
Ecosystem developers responded by introducing Block-STM—a highly efficient, multi-threaded, in-memory parallel execution engine. Block-STM introduces an ingenious parallel execution engine that leverages Software Transactional Memory techniques with optimistic concurrency control. It adopts a pipelined and modular approach for the key stages of transaction processing that allow Block-STM to make late-stage execution decisions around gas, parallelism, and other objectives deterministically. This groundbreaking approach ensures that all transactions are eventually committed while avoiding the pitfalls of traditional STM libraries.
The implementation of Block-STM has set the standard for safe and simple parallel execution, igniting adoption in our ecosystem—and beyond—to transform the industry as we know it. For example, Polygon co-founder Sandeep Nailwal believes, "More and more parallelisation is coming faster than we all think," affirming the widespread adoption of parallel execution. It’s amazing to see peers like Polygon building in public to bring Block-STM to EVM. By carrying on the torch, parallelization is working its magic on EVM.
IYKYK
Polygon’s R&D team implemented parallelization (Block-STM) for EVM, and it has been live on Polygon PoS mainnet for ~4 months. 😊🙌
It is one of the primary reasons why POS chain has been processing >15mn txns a day on many days without any troubles. More and more
Georgios Konstantopoulos
@gakonst
2024 will be the year of the parallel evm - rooting for everyone working on this problem incl. monad/sei/polygon and other teams that I forget.
also excited for our own internal efforts there and pushing the boundaries on database design
Members of the Aptos ecosystem, like Econia, also emphasize that their on-chain order book would not have been possible on any other network. Specifically, step functions like parallel execution, optimistic concurrency and dynamic memory allocation have allowed Econia to usher a new era of open finance on Aptos—at scale and without the tradeoffs or limitations typically present on serial execution engines.
1/8 TL;DR Why did we build Econia on @Aptos_Network ? Because we couldn't build it anywhere else 🧵👇
Parallel execution +
Optimistic concurrency +
Dynamic memory allocation =
Econia, the web-scale order book DEX, offering atomic settlement & permissionless market making 🌐
The value of parallelism extends far beyond the Aptos ecosystem. For example, chains like Sei have implemented solutions based on Block-STM’s design that aim to improve concurrent execution performance. Monad similarly has validated the STM-based optimistic concurrency approach over different execution models, such as memory locks and actor models. As the performance gains from this technology become increasingly evident, Aptos Foundation is proud of the innovation first forged in the Aptos ecosystem. The growing adoption of parallel execution as an industry standard to date is testament to its merit and potential for Web3.
Block-STM's adaptability to varying workloads and its seamless integration into the Aptos blockchain position it as a cornerstone in blockchain design. Beyond being a parallel execution engine; it's a testament to Aptos ecosystem contributors' commitment to pushing the boundaries of Web3 technology. At the Aptos Foundation, we’re excited that the Aptos ecosystem has been able to leave mark after mark on blockchain design.
As Aptos Network is at the cutting edge of open-source innovation, the industry can anticipate continued breakthroughs in scalability and performance. The collaboration and community-driven ethos of Aptos contributors sets the stage for a pivotal 2024 in the continued development of parallelism.
Click here to learn more about BlockSTM by the Aptos ecosystem.
Sign up to receive industry news, helpful resources, exclusive access to upcoming events and
more.
1.
Aptos Foundation is committed to protecting and respecting your privacy, and we'll
only use your personal information to administer your account and to provide the products
and services you requested from us. From time to time, we would like to contact you about
our products and services, as well as other content that may be of interest to you. If you
consent to us contacting you for this purpose, please tick the box to say how you would
like us to contact you.
2.
You can unsubscribe from these communications at any time. For more information on how to
unsubscribe, our privacy practices, and how we are committed to protecting and respecting
your privacy, please review our Privacy Policy.
3.
By clicking the submit button, you consent to allow Aptos Foundation to store and process
the personal information submitted above to provide you the content requested.
public fun ignite_chain_reaction(): bool { // Spark innovation // Fuel momentum // Chain it with Aptos return true;}public fun deploy_with_confidence(): bool { // Test it // Ship it // Trust Aptos to scale it return true;}public fun empower_creators_on_aptos(): bool { // Tools for builders // Freedom for creators // Power by Aptos return true;}public fun redefine_possibilities(): bool { // Break limits // Build freely // Launch globally on Aptos return true;}public fun grow_without_limits(): bool { // No ceilings // No bottlenecks // Just Aptos performance return true;}public fun connect_across_chains(): bool { // Interoperability // Security // Aptos at the core return true;}public fun code_scale_repeat(): bool { // Code smart // Scale fast // Repeat with Aptos return true;}public fun onboard_the_next_billion(): bool { // Real users // Real speed // Onboard the world with Aptos return true;}public fun ignite_chain_reaction(): bool { // Spark innovation // Fuel momentum // Chain it with Aptos return true;}public fun deploy_with_confidence(): bool { // Test it // Ship it // Trust Aptos to scale it return true;}public fun empower_creators_on_aptos(): bool { // Tools for builders // Freedom for creators // Power by Aptos return true;}public fun redefine_possibilities(): bool { // Break limits // Build freely // Launch globally on Aptos return true;}public fun grow_without_limits(): bool { // No ceilings // No bottlenecks // Just Aptos performance return true;}public fun connect_across_chains(): bool { // Interoperability // Security // Aptos at the core return true;}
public fun ignite_chain_reaction(): bool { // Spark innovation // Fuel momentum // Chain it with Aptos return true;}public fun deploy_with_confidence(): bool { // Test it // Ship it // Trust Aptos to scale it return true;}public fun empower_creators_on_aptos(): bool { // Tools for builders // Freedom for creators // Power by Aptos return true;}
public fun ignite_chain_reaction(): bool { // Spark innovation // Fuel momentum // Chain it with Aptos return true;}public fun deploy_with_confidence(): bool { // Test it // Ship it // Trust Aptos to scale it return true;}public fun empower_creators_on_aptos(): bool { // Tools for builders // Freedom for creators // Power by Aptos return true;}public fun redefine_possibilities(): bool { // Break limits // Build freely // Launch globally on Aptos return true;}public fun grow_without_limits(): bool { // No ceilings // No bottlenecks // Just Aptos performance return true;}public fun connect_across_chains(): bool { // Interoperability // Security // Aptos at the core return true;}public fun code_scale_repeat(): bool { // Code smart // Scale fast // Repeat with Aptos return true;}public fun onboard_the_next_billion(): bool { // Real users // Real speed // Onboard the world with Aptos return true;}public fun ignite_chain_reaction(): bool { // Spark innovation // Fuel momentum // Chain it with Aptos return true;}public fun deploy_with_confidence(): bool { // Test it // Ship it // Trust Aptos to scale it return true;}public fun empower_creators_on_aptos(): bool { // Tools for builders // Freedom for creators // Power by Aptos return true;}public fun redefine_possibilities(): bool { // Break limits // Build freely // Launch globally on Aptos return true;}public fun grow_without_limits(): bool { // No ceilings // No bottlenecks // Just Aptos performance return true;}public fun connect_across_chains(): bool { // Interoperability // Security // Aptos at the core return true;}
