-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
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
Monero Library Tracking Issue #102
Comments
|
8a24fc3 fixed an issue where scanned funds may be unspendable via monero-serai. This was possible to reach on the Monero mainnet due to some very specific protocol complexities, which we prior accommodated yet I missed the scanner didn't also accommodate. Yanking all current releases accordingly. |
The newly added reserialize_chain binary ensures we can ser/deser all blocks/TXs. I'm running it now. |
We have |
We should test read_point for such cases... |
Closing. Only #104 stands and the library is effectively at the 1.0 rc, being queued for audits. I don't believe the dedicated tracking issue here is better than the tag. |
This is solely discussing the Monero library, and explicitly NOT the FROST aspects which are pending the IETF draft finalization and so on.
For all open issues: https://github.com/serai-dex/serai/issues?q=is%3Aopen+is%3Aissue+label%3Amonero
The following table is meant to go over all of them, along with other impactful issues.
If any issue is closed, it'll be removed from the table. If a new issue is created, it should be added.
Additional tasks:
Additional requirements:
Additional notes:
The text was updated successfully, but these errors were encountered: