mirror of
https://github.com/serai-dex/serai.git
synced 2025-12-08 12:19:24 +00:00
Remove note about adding in a DB handle
It'd arguably be safer yet it isn't worth the API complexity.
This commit is contained in:
@@ -213,7 +213,6 @@ impl Scanner {
|
|||||||
/// When a new scanner is created, ALL saved output keys must be passed in to be secure.
|
/// When a new scanner is created, ALL saved output keys must be passed in to be secure.
|
||||||
/// If None is passed, a modified shared key derivation is used which is immune to the burning
|
/// If None is passed, a modified shared key derivation is used which is immune to the burning
|
||||||
/// bug (specifically the Guaranteed feature from Featured Addresses).
|
/// bug (specifically the Guaranteed feature from Featured Addresses).
|
||||||
// TODO: Should this take in a DB access handle to ensure output keys are saved?
|
|
||||||
pub fn from_view(pair: ViewPair, burning_bug: Option<HashSet<CompressedEdwardsY>>) -> Scanner {
|
pub fn from_view(pair: ViewPair, burning_bug: Option<HashSet<CompressedEdwardsY>>) -> Scanner {
|
||||||
let mut subaddresses = HashMap::new();
|
let mut subaddresses = HashMap::new();
|
||||||
subaddresses.insert(pair.spend.compress(), None);
|
subaddresses.insert(pair.spend.compress(), None);
|
||||||
|
|||||||
Reference in New Issue
Block a user