Jack Grigg
Jack Grigg
The other relevant issue is zcash/zcash#1614 and the issues linked therein.
This is the [list of conditions](https://github.com/zcash/zcash-seeder/blob/01fc41b063d83a9bc19ebb12e9e48bb7ae659096/db.h#L104-L120) enforced by `zcash-seeder` on peers in order for their IPs to be given out: - The peer's port must be 8233 on mainnet or...
TREZOR's transparent transaction workflow is documented here: https://wiki.trezor.io/Developers_guide:Message_Workflows
Extracts from the discussion that led to me posting the above comment: - RedJubjub is the operation that defines spend authority. Everything else in the list above is for the...
Currently, we store witness-related data with the wallet transaction it belongs to. IIRC we considered having a single witness data entity and then decided against it (possibly to try and...
```mermaid flowchart BT FullPrivacy --> AllowRevealedAmounts AllowRevealedAmounts --> AllowRevealedRecipients AllowRevealedAmounts --> AllowRevealedSenders AllowRevealedSenders --> AllowLinkingAccountAddresses AllowRevealedRecipients --> AllowFullyTransparent AllowRevealedSenders --> AllowFullyTransparent AllowFullyTransparent --> NoPrivacy AllowLinkingAccountAddresses --> NoPrivacy ````
> Informed users may prefer to use Zcash as is actively encouraged: only using fully shielded transactions. Unified addresses do not prevent this use case. A "Unified Address" encodes the...
> It's expected and inevitable that Hush will diverge from how Zcash will use the memo field That may be the case, but there is still benefit in reducing the...
> In an attack scenario, where an attacker sends a 1MB memo data with "faked" 2 byte length field, what are wallets supposed to do? Without consensus rules to protect...
@daira requested that this proposal instead be combined with ZIP 302, and that we use ZIP 302 as the canonical memo field specification with future updates as necessary. Once #105...