<![CDATA[Ethereum Swarm - Medium]]> https://medium.com/ethereum-swarm?source=rss----6491b1f2d8f9---4 https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png Ethereum Swarm - Medium https://medium.com/ethereum-swarm?source=rss----6491b1f2d8f9---4 Medium Sun, 15 Nov 2026 22:54:27 GMT <![CDATA[Goodbye Medium, Follow us on Swarm News]]> https://medium.com/ethereum-swarm/goodbye-medium-follow-us-on-swarm-news-cc8b6c9822ca?source=rss----6491b1f2d8f9---4 https://medium.com/p/cc8b6c9822ca Wed, 24 Jan 2024 12:49:24 GMT 2024-01-24T12:49:24.761Z

Swarm Foundation’s blog started on Medium as our primary platform for posting articles and updates to the Swarm community. It served its purpose well, but now we have shifted to Swarm News, our self-hosted blog.

From this point forward, all new articles and updates will exclusively appear on Swarm News. We will no longer be publishing content on Medium. To ensure you don’t miss out on any important updates, we encourage you to follow us on Swarm News.

Thank you for your continued support!

Goodbye Medium, Follow us on Swarm News was originally published in Ethereum Swarm on Medium, where people are continuing the conversation by highlighting and responding to this story.

]]> <![CDATA[How to Create an NFT and store metadata on Swarm]]> https://medium.com/ethereum-swarm/how-to-create-an-nft-and-store-metadata-on-swarm-c57b39e623b0?source=rss----6491b1f2d8f9---4 https://medium.com/p/c57b39e623b0 Fri, 21 Jul 2023 12:15:11 GMT 2023-07-21T12:15:39.388Z

NOTE: This article was originally published on the official website, blog.ethswarm.org. Readers are encouraged to visit the official blog for the most up-to-date and original content.

TL;DR: This article provides step-by-step instructions on how to deploy, mint and import an NFT using Hardhat, Swarm Desktop App and Metamask. You will learn how to deploy an NFT contract on Gnosis, mint an NFT to your wallet address, store the NFT image and metadata on Swarm, and import your NFT in Metamask. The NFT example repo used in this article is intended to serve as an easy reference that can then be built upon to create collections of NFTs that store their data, decentralised, in the Swarm.

On NFTs

An NFT (Non-Fungible Token) is a type of digital asset that represents ownership or proof of authenticity of a unique item or piece of content, such as artwork, music, videos and even tweets. Unlike fungible tokens, such as cryptocurrencies, which are interchangeable and have the same value, each NFT is unique and can have its own distinct value, based on its rarity, historical significance or popularity. NFTs are typically stored on a blockchain, which provides a decentralised and tamper-proof record of ownership and transaction history. This makes NFTs an exciting new way for creators and collectors to monetise and trade digital assets, while also providing a new level of transparency and authenticity in the digital world.

Prerequisites

Before we get started, make sure you have the following prerequisites:

Deploying an NFT Contract on Gnosis

The first step to creating an NFT is to deploy an NFT contract on Gnosischain. Here’s how to do it:

Clone repository and install packages

Let’s clone the NFT Example repository and install the packages

git clone https://github.com/rampall/nft-example.git
cd nft-example
npm install

Deploy NFT contract

Steps to deploy the NFT contract:

  1. Copy the contents of .env.example in the project root to a new .env file : cp .env.example .env
  2. Create a new account in Metamask and fund it with a small amount of XDAI (XDAI 0.10 is enough) on Gnosischain; this will be your deployment account.
  3. In Metamask, click the three dots next to your account address and select “Account Details”, then “Export Private Key”.
  4. Enter your password and then copy the private key into your .env file after GNOSIS_PRIVATE_KEY=0x (it should have an 0x prefix).
  5. Deploy your contract using the following command: npx hardhat run --network gnosis scripts/deploy.ts
  6. The NFT contract address should be printed in the output message. Copy and paste it into .env after NFT_TOKEN_ADDRESS=0x.

Mint NFT

  1. Start up Swarm Desktop.
  2. Buy a postage stamp batch by following these steps. This should give you a Batch ID.
  3. Copy the Batch ID value into the .env after POSTAGE_BATCH_ID=
  4. Create another new account in Metamask and copy the address into .env after NFT_TO_ADDRESS=0x; this is the address that will receive your NFT.
  5. Mint your NFT using the following command: npx hardhat run --network gnosis scripts/mint.ts

Import NFT

  1. In Metamask, with your NFT_TO_ADDRESS account selected, select network ‘Gnosis Chain’, click NFT then scroll down and select Import NFTs.
  2. Copy the NFT contract address from step 6 into the Address field and input 0 as the Token ID.
  3. You should be able to see your own Beelon Musk NFT in your Metamask wallet; keep it or send it to a friend!
  4. Replace {{0x...}} in this url with your contract address from step x and open the link https://gnosis.nftscan.com/{{0x...}}/0. You should be able to see your Beelon Musk NFT on nftscan!

Congratulations 👏! You’ve successfully created an NFT and stored its metadata on Swarm. You can use this repo as a starting point to create collections of NFTs that store their data, decentralised, in the Swarm.

References

Join Swarm’s community

How to Create an NFT and store metadata on Swarm was originally published in Ethereum Swarm on Medium, where people are continuing the conversation by highlighting and responding to this story.

]]> <![CDATA[Swarm Virtual Summit — Swarm is ready. Ready to grow.]]> https://medium.com/ethereum-swarm/swarm-virtual-summit-swarm-is-ready-ready-to-grow-89ba17cf8dee?source=rss----6491b1f2d8f9---4 https://medium.com/p/89ba17cf8dee Fri, 21 Jul 2023 12:02:48 GMT 2023-07-21T12:02:48.749Z Swarm Virtual Summit — Swarm is ready. Ready to grow.

NOTE: This article was originally published on the official website, blog.ethswarm.org. Readers are encouraged to visit the official blog for the most up-to-date and original content.

Day 1*

As the summer light symbolically vanquished the darkness on 21 June, Swarm network kicked off its three-day Swarm Virtual Summit. This year, the network’s global community gathered in the virtual world, giving all its diverse members a chance to watch and listen to leading voices and keen enthusiasts across different fields on the online stage.

They shared their insights, fresh ideas, and experience relating to Swarm and Web3, creating an engaging event for everyone in the audience. Below is a recap of the first day, which includes the latest network updates, new partnerships and use cases for the network.

Swarm is ready to g(r)o(w)

