Skip to main content
The React Native example demonstrates wallet registration and a signing interface with @glideco/ows-react-native. Its demo backend returns fixed addresses, a placeholder public key and a fake signature. It does not generate hardware-backed keys or verify a payment on-chain.

​
Read the example

Start with examples/embed-ows-react-native/App.tsx in the product repository. Follow that example’s dependency and platform setup instructions. The example:
  1. Implements OwsSignerBackend with getAddress, getPublicKey and sign.
  2. Calls buildGlideOwsWallet with that backend and selected chains.
  3. Refreshes the wallet accounts.
  4. Registers the wallet with registerGlideOwsWallet.
  5. Displays a demo signing result when you choose Demo: sign a message.
Registration exposes the wallet to compatible runtimes in the same JavaScript context. It does not register an agent identity with the MCP gateway or authorize a payment.

​
Supply a real signer

For real signing, implement a backend appropriate to the selected chain and signing algorithm. The example’s ios/setup.md and android/setup.md describe native integration patterns; they are not prebuilt Secure Enclave or StrongBox modules. Verify device support, key storage, user confirmation, signature encoding and chain compatibility in your implementation. Do not treat the demo signature or a simulator run as proof of hardware protection.

​
Source

Read the React Native example. Source access is required.

​
Next