Right now, there are two primary directions in our work: developing the platform and building the community — both are the foundations for the Fluence ecosystem. These goals set the update’s structure: you are already familiar with the “Community” part — you can always find the news on meetups/workshops and other events there, in addition to that, monthly project updates will now include “Engineering” — delivering the report on the latest features and global platform updates.
And the big news for a starter :
Fluence Devnet Hackathon Recap: Projects, Winners And Takeaways
Decentralization, clusters, validators, functional programming, smart contracts, networks — all together this might be…
The first Fluence hackathon had been a huge success! During eight hours 35 hackers used Fluence Devnet to build decentralized apps. Shared canvas, fair poker, verifiable random functions, a turn-based strategy game backend, and a toy DEX — the participants figured out that Fluence high performance in real-time along with the ability to execute complex backend logic might be just what these apps need to shine. It was also a great way to test-drive the Devnet in real life environment: the feedback we’ve received was invaluable and showed that the network is close to a production-ready state.
Speaking of the Devnet, we have forked a popular open-source NoSQL database Redis and ported the fork to WebAssembly. This fork is now available for deployment from our dashboard.
We plan to further expand a collection of components available in the Fluence ecosystem.
Community and Events
The Devnet hackathon was not the only place, where you could learn about Fluence and try building apps with it:
- Berlin, March 25 — “Decentralized games on Fluence” workshop — try it with our tutorial
- San Francisco, April 8–11 — Whiteboard session with Near Protocol (video coming soon). Two meetups in San Francisco and Santa Clara (video)
- Moscow, April 13 — Fluence Devnet Hackathon — check out the recap.
- Split, April 25 — Fluence workshop during the BlockSplit
- Minsk, April 26 — A talk on the DApp Developer Survey Results at the CryptoGames conference
- Minsk, April 27 — Fluence workshop during the CryptoGames conference
Coming up Next
- New York, May 12–19 — Meet with us during the blockchain week
- Madrid, May 24 — Attend Fluence tech talk at the Swarm Orange Summit
We’re also preparing a series of hackathons in Europe, stay tuned for the exact dates and locations!
While the work on the Fluence core goes according to the roadmap (expect updates soon), we’re also releasing features that will make the Devnet more approachable for the developers and enable them to iterate faster through produce/test/deploy cycle or port new components to the ecosystem:
- IPFS support was added, along with Swarm, for even faster applications deployment
- The capacity to deploy your app to the Devnet right from the dashboard. Previously, CLI was the only option
- AssemblyScript SDK: code on Fluence with a familiar-looking TypeScript-like language ( example, docs)
- Multi-module support: use components developed in different languages, e.g., embed a database into your AssemblyScript app (example)
- C/C++ SDK: there’s a ton of great tools and libraries available in C/C++, the SDK makes it easier to port them to Fluence or to build your app (SDK, C template, C++ template, docs)
- Debugger 0.1: develop and debug your code in a Docker container on a local machine (docs).
Securing Decentralized Databases
Securing Decentralized Databases, Part I
Before the advent of the personal computer, there was an epoch of mainframes providing computational resources to…
Alex (Fluence Chief Scientist) has published his thoughts on the existing approaches to data storage security and scalability in the decentralized cloud. The article reflects some aspects of ongoing research that we do to further develop Fluence and explains in detail how the problem is currently dealt with in centralized and decentralized systems.
That’s all for now!
More about Fluence in our official groups:
- Discord: Fluence Network
- Twitter: @fluence_one
- Reddit: /r/Fluence
- Telegram: FluenceOne
- Github: Fluence Labs
Also: important Devnet links.