Partnered With:

Swarm Adami v1.1.0 has been officially launched

Read this article in 8 Minutes

Swarm has released its latest version 1.1.0, which fixes bugs while adding four new features.

Swarm Mainnet Release -- Adami V1.1.0 is live!

Swarm Medium

On June 21, 2021, Swarm main network was officially launched. Swarm released its latest version 1.1.0 today, fixing bugs and adding four new features.

The test net has been updated four times

The test network and the main network belong to two different environments. After the mainnet went live, some new network behaviors appeared. Most of the problems were solved through community feedback and team programming. With four versions of the Testnet, the Bee team and the community went through a lot of critical testing and finally released Adami V1.1.0 on August 24. All future releases are expected to be released to the same exacting standards.

Bee V1.1.0 has four new features. Much of the focus has been on detecting the online behavior of products and resolving problems and vulnerabilities. The problem of upload data resistance has been solved. This means that data can be uploaded more quickly and reliably. Right now we're working on some basic features.

The Bee team is also working to improve the developer experience, making it easier and faster to build on Swarm. If you are running Bee nodes on the main network, please update as soon as possible. Please review the release notes and upgrade documentation.

Important points for node operation

The xDai chain will undergo London hard bifurcation. Keep an eye on and update your infrastructure. Because OpenEthereum clients have not yet determined whether they will support a hard fork.

Let's take a look at what's new in v1.1.0. For more complete update details,See here.

There are two incompatible changes

· The log field traceid is changed to traceid

· Single player mode has been phased out (developer mode is supported)

Four new features

· Added estimates of batch life expectancy. Uploaders now have a better idea of how long their data will last;

· Increased possibility of cancelling transactions so nodes are no longer stuck due to sudden increases in gas charges;

· Allow nodes to start in developer mode without the blockchain backend. All storage is done in memory and the back-end behavior is emulated so you can develop your App on Swarm faster. Try running./bee dev;

· Add block upload endpoints that can transfer blocks over WebSockets.

Improve performance and fix bugs

· Fixed contextual pauses in push synchronization and retrieval protocols. This leads to thread leaks and increased memory consumption;

· Fixed mantaray's previous lookup bug where shared prefix files could not be found correctly;

· Fixed a bug in Kademlia that resulted in the selection of the closest block to the sanctioned peer;

· Fixed the bug of long time shutdown caused by index refresh;

· Improved the efficiency of PSS;

· Fixed the bug of using timestamp incorrectly in time settlement;

· Fixed the correct block time for XDAI;

· Fixed possible gcSizeChange inconsistency issues;

· Improve CONSISTENCY of the API by limiting concurrent access to some parts of the API resources, as BEE does not support operations on parallel chains;

· Query headers not blocks (solve problems related to London hard fork)

· Fixed a bug in random checks to cancel trades

· Fixed a bug for unnecessary refreshes of unchanged metrics in Kademlia

other

· Updated ethereum version

· Installation congestion

· Added the function of batch processing library verification

· Published trading apis

· Add endpoints that contain information about batching internal conflicts

· Kademlia metrics can be refreshed in a separate Goroutine in a new way that does not affect connection management over long periods of time.

Swarm test net

Updates and bug fixes are essential for any new software. Swarm's development team is working to address the issues raised by node operators. As always, other updated beta web versions will be released soon, so stay tuned. You can use exclusive & NBSP;Discord channelTo follow these releases. The next mainnet release is usually released after a few tests of the test net. All mainnet versions will be posted on our social media channels.

Running test network nodes is the best way to help build a truly stable and flexible network. Swarm is also available for internal testing if you are running multiple nodes on the test network. Please contact the Bee team at trainspotter@ethswarm.org.

· For technical support and more information about the mainnet version, check out Swarm's Discord channel.