19664967ed
This still sends a fingerprinting flare up if you send to a subaddress which needs to be fixed. Despite that, Monero no should no longer fail to scan TXs from monero-serai regarding additional keys. Previously it failed becuase we supplied one key as THE key, and n-1 as additional. Monero expects n for additional. This does correctly select when to use THE key versus when to use the additional key when sending. That removes the ability for recipients to fingerprint monero-serai by receiving to a standard address yet needing to use an additional key. |
||
---|---|---|
.. | ||
generators | ||
src | ||
tests | ||
build.rs | ||
Cargo.toml | ||
LICENSE | ||
README.md |
monero-serai
A modern Monero transaction library intended for usage in wallets. It prides itself on accuracy, correctness, and removing common pit falls developers may face.
monero-serai contains safety features, such as first-class acknowledgement of the burning bug, yet also a high level API around creating transactions. monero-serai also offers a FROST-based multisig, which is orders of magnitude more performant than Monero's.
monero-serai was written for Serai, a decentralized exchange aiming to support Monero. Despite this, monero-serai is intended to be a widely usable library, accurate to Monero. monero-serai guarantees the functionality needed for Serai, yet will not deprive functionality from other users, and may potentially leave Serai's umbrella at some point.
Various legacy transaction formats are not currently implemented, yet monero-serai is still increasing its support for various transaction types.