The entire Swarm Virtual Summit is available here

The summit opened with the latest news in the Swarm network. In the last six months, Swarm has made impressive progress regarding the upgrade and optimisation of its basic infrastructure, along with recalibrated storage prices making running a node profitable, i.e. making the network economically sustainable:

  • Enhanced syncing, multi-stamps per chunk, pinning
  • Phases 3 and 4 finalisation, plus inclusion proofs
  • Reduced freezing in redistribution game
  • Reliable network, 0% error rate for data retrieval

“We have been through every stress test; we’ve already scaled up thousands of nodes in the network; we’ve had doublings; we’ve had everything and that 0% has been maintained,” Callum Toner from the Research Track stressed. And with better syncing, multiple stamps per chunk, pinning of files and more, Swarm provides a stable foundation for a plethora of future use cases, Callum added.

The new edition of the Book of Swarm is out

All that Swarm encompasses is also brought together in the revised and recently fully updated edition of the Book of Swarm, including the upgraded storage incentives mechanism. It details all the inner workings of the network, so if you have any technical questions, the Book of Swarm is the best source to go to.

Help make Swarm even better with SWIPs

Everyone interested in making the Swarm network even better and richer with features is invited to submit a formal proposal in the form of Swarm Improvement Proposals (SWIPs). Every sensible suggestion will be taken up by the research and development teams and put into action.

Impending roll out of the local store and decentralised price oracle

Regarding the near future, Callum pointed out the mainnet roll out of the updated localstore, which will be a breaking release, happening this week. The next big thing coming to Swarm in about five weeks is the decentralised price oracle (Phase 3), which will mark the completion of the core components of the storage incentives mechanism, along with the completion of Phase 4.

New partnerships

During the first day of the summit the Swarm Foundation also announced four new partnerships:

  • DAppNode — A plug-n-play node provider for different blockchain networks. From 1 July, Dappnode will provide invitation codes in every purchased device to run the initial stake required to spin a Bee node.
  • MiPasa — provides verified data for informed decision making. In his brief demo, Jonathan Levi showcased the browser-based app and its effortless integration with Swarm. It will allow researchers and analysts to pull verified models and data directly from Swarm, process and enrich it, and store them back to Swarm, all from their browsers.

Watch video

  • Kiwix — stores and provides internet content for people without internet access. Stephane Coillet-Matillon pointed out the problem of trust that AI will introduce and the need for establishing and verifying trust. In this kind of environment it is also important to have projects like Wikipedia on Swarm that people can trust and reference.

Watch video

  • CleanApp — a global coordination game for waste and hazard mapping. According to Boris Mamlyuk, blockchain is important in this effort because polluters work very hard to keep waste hotspots out of people’s perception and blockchain makes them permanent. CleanApp’s integration with Swarm will help put pollution evidence on a public storage solution where it will be free from tampering and censorship attempts.

Watch video

Talks

Bringing Nextcloud to Swarm

In his talk, Björn Magalhães from MetaProvide discussed the possibilities of how 400,000 of already existing Nextcloud-servers could be used with Swarm for decentralised data-storage, blockchain interaction, and Bee node hosting. The demo focused on how you can connect your self-hosted Nextcloud instance to Swarm and leverage the potential of a decentralised storage network. Also, Nextcloud wallet-login is currently in the works that in the future could take advantage of Swarm’s native token, BZZ.

Watch video

Creating digital hives — a Web3 builder’s toolkit

How create decentralised systems that are value-driven and where positive uses of the system are incentivised? Michal Matlon dissects the nine-part toolkit called The Hivemaker’s Code which is based on the three principles of how living organisms organise themselves: self-organisation (the system creates its own purpose), decentralisation (no subsystem can control other subsystems) and emergent creativity (the system must constantly adapt and create new solutions).

Watch video

Enabling parallel societal structures through decentralised technologies

Joseph Jelacic takes the audience through the genesis of Paralelni Polis, one of Europe’s most prominent cryptoanarchic establishments, its philosophical foundations laid by Vaclav Benda and how they are involved in today’s crypto scene in Europe.

Watch video

Bringing good data to Swarm

The last talk of the day was reserved for Črt Ahlin who presented the Great Data Upload initiative that aims to bring the world’s data to Swarm. Starting with public data, the goal is to preserve popular data, data that is costly to host and data that should be stored in a decentralised manner. Črt presented the tools that can be used to upload the data, the file format used, how to download the data and download limitations.

Watch video

Day 2

On the second day of the Swarm Virtual Summit the talks meandered between real-world examples of how Web3 can improve our world, the exploration of novel concepts like digital integrity and how this technology can be used to fight censorship.

Talks

Swarm — a value-aligned storage layer for the world computer

The first talk of the day was held by Swarm Team Lead, Viktor Trón. In it, he focused on what makes Swarm unique as the data layer for the world computer.

When designing such a layer, architectural decisions are key because they determine how easily it is engineered to the needs of the end user. Broadly, there are three major groups by which such a layer can be evaluated:

  • Data representation (how is data transformed into smaller units and how these form higher level structures relevant to the user)
  • Persistence guarantees (how long and how certain we are that we can access data)
  • Privacy requirements on access (who can access the data and who knows who can access the data)

As Viktor explained, there are commonalities between different contenders that offer decentralised storage, such as slicing data into smaller units, routing and forwarding chunks of data, using different incentives for bandwidth and storage etc. The differences lie in where the data is stored and how routing is implemented.

Strong incentives are key to make the network work in a hands-off mode

Swarm uses a proximity-based storage model, which is supported by a robust incentivisation mechanism that keeps the nodes aligned with the network’s needs. The (positive) incentives are fundamental to this model in which the nodes are seen as profit-maximising agents for whom optimal economic interests coincide with the needs of the network.

Anonymity and practicability

The architectural choices implemented in Swarm also allow behaviours such as “upload and disappear” for devices with limited storage, meaning they can stream data directly into the network. At the same time, relationships between data chunks are concealed, providing anonymity for the owner of the data.

Data is always available and easily reconstructed

The built-in redundancy of the network promotes data availability and flexible data reconstruction and also offers the user the option to configure their levels of risk and security when it comes to errors or even a potential network split.

A wide spectrum of communication options

In addition, there are two serverless communication innovations (feeds and node-addressed messages) in Swarm, which, when used together, are very powerful and enable a whole spectrum of communication, from group chats to encrypted, zero-leak communication systems.

