governance proposals for concurrent fa balance

[igor-aptos]

Description

AIP: AIP-70
Release: supported by v1.14

Security Consideration

Main capability powering this feature is AggregatorsV2. They have been extensively tested (including replay is the same when they are using simple sequential fallback), and audited by OtterSec, and have been in production for months.

Code for concurrent FA balance itself is short, and has been audited by Aptos Labs. For the past 3 weeks, we have run devnet with defaulting all new accounts to concurrent FA balance.

Test Result

state-sync via execution mode on devnet, with aggregators disabled, succeeds.
This feature has been enabled in devnet and testnet since end of June.

for aggregators themselves, passing replay-verify of mainnet and testnet, with simple sequential fallback.

Ecosystem Impact

In v1.14, we have the callout:

Breaking Changes

• [AIP-70] Parallelize Fungible Assets - opt-in parallel fungible balance
  • Ecosystem Impact: In order to track fungible asset balances correctly (for the accounts that opt-in to the new feature), now both old and new field needs to be summed up: FungibleStore.balance + ConcurrentFungibleBalance.balance. If using indexer, this change will make it transparently handled by provided processors. fungible_asset::balance view function will continue providing correct balance.
  • Dependencies: None
  • Feature Flag: CONCURRENT_FUNGIBLE_BALANCE