1. Testnet Beta RC1 is Testnet 7.0   

2. Testnet RC3 is Testnet 9.0   

3. DevNet is DevNet   

The mobile application will point to the Testnet Beta RC1  endpoint, which will be compatible with the Testnet Beta RC1 branch (Develop Branch – tag cli-v1.0.0-rc1.2) in the CLI and Testnet Beta RC1 in the Explorer (https://beta.explorer.accumulatenetwork.io/). To use new features in Accumulate, connect to the Testnet (9.0) Branch (Develop Branch – Tag cli-v1.0.0-rc3) in the CLI and use the Testnet RC3 option in the Explorer (https://explorer.accumulatenetwork.io/). To interact with the Devnet use the Develop branch in the CLI and the Devnet option in the explorer (https://dev.explorer.accumulatenetwork.io/).   

To switch from one branch to another in the CLI type git branch and the branch you would like to connect to. Make sure to do a git pull and go build to get the latest updates in the CLI.   

Protocol Highlights  

• Import Pre-allocated ADIs – Adds a mechanism to add pre-defined ADIs to genesis and fixes some bugs.
• Create identity sliding fee schedule – Add a sliding fee schedule for CreateIdentity transactions that charges more for shorter ADIs. The default schedule is exponential where 13 characters and below cost $5 and every character less multiplies the fee by 2 up to $20,480 for 1 character ADIs. This calculation is done after removing the `.acme` suffix. The dollar value is subject to change before Mainnet. 
• Tag validator info with operator – Add an `Operator *url.URL` field to `ValidatorInfo` so validator entries can be tagged with the operator they belong to. 

https://docs.accumulatenetwork.io/accumulate/getting-started/fees

Accumulate Release Candidate 3 (RC3) Release Notes – 09/26/22 

🚀  New   

• Prepare to upgrade testnet from RC2 to RC3  
• Fix accounting of the faucet  
• Factom genesis v2  
• Export API types  
• Import pre-allocated ADIs  
• Fuzz test for executors  
• Add index, time to block ledger  
• Tag validator info with operator  
• Support different peer addresses              
• Include the major block index      
• Stop on fatal error  
• Shutdown if the DN stalls  
• Create identity sliding fee schedule 

🔧  Fixes   

• DN anchor accounting  
• Anchor multisig bug  
• Race condition on develop  
• Cross-partition updateKeyPage signing    
• JSON unmarshalling for some unions        
• Entry hash in transaction result   
• Refactor snapshots  
• Don’t sign anchors when following            

✨ Improvements   

• Fix compatibility of transaction status  
• Require key hashes to be 32 bytes             
• Add read header timeout  
• Support BPT entries with no account state  
• Prevent or catch query tx panic   
• Negative values check  

Additionally, from this point onwards (until further notice), there will be two Testnets to make sure that third-party applications can remain stable. In addition, the DevNet will remain. The mobile application is compatible with the Beta RC1 version of the Testnet.   

1. Testnet Beta RC1 is Testnet 7.0   
2. Testnet Beta RC2 is Testnet 8.0   
3. DevNet is DevNet   

The mobile application will point to the Testnet Beta RC1 is Testnet 7.0  endpoint, which will be compatible with the Testnet Beta RC1 branch (Develop Branch – tag cli-v1.0.0-rc1.2) in the CLI and Testnet Beta RC1 in the Explorer (https://beta.explorer.accumulatenetwork.io/). To use new features in Accumulate, connect to the Testnet Beta (8.0) Branch (Develop Branch – Tag cli-v1.0.0-rc2) in the CLI and use the Testnet Beta RC2 option in the Explorer (https://explorer.accumulatenetwork.io/). To interact with the Devnet use the Develop branch in the CLI and the Devnet option in the explorer (https://dev.explorer.accumulatenetwork.io/).   

To switch from one branch to another in the CLI type git branch and the branch you would like to connect to. Make sure to do a git pull and go build to get the latest updates in the CLI.   

Protocol Highlights  

• Integrate Factom snapshot with Accumulate Genesis Tool – this will allow Accumulate to take a snapshot of Factom at a particular block height and import data into the Accumulate Genesis Block 
• Allow new Factom data entries – a user can choose to write data in the same manner as a Factom data entry 
• Variable fee schedule update – for multi-operation commands in Accumulate, such as sending ACME tokens to multiple outputs, each additional output will be charged a fee. Please see the change in the fee schedule below: 
   
  https://docs.accumulatenetwork.io/accumulate/getting-started/fees 
   

Accumulate Release Candidate 2 (RC2) Release Notes – 09/06/22 

🚀  New   

• Add height to /status 
• Integrate factom snapshot with accumulate genesis tool 
• Allow new Factom data entries 
• Variable fee schedule update 
• Limit delegation depth 
• Validate validator set at Genesis 
• Validate anchor and synthetic transaction keys against dn.acme/network instead of dn.acme/operators 
• Route when query-tx with txid 
• Send synthetic transactions as an RPC batch 

🔧  Fixes   

• ParseLiteAddress panics on small hex values 
• getVersion is exiting with check errors when it should be returning error 
• Do not allow adding a page as an authority 
• Various performance improvements 
• Correct configuration issue with routing transactions to DN 
• Limit URL length 
• Update Tendermint to 0.35.9 
• Pending synthetic transactions cause performance to suffer badly 
• Delegation allows replay 
• StateManager.AddAuthority checks the wrong URL 
• Able to Remove Delegate Entry (Only Entry) on Highest Priority Key Page  
• Able to add Duplicate Keys When Creating a New Key Page 
• UpdateKey doesn’t work with a delegated signature 

✨ Improvements   

• Add more logging to the sequence healing code 
• Eliminate remote transactions 
• Accumulated logs are a little too silent at startup 
• Decouple API v2 from ABCI 
• Query-tx API should accept the fully qualified tx ID (URL) 
• Replace block index with an account 
• Export the client 
• Move URL package to not internal 
• Remove deprecated terms 

Additionally, from this point onwards (until further notice), there will be two Testnets to make sure that third-party applications can remain stable. In addition, the DevNet will remain. The mobile application is compatible with the Stable version of the Testnet.  

1. Testnet Stable is Testnet 4.0  

2. Testnet Beta is Testnet 7.0  

3. DevNet is DevNet  

The mobile application will point to the Testnet Stable (4.0) endpoint, which will be compatible with the Testnet Stable Branch (Develop Branch – Tag v0.6.0 of the Devnet) in the CLI and Testnet Stable option in the Explorer (https://explorer.accumulatenetwork.io/). To use new features in Accumulate, connect to the Testnet Beta (7.0) Branch (Develop Branch – Tag v1.0.0-rc1) in the CLI and use the Testnet Beta option in the Explorer (https://beta.explorer.accumulatenetwork.io/). To interact with the Devnet use the Develop branch in the CLI and the Devnet option in the explorer (https://dev.explorer.accumulatenetwork.io/).  

To switch from one branch to another in the CLI type git branch and the branch you would like to connect to. Make sure to do a git pull and go build to get the latest updates in the CLI.  

Protocol Highlights 

• Lock Lite Token Accounts – The ability to lock Lite Token Accounts is necessary for the initial ACME Token distribution 
• Create Snapshot of Factom Entries – Accumulate needs to be able to port over Factom’s data. This can be done through a snapshot. 
• Add Entry Blocks to the Flat Files of the Factom Entry Extraction – This process allows Accumulate to Export Entry Data from Factom to Flat Files, which will then be added to the Accumulate Blockchain 
• Replace Scratch Accounts with Scratch Chains – Before ADI Data Accounts and ADI Scratch accounts were two separate Account Types. Now, there is only a Data Account that can write to a Data Chain or a Scratch Data Chain 
• `.acme` is a valid ADI name – All ADIs must to end with .ACME 
• Multiple output issue tokens – When Issuing Tokens multiple outputs can be specified 

Accumulate 0.8, 0.9, and Release Candidate1 (RC1) Release Notes – 07/19/22, 2022 

🚀  New  

• Add network file deployment test 
• `.acme` is a valid ADI name 
• A synthetic transaction will never be delivered if it arrives after its anchor 
• Add Entry Blocks to the flat files of the Factom Entry Extraction 
• Add guards for –reset 
• Add security for proxy / validator config 
• Allow new Factom data entries 
• Block self-delegation 
• CLI import key makes bad assumption about key type 
• CLI tx execute: accept YAML 
• Configurable routing 
• Convert batch to data model entity 
• Convert transaction to data model entity 
• Create data model based database infrastructure 
• Create Snapshot of Factom Entries 
• Dataset logger for creating tabular data 
• Debug TestMissingSynthTxn 
• Deprecate use of persistent peers 
• Enforce anchor sequence and delivery 
• Gen-types –include is broken 
• Halt Factom at a Particular Block Height 
• Include a version in the snapshot header 
• Include the list of accounts within an ADI as part of the ADI’s state 
• Leverage checktx priority for SyntheticTransactions 
• Lock lite token accounts 
• Major Block API Task 
• Make transaction blacklist marshal as a list 
• Make validator key books subordinate to dn/operators 
• Minor block API excludes anchors 
• Move account indices to data model 
• Multiple output issue tokens 
• Not able to generate lite Identity/lite token account with already created “key”/”public key” 
• Partially Refund ACME Balance for Failed Add Credit Transaction (Deduct 1 Credits worth of ACME) 
• Preserve state during CheckTx 
• Prevent refund cycle 
• Reduce the signature fee to match the scratch write data fee 
• Refactor accumulated config directory structure 
• Refactor transaction status 
• Remove grpc support  
• Remove IDE-specific files 
• Remove Private Key import from command line input in CLI 
• Remove the validator key book 
• Replace scratch accounts with scratch chains 
• TestAdd/RemoveKey tests broken 
• Update indices and SMT to use the struct cache 
• Update the Devnet to run in dual-mode (pairing BVN node and DN node) 
• Update type generator 
• UpdateKey can create duplicates 
• Use a fixed set of chains 
• Use a full snapshot as the genesis document 
• Use data model for database cache 
• Use full chainId/accountId as the lite data url 
• Validate major block API in CI and make major block timing configurable 
• Validate synthetic and anchor signers against dn/network 
• Wallet Backup Import and Export Design 
• When Creating a Duplicate Authority the Transaction Should Fail 
• Write Load Code Utility 

🔧  Fixes  

• Able to Set Threshold to 0 
• Fix add credits 
• Handle IssueTokens failure 
• Issuing Custom Tokens to an ACME Token Account Changes ACME Account Balance 
• Not able to generate lite Identity/lite token account with already created “key”/”public key” 
• Panic in SubnetSyntheticLedger.Add 
• Sending a synthetic transaction to the DN crashes it 
• TestCLI is failing in CI (June 13) 
• Updating a Key Book URL and Public Key Hash with a different Delegate (Key Book URL) (signing with the Public Key Hash)(Entry: Public Key Hash, Delegate) Fails 
• Updating a Public Key Hash Entry to Include the Same Public Key and a New Key Book URL Produces a “Cannot have duplicate entries on key page” Error 

✨ Improvements  

• Cleanup CLI help 
• Fix static analysis issues 
• Many CLI subcommands appear to accept more parameters than they really do 
• Remove key page index and height parameters from CLI commands 
• Rename subnet to partition 

Join Accumulate social communities to get the latest updates!

With article contributions from Drew Mailen & WIsdom Nwokocha

Accumulate developers are announcing the release of Testnet 6.0, Zakim Bridge, named after the Leonard P. Zakim Bridge, which is located in Boston, Massachusetts. The Zakim Bridge and a connecting tunnel were both designed as part of the Big Dig, which was the largest highway construction project in the United States. 

From this point onwards (until further notice), there will be two Testnets to make sure that third-party applications can remain stable. In addition, the DevNet will remain. The mobile application is compatible with the Stable version of the Testnet.  

1. Testnet Stable is Testnet 4.0  
2. Testnet Beta is Testnet 6.0  
3. DevNet is DevNet  

The mobile application will point to the Testnet Stable (4.0) endpoint, which will be compatible with the Testnet Stable Branch (Develop Branch – Tag v0.6.0 of the Devnet) in the CLI and Testnet Stable option in the Explorer (https://explorer.accumulatenetwork.io/). 

To use new features in Accumulate, connect to the Testnet Beta (6.0) Branch (Develop Branch – Tag v0.8.1-beta) in the CLI and use the Testnet Beta option in the Explorer (https://beta.explorer.accumulatenetwork.io/). 

To interact with the Devnet use the Develop branch in the CLI and the Devnet option in the explorer (https://dev.explorer.accumulatenetwork.io/).  

To switch from one branch to another in the CLI type git branch and the branch you would like to connect to. Make sure to do a git pull and go build to get the latest updates in the CLI.  

Protocol Highlights 

• Major Block Implementation – Major Blocks capture the state of the network every 12 hours and will be anchored into other Layer 1 Protocols 
• Add Factom Entries to Accumulate Block Validator Network – the capability to move Factom data to our Block Validator Networks has been realized 
• Use ACME as a Top-Level Domain for Identities – Going forward, all Identities will end in .acme 
• Require approval from all authorities for UpdateKeyPage and UpdateAccountAuth – When executing UpdateKeyPage or UpdateAccountAuth, require approval from all authorities, including disabled authorities. In other words, when executing one of those transactions, ignore the Disabled field of the authority set. 
• Tendermint Snapshots – Ability to synchronize nodes to the current state using snapshots 

Accumulate 0.7 Release Notes – 06/08/22

🚀  New  

Change BurnTokens fee 

Tools for testing 

Remove data entry version field 

Create test data for merkle hashes 

Synthetic Transaction Failure Output 

Require approve from all authorities for UpdateKeyPage and UpdateAccountAuth 

Improve the routing info tool (for debugging) 

Allow the first entry to contain data entry on lite data account in cli 

Show lite identity info when showing a lite token account (CLI) 

Tendermint snapshots 

Send synthetic transactions separately 

Update the BPT to track the ADIs of accounts 

Make all transaction IDs routable 

Use acme as a TLD for identities 

Validate keys used to sign synthetic transactions and anchors 

Query BVN blocks for a given DN block 

Synchronize global values via anchor transactions 

Create a DN data account that defines the set of subnets 

Flush pending writes after each transaction 

Checktx guard against back door 

Add Factom Entries to Accumulate Block Validator Networks 

Advanced routing framework 

BVN/DN performance study and analysis (1 of 2) 

Major blocks 

🔧  Fixes  

Rounding error for validate threshold computation 

Fix devnet deploy 

CLI: Querying a lite token account uses the wrong precision for credits 

CLI account list gives error 

Partially Refund ACME Balance for Failed Add Credit Transaction (Deduct 1 Credits worth of ACME) 

API returns wrong chain state hashes 

TestMissingSynthTxn is flaky 

Account Creation with incorrect Principal e.g. creating an ADI token account referencing an ADI Token Account as the Principal 

Current Credit Balance Gets written over by New Credit Amount Added 

Keys are generated, but there is an error saying Key Required 

With article contributions from Drew Mailen & WIsdom Nwokocha

Accumulate developers are announcing the release of Testnet 5.0, Pennybacker, named after the Pennybacker Bridge in Austin, Texas. The through-arch bridge crossing Lake Austin connects the northern and southern sections of the Capital of Texas Highway. Nearly 48,000 vehicles cross the bridge daily. Often referred to as the “360 Bridge,” it is one of the most scenic roads because of its hills and weathering steel. Read more about the fixes, updates, and releases that are now live on Accumulate as a part of Testnet 5.0. 

Compatibility

From this point onwards (until further notice), there will be two Testnets to make sure that third-party applications can remain stable. In addition, the DevNet will remain. The mobile application is compatible with the Stable version of the Testnet. 

1. Testnet Stable is Testnet 4.0 
2. Testnet Beta is Testnet 5.0 
3. DevNet is DevNet 

The mobile application will point to the Testnet Stable (4.0) endpoint, which will be compatible with the Testnet Stable Branch (Develop Branch – Tag v0.6.0 of the Devnet) in the CLI and Testnet Stable option in the Explorer (https://explorer.accumulatenetwork.io/). 

To Use New Accumulate Features 

To use new features in Accumulate, connect to the Testnet Beta (5.0) Branch (Develop Branch – Tag v0.7.0-beta) in the CLI and use the Testnet Beta option in the Explorer (https://beta.explorer.accumulatenetwork.io/). 

Interacting with Devnet 

To interact with the Devnet use the Develop branch in the CLI and the Devnet option in the explorer (https://dev.explorer.accumulatenetwork.io/). 

Switching Between Git Branches 

To switch from one branch to another in the CLI type git branch and the branch you would like to connect to. Make sure to do a git pull and go build to get the latest updates in the CLI. 

Protocol Highlights

• Sign a message with the CLI – The ability to sign a message with the CLI will be particularly helpful for our Staking Model. A transaction will need to be signed to withdraw tokens.
• Guarantee Synthetic Transaction Delivery – Provides a proof that synthetic transactions have reached their destination
• Major Block Design – Major Blocks capture the state of the network every 12 hours and will be anchored into other Layer 1 Protocols
• Add Test Coverage for Different Signature Types – 
• Anchoring the DN into the DN – This is necessary for providing cryptographic proofs

Accumulate 0.6.1 Release Notes – 05/01/22

🚀  New 

Routing debug tool

Remove redundant slippage parameter from cli credit purchase

Handle synthetic transactions sent out of order

Rename key page entry ‘owner’ to ‘delegate’

Eliminate the mirror transaction

Add linters

Sign a message with the cli

Anchor the DN in the DN

Require approval from a key book when adding that key book to the authority set of an account

Review Rosetta API Endpoints

Staking Implementation Document

Eliminate the data chain

Split up synthetic anchor transaction

Query specific block by height

 Create the operator key books

Major block design

Clarify wording in receipt

Add test coverage for legacyEd25519, btc, btcLegacy, eth in cli tests

ABCI snapshot functions

Do not create empty blocks

Require proof of external dependencies when executing certain operations

Guarantee synthetic transaction delivery

🔧  Fixes 

Improve error messages

Fix flaky anchor test

API does not support delegated signatures

Query-minor-blocks does not return “total”

Refactor delegated signatures and key handling

Unionize executor requests

Make data entry a tagged union

Move test coverage of administrative test function in validate.sh to separate file

With article contributions from Drew Mailen

Accumulate is pleased to announce the deployment of Testnet 4.0, Golden Gate. Named after the landmark art deco suspension bridge completed in 1937 that connects the San Francisco Bay with the Pacific Ocean, the Golden Gate Testnet release includes a robust list of upgrades.  

Compatibility  

From this point onwards (until further notice), there will be two Testnets to make sure that third-party applications can remain stable. In addition, the DevNet will remain. The mobile application is compatible with the Stable version of the Testnet. 

1. Testnet Stable is Testnet 3.0 
2. Testnet Beta is Testnet 4.0 
3. DevNet is DevNet 

The mobile application will point to the Testnet Stable (3.0) endpoint, which will be compatible with the Testnet Stable Branch (testnet-stable-release-v0.4.0) in the CLI and Testnet Stable option in the Explorer (https://explorer.accumulatenetwork.io/). To use new features in Accumulate, connect to the Testnet Beta (4.0) Branch (testnet-beta-release-v0.5.1) in the CLI and use the Testnet Beta option in the Explorer (https://beta.explorer.accumulatenetwork.io/). To interact with the Devnet use the Develop branch in the CLI and the Devnet option in the explorer  (https://dev.explorer.accumulatenetwork.io/). 

To switch from one branch to another in the CLI type git branch and the branch you would like to connect to. Make sure to do a git pull and go build to get the latest updates in the CLI. 

Protocol Highlights 

• Basic Routing and Connection Framework for Nodes – routing identities to the appropriate nodes based on the health of a node. 
• Initial Implementation of Managed Chains – The ability to assign and un-assign a manager to any account type except for Lite Accounts (i.e. ADI Account, Sub ADI Account, Key Book Account, Key Page Account, Token Account, Data Account, etc.) 
• Lite Token Account Identity and Directory – In the future, Lite Token Accounts will be able to support different token types. A Lite Token Account Identity will act as a directory using the same public key to create different Lite Token Account types. 
• Manual ACME Oracle – To determine the payout of Credits based on the price of ACME, there will be a manual oracle in place that will determine the price. 
• Binary Encoding Scheme – implementation of backward-compatible encoding scheme. This will enable the protocol to grow and expand while allowing ecosystem developers to make updates on their own time. The encoding code generator was expanded with the capability of supporting other languages such as Dart and Javascript. Ecosystem developers no longer have to handwrite encoding code, which makes it much easier to update as the protocol evolves.  
• Multi-sig threshold support – Clearly defines the n in the m of n for a multi-signature transaction 
• Sub-ADIs – ADIs that are nested within an ADI that contain its own set of Key Book, Key Pages, Keys, and Accounts. Creating a Sub-ADI is just creating an ADI where the URL is foo/bar instead of foo (also it has to be signed by foo).  
• Nested Key Pages – Instead of having ADI/KeyBook and ADI/KeyPage, pages will now be nested within a KeyBook where the starting page is 1 and each additional page is incremented by 1. For example, ADI/Keybook/1, ADI/KeyBook/2 etc. 
• Locked Key Pages – Add the ability to lock a key page. A locked key page cannot modify (or add) keys. A locked key page cannot execute ‘UpdateKeyPage’ except when a key is modifying its own spec (keys can still update themselves).
• Add memo and metadata field to the transaction – A user can specify additional data they want to add to a transaction. 
• Support Factom RCD1 signatures – Factom has a signature method called RCD1 that needs to be supported for upgrading Factom to Accumulate 
• Support querying lite data accounts by URL (Factom) – Factom compatible Lite Data accounts can be queried  
• Factom Scraping Tool – Tool for scraping data from data chains in Factom to Lite Data Accounts in Accumulate. As a side note, Factoid transaction history and Entry Credits will not be ported over to Accumulate. However, the Factom explorer will be maintained to preserve Factoid History. The Factoid Account balances will be converted to ACME tokens in Accumulate 
• Burn ACME to Buy Credits – The API to buy credits has changed requiring a user to specify the maximum amount of ACME they want to spend to buy credits.  
• Exploratory Data Server Network (DSN)- Every major block, the network will produce an incremental snapshot that rolls up the last 12 hours of changes across the network. That will be sent to the DSN, which will be its own Tendermint network. The DSN will process the snapshot and send back proof that it got everything. When the network receives that proof, it will prune the historical records from that major block. 
• Index Chains – index chains allow the protocol to timestamp transactions within Accumulate 

Accumulate 0.5.1 Release Notes by Wisdom Nwokocha – April 6, 2022

🚀  New 

• We have added support for executing multiple key page updates as a single transaction (We have added multi-operation key page updates) 
• We added API support for other signature types 
• Create an access control framework 
• Add transactions for adding, removing, updating a validator 
• Envelope and synthetic transaction redesign 
• Capture evidence from Tendermint 
• Capture votes from Tendermint 
• Create index chains 
• Add an API call that constructs a proof of the state of an account 
• Add memo and metadata field to the transaction 
• CLI Command to display how many Credits you receive per ACME 
• Add the ability to lock a key page 
• Support Factom RCD1 signatures 
• We created Sub-ADIs 

🔧  Fixes 

• A synthetic transaction with an invalid origin is not saved 
• We fixed a bug that could cause the Testnet to stall due to an invalid synthetic transaction We built a solid Monitoring infrastructure 

🔧  Improvements 

• Key page entries must be key hashes 
• Deprecate extids on data accounts 
• Document API methods 
• Rename the pending chain 
• Run two nodes side-by-side 
• Use ‘timestamps’ instead of ‘nonces’ 
• Track the key page version 
• Track issued tokens instead of the remaining reserve 
• Accumulate only check the nonce of the first signature 
• Burn ACME to buy credits 
• We added Nest Key Pages with Key Books (acc://ethan/book/1) 
• Keys must be hashed with SHA-256 

Accumulate 0.5 Release Notes by Wisdom Nwokocha

🚀  New 

• Expose the number of signatures required for a pending transaction in the protocol 
• Assign a manager to an account in the CLI 
• Lite Account Identity in the CLI 
• Add Scratch Flag to ADI Data Account and ADI Token Account Creation in CLI 
• Add Token Issuance to CLI 
• Prove the inclusion of an entry in a chain 
• Support signatures other than ED25519 in the protocol 

🔧  Fixes 

• Add human-readable output for token transactions in the CLI 
• URL-based query for a data entry by hash returns the wrong entry hash in the protocol 
• CLI can’t read Account Balance 

🔧  Improvements 

• Improved the Update key book references in the protocol 
• Allow the version check to be ignored when onboarding a node in the CLI 
• Create a CLI Command to Un-assign a Manager 
• Improved Document new encoding scheme in the protocol 
• Improved manual ACME oracle in the protocol 
• Improved the return Threshold of Pending Transaction Through API in the protocol 
• SDK Backwards compatibility for token issuer 
• Use the SDK client interface improved 
• Change Token Type for Token Issuer  
• Display Synthetic Transaction Success or Failure in CLI  
• Add Command to CLI to show Pending TXs 
• Make a chain unmanaged 
• Add a manager to an existing chain 
• Assign manager key book when a record is created 

More specific additions include: 

Explorer 

• Signature Chain Support  
• Rendering of ADI Token Issuance Account 
• Rendering of Custom ADI Token Account 
• Rendering of Custom Token Types
  Rendering of Sub-ADIs 
• Rendering of Nested Key Pages 
• Multi-Signature Support 

CLI 

• Assigning and un-assigning a manager to/from an account 
• ACME Oracle 
• Sub-ADI Creation 
• Nested Key Books and Key Pages 
• Multi-Signature Support 

Infrastructure  

• Create a Validator TX (Will be used to onboard Factom ANOs, Dynamic Mining, etc.) 
• BVN and DN run together on the same server 
• Docker container for easy deployment of Node (Clone Accumulate/Docker ./run)  
• Initial Implementation of Node CLI 

With article contributions from Drew Mailen

Today is the official launch of the Accumulate Testnet 3.0 Helix, named after the landmark pedestrian Helix Bridge that connects Singapore’s Marina Centre and Marina South. 

The Testnet 3.0 Helix release notes significant improvements in the following areas: 

• Protocol
• Command Line Interface (CLI)
• Explorer
• Software Development Kits (SDKs)
• Mobile App
• Ledger Hardware Wallet Development
• Technical Documents

Rooted in identity and key management, Accumulate is a universal interconnect protocol that’s interoperable across Web 2 and Web 3 addresses from layer 1 blockchains to enterprise tech stacks, to websites. 

Protocol

• Anchoring: Anchors represent the state of a particular chain, BVN, or DN up to a certain point in time. Anchors are necessary for cryptographically proving transactions.
• Transaction Batching: The ability for transactions to be batched must exist, such that a set of transactions is processed in a specific order. Synthetic transactions sent between BVNs must be batched.
• Validator Onboarding: To secure the Accumulate, validators are needed to verify transactions. Accumulate can begin to onboard external parties to participate in validation.
• Fee Schedule: Every action in Accumulate requires Credits. The Accumulate fee schedule outlines credits required per each action.
• Burning Tokens: ACME Tokens that are burned when purchasing credits will be added to the uncirculated supply.
• API Changes to V0.2: See changes here.

Command Line Interface

• Multi-sig: Individuals or enterprises can construct sophisticated Multi-sig transactions. Multi-sig transactions are specified by m of n keys required within a Key Page.
• ADI Scratch Accounts: An ADI scratch account can write data to the blockchain that is pruned over a certain period of time (roughly 2 weeks). In Accumulate there are ADI Scratch Data Accounts and ADI Scratch Token Accounts. Because the Data is pruned, Scratch Data and Token transactions are cheaper.
• Scratch Spaces: This is a transient blockchain (data is stored for 2-3 weeks) with fast block times that allows different parties to reach a consensus off-chain (e.g. they are negotiating the terms of a deal and developing a multi-signature smart contract). Scratch Spaces are good for privacy because a user may not want to broadcast their decision-making process to the main blockchain. Scratch Spaces reduces cost because a user posts the conclusion, not the work. Instead of a dozen transactions (the work), you post 1 transaction (the conclusion).
• Token Issuer: Custom tokens can be created on Accumulate.
• Lite Data Chain: A data chain that anyone can hash data to.
• Credits: In order to execute a transaction, credits must be funded in the lite token account or ADI Key Page. Credits are acquired through burning ACME tokens.
• QR Codes: QR codes can be used to receive transactions.

Explorer 

• Key Book and Key Page: Key Books and Key Pages can be viewed by URL instead of ChainID.
• ADI Data Accounts: ADI Data Accounts can be displayed with their entry info, external IDs, and Data.
• Lite Data Account: Lite Data Accounts can be displayed with their entry info, external IDs, and Data.
• ADI Scratch Data Account: ADI Scratch Data Accounts can be displayed with their entry info, external IDs, and Data. A scratch data account will be identified by a pop-up above the Account URL.
• ADI Scratch Token Account: ADI Scratch Token Accounts can be displayed with their entry info, external IDs, and Data. A scratch token account will be identified by a pop-up above the Account URL.

Web App

The first version of the UI has been created for Accumulate’s Web App. There will be a series of releases where the Web App will have all the features of the mobile app plus additional features.

Software Developer Kits (SDKs)

• Accumulate.js – Javascript SDK Beta Version 
• Golang SDK Beta Version

Ledger Hardware Wallet

ACME compatibility with the Ledger Hardware wallet is in progress now with the below updates. 

• Ledger Hardware Integration 
• Ledger Toolchain
• Firmware Update
• Debug Test Environment Setup

Mobile App

• Transaction Receive Token Dropdown: The top drop menu here is to allow the user to choose either a lite account or Token Account so if they have already light account selected, the drop menu should just show token account, and vice versa.
• Transaction Token Address book workflow: the address book icon should be linked to the address book workflow so users can access the address book to populate the manual field.
• The App now gives you an error if you have insufficient funds to cover a transactionKey page screen shows the credit balance for each key page in an ADIMobile app now lists the credit fee for each transaction type a user can do.
• Transaction History Section: Fix faucet transactions so they show in the “incoming” section of the transaction history.
• History filter: The ability to filter transaction history by transaction type, receiving account, sending account, etc.
• Notifications: The app will now send push notifications to the user for things like a successful transaction.
• Setting Section: Additional upgrades to the Address Book settings.
• Dashboard Improvements: There will now be a Dashboard that the user can see all the information on their account from, including details about the user’s ADIs and ADI accounts, and Lite accounts.
• Additional Improvements:
  • Layout Enhancements for better user experience
  • App Responsiveness & Bug Fixes for better user experience

With article contributions from Drew Mailen

Today we are officially announcing the launch of the Accumulate Testnet 2.0 Brooklyn release. The Testnet 2.0 release marks a major milestone in the development of Accumulate before the Mainnet launch. Rooted in validating identity communication and management, Accumulate works interoperably across Web 2 and Web 3 addresses– from layer 1 protocols to enterprise tech stacks to websites. 

As an identity-based protocol, Accumulate can integrate with traditional tech stacks while being the first blockchain to provide key management and off-chain consensus-building with Scratch Spaces. 

Features in Testnet 2.0 Brooklyn: 

• URL addressing: Accumulate identities, data, transactions, and state Traditional technology stacks easily integrate with URL addressable data and endpoints with a much-improved user experience. Enables integration with browsers.  
• ADIs: ADIs give users access to the full range of features provided by the Accumulate network including smart contracts, off-chain consensus building, and dynamic key management. ADI accounts are different chains that store information on the Accumulate Network. An example of accounts that it manages are Token Account, Data Account, Scratch Account, and Staking Account.  
• ADI Token Account: An ADI Token Accounts is one of the types of accounts an ADI can control. An ADI token account holds tokens and can be represented as so:  

acc://Bob/Tokens/ACME  

When you are sending or receiving tokens you would specify this URL. 

• ADI Data Account: An ADI Data Accounts is one of the types of accounts an ADI can control. An ADI data account holds data and can be represented as so:  

acc://Bob/Data/  

When you are hashing data to your account, you would specify this URL. 

• Key Books: A Key Book is a prioritized list of Key Pages. Different ADIs can specify different Key Books. The Key Books used to administer the ADI for administrative tasks do not have to be the same Key Books for a given transaction.  
• Key Pages: A Key Page can specify how many Keys are required to validate a transaction. A transaction can either be single signature or multi-signature. A Key Page can also indicate that a Key comes from a particular Key Book of another ADI, or modify itself or a Key Page of lower priority  
• Keys: Wallets create transactions and sign them with their private key.   
• Mobile Wallet App: The mobile wallet app is a user-friendly extension of the Testnet that will allow users to send and receive tokens, create lite accounts, ADIs, create ADI Token Accounts, access sophisticated Key Management features, and use the faucet within the app. 
• Faucet: Allows users to generate test tokens to send to their lite account or to other Lite Accounts.  
• Command Line Interface (CLI) Tool: Create, import, or export token accounts, create token transactions, get data by an Accumulate URL. The CLI Tool can create the following: ADIs, ADI Token Accounts, ADI Data Accounts, and hierarchical Key Management. 
• Explorer: Free and open data insights of the Accumulate Testnet with the ability to query by URLs and Transaction IDs. 

What is the Brooklyn Release? 

Brooklyn is the internal codename for this release. The Brooklyn Bridge was innovatively designed for its time, known for being the first suspension bridge to use steel as a cable wire.  

Stay tuned for these features in upcoming releases: 

• Multi-sig: Individuals or enterprises will be able to construct sophisticated Multi-sig transactions. Multi-sig transactions are specified by m of n keys required within a Key Page. 
• Managers for ADI accounts: Accounts within an ADI can be assigned a manager, requiring an extra signature for the transaction to be processed. 
• Token Issuer: The ability to issue customized tokens will be realized. 
• Lite Data Chain: A data chain that anyone can hash data to. 
• ADI Staking Account: Ability for validators and delegators to stake tokens, which will secure the network and generate rewards 
• ADI Scratch Account: An ADI scratch account can write data to the blockchain that is pruned over a certain period of time (roughly 2 weeks) 
• Scratch Spaces: This is a transient blockchain (data is stored for 2-3 weeks) with fast block times that allows different parties to reach a consensus off-chain (e.g. they are negotiating the terms of a deal and developing a multi-signature smart contract). Scratch Spaces are good for privacy because a user may not want to broadcast their decision-making process to the main blockchain. Scratch Spaces reduces cost because a user posts the conclusion, not the work. Instead of a dozen transactions (the work), you post 1 transaction (the conclusion). 
• Security: Accumulate’s network security will be maintained by Sentry Nodes which will detect malicious behavior on the Accumulate Network. Accumulate will have advanced cryptography for validating transactions. Transactions will be anchored to Layer 1 protocols (Bitcoin, Ethereum, Solana) so that a successful attack on the Accumulate network requires that these other protocols be compromised.  
• Web App: Accumulate’s web application will support some of the more sophisticated actions such as managing accounts and creating ADI scratch accounts. In addition, cold storage wallets will be interoperable with the Web App. 

With article contributions from Drew Mailen

Today we are officially announcing the launch of the Accumulate Testnet 1.0 Rialto release. This marks a major milestone in the development of Accumulate before the Mainnet launch. Accumulate is designed to power decentralized finance (DeFi) and decentralized applications (DApps). As a Universal Layer 2, Accumulate is interoperable with any Layer 1 protocol. Additionally, the protocol is identity-based and can integrate with traditional tech stacks while being the first blockchain to provide key management and off-chain consensus-building with Scratch Spaces.

Features in Testnet 1.0 Rialto:

• Lite Accounts: Used to send and receive tokens and maintain a record of users’ token accounts and transactions. A user can send and receive transactions from one Lite Account to another, or one wallet to another on the app. 
• Mobile Wallet App: The mobile wallet app is a user-friendly extension of the Testnet that will allow users to send and receive tokens, create lite accounts, and use the faucet within the app.
• Faucet: Allows users to generate test tokens to send to their lite account or to others. 
• Command Line Interface (CLI) Tool: Create, import, or export token accounts, create token transactions, get data by an Accumulate URL. The CLI Tool has ADI creation and Key Management capability at this time.
• Explorer: Free and open data insights of the Accumulate Testnet.

What is Rialto?

Rialto is the internal codename for this release. Rialto is a famous bridge in Venice and apart from its engineering and architecture fame, the bridge is considered a key hub for financial exchange and marketplaces.

Stay tuned for these features in upcoming releases:

• ADIs: ADIs give users access to the full range of features provided by the Accumulate network including smart contracts, off-chain consensus building, and dynamic key management. An ADI is the umbrella account that holds subaccounts. These subaccounts are different chains that store information on the Accumulate Network. An ADI can have different chains that it manages i.e. Token Account Chain, Data Chain, Scratch Chain, Token Issuance Chain, Key Chain, Managed Chains. 
• URL addressing: Accumulate identities, data, transactions, and state Traditional technology stacks easily integrate with URL addressable data and endpoints Much improved user experience. Enables integration with browsers. 
• Security: Accumulate’s network security will be maintained by Sentry Nodes which will detect malicious behavior on the Accumulate Network. Accumulate will have advanced cryptography for validating transactions. Transactions will be anchored to Layer 1 protocols (Bitcoin, Ethereum, Solana) so that a successful attack on the Accumulate network requires that these other protocols be compromised. 
• Keys: Wallets create transactions and sign them with their private key.  
• Key Pages: A Key Page can specify how many Keys are required to validate a transaction. A transaction can either be single signature or multi-signature.  A Key Page can also indicate that a Key comes from a particular Key Book of another ADI, or modify itself or a Key Page of lower priority 
• Key Books: A Key Book is a prioritized list of Key Pages. Different ADIs can specify different Key Books. The Key Books used to administer the ADI for administrative tasks do not have to be the same Key Books for a given transaction. 
• Scratch Spaces: This is a transient blockchain (data is stored for 2-3 weeks) with fast block times that allows different parties to reach a consensus off-chain (e.g. they are negotiating the terms of a deal and developing a multi-signature smart contract). Scratch Spaces are good for privacy because a user may not want to broadcast their decision-making process to the main blockchain. Scratch Spaces reduces cost because a user posts the conclusion, not the work. Instead of a dozen transactions (the work), you post 1 transaction (the conclusion).

Resource Links:

• Accumulate Testnet Mobile Wallet
• Github
• Accumulate Developer Documentation 
• Contact
• Community