All of this taken together makes Swarm a layer that enables high-level features as well as secure messaging implementations, Viktor concluded.

Watch here

Byzantine-tolerant error correction — a use case for Swarm

Erasure coding is nothing new in providing data redundancy in distributed storage systems. The problem with Byzantine fault-tolerant erasure coding lies in some false assumptions when designing the system. Independent Web3 geek Silur talks about these fallacies and gives his insights how a network like Swarm could build an adversarial-resistant erasure coding system.

Watch here

Are we entitled to digital integrity?

In the current extractive data economy there’s a search for a core human right relating to the digital world. Alexis Roussel from Nym discusses the concept of digital integrity through the lens of the recent Swiss referendum that enshrined it in the constitution. His talk focuses on how digital integrity extends the concept of physical and mental integrity, its relevance for digital self-determination and how it changes and refocuses the privacy narrative.

Watch here

Decentralising musical rights organisations

Today, copyright management organisations (CMO) are centralised, country-based entities that physically store musical scores and audio supports. Matteo Alessio Tambussi discusses his proof-of-concept to create a decentralised registry and payout system based on usage type running on Swarm.

Watch here

Gaming on the blockchain — is it delivering the promises?

Mark Engelhardt from AMG DAO talks about the big promises blockchain gaming introduced into the gaming industry. From full ownership, open economies, interoperable games to trustlessness. But is it delivering?

Watch here

Fixing the food chain

Over 100 million tonnes of perfectly edible food are discarded every year. Balint Drahota demonstrates how the two companies he’s involved in, Essence Food and Fair Food Data, upcycle the available food and help make the logistics chain involved in food distribution much more traceable and transparent.

Watch here

The importance of resisting censorship: how activists can use blockchain as a tool

A panel discussion with Nadya Tolokonnikova (PussyRiot), Mike Bonnano (The Yes Man) and Scott Beibin (Mordechai Tuchasman) moderated by Lou de Kerhuelvez.

Watch here

Day 3

The summit’s last day was a vivid and interesting mix of topics that spanned across AI in blockchain, big brain data NFTs and importance of UX in decentralisation.

Talks

Hey, AI, write my smart contract

Sasha Pitkevich gives an unapologetic talk about what AI today can do for a blockchain delivery team. No magic, no false promises, real facts and examples. Hint: AI is a big help, but it needs a friendly human to help it as well.

Watch here

The challenges of keeping big brain data secure

Are we entering big brain data and does this pose a new security risk? Jurij Dreo from BrainTrip discusses the issue in his talk by looking at how the advent of neuro imaging and data processing technologies, coupled with a dramatic increase in available neuro data, has also increased the potential of its misuse in the future.

Watch here

From normies to degens — a Solarpunk tale

Barbara R. Lőrincz from solarpunk.buzz talks about the guidelines and contemplations that underpin the Solarpunk movement.

Watch here

Minting NFTs from your WordPress archive with Kredeum

Alain Papazoglou and Philippe Pérou from Kredeum demonstrate how WordPress users can plug their WordPress archive to the Swarm network and easily mint and sell NFTs in a personally curated marketplace.

Watch here

Making NFTs unstoppable on Swarm

NFTs and their metadata are usually at risk of being lost when stored on centralised solutions. Alexander Shedogubov from Envelope DAO shares their solution on how to create a semi-public service of pinning NFTs to Swarm by creating a mechanism that will allow NFT owners to easily request node operators to pin their files to Swarm for them.

Watch here

Exploring Ethereum transactions with Blobscan

When Ethereum introduced the EIP-4844 it changed the transaction format which allows for a much bigger block data field, called a blob. In his talk, Gabi demonstrated Blobscan, the first blob explorer of its kind and one that uses Swarm to store blob data.

Watch here

Etherna: redefining video sharing with decentralisation, transparency, and uncensorable contents

Sergio Marchese demonstrates Etherna, a decentralised, zero-data and censorship resistant video platform. Etherna is centred around empowering community content creation and curation based on fair incentives for content producers and users.

Watch here

From S3 to Swarm — less friction more decentralised storage

To encourage more people to adopt decentralised storage, we need to eliminate key friction points from the onboarding and migration process. Sam Lauridsen from Protobox unveils their S3 API gateway for Swarm that removes a lot of friction from adding Swarm’s decentralised storage to your toolbox.

Watch here

Increasing decentralisation capability through UX

Achieving decentralisation is not easy. But we can dramatically increase the ability to decentralise a system with great UX. Pol Lanski from DappNode explains how and why UX is crucial in this role.

Watch here

  • All talks are not yet available in the archive. The blogpost will be updated once they are.

Join Swarm’s community

Swarm Virtual Summit — Swarm is ready. Ready to grow. was originally published in Ethereum Swarm on Medium, where people are continuing the conversation by highlighting and responding to this story.

]]> <![CDATA[State of the Network — June 2023]]> https://medium.com/ethereum-swarm/state-of-the-network-june-2023-446d70019a09?source=rss----6491b1f2d8f9---4 https://medium.com/p/446d70019a09 Fri, 21 Jul 2023 12:00:44 GMT 2023-07-21T12:00:44.393Z State of the Network — June 2023

NOTE: This article was originally published on the official website, blog.ethswarm.org. Readers are encouraged to visit the official blog for the most up-to-date and original content.

The last few months have been a transformative time for Swarm. Development is progressing on multiple fronts, and the hard work of the research and development teams is reflected by network growth and performance improvements. In this article we discuss the state of the network on multiple fronts. We’ll kick things off with an overview of Swarm network economics and network growth. In the next section we will tackle the issue of network capacity, and to wrap things up we’ll take a closer look at how the recent developments on the Bee client have led to advances in network performance.

Swarm Network Continues to Mature

The rollout of Swarm’s storage incentives system has been ongoing since late 2022. Starting in February 2023 there was a dramatic increase in storage incentives which has made it financially viable for node operators to start contributing their services. Over the last two months the network has grown from only 1000 nodes participating in staking to over 2700! Geographically these nodes span the entire globe, including countries in Asia, Europe, Australia, and North and South America. There are currently 30,792 in staked xBZZ amongst all these nodes, and a total of approximately 60,000 xBZZ has been paid out in incentives since the incentives system went live.

Reward Statistics Overview

The Swarm research team is still in the process of defining the methodology for calculating expected return rates for Swarm node operators. The team has provided some data relating to node operator earnings, however these data have many limitations and should not be interpreted as being predictive for any prospective node operators, or used for planning of business operations, and are merely provided for educational purposes. These data were collected from nodes monitored by the Swarm research team, and it excludes nodes which did not win any xBZZ.

