You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When address first init (first receive tkx from other account), it do not have public key infomation.
Call simulate with wrong public key type /cosmos.crypto.ed25519.PubKey return error.
But after try use keplr to send tkx from that account => it have public key information after that. And Call simulate again with still wrong public key type => it success this time . WHY is it happen.
Issue meet before:
Very new address do not have public key info => error when create delegate transaction
Proceduce step:
send tkx to very new address (that address do not have public key information when retrieve account info)
use new address to create transaction (in tkxscan.io)
delegate : error when verify signature
First transaction have high probability to fail with gas error. But after that public key information have created and everything after that become normal
The text was updated successfully, but these errors were encountered:
Summary
When address first init (first receive tkx from other account), it do not have public key infomation.
Call simulate with wrong public key type /cosmos.crypto.ed25519.PubKey return error.
But after try use keplr to send tkx from that account => it have public key information after that. And Call simulate again with still wrong public key type => it success this time . WHY is it happen.
Issue meet before:
Very new address do not have public key info => error when create delegate transaction
Proceduce step:
send tkx to very new address (that address do not have public key information when retrieve account info)
use new address to create transaction (in tkxscan.io)
delegate : error when verify signature
First transaction have high probability to fail with gas error. But after that public key information have created and everything after that become normal
The text was updated successfully, but these errors were encountered: