On September 5th at Full Node in Berlin, Status, Golem and Raiden finally got together after months of getting to know each other virtually to enjoy an evening of awareness, friendship, great talks and tasty snacks.


The three projects have been developing their products and solutions for long and it was time that we refrained from the standard product pitches, and we get together to raise awareness on what we are doing to generate a more dev & user-friendly Web 3.0 thanks to our development teams.


We got together under one single premise: become more user-focused and facilitate onboarding and seamless experiences when it comes to interacting with dApps.
For this, Golem + Status, with their first use-cases on mainnet, were crucial to explain how an dApp evolves, targets users, gathers their feedback, improves and hence becomes more user-friendly. But to do this, building on Ethereum, we are still facing issues both in UX, scalability and more. As Golem and Status presented this, Raiden was invited to showcase a possibility how to make token transfers for Ethereum near-instant, low-fee and scalable using an off-chain scaling solution.


Raiden represents one building block that could support mass adoption of Ethereum and enable certain use cases through cheaper, faster and more scalable token transfers via a layer two payment channel network. This could in future be especially interesting for micropayment related use cases (e.g. paid API calls),  M2M and IOT transactions just to name a few.. The implementation of Raiden should be as easy as possible for developers and early users: it can be used both through a WebUI, as well as programmatically. The Raiden API aims to abstract from the complex technicalities of payment channel networks, such that developers can interface with a simple API to build scalable decentralized applications based on the Raiden Network. Raiden is live on the Ropsten testnet and welcomes testers and feedback on the latest release.


Golem is building a decentralized, robust and secure p2p marketplace for generalized computing power. As we continue to improve our software, we also presented our use-case pipeline which is aimed to generate a wider user base with new use-cases. The goal of Golem’s Use Case Pipeline is to aid in our evolution toward general purpose computing, supporting a wide variety of usecases from machine learning to scientific computing, and everything in between. We are building for the community - so the community should have a saying on what should be built on top of Golem, and we will endeavor to support them. Moreover, we explained our UX challenges from mainnet launch, to the gradual improvements on each software iteration, and our wishlist for the upcoming months.


Status, on their side, is building a distributed mobile chat, wallet, and DApp browser. They are also working on a desktop application, scaling solutions, framework tools, as well as accelerating independent projects. They presented the work being done on extensions for DApps to function more seamlessly within their client. This is really exciting work which will allow DApp developers to create more integrated experiences for the end user. Their talk also focused on the design decisions made to increase usability and lower the learning curve into blockchain technology. UX Research methods used to inform the design decisions made from Alpha to Beta were discussed, as well as key feature developments and improvement. The status application is currently on mainnet

It is important to understand that dApps need help - and for instance, scaling solutions can be a part of that help. While we go through our own improvements, we need to stay united and keep up with fellow projects’ development. We are all building for the user, in different levels.

Video Playlist:  


We want Ethereum to thrive as well as other Blockchains, and our main goal is for Web 3.0 to finally be adopted, as a collaborative ecosystem made of dApps and protocols that push a more secure, censorship-resistant and better internet where users take back the control of their data.