PollarPollarDemo

Products

AuthenticationWalletTransactions

Integrations

KYCSoonRampNewSwapNewEarnNew

Wallet Adapters

Stellar Wallets KitPrivyNewCosmos WalletNew

Adapters

Trustless Work

Built with Pollar

LumenWipeNew
OverviewSetupTest

Test Cosmos Wallet

Probe the raw window.cosmosWallet provider, then run the real Pollar SEP-10 login through the adapter.

Before you start

  1. 1.Clone github.com/CosmosPay/CosmosPay-Wallet and build the extension.
  2. 2.Load it unpacked in Chrome: open chrome://extensions, turn on Developer mode, click Load unpacked.
  3. 3.Create or import a wallet in the extension. Matching its network to the toggle in this demo's navbar is optional — it only changes what the extension itself displays.
  4. 4.Reload this page so the content script injects the provider.

1. Raw provider

These call window.cosmosWallet directly, with no Pollar involved. getAddress() opens the extension's approval window the first time this origin asks.

…

Result

Nothing yet. Run a call above.

2. Login through Pollar

Runs login({ provider: 'cosmos-wallet' }): the adapter connects, Pollar requests a SEP-10 challenge, the wallet counter-signs it and the session is minted. Expect two approval windows the first time.

Auth stateidle
App networktestnet
AddressNot logged in
Provider-
Verifiedfalse

Known limits of this wallet

  • No signAuthEntry: Soroban auth-entry signing is unavailable.
  • No SEP-53 message signing: the wallet signs raw bytes, so ownership proofs are not wired up.
  • The extension's network is its own setting. The login works either way — Pollar signs with its own passphrase — but the balances shown inside the extension follow the extension's network.
  • The provider never rejects on its own: a request whose reply is lost stays pending forever. The adapter bounds every approval and pings the extension to keep its service worker awake.