Key generation process
The differences between key generation in Blanksquare Web App and Mobile
Mobile users: migration required
With the Web App ↔ Mobile compatibility update, existing legacy shielded accounts created on mobile are deprecated.
To access your previous account and migrate your funds, please refer to the guide below.
Key generation process
In the Blanksquare Mobile Wallet this happens behind the scenes. In the Web App, key generation involves your connected wallet.
When connecting your wallet to a Blanksquare Shielded Account via the Web App, you'll be prompted to sign the following message using your wallet:
"please create shielded account {public address}"
Your signature is used to generate a unique cryptographic key. This key allows our app to securely generate your private shielded account, create cryptographic proofs, and sign shielded transactions on your behalf.
Beware of scammers
As it's a standard message your wallet can sign, make sure to always verify you're interacting with the official Blanksquare App website before signing.
Signing this message is equivalent to granting full control over your shielded account. This has benefits, as you do not depend solely on the app's UI to access your assets, but poses a risk if you sign this message in an phishing app.
Differences between Mobile and WebApp
The Mobile app supports one shielded account per seed. In the Web App, that same account becomes available when you connect the seed’s main address. If you connect a different address derived from the same seed (any non‑main derivation address), the Web App will create and show a separate shielded account for that address—this additional account is Web-only and won’t appear in the Mobile app.
Legacy Mobile app approach
In the previous versions of the Mobile application, keys were derived directly from the wallet’s private key (device-side), which avoids the need for message signing in the app flow.
Important: Shielded accounts created using the legacy Mobile approach are not the same as Web-generated shielded accounts. To ensure full compatibility going forward, legacy Mobile users must migrate to the current (Web-compatible) scheme.
Legacy Account Migration Guide
To migrate your shielded assets to the current (Web-compatible) shielded account format:
Enable Legacy Mode Compatibility - go to Settings → Preferences → enable "Legacy Mode Compatibility."
Withdraw your shielded assets from the legacy shielded account into a new, fresh address.
Disable Legacy Mode Compatibility - Return to Settings → Preferences and turn "Legacy Mode Compatibility" off.
Shield your assets again (now under the current Web-compatible shielded account format).
After this migration, your shielded account is compatible across Web and Mobile, and supported by future versions of the app.
Last updated