Connector

​

Install

npm install @chipi-stack/starknet-connector

​

Add it with starknet-react

import type { ReactNode } from "react";
import {
  StarknetConfig,
  InjectedConnector,
  publicProvider,
  ready,
  braavos,
} from "@starknet-react/core";
import { mainnet } from "@starknet-react/chains";
import { chipi } from "@chipi-stack/starknet-connector";

const connectors = [
  chipi(), // "Connect with Chipi"
  new InjectedConnector({ options: { id: "bramble", name: "Bramble" } }),
  ready(), // Ready (formerly Argent X)
  braavos(),
];

export function Providers({ children }: { children: ReactNode }) {
  return (
    <StarknetConfig chains={[mainnet]} provider={publicProvider()} connectors={connectors}>
      {children}
    </StarknetConfig>
  );
}

• List every wallet yourself. useInjectedConnectors only picks up objects with the legacy keys (provider, isConnected, enable, isPreauthorized). Neither window.starknet_chipi nor window.starknet_bramble has all of them, so it finds neither.
• injected({ id: "bramble" }) also works, but in 5.0.3 injected() takes only id: the label is Bramble’s own name once it has injected, and "bramble" before that.
• argent() is an alias of ready(). Use ready().
• InjectedConnector looks up window.starknet_bramble each time it is used, so Bramble’s late injection is fine. autoConnect runs once on mount: if Bramble has not injected by then, its last session is not restored.

​

Add it with get-starknet v4

import { getStarknet } from "@starknet-io/get-starknet-core";
import { chipi } from "@chipi-stack/starknet-connector";

declare const connectButton: HTMLButtonElement;
declare function pickedWalletId(): "chipi" | "bramble"; // from your wallet picker

// Puts window.starknet_chipi on the page.
chipi();

// Bramble injects window.starknet_bramble after page load, then fires
// "starknet#initialized". Scan after that, or after a short timeout.
function waitForInjectedWallets(timeoutMs = 3000): Promise<void> {
  return new Promise((resolve) => {
    if ("starknet_bramble" in window) return resolve();
    const done = () => {
      clearTimeout(timer);
      window.removeEventListener("starknet#initialized", done);
      resolve();
    };
    const timer = setTimeout(done, timeoutMs);
    window.addEventListener("starknet#initialized", done);
  });
}

await waitForInjectedWallets();
const gsc = getStarknet();
const wallets = await gsc.getAvailableWallets();
// Both are listed: wallets.map((w) => w.id) includes "chipi" and "bramble".

// Prompts only from a click: Chipi opens its popup, Bramble its side panel.
connectButton.onclick = async () => {
  const wallet = wallets.find((w) => w.id === pickedWalletId());
  if (wallet) await gsc.enable(wallet);
};

​

Works next to Bramble

• No id collision. Chipi is window.starknet_chipi with id "chipi". Bramble is window.starknet_bramble with id "bramble". get-starknet v4 and starknet-react key wallets by id, so both are listed.
• Neither writes window.starknet.
• When each object exists. window.starknet_chipi exists only after a ChipiConnector is created (unless register: false). disconnect() removes it until the next connect(). window.starknet_bramble appears after page load, followed by starknet#initialized.
• A wallet scan never opens Chipi. get-starknet v4’s getAuthorizedWallets() and getLastConnectedWallet() send wallet_getPermissions to every wallet at page load. Since 0.5.0, Chipi answers that and the other passive calls itself ([] before the user connects) and does not try to open its popup.
• Bramble’s rules apply to Bramble. Prompts only from a click, at most 5 pending prompts per site, strict params (an extra key fails with 114), a typed-data chainId equal to its active network, no wallet_disconnect (114), one account per site. starknet-react’s InjectedConnector.disconnect() does not send wallet_disconnect. Signatures are [r, s] for OpenZeppelin and Braavos accounts and ["1", "0", pub, r, s] for Argent accounts: verify them with the account’s is_valid_signature (or Sign in with Starknet), not by length. Full list: Bramble rules to follow.

​

How it works

your dApp                          Chipi hosted wallet (wallet.chipipay.com)
─────────                          ──────────────────────────────────────────
ChipiConnector.connect()
  ├─ opens a popup ──────────────►  /connect  (the user's authenticated wallet)
  └─ postMessage  ◄────────────►    approval UI (passkey + gasless paymaster)
account.execute(calls)
  └─ wallet_addInvokeTransaction ─►  user approves ─► sponsored tx ─► tx hash

1. ChipiConnector only carries messages. It opens the hosted wallet in a popup and forwards get-starknet wallet_* calls over postMessage. It holds no keys and signs nothing.
2. The hosted wallet (/connect) signs the user in, shows an approval for each connect, sign and execute, then runs the passkey + paymaster path and posts the result back.
3. connector.account(provider) wraps the channel in a starknet.js WalletAccount, so the dApp gets a standard AccountInterface.

​

Also on the extension

​

Try the example

✅ Verified against the SDK source on 2026-10-12.