From 2fc9dc814dbd95675f8fadd5ab52535e1d509435 Mon Sep 17 00:00:00 2001 From: Jack Grigg Date: Fri, 29 Apr 2022 10:26:25 +0000 Subject: [PATCH] book: Fix TODOs on Actions design page Closes zcash/orchard#78. --- book/src/design/actions.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/book/src/design/actions.md b/book/src/design/actions.md index 3da38a95..5bbcec98 100644 --- a/book/src/design/actions.md +++ b/book/src/design/actions.md @@ -18,10 +18,9 @@ bundle of actions, where each action is both a spend and an output. This provide inherent arity-hiding as multi-JoinSplit Sprout, but using Sapling value commitments to balance the transaction without doubling its size. -TODO: Depending on the circuit cost, we _may_ switch to having an action internally -represent either a spend or an output. Externally spends and outputs would still be -indistinguishable, but the transaction would be larger. - ## Memo fields -TODO: One memo per tx vs one memo per output +Each Orchard action has a memo field for its corresponding output, as with Sprout and +Sapling. We did at one point consider having a single Orchard memo field per transaction, +and/or having a mechanism for enabling multiple recipients to decrypt the same memo, but +these were decided against in order to keep the overall design simpler.