public key mismatch error in
See ProofService FAQ.
Does KVService rely on an existed Persona / binding on ProofService?
Not really! You can use this as a storage for every secp256k1 keypair
platform == nextid && identity == "0xPUBLIC_KEY") without even
using it on ProofService.
But, if you want to save data related to a specific account, we still
encourage you to put it under precise
A typical case is, your DApp allows user to set different NFT avatar
on Twitter and Github. In this case,
be specified (instead of being put under an ambiguous avatar pubkey).