Expected behavior The Signed_Transaction

The described issue is fixed after applying <a class="issue-link js-issue-link" data-e

Signed_Transaction cannot handle appbase transactions with beneficiaries about beem HOT 2 CLOSED

holgern commented on June 2, 2024

Signed_Transaction cannot handle appbase transactions with beneficiaries

from beem.

Comments (2)

crokkon commented on June 2, 2024

Just realized that beempy verify is affected in the same way:

appbase:

$ beempy set nodes https://api.steemit.com
$ beempy verify --trx 3 25304468
[...]
  File "/usr/local/lib/python3.6/site-packages/beembase/objects.py", line 268, in __init__
    raise Exception("Unknown CommentOptionExtension")
Exception: Unknown CommentOptionExtension

non-appbase:

$ beempy set nodes wss://rpc.steemviz.com
$ beempy verify --trx 3 25304468
+-----+-------------------------------------------------------+--------------+
| trx | Signer key                                            | Account      |
+-----+-------------------------------------------------------+--------------+
| 3   | STM8UsiAQE3nCAjs719SJ3cBTJzH8KQ5jwAemcrn6DVVCphQvjH2j | buffalo-goku |
+-----+-------------------------------------------------------+--------------+

However, the problem seems to be broader than just beneficiaries:
Checking the signatures of transactions gives empty results when Amounts in the appbase format (e.g. {'amount': '3', 'precision': 3, 'nai': '@@000000021'}) are contained:

appbase:

$ beempy verify --trx 5 25304468
+-----+------------+---------+
| trx | Signer key | Account |
+-----+------------+---------+
| 5   | []         | []      |
+-----+------------+---------+

non-appbase

$ beempy verify --trx 5 25304468
+-----+-------------------------------------------------------+----------+
| trx | Signer key                                            | Account  |
+-----+-------------------------------------------------------+----------+
| 4   | STM8NyQwZLPM4AVAVUf5Koqn2WFE5cD1TaUqk5nGQq1E8KddBJS8g | all.cars |
+-----+-------------------------------------------------------+----------+

It seems to me that this is a general problem with the serialization. I didn't manage to fix it, yet. If you have a pointer where to best address this, let me know!

from beem.

holgern commented on June 2, 2024

The described issue is fixed after applying #77

from beem.

Recommend Projects