Author Topic: [ERROR] Unlocked wallet can't decrypt memo  (Read 1452 times)

0 Members and 1 Guest are viewing this topic.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I think the wallet tries to decode the memo as if it was an incoming transaction and thus tries to derive the shared key using your own public key and the others private key (which the wallet doesn't have) instead of doing it the other way round

Offline ByronP

  • Full Member
  • ***
  • Posts: 70
    • View Profile
Is it possible that the reason for this error is the wallet is trying to decrypt the memo from a send transaction and it can't because it only has the public key? I haven't had time to look at the code but it was the first logical reason that i could think of. If this is the case the wallet should not throw an error on this at all as it should check the op type and to/from to make sure it actually should bother trying to decrypt it.

Offline ByronP

  • Full Member
  • ***
  • Posts: 70
    • View Profile
My wallet has been showing this strange error lately

Code: [Select]
2107186ms th_a       wallet.cpp:2442               operator ()          ] Error
when decrypting memo: 10 assert_exception: Assert Exception
wallet._keys.count(op.memo->to): Memo is encrypted to a key <KEYREMOVED4SECURITY> not in this wallet.
    {"k":"<KEYREMOVED4SECURITY>"}
    th_a  wallet.cpp:2435 graphene::wallet::detail::operation_printer::operator
()

It doesn't make sense that the wallet can't decrypt a transaction it has sent (yes it is unlocked) or have the key to do so. Why would "memo->to" be encrypted, shouldn't just the message be encrypted.

« Last Edit: October 29, 2015, 11:50:39 am by ByronP »