Yes. Pass your node URL to Client, either as a single endpoint or inside an endpoint list.
const client = new Client(['https://your-rpc.example.com']);
Yes. Pass an array of endpoints. The first healthy endpoint remains sticky across successful calls, and timeout failures can move the client to another endpoint.
See failover.md.
Electron is not tested as a separate target in this repository. It should be evaluated according to the runtime you use: Node.js >=18 for main-process style usage, or a browser environment with native fetch and AbortController for renderer usage.
React Native is not declared as a supported target in package metadata and no dedicated React Native test is currently present. Treat it as unverified until your project validates the required globals and bundling behavior.
No. Blurt Layer 1 helpers such as condenser, database, accountHistory, broadcast and blockchain do not require Nexus. Nexus is only needed for client.nexus / Bridge social views. See Blockchain model.
ClientOptions exposes chainId and addressPrefix, which are the relevant knobs for non-mainnet usage. Actual compatibility depends on the target RPC node and chain settings, so validate your testnet setup before relying on it.
The client uses the configured endpoint list and keeps a healthy endpoint sticky across successful calls. Timeout failures can trigger movement to another endpoint. See failover.md for the tested behavior.
You can prepare a transaction and call client.broadcast.sign(tx, key) without immediately broadcasting that signed object. Preparing a transaction still requires fresh chain data from an RPC node.
No. dblurt can sign and broadcast if your application provides keys. Wallet UX, key custody and user approval flows remain application responsibilities.
Useful resources: