Migration Guide

Migrating Blocto wallet from v1 to v2

This guide is primarily for early Flow developers adopting Blocto wallet who want to learn about our latest progress on Flow & Blocto. Read the following guide to enhance your experience with Blocto.

For why to use @blocto/fcl instead of @onflow/fcl, check out this Github PR for further information.

Changes

  • Latest version of @blocto/fcl@1.4.0 has been released

  • New version of the blocto wallet interface and endpoints

  • Update some deprecated methods or properties

Upgrading Dependency

Upgrade the @blocto/fcl in the package.json to ^1.4.0

yarn upgrade @blocto/fcl@^1.4.0

Upgrading the FCL Configuration

Replace the value of accessNode.api and configuration keys:

import * as fcl from "@blocto/fcl";


fcl
  .config()
- .put("accessNode.api", "https://access-mainnet.onflow.org")
+ .put("accessNode.api", "https://rest-mainnet.onflow.org")
- .put("challenge.handshake", "https://flow-wallet.blocto.app/authn")
+ .put("discovery.wallet",`https://wallet-v2.blocto.app/${YOUR_DAPP_ID || "-"}/flow/authn`)

For dApps that haven't applied for a dApp ID, we recommend you apply for a better user experience, or use - as an alternative.

Visit Register App ID to learn how to register App ID

If you have been using the back channel to communicate with FCL, follow the guide below:

import * as fcl from "@blocto/fcl";

fcl.config()
- .put("accessNode.api", "https://access-mainnet.onflow.org")
+ .put("accessNode.api", "https://rest-mainnet.onflow.org")
- .put("discovery.wallet", "https://flow-wallet.blocto.app/api/flow/authn")
+ .put("discovery.wallet",`https://wallet-v2.blocto.app/api/flow/authn`)
+ .put("app.detail.id", YOUR_DAPP_ID)// this line is optional
  .put("discovery.wallet.method", "HTTP/POST")

For dApps that haven't applied for a dApp ID, there is no need to set the app.detail.id key.

Last updated

Change request #370: docs: add web sdk v0.5.0 ERC-4337 docs