forked from trezor/trezor-core
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
3 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,8 +8,6 @@ REVIEWER = Tomas Susanka <[email protected]>, | |
Jan Pochyla <[email protected]>, | ||
Ondrej Vejpustek <[email protected]> | ||
|
||
ADVISORS = | ||
|
||
----- | ||
|
||
This Monero implementation was implemented from scratch originally for TREZOR by porting Monero C++ code to the Python codebase. | ||
|
@@ -249,7 +247,7 @@ will load encrypted TX keys, decrypt it and generate the proof. | |
|
||
## Implementation notes | ||
|
||
Few notes on desing / implementation. | ||
Few notes on design / implementation. | ||
|
||
### Cryptography | ||
|
||
|
@@ -307,7 +305,8 @@ MLSAG may need to be slightly changed when implementing multisigs | |
|
||
Bulletproof generation and verification is implemented, however the device can handle maximum 2 batched outputs | ||
in the bulletproof due to high memory requirements (more on that in [monero-doc]). If number of outputs is larger | ||
than 2 the offloading to host is required. | ||
than 2 the offloading to host is required. In such case, the bulletproofs are first computed at the host and sent to | ||
Trezor for verification. | ||
|
||
Bulletproof implementation is covered by unit tests, the proofs in unittest were generated by the Monero C++ | ||
implementation. | ||
|