Skip to main content

Core Web dapp connections

Core Web inverts the usual relationship: instead of your dapp finding a wallet in the page, the user is already inside their wallet. That changes what "integrating" means.

What this means for your dapp​

There is no provider to detect and no Core Web-specific API. Users act on your protocol from Core Web's own surfaces:

  • Discover lists dapps and protocols users can open from inside Core.
  • Portfolio actions — swap, stake, DeFi positions — execute against protocol contracts directly.
  • DeFi positions from protocols Core Web integrates show up in the user's portfolio view automatically.

If your goal is "let Core users use my dapp," the integration surface is the same one every other wallet sees: your dapp's public site plus extension and mobile connectivity.

How Core Web signs​

Core Web signs with whichever key source the user brought: a seed phrase account, a seedless (social-login) account, Core Extension, or a hardware wallet. Requests flow through the same approval pipeline as the extension — including Blockaid transaction screening — so behaviour stays consistent across surfaces.

Testing against Core Web​

Core Web has a testnet mode (Settings → Advanced) that mirrors the extension's developer mode: every network switches to its test variant, and the testnet faucet funds accounts on Fuji and other test networks.