The September Swarm Community Call started with Niki Papadatou and Esad Akar presenting the core updates and setting the stage for an information-packed call.
In the past month, the most notable release was Bee 1.17.4. It features an advanced Bee logging system for the pushsync and the retrieval protocols, vital components responsible for syncing chunks among nodes. Since this is a breaking change, all node operators should update to the latest version of Bee as soon as possible, if they haven't yet.
Other improvements include the introduction of an immutable default batch type, which ensures that any tampering with the node doesn’t accidentally override stored data. Additionally, a new configuration enables a fresh Bee install to initiate the node in ultra-light mode, sidestepping potential errors. On the data upload front, uploads are made to the local Bee node first, rather than directly to the Swarm network.
The main focus of development teams is now on the ongoing hardening phase, while streamlining internal development processes. The transition to a support network for the testnet (move to Sepolia) is also on the agenda.
The price oracle is on the testnet
But the call’s main news was that the long-awaited decentralised price oracle is now in the testing phase. As Callum Toner explained, the oracle aims to ensure that the price of storage in Swarm isn't volatile, preventing sudden spikes or drops that could impact users. Even under extreme conditions, the price cannot more than double in less than a year.
As the network grows and more data is stored, the system will naturally become more stable, allowing for potential adjustments to the oracle's sensitivity.
The primary advantage of this decentralised price oracle is that the storage price in Swarm will be determined purely by its internal supply and demand. Any questions, feedback or observations can be directed at the team on the Swarm Foundation Discord, while you are welcome to read more about the price oracle and its mechanics here.
Making the most out of Swarm
While working with Web3 can be tricky at times, Swarm offers developers a plethora of tools to ease their work. During the call, Noah Maizels delved into the various JS tools available for working with Bee and building on Swarm, as well as providing a sneak peek at tools still under development.
Here are some tools you can already use (check out the GitHub repo too):
- BeeJS: A Node.js package that allows developers to seamlessly interact with a Bee node, bypassing the need to directly interact with an HTTP API.
- Swarm CLI: A command-line tool designed for an intuitive node interaction. A new feature, the “status” command, provides pertinent information about the node's current state.
- Ether Proxy: Tailored for node operators with multi-node setups. It reduces the number of RPC calls preserving resources with providers like Infura.
- Bee Dashboard: Serving as a frontend for the Bee node, the dashboard powers the Swarm Desktop app. New features include the ability to top up and dilute stamp batches and an added tooltip explaining the mutability option.
Tools Under Development:
- Ethercomb: A CLI tool designed to automate the creation of a multi-node Docker setup.
- Etherjot: This tool facilitates the creation and management of blogs on Swarm.
- Gateway Proxy Tool: This tool offers features such as stamp management and enables users to create access to Swarm without having a Bee node.
- Ethercast: Still in its infancy, this tool promises live streaming capabilities directly on Swarm.