March, 2023Total Wins in xBZZ (per node)Min3.9141st Quartile6.410Median12.531Mean14.9573rd Quartile18.959Max73.165April, 2023Total Wins in xBZZ (per node)Min5.9931st Quartile6.326Median12.531Mean13.9213rd Quartile18.869Max100.823May, 2023Total Wins in xBZZ (per node)Min5.8641st Quartile6.354Median12.508Mean14.2963rd Quartile18.948Max107.420

Data collected from https://swarmscan.io/

Network Performance Improvements

Parallel to the ongoing rollout of the storage incentives system, the Swarm dev team has also been working at improving other aspects of Swarm network performance. Some of the most significant improvements are those related to the push-sync, pull-sync, and retrieval protocols which make up the technical infrastructure responsible for uploading and downloading data from the Swarm network. The teams’ work is reflected in the most recent performance metrics measuring error rates as well as download / upload speeds.

Let’s take a look at exactly how all those changes have actually affected network performance. Based on metrics collected by the Bee dev team, there have been major improvements in network performance over the month of May. Starting with upload speed — in April the average upload speed was 187 kbps, while in May it increased to 1700 kbps, an almost tenfold increase! The download error rate has also decreased to practically zero since the 1.16.0 update from mid-May. Download speeds have not changed significantly, but have remained at a stable speed of close to 450 kbps. For an average website of around 2000 kb, it would take a little over one second to complete an upload, and from four to five seconds for a download.

April Smoke Test

May Smoke Test

Moving Forward

Make sure to follow Swarm on Twitter to get the latest development and ecosystem updates, and join the Discord channel to get in on the conversation. And don’t forget to mark your calendar for the upcoming Swarm summit!

Join Swarm’s community

State of the Network — June 2023 was originally published in Ethereum Swarm on Medium, where people are continuing the conversation by highlighting and responding to this story.

]]> <![CDATA[Anticipating the buzz: The return of the Swarm Virtual Summit]]> https://medium.com/ethereum-swarm/anticipating-the-buzz-the-return-of-the-swarm-virtual-summit-f8247ff7b97d?source=rss----6491b1f2d8f9---4 https://medium.com/p/f8247ff7b97d Fri, 09 Jun 2023 13:15:40 GMT 2023-06-09T13:15:40.523Z

NOTE: This article was originally published on the official website, blog.ethswarm.org. Readers are encouraged to visit the official blog for the most up-to-date and original content.

The wait is over: the return of the Swarm Summit

It has been three long years since our last gathering in the vibrant city of Madrid, where ideas sparked, connections were made, and the Swarm community came together. So it is with great pleasure to be able to announce that the Swarm Virtual Summit is back on our calendars. From 21 to 23 June the Swarm community will get together in a virtual setting for three days packed with knowledge, collaboration and just a touch of excitement.

Sharing is caring — workshops, talks, announcements, and more

The summit will feature an array of experts, enthusiasts and trailblazers who are ready to share their insights, experience and visions for the future of Swarm. From hands-on workshops to engaging talks, from surprise announcements to cosy fireside chats — it’s all there.

Embrace the Swarm

The Swarm Virtual Summit is an opportunity for you to engage, learn and collaborate with other members of the community. The emphasis is on fostering a space where ideas can flow freely, and where every voice can be heard. Whether you’re a seasoned code creator or just a curious newcomer, you’re sure to find something that will pique your interest and broaden your understanding of Swarm.

The countdown has begun

As the countdown to the summit begins, you’re invited to join us in the excitement. Swarm has come a long way since Madrid and has a bright future ahead. Become part of the Swarm as we chart the course for the future together.

We look forward to seeing you there!

Join Swarm’s community

Anticipating the buzz: The return of the Swarm Virtual Summit was originally published in Ethereum Swarm on Medium, where people are continuing the conversation by highlighting and responding to this story.

]]> <![CDATA[Monthly Development Update — May 2023]]> https://medium.com/ethereum-swarm/monthly-development-update-may-2023-6f7fba3e1e74?source=rss----6491b1f2d8f9---4 https://medium.com/p/6f7fba3e1e74 Tue, 06 Jun 2023 07:31:07 GMT 2023-06-06T07:31:07.158Z Monthly Development Update — May 2023

NOTE: This article was originally published on the official website, blog.ethswarm.org. Readers are encouraged to visit the official blog for the most up-to-date and original content.

The Swarm network was abuzz with activity in May and there’s a lot of ground to cover, so let’s dive right in. The Bee Track has released versions 1.15.0 and 1.16.0, introducing new features and several improvements. In version 1.15.0, a new pushsync feature has been introduced to improve chunk syncing and replication during uploading. Other enhancements include improved blocklist display, storage radius adjustment, chainstate total amount, and peer mode added to the status protocol, and reduced workload during initial historical syncing.

Version 1.16.0 introduces “salud”, a health check system for connected peers using data acquired from the status protocol. A self-check is also in place where if the node’s own storage radius does not match that of the network, the node won’t participate in the Schelling game. Version 1.16.0 brings a breaking change where the status protocol includes the reachability of a peer and the total batch commitment of the network reported by each peer.

This version also addresses a bug and eases the requirements of the pushsync protocol for improved performance. The patch release v1.16.1 fixes a panic in the salud service and introduces a health service for monitoring the effects & storage incentives. This moves the network towards getting realistic hardware requirements. Progress has been made on the inclusion proof for Phase 4, with testing in the final stages.

Research Track saw the completion of the Storage Incentives paper and diagrams, which are now out for community feedback. Notably, DISC specs are also in their final version. The Phase 4 testing environment is being prepared to release Phase 4, and work on erasure coding documentation and graphical statistics representation is progressing.

In JS Track, Bee JS v6.0.0 was released, introducing streaming upload support for single files and numerous bug fixes, including the one causing incompatibilities between Node versions 16, 18 and 19. Swarm Desktop v0.25.0 was upgraded to the latest Bee v1.16.1.

Fair Data Protocol updates include some notable novelties. FairOS now supports ChatGPT plugin and has moved to Sepolia testnet. The Fairdrive Web App has seen significant improvements and enhancements and the Fairdrive Desktop App saw the release of v0.1.6. Blossom version 0.4.0 is already available in the Chrome Store.

DevOps Track created a 1,000-node private cluster for testing and released Beekeeper (0.12.3).

