The new Aqua 0.4.1 just arrived. Among refactorings & bugfixes a new language feature comes: closures.

Now you can create Aqua functions (arrows) within Aqua functions, call them immediately or pass further as an argument. Closures capture service resolutions and values available in the definition scope. See documentation for details.

Closures is a part of the effort to make Aqua code more modular and flexible, therefore composable and reusable. This is quite important for big projects and complex algorithms. More features addressing Aqua logic modularization are to come.

Another minor feature that comes with 0.4.1 is the --scheduled CLI flag that makes the compiler produce AIR in the Fluence's Script Storage format. If you have any other idea about how to make Aqua developer's life easier, please file an issue.

Our next community call is scheduled for tomorrow, Thursday, Nov 11 at 18.00 CET (11 am CDT).

We are trying to make these calls helpful, educational, and entertaining for everyone who is getting into Fluence. Sometimes they take longer than we expected so feel free to join or drop off any time.

The preliminary agenda is:

- Updates from Fluence Labs (15 min)
- Apps demos by community members (15 min)
- Q&A, open discussions (15 min)
- Lecture about Marine (45 min)

During the lecture, we'll dive into Marine, our general-purpose Wasm runtime intended to run multi-modules Wasm applications with help of interface-types and shared-nothing linking scheme. We'll talk about the runtime architecture, API, and how it works internally.

Check out previous calls here:
- Recordings on Youtube
- Notes and future topics in Notion
- Add to Calendar

The new minor release of fluence-js has arrived: 0.14.3

Error handling has been improved. Now promises return from aqua call functions will fail early with user-friendly messages if the particle was not successfully sent onto the network.
Also some minor bugfixes delivered.

Please, refer to the changelog for more info.

AsyncVM is finally shipped on Krasnodar

AquaVM 0.15.0 enables service calls parallelization on a single peer, managed by Aqua scripts.

Previously parallelization in Aqua scripts worked only in the case of different machines: within the same peer, be it Rust node of Typescript, `par` / `co` code was actually executed sequentially. Now peer-local parallelism is managed by Aqua, just as expected.

This is not a protocol level change, so previous versions of Fluence peers keep working as expected.

The new AquaVM is now delivered both to the Rust peer and TypeScript peer. In the case of TypeScript, it also enables asynchronous services and callbacks, as AquaVM does not block anymore.

Announcing Aqua 0.5.0. This release fixes the issue with using streams within for loops. Now streams are restricted to the scope of the iteration or of a function, which is much more intuitive. See the documentation updates here.

This is a breaking change: Aqua 0.5 targets the latest AquaVM bundled within FluenceJS 0.15.0+ and Fluence Node v0.0.23+. fldist does not support the new AIR scripts at the moment, so please use aqua --run to run Aqua from CLI.

With Aqua 0.5, we expect no more critical bugs in the compiler. So if you find any, please assume that it is unknown and file an issue.

Added Peer.timeout(delay_ms: u32, message: string): string function to the Fluence Peer's builtins, available in @fluencelabs/aqua-lib v0.2.1.

It enables the timeout pattern between parallel execution branches: wait for some code to be executed, or do a failover if it does not respond in time. See Timeout pattern in the Aqua Book for the usage example.

🔔Developer community call, today, in 15 min, 17.00 CET/10 am CT
Jump in/out anytime

Agenda:

- Updates from the core team
- Demo by community members
- Q&A, open discussions
- Lecture: JS SDK, Fluence for JS developers

👉Join via link https://us06web.zoom.us/meeting/register/tZYtdeytqjwtHNPupTLlURpqIqpKzCeCImJM
Add event in your calendar

The new minor release of fluence-js has arrived: 0.15.1

It fixes the bug in service registration functions when the service is implemented as a class.

Now the correct class context is preserved when storing such implementations. Also includes minor bug fixes.

Please, refer to the changelog for more info.

The last developer community call of the year is tomorrow, Dec 16, 17.00 CET / 10 am CT

- Fluence tech AMA
- Yearly tech recap
- Nodes architecture talk

Add to calendar
Join the call

Announcing Aqua 0.5.1. This release adds a lot of features into aqua run command. Now you can pass any arguments as JSON, change log level, print generated air code, etc. Also you can create and pass your secret key. All features you can see in aqua run --help or in new documentation for CLI.

For the more detailed update, refer to the changelog.

