Known Documentation Differences
Confirmed limitations of the DCENT Web Bridge signing wire, verified against the implementation (source priority: implementation › playground › bridge service › guides).
Confirmed limitations
The bridge only signs — it never looks anything up for you. Consensus fields (nonce, sequence, blockhash, blockRef, and similar) are never fetched — they must arrive already filled in from your app, and a missing one fails closed with param_error before the request reaches the device. Some other fields have defaults or are signed as 0 when omitted (for example the Hedera fee and valid start, or the Algorand fee and the Cosmos fee.amount) — see each chain page. Polkadot still reads runtime metadata for display safety. (verified against the bridge)
Cosmos — bank MsgSend only. Only MsgSend (Amino StdSignDoc input, single-message) is signed; a Protobuf SignDoc is not supported (see Cosmos). Coreum AssetFT tokens transfer via a MsgSend carrying an assetft denom; CW20 (MsgExecuteContract) and IBC (MsgTransfer) are not supported — other typeUrls and multi-message txs are rejected with -32601. (verified against the bridge)