🔗Connect with Blade

Connect wallet integration through deep-link

Connection flow

This is a high-level sequence diagram of integration

Sequence diagram of an implementation

Integration steps

Deep-link

To use the flow, deep-link should contain dApp_code url parameter. dApp_secret & dApp_nonce can be provided to ensure the authenticity of an interaction.

Blade deep-link parameters

Name
Description

dApp_code

dApp id, used to identify dApps

dApp_nonce

(optional) Nonce token, generated by dApp

dApp_secret

(optional) Token that will be given by Blade team before integration

Blade deep-link example. Account creation / linking

https://link.bladewallet.io/?link=https://api.bladewallet.io/mobile/profile/attachAccount?dApp_code%3Dcode%26dApp_nonce%3Dnonce_token_value&apn=org.bladelabs.wallet&isi=1623849951&ibi=org.bladelabs.bladewallet

dApp redirect deep-link

After all the processing is done on Blade Wallet (account creation etc), Blade will do a redirect to the dApp.

Base redirect deep-link url should be sent to Blade team, during integration onboarding

dApp redirect parameters

Name
Description

signedNonce

(optional) dApp_nonce signed by users's private key. Note: will be sent back only if dApp_nonce was sent during the flow initiation.

accountId

Hedera account id of a user

dApp can validate signedNonce by using public key of an account. Public key could be retrieved from Hedera's mirror-nodes.

Last updated