Just released the new Aqua 0.5.2. This version contains one new feature: CLI command to upload files to Fluence Peer's companion IPFS, as a part of the effort to sunset fldist and move its logic into Aqua CLI.

Another big change is done under the hood: topology reasoning and transform was completely rewritten, eliminating all the known topology-related issues.

We are proud to announce a holidays present for all Fluence JS users.

Starting from version 0.17.1 all particles are being processed in background thread by default. It gives a massive performance boost especially in applications with lots of aqua code. This is achieved by using AVM runner instead of embedded AVM Interpreter.

The latest version of the package is 0.18.0. It contains the most up to date AquaVM. Please use this one when you upgrade.

Important note: using Fluence JS in browsers now requires additional configuration. See documentation for info.

You can find the full Fluence JS changelog here: https://doc.fluence.dev/docs/fluence-js/changelog

Introducing Aqua 0.5.3. In this version we enrich the language with an explicit join expression, and access to collection elements using non-literal indices:

func collectResponding(peers: []string, n: i16) -> []string:
stream: *string

for p <- peers par:
on p:
stream <<- p

join stream[n]
-- now stream contains at least n+1 elements
<- stream

Follow the links in the changelog to find out the details.

If you are looking to learn how to implement a dedicated signing node with Fluence JS or wrap EVM RPC APIs with Marine and use Aqua to seamlessly compose those services into protocols, look no further than the recently released near-integration examples.

Finally, the rust node is switched to the recent vanilla rust-libp2p v0.42.0 and fluence-js is updated to the latest typescript-compatible js-libp2p v0.33.0. The changes are not backwards compatible, so you need to update your projects to at least fluence-js v0.19.0. But feel free to run our examples, they are up-to-date.

Aqua 0.6.1 (as well as 0.6.0) is out. While 0.6.0 was mainly focused on internal changes to unlock new language features in the near future, 0.6.1 brings new functionality to work with the Fluence network, most notably deploy and remove services with aqua dist.
We have also completely deprecated fldist tool that was previously used to interact with the network. Be sure to switch over from fldist to aqua everywhere!

The next developer community call is tomorrow, on Thursday at 18.00 CET/11 AM CT!

Agenda
- Demos of the projects built with Fluence by the community members
- Q&A
- Fluence Registry, the default routing layer for the Fluence network. Design overview & demo
Add to calendar

The call is via zoom


We are going to present Fluence Registry, the default routing layer for the Fluence network. Will have design overview and demo. Going to be fun (everyone will be able to participate in the demo, if it's going to work actually:), and useful for almost any real-life use-case of Fluence: replica sets, worker clusters, peer-to-peer message delivery, and more. Also we will touch TrustGraph, but it's not going to be covered

Released Aqua 0.6.2 – a minor update with two user-facing changes: support for scheduling scripts on the Fluence network using Aqua CLI, and support for Top/Bottom types for better debugging experience that's going to be delivered to aqua-lib/builtins.aqua later. See the Changelog for details.

We are proud to announce that we have reached the 1st milestone of Marine-web! It is a technology intended to run wasm modules in browser and Node.js environments. It works like wasm-bindgen, but has more potential and can run wasm modules built with marine.

The Marine-web project is divided into 3 milestones:
✅Moving AquaVM from wasm-bindgen to Marine-web. Integrated into fluence-js 0.20
☑️ Single-module marine services support: it will be possible to run them smoothly in Node.js and browser, like on Rust Fluence Peer.
☑️ Multi-module services support. We will use it to implement a full-featured Fluence JS Peer with full WASM support.

It is not only a huge improvement of the Fluence network, but also a WASM ecosystem upgrade: it is the first browser runtime that supports Interface Types with its ability to easily pass complex structures and arrays between JS and WASM modules!

Released AquaVM 0.21 with a support of recursive streams. Such streams allows extentsion while iterating over it - it's possible to write to a stream inside a fold block and then iterate over new values again. It lets on to implement a bunch of distributed algos and was a major blocker for Kademlia.

Just released Aqua 0.6.3, a minor update with one syntax addition that's expected to be very useful: collection creation. Now you can use ["hello"] to create a value of type []string, ?[flag!] to create ?bool, and even *[1, 2, 3] to create a stream of numbers. Compiler will try to derive the type of the resulting collection by intersecting all the argument types. See more in the Aqua PR#445.