The world of Akroma is changing fast, each day new software is released, new 3rd party support is launched, the community grows and Akroma becomes more stable. Here is a quick look at what we’ve seen in the last few weeks.
Akroma release 0.2.5
Thanks to the work of seanjnkns, we’ve released the next version of Akroma that includes massive performance improvements, bug and security fixes, and new APIs. This release merges in months of work from upstream projects (ETH and ETC) and brings Akroma up to version 1.8.13.
If you run a masternode, miner, miner pool, or exchange; this release offers major improvements for your services.
You can see the full release notes here: https://github.com/akroma-project/akroma/releases/tag/0.2.5
- Overall this release is ~28% lighter on disk IO and ~23% faster on block processing.
- Reduce full-node database rate of growth by 28%
- Speed up ethash verification cache generation by 24%
- Increase the Merkle trie hashing performance by 12–50%
- Increase block processing and propagation speed by 15–25%
- Reduce runtime complexity of retrieving pending transactions
- Cap cache allowance to Go’s GC limits and stabilize memory
- Reduce database lookups for reverse header retrieval requests
- Discovery ping/pong logic uses less goroutines
- The intermediate trie GC buffer now uses less memory
- The EVM big integer pool is reused across transactions
- MSTORE and SLOAD EVM instructions are a bit faster
- Fix invalid errors for balance retrievals of non-existing blocks
- Enforce RPC timeouts to avoid stalling HTTP connections
- Fix a goroutine leak in light clients for cancelled requests
- Fix a goroutine leak in light clients for timed out requests
- Fix an invalid header request handling in light servers
- Fix light server tracking regression in light clients
- Fix miner to handle side blocks more gracefully
- Fix 4byte tracer to count external CALLs too
- Fix shutdown hang on invalid genesis json
- A crash in the LES header fetcher is resolved
We’ve seen many people jump into the new masternode types. Rather then just the “full node” type, these masternodes provide direct and unique features to the Akroma network. You can read more about Akroma masternodes here: https://medium.com/akroma/masternode-update-oct-2018-b323da92c2f7
Docker deployment tool
For those looking for a simple deployment option for their masternode, a new Docker based install method has been published by community member “Void”. You can find out more about this method of masternode configuration on Void’s GitHub repository. https://github.com/cryi/aka-remote-mn and https://github.com/cryi/aka-mn
Android wallet becomes fully decentralized
With the introduction of the “transaction indexing” API features in the new Akroma client and the remote masternodes; it is now possible to create decentralized applications. Most wallets and 3rd party applications require an API — such as a centralized explorer’s API — to get information about the network, However, since Akroma’s remote masternodes offer a fully decentralized API, we can build applications that don’t rely on such centralized services.
You can download the Akroma Android wallet from the play store here: https://play.google.com/store/apps/details?id=com.wallet.crypto.akroma&hl=en
Swirl Pay launches with Akroma support
Swirl Pay is a WooCommerce extension that lets anyone running a WooCommerce e-commerce website accept crypto currency and AKA is one of their premier launch partners.
You can learn more about Swirl at https://swirlpay.io/
Graviex minor outage
Graviex had a small outage, contacted us directly and were able to resolve their issue in a very quick fashion. We are really happy to see them contact us for support, it shows the level of interest for AKA on the Gravies exchange. Also, they announced that AKA was available for trading again and included this amazing meme from our long ago meme-off:
api.akroma.io is dead, long live remote.akroma.io
The centralized explorer API is offline, anyone that wants to build dApps should focus on using remote.akroma.io’s APIs.
The documentation for remote.akroma.io can be found here: https://docs.akroma.io/using-akroma/akroma-geth-rpc-api
When using remote.akroma.io, replace the url in the example (localhost:8545) with
The Akroma documentation currently focused on API methods that are unique to Akroma, you can find the default list of API methods here, until we complete our API documentation, : https://github.com/ethereumproject/go-ethereum/wiki/JSON-RPC