Releases: blocknative/web3-onboard
[ledger]: Provider Fixes
The release of the Ledger includes two important bugfixes:
- The Ledger Live derivation path was incorrectly deriving addresses which is now fixed
- The provider was missing a
request
function to proxy any RPC requests that are not explicitly patched.
Changelog:
[keystone]: Provider Request Function
This release adds a provider request
function that passes on any RPC requests to the RPC URL that are not explicitly patched.
Changelog:
- [fix]: Hardware Wallet Providers Send Transaction (#894)
[keepkey]: Provider Request Function
This release adds a provider request
function that passes on any RPC requests to the RPC URL that are not explicitly patched.
Changelog:
- [fix]: Hardware Wallet Providers Send Transaction (#894)
react: 2.0.5
This release includes a fix for handling initial state more reliably when components using the hooks render before a wallet is set.
This gives initial state to all the hooks using the web3-onboard api strengthening reliability and uniform functionality throughout your application using the hooks.
react: 2.0.4
This release includes incremented version for the web3-onboard core and common packages in the react hook package.
These updates include a new instance
prop in the walletInterface type to allow passing of a wallet instance along with the provider in certain wallet modules.
This is beneficial for wallets that have extra methods built in to the walletInstance that is not standard across wallets.
e.g. Magic wallet has methods userMetaData()
and resetEmail()
that are exposed through the instance property
type WalletInterface = {
provider: EIP1193Provider,
instance?: unknown
}
Changelog:
- web3-onboard/react:v2.0.4: [update] - Update deps for React Package #882
magic: 2.0.0
The Magic module provides email login support for the Magic Wallet through web3-onboard.
Install
npm i @web3-onboard/magic
Head over to https://magic.link/ and signup to get an API key for your DApp
Login options
- Email - The Magic module comes with a built in email login modal that is customizable
in the same fashion that all other web3-onboard UI components are
- note: The Magic Module currently only supports email login but we are open to expand to sms or socials*
Initialization Options
type magicOptions = {
apiKey: string
}
Usage
import Onboard from '@web3-onboard/core'
import magicModule from '@web3-onboard/magic'
const magic = magicModule({ apiKey: 'API_KEY' })
const onboard = Onboard({
// ... other Onboard options
wallets: [
magic
//... other wallets
]
})
const connectedWallets = await onboard.connectWallet()
console.log(connectedWallets)
Accessing the Magic Wallet Internals
When a Magic wallet is connect the Magic instance is exposed.
This can be used to get information such as user Metadata, update a user's email address or handle the user's token.
const [magicWallet] = await onboard.connectWallet()
try {
const { email, publicAddress } = await magicWallet.instance.user.getMetadata();
} catch {
// Handle errors if required!
}
For full documentation and examples please visit Magic's official docs
Changelog:
- web3-onboard/magic:v2.0.0: [feature] - Magic wallet module addition #879
fortmatic: 2.0.2
This release includes a bug fix that was not allowing the provider to properly reset and patch after wallet_switchEthereumChain
is called
Changelog:
- web3-onboard/fortmatic:v2.0.2: [feature] - Magic wallet module addition #879
core: 2.0.11
Handling of the new instance
prop in the walletInterface type to allow for passing of a wallet instance with the provider in certain wallet.
This is beneficial for wallets that have extra methods built in to the walletInstance that is not standard across wallets.
e.g. Magic wallet has methods userMetaData()
and resetEmail()
that are exposed through the instance property
type WalletInterface = {
provider: EIP1193Provider,
instance?: unknown
}
Changelog:
- web3-onboard/core:v2.0.11: [feature] - Magic wallet module addition #879
common: 2.0.3
Addition of the instance
prop to walletInterface type to allow for passing of a wallet instance with the provider in certain wallet.
This is beneficial for wallets that have extra methods built in to the walletInstance that are not standard across wallets.
e.g. Magic wallet has methods userMetaData()
and resetEmail()
that are exposed through the instance property.
type WalletInterface = {
provider: EIP1193Provider,
instance?: unknown
}
Changelog:
- web3-onboard/common:v2.0.3: [feature] - Magic wallet module addition #879
[torus][fortmatic] - Bugfixes
Two small releases for the torus
and fortmatic
modules which fixes bugs where calls to parseInt
with hex string values were incorrectly using a radix of 10
.
Changelog:
- [fix] parseInt Calls (#875)