Migration from Blocknative
TomoEVMKit provides an API interface for projects based on @web3-onboard to migrate with minimum efforts.
Update Initiate
To initiate the onboard in TomoEVMKit, you need to add the await keyword.
// Old
import Onboard from '@web3-onboard/core'
// New
import { Onboard } from "@tomo-inc/tomo-evm-kit";
// Old
onboard = Onboard({
wallets,
chains,
appMetadata,
…
});
// New
onboard = await Onboard({
wallets,
chains,
clientId: "..", // client id from tomo
projectId: "..", // project id for wallet connect
…
});You can get clientId from the Tomo dashboard and projectId from the Walletconnect dashboard.
Done!
Different API logics
Due to the different logic of implementation of TomoEVMKit and Blocknative, we do not support all options in onboardnow, below are lists:
InitOptions
✅ Fully Support, ⚠️ Partial Support, ✖️ Not Support,
onboard API
onboard.connectWallet
Currently, if you call connectWallet it only supports no parameter input way and will return a connected status window.
connect configuration
We only support the automatical reconnect mode
Unsupported Wallets
@web3-onboard/arcana-auth
❌
@web3-onboard/bloom
❌
@web3-onboard/capsule
❌
@web3-onboard/cede-store
❌
@web3-onboard/dcent
❌
@web3-onboard/finoaconnect
❌
@web3-onboard/fortmatic
❌
@web3-onboard/keepkey
❌
@web3-onboard/magic
❌
@web3-onboard/particle-network
❌
@web3-onboard/passport
❌
@web3-onboard/portis
❌
@web3-onboard/taho
❌
@web3-onboard/tallyho
❌
@web3-onboard/transaction-preview
❌
@web3-onboard/trezor
❌
@web3-onboard/venly
❌
@web3-onboard/web3auth
❌
Last updated