Big news on the DevRel side. New and updated Swarm documentation is out. It’s more comprehensive and user-friendly than the previous editions and is aimed at anyone who wants to take a deep dive into the world of Swarm. The latest addition to our resources is the Bee Node Hardware Requirements and Performance Benchmarking Guide, now available on the Swarm. It’s a great read for anyone looking to benchmark their node. A new Mandarin language section was also added to Swarm News to bring Swarm closer to audiences in China. Etherjot has received various improvements to make it more potent.

Tracks

Bee Track

Released 1.15.0

  • With this release, we introduce a new pushsync feature to improve chunk syncing and replication in the network during uploading. Peers that forward chunk into the neighbourhood will fire multiple requests to target multiple storer nodes. Forwarding will also terminate at the first peer within the neighbourhood and will no longer be forwarded to the closest peer within the network.

Breaking changes

  • Pushync forwarding nodes one hop from the neighbourhood multiplexes the chunk to multiple storer nodes in the neighbourhood. Forwarding terminates at the first neighbour.

Hardening

  • Blocklist endpoint now correctly displays the mode and reason for the blocklisting of the peer.
  • Storage radius decreasing based on reserve size increased back to the 50% threshold.
  • Chainstate total amount and peer mode added to the status protocol.
  • Connecting light nodes are not rejected based on bin size.

Performance improvements

  • Initial historical syncing is limited to reduce workload.
  • Peer skiplist mechanism in retrieval and pushsync protocols now prune peers in a much more efficient way.
  • For a full PR rundown, please consult the v1.15.0 diff.

Released v1.16.0

With salud, nodes will periodically perform certain health checks on their connected peers with data acquired from the status protocol. The checks as of this release are based on the duration of response to the status protocol msg, number of connected peers, the storage radius, and total batch commitment as computed by each peer. For duration and number of connected peers, each peer must be within the 80th percentile to be deemed healthy. Radius and batch commitment are measured in terms of the most common values as reported by each connected peer. Measurements are created anew for each periodic health check. A self-check is also in place where, if the node’s own storage radius does not match with the rest of the networks’, the node won’t participate in the Schelling game. With this release, only the pushsync protocol utilises the filtering of peers for requests based on the health status.

Breaking changes

  • The status protocol now includes the reachability of a peer and the total batch commitment of the network reported by each peer.

Bug fixes

  • Fixed the last played round field in the redistribution state endpoint to report the current round instead of the previous round.

Hardening

  • Loosened the requirements of the pushsync protocol so that when a neighbourhood is down or does not exist, the chunk is pushed as close as possible to its neighbourhood.
  • Increased the wake up interval for the depth monitor from 5 to 15 minutes.

Released v1.16.1

  • This one is a patch release to address a bug found in the new salud service.
  • Bug fixes: Fixed a panic in the salud service when the response to the status request is terminated early by the peer.
  • Health service released, monitoring the effects & storage incentives: this is progress towards getting realistic hardware requirements and putting any missing rules in place.
  • Phase 4 inclusion proof is in the final stages of testing & then looking for a release window on/after localstore dates.
  • Localstore testing begins on large cluster.

Research Track

  • The Storage Incentives paper and all diagrams are complete and out for feedback to the community.
  • Investigations into freezing/sampling problems and other edge cases.
  • DISC specs & SI paper in final version.
  • The Phase 4 testing environment is coming along to test and be able to release Phase 4.
  • Erasure coding documentation and graphical stats and representation progressing (discovery phase).

JS Track

Bee JS v6.0.0

  • Adds streaming upload support for single files.
  • Fixes a segmentation fault when running tests in a project where bee-js is a dependency.
  • Fixes incompatibilities between Node versions 16, 18 and 19.
  • Fixes an issue with directory and website uploads, where the resulting tar file had more zero-byte padding than standard, causing a connection reset from Bee’s side.
  • Fixes a bug where projects could not be installed as root where bee-js is a dependency.
  • Fixes a bug related to code splitting, causing frontend projects built with webpack not being able to fully load bee-js.
  • Can now be built with slim Docker images, Python is no longer a dependency during project build.
  • Swarm Desktop v0.25.0
  • Upgrades Bee to the latest version (1.16.1).

Ecosystem

Fair Data Protocol

Blossom

fdp-storage

FairOS

Fairdrive Web App

Fairdrive Desktop App

Fair Portal

DevOps Track

  • Created 1000-node private cluster for testing session for Bee team.
  • Beekeeper 0.12.3 released.
  • Deployed 1.16.1 Bee to testnet and mainnet.
  • Setup internal Sepolia node for testnet.

DevRel

Docs update

Educational content

Swarm Community Call

  • Swarm Community Call, our main monthly online event, was held on 25 May. You can read a recap blog post about it here.

Apps:

Etherjot

  • Improves the overall design of the generated blog.
  • Adds optional search functionality.
  • Adds optional newsletter functionality.
  • Adds many customisation options, such as header and footer description, social links, link to external website, etc.
  • Adds option to promote blog posts on the front page.
  • Images are now also part of the Mantaray and not hosted as separate files.

Gateway Proxy

  • Improvement, rebranding, usage with Docker and ngrok. Gateway Proxy is in the shadows and has bad UX. By fixing the UX and showing multiple ways of using it, we could elevate it from its current state.

Upcoming events

  • Swarm Virtual Summit — Call for Papers — Are you using Swarm to supercharge your project? Then submit a proposal for a talk at Swarm Virtual Summit, which will take place from 21 to 23 June. Due date for proposals is 5 June. Target format: 30 minutes in total — 20-minute presentation followed by Q&A or a 45-minute workshop.
  • Join the hive and submit your talk proposal.

Monthly Development Update — May 2023 was originally published in Ethereum Swarm on Medium, where people are continuing the conversation by highlighting and responding to this story.

]]> <![CDATA[Bee Node Hardware Requirements and Performance Benchmarking Guide]]> https://medium.com/ethereum-swarm/bee-node-hardware-requirements-and-performance-benchmarking-guide-56893210034f?source=rss----6491b1f2d8f9---4 https://medium.com/p/56893210034f Mon, 22 May 2023 12:27:23 GMT 2023-05-22T12:27:23.361Z

NOTE: This article was originally published on the official website, blog.ethswarm.org. Readers are encouraged to visit the official blog for the most up-to-date and original content.

