Difference between revisions of "Aptos (APT)"
m (→Funding) |
|||
Line 34: | Line 34: | ||
===How it works=== | ===How it works=== | ||
*From this (critical) Twitter [https://twitter.com/AlwaysKMxbt/status/1547212855379779590 thread] (13-7-2022): | *From this (critical) [[Twitter]] [https://twitter.com/AlwaysKMxbt/status/1547212855379779590 thread] (13-7-2022): | ||
''"How is it safe ser? As discussed on the [https://twitter.com/AlwaysKMxbt/status/1547212871733415937?s=20&t=lBo8V2uwZqg2q38bXWv_rQ thread above], Move enables [[Smart Contract (SC)|smart contracts]] interaction with validators to be deterministic, hermetic ([[state]] change is predictable; untainted) and metered (protection against [[Denial-of-Service attack (DoS attack)|DOS attacks]]). All can be verified by Move Prover. Aptos decouples the codependent execution and consensus layers through a parallel execution engine which synchronize eventually. The parallel execution layer leverages the design of Block-STM's that executes transactions optimistically then detects and manages conflicts before synchronizing and changing the state.'' | ''"How is it safe ser? As discussed on the [https://twitter.com/AlwaysKMxbt/status/1547212871733415937?s=20&t=lBo8V2uwZqg2q38bXWv_rQ thread above], Move enables [[Smart Contract (SC)|smart contracts]] interaction with validators to be deterministic, hermetic ([[state]] change is predictable; untainted) and metered (protection against [[Denial-of-Service attack (DoS attack)|DOS attacks]]). All can be verified by Move Prover. Aptos decouples the codependent execution and consensus layers through a parallel execution engine which synchronize eventually. The parallel execution layer leverages the design of [[Block]]-STM's that executes transactions optimistically then detects and manages conflicts before synchronizing and changing the state.'' | ||
''But ser, what about the detected conflicts? They are picked up by at most 1 thread in the parallel execution engine and re-executed based on the execution queue, and re-validated through a queue along with its subsequent txs. Abstractions are separated from trivial executions and validations. This is all possible due to preset orders with indexes that map transactions throughout the execution and validation cycle. Block-STM algorithms handles seamless operations.'' | ''But ser, what about the detected conflicts? They are picked up by at most 1 thread in the parallel execution engine and re-executed based on the execution queue, and re-validated through a queue along with its subsequent txs. Abstractions are separated from trivial executions and validations. This is all possible due to preset orders with indexes that map transactions throughout the execution and validation cycle. Block-STM [[algorithms]] handles seamless operations.'' | ||
''With 32 threads working in parallel through the Block-STM design, complemented by its robust state synchronization mechanisms to reduce latency, Aptos would be able to boast up to 100k+ tps with sub-second finality."'' | ''With 32 threads working in parallel through [[the Block]]-STM design, complemented by its robust state synchronization mechanisms to reduce latency, Aptos would be able to boast up to 100k+ tps with sub-second finality."'' | ||
*From their [https://medium.com/aptoslabs/expanding-the-aptos-community-38c5b18a84b7 blog] (15-3-2022): | *From their [https://medium.com/aptoslabs/expanding-the-aptos-community-38c5b18a84b7 blog] (15-3-2022): | ||
Line 56: | Line 56: | ||
==Their Other Projects== | ==Their Other Projects== | ||
==Roadmap== | ==Roadmap== | ||
*Can be found [Insert link here]. | *Can be found [Insert [[LINK|link]] here]. | ||
==Usage== | ==Usage== | ||
===Projects that use or built on it=== | ===Projects that use or built on it=== | ||
* [[CoinDesk (DESK)|Coindesk]] [https://www.coindesk.com/layer2/2022/08/04/master-of-anons-how-a-crypto-developer-faked-a-defi-ecosystem/ published] an article (8-2022) about [[Ian Macalinao]] wanting to go to Aptos and potentially redo his [[Solana (SOL)|Solana]] [[Total Value Locked (TVL)|TVL]] scheme. So be advised. | |||
==Competition== | ==Competition== | ||
* [[Layer One|Layer 1]] blockchains and [[Sui (SUI)|Sui]] in particular. From this Sui & Aptos [https://twitter.com/cryptoalvatar/status/1551878534926401537?s=21&t=UkAbX2-e_7BKPxU7tJzQFw comparison] thread (26-7-2022): | * [[Layer One|Layer 1]] [[blockchains]] and [[Sui (SUI)|Sui]] in particular. From this Sui & Aptos [https://twitter.com/cryptoalvatar/status/1551878534926401537?s=21&t=UkAbX2-e_7BKPxU7tJzQFw comparison] thread (26-7-2022): | ||
''"Sui's version of Move has introduced some modifications, the most visible being the ownership API. It is more clean and it exposes the blockchain design more clearly IMO. But the libraries feel a little bit less developed than Aptos'. Aptos uses BlockSTM, which is an evolution of the high-performance HotStuff algorithm, and introduces parallelization by dynamically detecting dependencies and scheduling execution tasks (taking its inspiration from Software Transactional Memory). It's hard to tell which one will perform better in practice, but my bet is with Sui. Aptos has done already a very good job at optimizing their current design, whereas Sui seems to have more room. The two-paths of byzantine agreement give Sui an edge as well.'' | ''"Sui's version of Move has introduced some modifications, the most visible being the ownership API. It is more clean and it exposes the blockchain design more clearly IMO. But the libraries feel a little bit less developed than Aptos'. Aptos uses BlockSTM, which is an [[evolution]] of the high-performance HotStuff algorithm, and introduces parallelization by dynamically detecting dependencies and scheduling execution tasks (taking its inspiration from Software Transactional Memory). It's hard to tell which one will perform better in practice, but my bet is with Sui. Aptos has done already a very good job at optimizing their current design, whereas Sui seems to have more room. The two-paths of byzantine agreement give Sui an edge as well.'' | ||
''Sui tackles [<nowiki/>[[state]] bloat] via efficient [[sharding]] of the store, focusing on horizontally scaling the resources. Aptos on the other hand puts more emphasis on supporting heterogeneous validators (contrained [[CPU]] and/or constrained storage). I like Sui's take on this.'' | ''Sui tackles [<nowiki/>[[state]] bloat] via efficient [[sharding]] of the store, focusing on horizontally scaling the resources. Aptos on the other hand puts more emphasis on supporting heterogeneous validators (contrained [[CPU]] and/or constrained storage). I like Sui's take on this.'' | ||
Line 76: | Line 79: | ||
*AptosLabs, [https://twitter.com/AlwaysKMxbt/status/1547212857984421889?s=20&t=lBo8V2uwZqg2q38bXWv_rQ used to] work on [[Diem]]. | *AptosLabs, [https://twitter.com/AlwaysKMxbt/status/1547212857984421889?s=20&t=lBo8V2uwZqg2q38bXWv_rQ used to] work on [[Diem]]. | ||
*"25+ members" ([https://medium.com/aptoslabs/expanding-the-aptos-community-38c5b18a84b7 15-3-2022]) | *"25+ members" ([https://medium.com/aptoslabs/expanding-the-aptos-community-38c5b18a84b7 15-3-2022]) | ||
*[https://twitter.com/milesdeutscher/status/1552281919718445057?s=20&t=rxmFNledc_78Pd_TP_TJ7A Took] the Head of Marketing from Solana and made it Director of Ecosystem at Aptos (19-7-2022). | *[https://twitter.com/milesdeutscher/status/1552281919718445057?s=20&t=rxmFNledc_78Pd_TP_TJ7A Took] the Head of Marketing from [[Solana]] and made it Director of Ecosystem at Aptos (19-7-2022). | ||
===Funding=== | ===Funding=== | ||
Revision as of 04:03, 8 August 2022
Aptos is a L1 blockchain built with Move, by the old Diem team
Basics
- Based in:
- Started in / Announced on: 24-2-2022 announced but started 'in the past few months' before it but also mentions having worked on their BFT engine for 3 years already. This is due to the team having worked on Diem before.
- Testnet release: 15-3-2022devnet; "Later in Q2, there will be an incentivized testnet to help scale the network and stress test it as it marches toward mainnet."
- Mainnet release: "We expect Mainnet to occur in Q3 2022" (15-3-2022)
History
- Team comes from Diem, but moved on to build Aptos after government issues arose.
Audits & Exploits
- Bug bounty program can be found [insert here].
Bugs/Exploits
Governance
Admin Keys
DAO
Treasury
Token
Launch
Token Allocation
Utility
Other Details
Stablecoin
Coin Distribution
Technology
- Whitepaper or docs can be found [insert here].
- Code can be viewed here.
Implementations
- Programming language used: Move
Transaction Details
- Capacity (TPS): "we achieve over 130k transactions per second with only 32 cores in our execution only benchmark." (15-3-2022). Later had a blog post titled "the path to 100k+ TPS (13-7-2022).
- Latency:
How it works
"How is it safe ser? As discussed on the thread above, Move enables smart contracts interaction with validators to be deterministic, hermetic (state change is predictable; untainted) and metered (protection against DOS attacks). All can be verified by Move Prover. Aptos decouples the codependent execution and consensus layers through a parallel execution engine which synchronize eventually. The parallel execution layer leverages the design of Block-STM's that executes transactions optimistically then detects and manages conflicts before synchronizing and changing the state.
But ser, what about the detected conflicts? They are picked up by at most 1 thread in the parallel execution engine and re-executed based on the execution queue, and re-validated through a queue along with its subsequent txs. Abstractions are separated from trivial executions and validations. This is all possible due to preset orders with indexes that map transactions throughout the execution and validation cycle. Block-STM algorithms handles seamless operations.
With 32 threads working in parallel through the Block-STM design, complemented by its robust state synchronization mechanisms to reduce latency, Aptos would be able to boast up to 100k+ tps with sub-second finality."
- From their blog (15-3-2022):
"Our team has developed a production-grade, low latency Byzantine Fault Tolerant (BFT) engine. We have implemented our fourth iteration of the protocol (the most advanced HotStuff derivative) over the past three years. During that time, we have upgraded the consensus protocol in a private mainnet environment with a diverse set of operators and zero downtime. Our first implementation of the BFT protocol added an active pacemaker that used timeouts to synchronize validators much more quickly than waiting for increasing timeouts. With our latest improvement to the protocol, blocks are committed in as few as two network round-trips, making sub-second finality the common case. Our novel reputation system analyzes the on-chain state and automatically updates leader rotations to adjust for non-responsive validators without any human intervention, making it well suited for decentralized environments. Furthermore, our protocol clearly separates liveness from safety. No matter if the network is unreachable or the non-safety core is compromised in some way, the chain will not fork as long as the BFT honesty guarantees are upheld. The safety of our consensus protocol has been both audited and formally verified."
Fees
Upgrades
Staking
Validator Stats
Liquidity Mining
Scaling
Interoperability
Other Details
Oracle Method
Compliance
Their Other Projects
Roadmap
- Can be found [Insert link here].
Usage
Projects that use or built on it
- Coindesk published an article (8-2022) about Ian Macalinao wanting to go to Aptos and potentially redo his Solana TVL scheme. So be advised.
Competition
- Layer 1 blockchains and Sui in particular. From this Sui & Aptos comparison thread (26-7-2022):
"Sui's version of Move has introduced some modifications, the most visible being the ownership API. It is more clean and it exposes the blockchain design more clearly IMO. But the libraries feel a little bit less developed than Aptos'. Aptos uses BlockSTM, which is an evolution of the high-performance HotStuff algorithm, and introduces parallelization by dynamically detecting dependencies and scheduling execution tasks (taking its inspiration from Software Transactional Memory). It's hard to tell which one will perform better in practice, but my bet is with Sui. Aptos has done already a very good job at optimizing their current design, whereas Sui seems to have more room. The two-paths of byzantine agreement give Sui an edge as well.
Sui tackles [state bloat] via efficient sharding of the store, focusing on horizontally scaling the resources. Aptos on the other hand puts more emphasis on supporting heterogeneous validators (contrained CPU and/or constrained storage). I like Sui's take on this.
They are both at a similar stage of development, with Aptos a bit ahead. It took me longer to set up the system than actually coding (I also happen to use NixOS). Learning the language and the environment involves some trial-and-error. Deploying to devnet is somewhat cumbersome in both as well. Fortunately, the unit test libraries are quite usable. The worst part has definitely been the obscure compiler errors, and devnet error responses that make no sense. These can be real time sinks."
Pros and Cons
Pros
Cons
Team, Funding and Partners
Team
- Full team can be found [here].
- AptosLabs, used to work on Diem.
- "25+ members" (15-3-2022)
- Took the Head of Marketing from Solana and made it Director of Ecosystem at Aptos (19-7-2022).
Funding
"Raised $150 million in a Series A funding round that was led by FTX Ventures, the venture capital arm of crypto exchange FTX, and Jump Crypto, according to a press release. The round included investments from Andreessen Horowitz, Multicoin Capital and Circle Ventures among other crypto firms."
- From their blog (15-3-2022):
"Raised $200 million in a strategic round led by a16z crypto with participation from Multicoin Capital, Katie Haun, 3 Arrows Capital, ParaFi Capital, IRONGREY, Hashed, Variant, Tiger Global, BlockTower, FTX Ventures, Paxos and Coinbase Ventures, as well as a great supporting cast of other phenomenal firms, executives and angels across the Web2 and Web3 ecosystems."
Partners
(:
Knowledge empowers all and will help us get closer to the decentralized world we all want to live in!
Making these free wiki pages is fun but takes a lot of effort and time.
If you have enjoyed reading, tips are appreciated :) This will help us to keep expanding this archive of information.