You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
aztec-nr isn't properly specifying the visibility of its re-exports so
there's a ton of warnings. This PR addresses some of them along with
some unused imports.
// When this initialization nullifier is emitted, an observer could do a dictionary or rainbow attack to learn the preimage of this nullifier to deduce the storage slot and contract address.
33
30
// For some applications, leaking the details that a particular state variable of a particular contract has been initialized will be unacceptable.
34
31
// Under such circumstances, such application developers might wish to _not_ use this state variable type.
35
-
// This is especially dangerous for initial assignment to elements of a `Map<AztecAddress, PrivateImmutable>` type (for example), because the storage slot often also identifies an actor.
32
+
// This is especially dangerous for initial assignment to elements of a `Map<AztecAddress, PrivateImmutable>` type (for example), because the storage slot often also identifies an actor.
36
33
// e.g. the initial assignment to `my_map.at(msg.sender)` will leak: `msg.sender`, the fact that an element of `my_map` was assigned-to for the first time, and the contract_address.
0 commit comments