Over the last several months the Bee dev team has been hard at work with the rollout of the storage incentives system which will ensure that node operators who share their disk space with the network will get rewarded. Along the way the dev team has been continually testing various aspects of the health of the network and monitoring community feedback in order to diagnose any issues. One issue which has come up is that of node performance. Some node operators may be missing out on earning storage incentives due to insufficient hardware performance. To address this issue, we’ve put together this guide for benchmarking node performance so node operators can make sure that their nodes are running optimally.

Recommended Bee Node Hardware Specifications

Due to a wide variety of variables affecting node performance including different processor architectures, manufacturers, operating systems, network environments, and much more, any hardware recommendations are just a rough guide, and it is important to perform benchmarking tests to find out if your node specifications are sufficient.

Recommended specs for each Bee node:

  • Recent generation 2ghz with 2 cores
  • 8gb RAM
  • 30gb SSD (HDD strongly discouraged)
  • 10mbps upload / download speed

Performance Benchmarking Step by Step:

First check that your network download and upload speeds are above 10mbps

sudo apt install speedtest-cli
speedtest

Next check whether hardware performance is sufficient. The sampler process is the main performance affected process for Bee nodes. It is the process where the node takes a sample of data from its reserve and calculates a hash as a part of the storage fee redistribution process. The process may fail or time out if the node’s hardware specifications aren’t high enough. If a node is able to complete the sampler process in under 6 minutes, then its performance should be sufficient. To check a node’s performance the /rchash/{depth}/{anchor} endpoint of the API may be used.

Before proceeding, first check that the node is fully synced, is not frozen, and has sufficient funds to participate in staking. To check node sync status, call the redistributionstate endpoint:

curl -X GET http://localhost:1635/redistributionstate | jq

Response:

{
 "minimumFunds": "18750000000000000",
 "hasSufficientFunds": true,
 "isFrozen": false,
 "isFullySynced": true,
 "phase": "commit",
 "round": 176319,
 "lastWonRound": 176024,
 "lastPlayedRound": 176182,
 "lastFrozenRound": 0,
 "block": 26800488,
 "reward": "10479124611072000",
 "fees": "30166618102500000"
}

Confirm that hasSufficientFunds is true, and isFullySynced is true before moving to the next step. If hasSufficientFunds if false, make sure to add at least the amount of xDAI shown in minimumFunds (unit of 1e-18 xDAI). If the node was recently installed and isFullySynced is false, wait for the node to fully sync before continuing. After confirming the node’s status, continue to the next step.

