We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
confirmed_at_index
When checking the transaction history, the value of confirmed_at_index is always 0.
This leads to confusing replies by CLI and RPC:
chia wallet get_offers -id 0xff211040f9b946d1461d1631fcc0c812b7bc24735989cdf58598d9f6dd3b7bfe Record with id: ff211040f9b946d1461d1631fcc0c812b7bc24735989cdf58598d9f6dd3b7bfe --------------- Created at: 2023-10-13 23:22:42 Confirmed at: Not confirmed Accepted at: 2023-10-13 23:22:42 Status: CONFIRMED ---------------
Relevant seems to be the status, but confirmed_at_index would be important / valuable information
Furthermore, the accepted_at_time is only beeing filled when is_my_offer = false. This might be a technical limitation.
accepted_at_time
is_my_offer
2.1.1
Linux
CLI
No response
The text was updated successfully, but these errors were encountered:
Quex where do we save this off in the DB?
Sorry, something went wrong.
Quexington
No branches or pull requests
What happened?
When checking the transaction history, the value of
confirmed_at_index
is always 0.This leads to confusing replies by CLI and RPC:
Relevant seems to be the status, but
confirmed_at_index
would be important / valuable informationFurthermore, the
accepted_at_time
is only beeing filled whenis_my_offer
= false. This might be a technical limitation.Version
2.1.1
What platform are you using?
Linux
What ui mode are you using?
CLI
Relevant log output
No response
The text was updated successfully, but these errors were encountered: