Currently blockchain balances are cached in-memory via @cache_response_timewise on ChainsAggregator. This means:

• Cache is lost on restart (forces a full re-query)
• No way to show cached balances instantly on app load
• Single API conflates "give me what you have" with "go refresh from nodes"

This plan moves the cache to SQLCipher (user DB), splits the API into fetch-from-cache and refresh, and tracks per-chain staleness.

The rotki frontend has 4 settings stores consumed by ~210 files (~39% of the codebase). currencySymbol alone is imported in 42 files. Components must know which store holds which setting, creating tight coupling and boilerplate. The goal is to create domain composables (following the existing useAmountDisplaySettings pattern) so most components never import a settings store directly.

The useWalletStore Pinia store eagerly imports both wallet backends at module level:

• WalletConnect (use-wallet-connect.ts): imports @reown/appkit + ethers — ~2 MB
• Local Bridge (use-injected-wallet.ts): imports ethers + cross-imports supportedNetworks from WC — ~300 KB
• wallet-constants.ts: imports formatUnits from ethers — pulls ethers into a constants file

The store is on the startup path via use-logout.ts and account.ts, both of which only use disconnect. This means ~2.5 MB of wallet libraries load on every page visit, even though most users never use the wallet feature during a session.

This document outlines an architectural redesign to rewrite the MusicBee Remote plugin core in Rust while maintaining a minimal C# shim for MusicBee API access.

┌─────────────────────────────────────────────────────────────┐
│                     MusicBee (C++)                          │
└─────────────────────────────────────────────────────────────┘

Party Mode is a permission-based access control system that allows the plugin administrator to restrict what actions remote clients can perform. This is useful for parties or events where you want to let guests control music but limit potentially disruptive actions (e.g., stopping playback, removing tracks, changing volume drastically).

The feature existed in the origin/old-develop branch and was removed during a major refactor. Key components:

A LockedTransfer is a message used to reserve tokens for a new mediated transfer.

For a LockedTransfer to be considered valid the following conditions have to be true.

• There is a channel which matches the given :term:`chain id`, :term:`token network` address, and :term:`channel identifier`.