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.- Latest version of
@blocto/[email protected]has been released - New version of the blocto wallet interface and endpoints
- Update some deprecated methods or properties
Upgrade the
@blocto/fcl in the package.json to ^1.4.0yarn
npm
pnpm
yarn upgrade @blocto/fcl@^1.4.0
npm install @blocto/fcl@^1.4.0
npm install @blocto/fcl@^1.4.0
Replace the value of
accessNode.api and configuration keys:import * as fcl from "@blocto/fcl";
fcl
.config({
"accessNode.api": "https://rest-mainnet.onflow.org",
"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.If you have been using the back channel to communicate with FCL, follow the guide below:
import * as fcl from "@blocto/fcl";
fcl
.config({
"accessNode.api": "https://rest-mainnet.onflow.org",
"discovery.wallet": "https://wallet-v2.blocto.app/api/flow/authn",
"app.detail.id": "YOUR_DAPP_ID"// this line is optional
"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 modified 2mo ago