Swarm Proof-of-Concept Release 3 Announced
The Swarm team is pleased to announce the immediate release of Swarm client v0.3, the third proof-of-concept release (POC3) of the Ethereum Swarm client. The POC3 code has now been merged into the official code. Master branch of go-ethereum repository.
Swarm 0.3 has been deployed on the public testnet and the Ethereum Foundation is running a 50-node robust cluster of Swarm nodes along with a public web gateway. https://swarm-gateways.net. we welcome everyone try it out Or commit to operating a stable node.
yesteryear
It’s been a year and a half since the first release of the POC2 series was distributed, The Swarm project has launched its public alpha network.. two swarm summittwo orange paper and 40,000 lines of code Time to stock up later.
The Swarm team has grown in size over the last year and we are now hard at work delivering our vision. We’ve been busy redesigning the network layer, rewriting the discovery protocol using stream abstraction, rewriting connection management and overlay network code, and developing sophisticated technologies. Network Simulation Framework Test algorithmic correctness, scalability, and fault tolerance of various subsystems. POC3 code was completed on time. Swarm Orange Summit in Ljubljana80 participants took part and had a very inspiring and creative week (Watch this 2-minute video hosted on Swarm.) explains dialogue and coding. It’s impressive to see it growing more and more. contributor and Companies that want to build on Swarm.
Swarm 0.3
Storing Swarm content is more than just “BitTorrent on steroids.” Technical details can be found here: chapter on architecture new and improved Swarm Guide. A more thorough academic presentation of Swarm’s components can be found at: orange paper Or learn more about Swarm by: recorded conference speech.
to Previous blog postintroduced the basics of Swarm storage and content distribution.
Basically, Swarm is a service that provides an API to upload and download content to the cloud through a URL-based addressing service. Virtual hosting of your website There are decentralized applications (dapps) without web servers using a decentralized peer-to-peer distributed infrastructure. The vision is to create a new Internet that is not only fault-tolerant, zero-downtime, and censorship-resistant, but also economically self-sufficient due to a built-in incentive system. By rewarding nodes for contributing bandwidth and disk space, these incentives aim, on the one hand, to achieve reliable, low-latency, scalable retrieval of popular content, and on the other hand, to achieve important but rarely It aims to ensure the persistence of inaccessible data. For seamless delivery, Swarm uses the SWAP protocol (planned in POC3.1) and a two-stage insurance system (planned in POC4) for storage guarantees.
In addition to the basic functionality for storing and forwarding data, the POC 3 release includes several new and experimental features.
P.S.S.
The same peer-to-peer connections used for data storage and delivery can also be used for node-to-node messaging. PSS supports Swarm routing (lol) and whisper(Shh) encrypted message format (lol+Shh=pss). in other words, P.S.S. A messaging protocol with strong privacy features that runs on top of the Swarm network. This messaging infrastructure could become the basis for a whole new system of node-to-node communication services (email, tweets, newsletters of the future). Postal service via Swarm.
PSS is fully functional but experimental on the new POC3 network and dapps can interact with PSS using the JSON RPC API. We work closely with companies and projects looking to build second-tier infrastructure using pss. mainframe We are building a Slack alternative collaborative group communication tool (onyx) and the corresponding web3 SDK situation Expressed interest in building this into mobile chat.
Variability
Another experimental new feature in POC3 is Swarm Mutable Resource. Typically, in peer-to-peer storage systems, content is addressed with a digital fingerprint (hash), and when the content changes, this address also changes. However, web users are familiar with mutable resources. When I visit the URL, I expect to see the latest version of ‘site’. Swarm integrates with the Ethereum Name Service to provide easy access to changing content from a persistent, human-readable address. (ENS) On the Ethereum blockchain. This allows you to refer to Swarm content by the following names: bzz://theswarm.eth.
Swarm POC3 adds another layer in the form of: Mutable Resource Update (MRU). This allows for off-chain updates of content associated with addresses, potentially at a faster rate than the blockchain’s ENS updates can support, and incurs no on-chain transaction costs.
MRU is currently an experimental feature on the POC3 testnet and is still undergoing changes.
fuse support
fuse Allows users to integrate Swarm data directly into their local file system (Linux and Mac only). This system allows users to “mount a Swarm manifest” as if it were a regular directory. Supports file system read and write operations with all content automatically synchronized with Swarm. In the future, combining FUSE with Swarm Mutable Resources will make it possible to sync entire home folders across devices, for example as a backend to distributed storage with Dropbox-like functionality.
Encryption support
Comes standard with Swarm 0.3 encryption You can upload your personal data securely. The way encryption works is that users can upload directories privately and still ‘share’ subdirectories with specific peers.
The Access Control Tree (Swarm 0.3.2) provides an API that allows users to manage access to content independently of publishing the content. Granted access operates across resource versions.
year ahead
The year ahead will be an exciting and challenging one. As part of the POC3 series, we plan to turn on the improved SWAP accounting system (Swarm 0.3.1) and enable ‘light’ Swarm nodes (Swarm 0.3.2). Implementation of erasure coding, proof of custody, and insurance are also covered. roadmap. We aim to deliver Swarm POC4 (pre-production beta release) in 2019.
We continue to build a community with allies who champion the value of web3 and actively collaborate through working groups and the underlying infrastructure that is the backbone of second-tier services such as databases.http://wolk.com), personal data management (http://datafund.io), rights and creative licenses (http://jaak.io), distributed version management (ethergit, http://epiclabs.io), video transcoding and streaming services (http://livepeer.org), communication and collaboration (https://mainframe.com) and The list is growing.
Contact us
We welcome your feedback and contributions. come visit us grid channel Or our github repository.