2022-09-29 04:47:55 -04:00
|
|
|
#![cfg_attr(docsrs, feature(doc_auto_cfg))]
|
2023-03-20 20:28:41 -04:00
|
|
|
#![doc = include_str!("../README.md")]
|
2024-06-22 14:37:43 -04:00
|
|
|
#![deny(missing_docs)]
|
2023-06-29 04:14:29 -04:00
|
|
|
#![cfg_attr(not(feature = "std"), no_std)]
|
|
|
|
|
|
2024-06-16 12:26:14 -04:00
|
|
|
pub use monero_io as io;
|
|
|
|
|
pub use monero_generators as generators;
|
|
|
|
|
pub use monero_primitives as primitives;
|
2022-08-21 06:36:53 -04:00
|
|
|
|
Monero: support for legacy transactions (#308)
* add mlsag
* fix last commit
* fix miner v1 txs
* fix non-miner v1 txs
* add borromean + fix mlsag
* add block hash calculations
* fix for the jokester that added unreduced scalars
to the borromean signature of
2368d846e671bf79a1f84c6d3af9f0bfe296f043f50cf17ae5e485384a53707b
* Add Borromean range proof verifying functionality
* Add MLSAG verifying functionality
* fmt & clippy :)
* update MLSAG, ss2_elements will always be 2
* Add MgSig proving
* Tidy block.rs
* Tidy Borromean, fix bugs in last commit, replace todo! with unreachable!
* Mark legacy EcdhInfo amount decryption as experimental
* Correct comments
* Write a new impl of the merkle algorithm
This one tries to be understandable.
* Only pull in things only needed for experimental when experimental
* Stop caching the Monero block hash now in processor that we have Block::hash
* Corrections for recent processor commit
* Use a clearer algorithm for the merkle
Should also be more efficient due to not shifting as often.
* Tidy Mlsag
* Remove verify_rct_* from Mlsag
Both methods were ports from Monero, overtly specific without clear
documentation. They need to be added back in, with documentation, or included
in a node which provides the necessary further context for them to be naturally
understandable.
* Move mlsag/mod.rs to mlsag.rs
This should only be a folder if it has multiple files.
* Replace EcdhInfo terminology
The ECDH encrypted the amount, yet this struct contained the encrypted amount,
not some ECDH.
Also corrects the types on the original EcdhInfo struct.
* Correct handling of commitment masks when scanning
* Route read_array through read_raw_vec
* Misc lint
* Make a proper RctType enum
No longer caches RctType in the RctSignatures as well.
* Replace Vec<Bulletproofs> with Bulletproofs
Monero uses aggregated range proofs, so there's only ever one Bulletproof. This
is enforced with a consensus rule as well, making this safe.
As for why Monero uses a vec, it's probably due to the lack of variadic typing
used. Its effectively an Option for them, yet we don't need an Option since we
do have variadic typing (enums).
* Add necessary checks to Eventuality re: supported protocols
* Fix for block 202612 and fix merkel root calculations
* MLSAG (de)serialisation fix
ss_2_elements will not always be 2 as rct type 1 transactions are not enforced to have one input
* Revert "MLSAG (de)serialisation fix"
This reverts commit 5e710e0c96658092c6ecfe5e4ea5a9c3dbee3ab3.
here it checks number of MGs == number of inputs:
https://github.com/monero-project/monero/blob/0a1eaf26f9dd6b762c2582ee12603b2a4671c735/src/cryptonote_core/tx_verification_utils.cpp#L60-59
and here it checks for RctTypeFull number of MGs == 1:
https://github.com/monero-project/monero/blob/0a1eaf26f9dd6b762c2582ee12603b2a4671c735/src/ringct/rctSigs.cpp#L1325
so number of inputs == 1
so ss_2_elements == 2
* update `MlsagAggregate` comment
* cargo update
Resolves a yanked crate
* Move location of serai-client in Cargo.toml
---------
Co-authored-by: Luke Parker <lukeparker5132@gmail.com>
2023-07-04 21:18:05 +00:00
|
|
|
mod merkle;
|
|
|
|
|
|
2023-11-12 15:18:18 +00:00
|
|
|
/// Ring Signature structs and functionality.
|
|
|
|
|
pub mod ring_signatures;
|
|
|
|
|
|
2022-09-29 05:25:29 -04:00
|
|
|
/// RingCT structs and functionality.
|
2022-05-22 02:24:24 -04:00
|
|
|
pub mod ringct;
|
2022-04-21 21:36:18 -04:00
|
|
|
|
2024-06-22 09:02:59 -04:00
|
|
|
/// Transaction structs and functionality.
|
2022-04-28 03:31:09 -04:00
|
|
|
pub mod transaction;
|
2024-06-22 09:02:59 -04:00
|
|
|
/// Block structs and functionality.
|
2022-05-21 21:35:25 -04:00
|
|
|
pub mod block;
|
2022-04-28 03:31:09 -04:00
|
|
|
|
2024-06-22 09:02:59 -04:00
|
|
|
/// The minimum amount of blocks an output is locked for.
|
|
|
|
|
///
|
|
|
|
|
/// If Monero suffered a re-organization, any transactions which selected decoys belonging to
|
|
|
|
|
/// recent blocks would become invalidated. Accordingly, transactions must use decoys which are
|
|
|
|
|
/// presumed to not be invalidated in the future. If wallets only selected n-block-old outputs as
|
|
|
|
|
/// decoys, then any ring member within the past n blocks would have to be the real spend.
|
|
|
|
|
/// Preventing this at the consensus layer ensures privacy and integrity.
|
2024-02-19 18:34:10 -08:00
|
|
|
pub const DEFAULT_LOCK_WINDOW: usize = 10;
|
2024-06-22 09:02:59 -04:00
|
|
|
|
|
|
|
|
/// The minimum amount of blocks a coinbase output is locked for.
|
2024-02-19 18:34:10 -08:00
|
|
|
pub const COINBASE_LOCK_WINDOW: usize = 60;
|
2024-06-22 09:02:59 -04:00
|
|
|
|
|
|
|
|
/// Monero's block time target, in seconds.
|
2024-02-19 18:34:10 -08:00
|
|
|
pub const BLOCK_TIME: usize = 120;
|