| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
| | |
| | |
| | | |
3.3 seconds -> 2.8 seconds on a test case
|
| | | |
| | |
| | |
| | | |
5.2 seconds -> 4.1 seconds on a test case
|
| |/ /
| |
| |
| | |
5.9 second -> 5.2 seconds on a test case
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Implements view tags as proposed by @UkoeHB in MRL issue
https://github.com/monero-project/research-lab/issues/73
At tx construction, the sender adds a 1-byte view tag to each
output. The view tag is derived from the sender-receiver
shared secret. When scanning for outputs, the receiver can
check the view tag for a match, in order to reduce scanning
time. When the view tag does not match, the wallet avoids the
more expensive EC operations when deriving the output public
key using the shared secret.
|
| | |
| |
| |
| |
| |
| | |
https://github.com/ArticMine/Monero-Documents/blob/master/MoneroScaling2021-02.pdf
with a change to use 1.7 instead of 2.0 for the max long term increase rate
|
| |\ \
| | |
| | |
| | | |
da9aa1f Copyright: Update to 2022 (mj-xmr)
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | | |
ae0a840 wallet2: decrease the amount of data exchanged for output export (moneromooo-monero)
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
bd27deb Bulletproofs+ (SarangNoether)
b7713cc Precompute initial transcript hash (SarangNoether)
b535d66 Updates from security audit (SarangNoether)
a0d80b1 plug bulletproofs plus into consensus (moneromooo-monero)
75bd004 ringct: a few minor optimizations from review (moneromooo-monero)
a345060 ringct: port some of vtnerd's review changes from BP+ to BP (moneromooo-monero)
4c94cfe store outPk/8 in the tx for speed (moneromooo-monero)
5acdd0e bulletproofs+: some minor cleanup from vtnerd's review (moneromooo-monero)
|
| | |/ / |
|
| |/ / |
|
| |\ \
| | |
| | |
| | | |
e08abaa multisig key exchange update and refactor (koe)
|
| | |/ |
|
| |/
|
|
|
| |
we reuse the wallet_keys_unlocker object, which does the right thing
in conjunction with other users of decrypt/encrypt (ie, refresh).
|
| | |
|
| |\
| |
| |
| | |
f9b5b52 fix serialization being different on mac (moneromooo-monero)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On Mac, size_t is a distinct type from uint64_t, and some
types (in wallet cache as well as cold/hot wallet transfer
data) use pairs/containers with size_t as fields. Mac would
save those as full size, while other platforms would save
them as varints. Might apply to other platforms where the
types are distinct.
There's a nasty hack for backward compatibility, which can
go after a couple forks.
|
| |\ \
| |/
|/|
| | |
f346e3e wallet_rpc_payments: implement multithreading (gdmojo)
|
| | | |
|
| |\ \
| |/
|/|
| | |
186271e monero-wallet-cli: Added command scan_tx (Horia Mihai David)
|
| | |
| |
| |
| | |
To implement this feature, the wallet2::scan_tx API was implemented.
|
| |/ |
|
| |\
| |
| |
| | |
ec14e4b8c wallet2: skip reorgs exceeding max-reorg-depth wallet setting (xiphon)
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
They are allowed from v12, and MLSAGs are rejected from v13.
|
| |\
| |
| |
| | |
07442a605 Fix build with Boost 1.74 (moneromooo-monero)
|
| | |
| |
| |
| | |
Thanks iDunk for testing
|
| |\ \
| | |
| | |
| | |
| | | |
85899230d simplewallet: allow setting tx keys when sending to a subaddress (moneromooo-monero)
e916201f1 wallet2: fix setting tx keys when another is already set (moneromooo-monero)
|
| | |/
| |
| |
| | |
The tx key derivation is different then
|
| |\ \
| | |
| | |
| | | |
7175dcb10 replace most boost serialization with existing monero serialization (moneromooo-monero)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reduces the attack surface for data that can come from
malicious sources (exported output and key images, multisig
transactions...) since the monero serialization is already
exposed to the outside, and the boost lib we were using had
a few known crashers.
For interoperability, a new load-deprecated-formats wallet
setting is added (off by default). This allows loading boost
format data if there is no alternative. It will likely go
at some point, along with the ability to load those.
Notably, the peer lists file still uses the boost serialization
code, as the data it stores is define in epee, while the new
serialization code is in monero, and migrating it was fairly
hairy. Since this file is local and not obtained from anyone
else, the marginal risk is minimal, but it could be migrated
later if needed.
Some tests and tools also do, this will stay as is for now.
|
| |/ /
| |
| |
| | |
This reverts commit 921dd8dde5d381052d0aa2936304a3541a230c55.
|
| |\ \
| | |
| | |
| | | |
76c16822d wallet2_api: implement runtime proxy configuration (xiphon)
|
| | |/ |
|
| |/ |
|
| |\
| |
| |
| | |
5ef0607da Update copyright year to 2020 (SomaticFanatic)
|
| | |
| |
| |
| | |
Update copyright year to 2020
|
| |/ |
|
| |\
| |
| |
| | |
7a8c1ee wallet2: fix subaddress expansion when receiving monero (moneromooo-monero)
|
| | | |
|
| |\ \
| | |
| | |
| | | |
8b655de simplewallet: report timestamp based expected unlock time on balance (moneromooo-monero)
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | | |
e509ede trezor: adapt to new passphrase mechanism (ph4r05)
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| | |
- choice where to enter passphrase is now made on the host
- use wipeable string in the comm stack
- wipe passphrase memory
- protocol optimizations, prepare for new firmware version
- minor fixes and improvements
- tests fixes, HF12 support
|