You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`unlock`|`unlock`| runtime-backed | Runtime-backed lifecycle unlock with request parsing, init precondition, password validation, and runtime-session authorization transition (`authorized=true`). |
48
+
|`unlock`|`unlock`| runtime-backed | Runtime-backed lifecycle unlock with request parsing, init precondition, password validation, runtime-session authorization transition (`authorized=true`), and default RGB wallet bootstrap from lifecycle mnemonic (auto-attached to newly created nodes). |
49
49
|`lock`|`lock`| runtime-backed | Runtime-backed lifecycle lock with init precondition and deterministic authorization transition (`authorized=false`) so runtime managers reject locked sessions until next unlock. |
50
50
|`connect_peer`|`connectPeer`| runtime-backed | Runtime-backed websocket peer-connect path with secp256k1/`host:port` validation and runtime-event application through shared transport pipeline. On `ldk_bridge`, peer state is runtime-manager authoritative and reconnect aliases reactivate persisted peers (`started=true`), with JSON/text alias compatibility for event/id fields and separator-normalized kinds. |
51
51
|`disconnect_peer`|`disconnectPeer`| runtime-backed | Runtime-backed disconnect path with secp256k1 validation and `peer_disconnected` transport transition application, including stale channel cleanup and runtime-manager-authoritative state transitions on `ldk_bridge`. |
52
52
|`close_channel`|`closeChannel`| runtime-backed | Runtime-backed channel-close transition via `channel_closed` transport event path with runtime-manager-authoritative application on `ldk_bridge`, runtime-ready guard parity, and stable not-found contract. Extended options path (`closeChannelWithOptions`) supports native-like peer/session validation, virtual-session status transitions (`active -> abandon_pending -> abandoned`), and `force=true` rejection for trusted virtual channels. |
|`issue_asset_nia`|`walletIssueAssetNiaValue` / `walletIssueAssetNiaJson` and wallet-handle `issueAssetNiaValue` / `issueAssetNiaJson`| runtime-backed |Wired to `rgb-lib-wasm``Wallet::issue_asset_nia`; legacy SDK-only `issueAssetNia*` remains compatibility-only/unsupported on wasm facade. |
55
-
|`issue_asset_cfa`|`walletIssueAssetCfaValue` / `walletIssueAssetCfaJson` and wallet-handle `issueAssetCfaValue` / `issueAssetCfaJson`| runtime-backed |Wired via `rgb-lib-wasm``Wallet::issue_asset_ifa` compatibility mapping; legacy SDK-only `issueAssetCfa*` remains compatibility-only/unsupported on wasm facade. |
54
+
|`issue_asset_nia`|node/facade `issueAssetNiaValue` / `issueAssetNiaJson`| runtime-backed |Node-level adapter wired to `rgb-lib-wasm``Wallet::issue_asset_nia`; default wallet is bootstrapped on `unlock`, auto-attached to created nodes, and lazily attached on first issuance call if missing (manual `attachWallet` still supported to override). |
55
+
|`issue_asset_cfa`|node/facade `issueAssetCfaValue` / `issueAssetCfaJson`| runtime-backed |Node-level adapter wired via `rgb-lib-wasm``Wallet::issue_asset_ifa` compatibility mapping; default wallet is bootstrapped on `unlock`, auto-attached to created nodes, and lazily attached on first issuance call if missing (manual `attachWallet` still supported to override). |
56
56
|`issue_asset_uda`|`walletIssueAssetUdaValue` / `walletIssueAssetUdaJson` and wallet-handle `issueAssetUdaValue` / `issueAssetUdaJson`| unsupported-by-design | Explicit unsupported contract: `rgb-lib-wasm` currently has no UDA issuance primitive; legacy SDK-only `issueAssetUda*` remains compatibility-only/unsupported on wasm facade. |
57
57
|`keysend`|`keysendValue` / `keysendJson`| runtime-backed | Runtime-backed payment send path enforcing native min amount parity (`SDK_HTLC_MIN_MSAT`), destination pubkey validation, RGB payload validation (`asset_id` format + `asset_amount > 0`), and no-route failure transitions through runtime payment-status events. On `ldk_bridge`, delivery requires connected destination peer state (`peer.started=true`). |
| Legacy grouped transfer endpoint | legacy sdk `sendRgbFromGroupsValue/Json`| Legacy grouped SDK adapter unavailable in wasm facade; runtime-backed grouped send is available on wallet surfaces (`walletSendRgbFromGroups*` / handle). | sdk facade, wallet-handle (runtime-backed path) |
163
-
| Native host-only virtual cleanup proofs |`openChannel*` / `closeChannel*` node surfaces | Wasm runtime implements virtual draft/session lifecycle + reconciliation and now enforces best-effort preflight guards from runtime payment ledger (`pending` HTLC block + net counterparty BTC/RGB value floor checks since session creation). Full native host-only proofs that depend on filesystem RGB temp artifacts and exact counterparty floor internals are still intentionally not replicated in browser runtime. | Node-level contract tests for virtual session lifecycle + validation are present |
163
+
| Native host-only virtual cleanup proofs |`openChannel*` / `closeChannel*` node surfaces | Wasm runtime implements virtual draft/session lifecycle + reconciliation and enforces conservative preflight guards from runtime payment ledger (`pending/claimable/claiming` HTLC block + net counterparty BTC/RGB value floor checks since session creation). Full native host-only proofs that depend on filesystem RGB temp artifacts and exact counterparty floor internals are still intentionally not replicated in browser runtime. | Node-level contract tests for virtual session lifecycle + validation are present |
0 commit comments