514563cef0
Unbeknowst to me, height doesn't have a universal definition of the chain length. Bitcoin defines height as the block number, with getblockcount existing for the chain length. Ethereum uses the unambiguous term "block number". Monero defines height as both the block number and the chain length. Instead of arguing about who's right, it's agreed it referring to both isn't productive. While we could provide our own definition, taking a side, moving to the unambiguous block number prevents future hiccups. height is now only a term in the Monero code, where it takes its Monero-specific definition, as documented in the processor. |
||
|---|---|---|
| .. | ||
| 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.