Cardano Updates

Signed-off-by: yHSJ <[email protected]>

Documentation here is sparse. It focusees on serializations that can fail

Signed-off-by: yHSJ <[email protected]>

A typo in an attribute could be a source of waste of time investigating the reason for the not
expected behavior. This gives an immediate feedback in case of error.

The wrong attribute name prevents the toggle switch in the subscriptions dropdown to work.

When the condition is met, (either due to error for bad navigation or because the notification is
removed), the correct action is to go back to previous page: pushing a new page injects into the
history a sort of infinite loop-back navigation, as a result the back button does not work.

For some reason (at least to me, unknown), the notifications returned by useNotificationsCenter
hook is initially undefined.
This means that when the last notification is removed, the hook returns undefined and the
navigation to the notifications center is not triggered.
Changed the check: when notifications is not undefined, even if an empty array, the navigation
must be triggered.

Signed-off-by: Chris Gianelloni <[email protected]>

Add webpack NPM package test to CI

Signed-off-by: Chris Gianelloni <[email protected]>

Implement interval-based rate limiting (~100 blocks/sec) in the subscription
loop to prevent memory exhaustion and system freezes during blockchain indexing.

The network can produce hundreds of blocks per second during historical sync,
but WASM processing is significantly slower (~30-50 blocks/sec). Without rate
limiting, resources accumulate in the DashMap faster than they can be consumed,
leading to unbounded memory growth and eventual OOM kills.

The rate limiter works in conjunction with the bounded event queue (10K capacity)
to provide complete backpressure control. Resources are created before the bounded
channel send() can block, so throttling at the production point is essential.

Changes:
- Add BLOCK_RATE_LIMIT_MS constant (10ms interval)
- Replace tokio::select! on follower.next() with interval-based tick
- Set MissedTickBehavior::Skip to prevent tick accumulation
- Add detailed comments explaining the resource lifecycle and why both
  bounded channels and rate limiting are necessary

This replaces the previous sleep-based throttle with a more idiomatic
tokio::time::interval approach that explicitly controls block polling rate.

* feat: add web file compression

* fix: add `glsl` to project dic

* move installation to flutter-base

* add flutter web and linux precache step in Earthfile

* refactor

* refactor

* test fix

* test fix

* test fix

* test fix

* back to previous config

* set flutter version to 3.35.1

* add .mjs file compression

* parameterize compression levels

* correct variable name for Brotli compression level

Signed-off-by: yHSJ <[email protected]>

Implement interval-based rate limiting (~100 blocks/sec) in the subscription
loop to prevent memory exhaustion and system freezes during blockchain indexing.

The network can produce hundreds of blocks per second during historical sync,
but WASM processing is significantly slower (~30-50 blocks/sec). Without rate
limiting, resources accumulate in the DashMap faster than they can be consumed,
leading to unbounded memory growth and eventual OOM kills.

The rate limiter works in conjunction with the bounded event queue (10K capacity)
to provide complete backpressure control. Resources are created before the bounded
channel send() can block, so throttling at the production point is essential.

Changes:
- Add BLOCK_RATE_LIMIT_MS constant (10ms interval)
- Replace tokio::select! on follower.next() with interval-based tick
- Set MissedTickBehavior::Skip to prevent tick accumulation
- Add detailed comments explaining the resource lifecycle and why both
  bounded channels and rate limiting are necessary

This replaces the previous sleep-based throttle with a more idiomatic
tokio::time::interval approach that explicitly controls block polling rate.