The {anchor} value can be set to any random string. To get the {depth} value, first call the topology debug API endpoint using jq to filter for the depth `value:

sudo curl -sX GET http://localhost:1635/topology | jq '.depth'

Output: 8

Call the endpoint using the value returned (8 in our example) like so:

sudo curl -X GET http://localhost:1633/rchash/8/randomstring | jq

If the sampler runs successfully, you should see output like this:

% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                Dload  Upload   Total   Spent    Left  Speed
100   659  100   659    0     0      3      0  0:03:39  0:02:54  0:00:45   161
{
 "Sample": {
   "Items": [
     "000003dac2b2f75842e410474dfa4c1e6e0b9970d81b57b33564c5620667ba96",
     "00000baace30916f7445dbcc44d9b55cb699925acfbe157e4498c63bde834f40",
     "0000126f48fb1e99e471efc683565e4b245703c922b9956f89cbe09e1238e983",
     "000012db04a281b7cc0e6436a49bdc5b06ff85396fcb327330ca307e409d2a04",
     "000014f365b1a381dda85bbeabdd3040fb1395ca9e222e72a597f4cc76ecf6c2",
     "00001869a9216b3da6814a877fdbc31f156fc2e983b52bc68ffc6d3f3cc79af0",
     "0000198c0456230b555d5261091cf9206e75b4ad738495a60640b425ecdf408f",
     "00001a523bd1b688472c6ea5a3c87c697db64d54744829372ac808de8ec1d427"
   ],
   "Hash": "7f7d93c6235855fedc34e32c6b67253e27910ca4e3b8f2d942efcd758a6d8829"
 },
 "Time": "2m54.087909745s"
}

If the Time value is higher than 6 minutes, then the hardware specifications for the node may need to be upgraded.

If there is an evictions related error such as the one below, try running the call to the /rchash/{depth}/{anchor} endpoint again:

error: "level"="error" "logger"="node/storageincentives"
"msg"="make sample" "error"="sampler: failed creating sample:
sampler stopped due to ongoing evictions"

While evictions are a normal part of Bee’s standard operation, the event of an eviction will interrupt the sampler process.

If you are still experiencing problems, you can find more help in the node-operators Discord channel (for your safety, do not accept advice from anyone sending a private message on Discord).

Bee Node Hardware Requirements and Performance Benchmarking Guide was originally published in Ethereum Swarm on Medium, where people are continuing the conversation by highlighting and responding to this story.

]]> <![CDATA[Build on Swarm: How to Run a Bee Node for Testing and Development]]> https://medium.com/ethereum-swarm/build-on-swarm-how-to-run-a-bee-node-for-testing-and-development-a8c1e98a7329?source=rss----6491b1f2d8f9---4 https://medium.com/p/a8c1e98a7329 Mon, 22 May 2023 12:24:28 GMT 2023-05-22T12:24:28.187Z

NOTE: This article was originally published on the official website, blog.ethswarm.org. Readers are encouraged to visit the official blog for the most up-to-date and original content.

Running a Bee node is essential for building decentralized applications on the Swarm network. However, as a developer, it is often convenient to work in an environment where interactions with the node/network can be tested rapidly and without putting the node’s storage data or the user’s tokens at risk.

In this article, we’ll explore three safe and risk-free options available for developers to simulate a Bee node running on Swarm primarily for testing and development:

  1. Run Bee in developer mode
  2. Run a local network with Bee Factory
  3. Run a local network with FDP Play

Whether you’re a beginner or an experienced developer, these options will help you get started with Swarm quickly. So let’s dive in!

Option 1: Run Bee in Developer Mode

When a Bee node is run in developer mode, it creates an instance with volatile persistence and mocked backends which makes this mode highly advantageous for experimenting and testing out various Bee node features. Any changes made to the node’s state are temporary and discarded when the node is stopped. As a result, there is no impact on real-world data or assets, making this mode an ideal option for developers looking to experiment with the Bee node.

Prerequisites

  • Ports 1633 and 1635must be free and available

Step 1: Install bee on your system

  1. Using the Installer packages
  • Ubuntu/Debian (*.deb)
  • CentOS (*.rpm)
  • MacOS (brew)

2. Use the installer script which automatically detects your execution environment and installs the latest stable version of bee on your computer

  • Linux (bee-linux-*)
  • MacOS (bee-darwin-*)
  • Windows (bee-windows-*)

3. Build from source on all systems.

You can download the most recent bee packages here: https://github.com/ethersphere/bee/releases/latest

Step 2: Start Bee in dev mode

Open a terminal window and run:

bee dev

 (                      *        )  (
 )\ )                 (  *    ( /(  )\ )
(()/(   (    (   (    )\))(   )\())(()/(   (
 /(_))  )\   )\  )\  ((_)()\ ((_)\  /(_))  )\
(_))_  ((_) ((_)((_) (_()((_)  ((_)(_))_  ((_)
 |   \ | __|\ \ / /  |  \/  | / _ \ |   \ | __|
 | |) || _|  \ V /   | |\/| || (_) || |) || _|
 |___/ |___|  \_/    |_|  |_| \___/ |___/ |___|


Starting in development mode

"time"="2023-03-08 13:55:59.008839" "level"="info" "logger"="node/localstore" "msg"="database capacity" "chunks"=1000000 "~size(GB)"=20.29025
"time"="2023-03-08 13:55:59.008726" "level"="info" "logger"="node" "msg"="starting debug api server" "address"="[::]:1635"
"time"="2023-03-08 13:55:59.022163" "level"="info" "logger"="node" "msg"="starting api server" "address"="[::]:1633"

Great! Our bee node is now running in dev mode. You can now safely interact with all of its API endpoints. Any changes to the node’s state resulting from your interactions will only be persisted to volatile memory.

Option 2: Run a local network with Bee Factory

Bee Factory offers a complete solution to simulate an entire Swarm Network on your machine. Bee Factory is a CLI tool used to spin up a Docker cluster of Bee nodes as well as a test Blockchain for advanced testing and development.

Prerequisites

  • Docker must be already be installed
  • node >= 16
  • Ports 1633 and 1635 must be free and already, but blocked from external connections

Step 1: Install Bee Factory

npm install -g @ethersphere/bee-factory

Step 2: Using Bee Factory

Spin up the cluster for a specific Bee version and attach to the Queen container and display its logs (Press Ctrl+C to stop):

bee-factory start 1.13.0

Or spin up the cluster for a specific Bee version, detach and exit:

bee-factory start --detach 1.13.0

Stop a running bee cluster:

bee-factory stop

To delete existing containers while switching versions, you can use the –-fresh flag:

bee-factory start 1.13.0 --fresh

To list all available subcommands:

bee-factory --help

To list help content for a specific subcommand:

bee-factory <subcommand> --help

You can check out https://github.com/ethersphere/bee-factory for more information on bee-factory.

Option 3: Run a local network with FDP Play

Fair Data Protocol (FDP) is a data interoperability protocol and a layer 2 solution built on top of Swarm. It promotes self-sovereignty and privacy for dApps that use personal data in the decentralised cloud.

Much like bee-factory, FDP Play is a CLI tool used to spin up a local development FDP environment with Docker. It includes a ganache blockchain for testing, a Docker cluster of bee nodes as well as a FairOS instance.

Prerequisites

  • Docker must be already installed
  • node >= 16
  • Ports 1633, 1635 and 9090 must be free and available

Step 1: Install FDP Play

npm install -g @fairdatasociety/fdp-play

Step 2: Using FDP Play

Start a bee cluster using the latest supported Bee version:

fdp-play start

Attach to the Queen container and displays its logs:

fdp-play logs queen --follow

Stop the cluster (container data persists between restarts):

fdp-play stop

Clear all data (fresh) and pull latest docker images:

fdp-play start --pull --fresh

Spin up the cluster using the specified blockchain image:

fdp-play start --detach --blockchain-image fairdatasociety/fdp-play-blockchain

You can check out https://github.com/fairDataSociety/fdp-play for more information on fdp-play.

What is next?

Now that we’ve explored three risk-free ways to get a bee node running for testing and development, it’s time to start interacting with it and building on the Swarm network. The Bee JS SDK and its documentation is a great place to get started.

Check out our growing list of free and open-source projects related to Swarm and its ecosystem. Join the #develop-on-swarm channel on Discord to connect with other developers in the Swarm community. If you have a great idea that can make an impact, consider applying for a grant. The Swarm is waiting for you!

Build on Swarm: How to Run a Bee Node for Testing and Development was originally published in Ethereum Swarm on Medium, where people are continuing the conversation by highlighting and responding to this story.

]]> <![CDATA[Swarm Community Call, 27 April — Recap]]> https://medium.com/ethereum-swarm/swarm-community-call-27-april-recap-96218fc8096?source=rss----6491b1f2d8f9---4 https://medium.com/p/96218fc8096 Mon, 22 May 2023 12:24:00 GMT 2023-05-22T12:24:00.099Z Swarm Community Call, 27 April — Recap

NOTE: This article was originally published on the official website, blog.ethswarm.org. Readers are encouraged to visit the official blog for the most up-to-date and original content.

The April Swarm Community Call was focused on tools that provide a more numbers-based look at the Swarm network, and on easy publishing of unstoppable content on Swarm.

In the introductory part of the call, Callum Toner first shared some network-wide updates that will be released in the coming days and weeks. Bee version 1.15 has been released, which addresses some of the known optimisations. This has resulted in the new version having a current error rate of 0%, with > 83% of the network size. You can also expect the introduction of new hardware, network & system and requirements for entering storage incentives.

On the research side, the final PRs have been drafted for the localstore rewrite and is currently being tested in a 1000-node private test environment to get a better insight into its behaviour

A test environment is also being set up for Phase 4 of the storage incentives roadmap as well, alongside ongoing research into the price oracle and how it performs in conjunction with storage incentives in a test environment.

The Schelling game statistics data is now available along with wider network figures

The call was also an opportunity for Gyuri Barabás to introduce a new statistics tool for the Swarm network. The tool provides a variety of data about the Schelling game. This includes data on revealers, distribution of skipped rounds, rewards, notes and stakes. With this tool, you can retrieve historical in-depth data, such as the total amount of rewards paid out in a specific neighbourhood, a custom period for the range of rounds, the number of winning events, the average number of revealers per neighbourhood, the neighbourhood depth…

The tool is particularly useful for node operators, who can use it to optimise their reward strategy. If you have suggestions or ideas on what else could be added to the tool, you can leave him your feedback in the Swarm Foundation Discord.

All data analysed by the new tool is gathered from Swarm scan, a complementary tool initially developed for Swarm’s internal needs. As Janoš Guljaš explained, Swarm scan is basically a stripped-down node that acts as a network scrapper. It collects network data and presents it in a structured way, either as a web page or as HTTP API.

Swarm scan provides a visual representation of the network via a world map and the connections between nodes on that map. You can also quickly see the number of active nodes, new nodes, new staking nodes, the amount of staked value and the storage price. Note that the data here is only a rough estimate due to the size of the network.

While the website provides limited data, what the API provides is much more diverse (see the API description for more information). You can get **a list of the nodes in the network, information about a particular node, the user agent, whether a node has changed from light to full and even get the complete dump of the network **for offline analysis.

If you want to optimise your reward strategy, mfw78, a member of the Swarm Foundation’s Discord community, has developed a tool for mining overlay addresses. It allows node operators to participate in the Schelling game in different network neighbourhoods and thus optimise their performance. You can find the recommended article with instructions here.

Unstoppable content on Swarm with Etherjot

In the second part of the call, it was time for Áron Soós to demonstrate Etherjot, a CLI tool for creating blogs and publishing markdown files as articles, a first such tool for Swarm. It uses a small set of simple commands to manage blogs and supports importing existing blogs written in Jekyll or Hugo. Áron announced four more features for the near future, including: design and layout customisation, decentralised commenting, searching through the blog content, and multiple blog management.

Join Swarm Summit from 21–23 June

After a two-year covid-induced hiatus, Swarm Summit is also back on the agenda, albeit in an online format. If you are using Swarm to power your project, click on the link above and submit a paper. From 21–23 June 2023, you can present your work to the Swarm community. The talks can be about anything Swarm-related — a tool or dApp that uses Swarm, a deep dive into one of Swarm’s features, or even an inspirational talk.

We look forward to seeing you there, and you can also join us live at one of the viewing parties happening in real life. More information will be announced at the next Swarm Community Call on 25 May.

The next Swarm Community Call will be held on 25 May at 17.00 CET on the Swarm Foundation Discord (add to calendar). Already have a question for the teams building the Swarm network? Send them a question by using this online form.

We are looking forward to seeing you there!

Swarm Community Call, 27 April — Recap was originally published in Ethereum Swarm on Medium, where people are continuing the conversation by highlighting and responding to this story.

]]> <![CDATA[Monthly Development Update — April 2023]]> https://medium.com/ethereum-swarm/monthly-development-update-april-2023-f034577e26ae?source=rss----6491b1f2d8f9---4 https://medium.com/p/f034577e26ae Mon, 22 May 2023 12:17:25 GMT 2023-05-22T12:17:25.469Z Monthly Development Update — April 2023

NOTE: This article was originally published on the official website, blog.ethswarm.org. Readers are encouraged to visit the official blog for the most up-to-date and original content.

In April, the Bee Track laid out the blueprint for the upcoming releases of the Bee client to fix the issues uncovered in their investigation. The localstore rewrite project is in its final phase before testing, which is expected to begin in the coming weeks. The Bee Track team are also working on the requirements that nodes must meet in order to participate in the storage incentives game.

During this time, the Research Track has refined its statistics and information gathering and is now working on improving security and multisig procedures.

The JS Track released a new Swarm Desktop version and is preparing for the latest bee-js 6.0.0 release.

The entire Fair Data Protocol stack underwent some important changes as well, including a batch of changes to the Fairdrive Web App, the launch of the Fair Portal and a new release of the Blossom browser extension that fixes several issues and adds new functionality.

Shifting to the community side, the Bee installation section is now more user-friendly, and an accompanying blog explaining how to easily run a Bee node for testing and development is available on the official Swarm blog. There are also a couple of active bounties still in progress (here & here).

Mark 21 June on your calendar, because that’s when the Swarm Foundation will hold the three-day Swarm Virtual Summit. If you are using Swarm to power your project, submit a paper and present your work with a talk. More details will be revealed at the next Swarm Community Call on 25 May, so make sure to join. In the meantime, you can keep yourself busy with Daniel A. Nagy’s presentation from Ethereum Zürich, titled “Storage Incentives in the Swarm Network”.

Tracks

Bee Track

  • There was the 1.15 release which tackled some of the known optimisations we identified after our investigation into the network’s health and retrieval in the previous week. This has resulted in a 0% error rate currently, with >83% of the network size on the new version.
  • The localstore rewrite has its last few PRs drafted and is currently being tested in a suitable environment. We also now have a larger scale 1000 node private testing environment for better insight into its behaviour.
  • The requirements for nodes and the storage incentives have been identified.

Research Track

  • Improving our statistics outlook and information, including that of the skipped rounds and frozen nodes reasoning.
  • The Storage Incentives paper has been completed and shared with the community on Discord and close peers, and we are in the process of receiving critical feedback.
  • Phase 4 testing environment and claim phase logic involved in this.
  • Upgraded security and multisig implementation are complete; reviews and additions pending.

JS Track

Ecosystem

Fairdrive Web App

Fair Portal

  • Fair Portal frontend was released, which is a catalogue of apps that use FDP protocol and are aligned with Fair Data Principles. Developers can submit and add their apps.

Blossom

FairOS

Fairdrive Desktop App

Finished bounties:

Other updates

DevOps Track

  • Deployed Bee to the mainnet (v1.14.1).
  • Released the Beekeeper (v0.12.1).

DevRel

Ethereum Zürich

Docs update

Educational content

Swarm Community Call

  • Swarm Community Call, our main monthly online event, was held on 27 April.

Apps: Etherjot

  • Etherjot allows you to effortlessly create a blog on Swarm. In the latest release, support for importing existing Jekyll or Hugo blogs has been added.

Upcoming events

  • Swarm Community Call — our main monthly online event, will take place on 25 May at 17:00 CET in the Swarm Foundation Discord (add to calendar). Meanwhile, you are welcome to send any questions you might have for the teams building the Swarm network by using this online form for them to be addressed on the call.
  • Swarm Virtual Summit — Call for Papers — Mark 21 June on your calendar, because that’s when the Swarm Foundation will hold the three-day Swarm Virtual Summit. More details will be revealed at the next Swarm Community Call on 25 May, so make sure to join.

Monthly Development Update — April 2023 was originally published in Ethereum Swarm on Medium, where people are continuing the conversation by highlighting and responding to this story.

]]>