taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 82a2e4cb27d583e0ae03b0047638f82ed87fbd32
parent 23575f9d30be7c161b8514681eef67fb970aa2c7
Author: Özgür Kesim <oec-taler@kesim.org>
Date:   Fri, 12 Dec 2025 11:38:13 +0100

[exchange] fix term for transfer _private key_ in melt/reveal

Diffstat:
Mcore/api-exchange.rst | 27+++++++++++++++------------
1 file changed, 15 insertions(+), 12 deletions(-)

diff --git a/core/api-exchange.rst b/core/api-exchange.rst @@ -2217,16 +2217,17 @@ Melt // ``master_refresh_seed)`` // // These batch seeds (however constructed) are relevant in the - // subsequent reveal step of the cut-and-chose. There, each of the - // revealed batch seeds is expanded to a batch of ``n`` transfer secrets + // subsequent reveal step of the cut-and-chose. Each of the + // revealed seeds is expanded to a batch of ``n`` transfer private keys // via HKDF: // - // ``ts[k][] = HKDF(n*sizeof(HashCode),`` - // ``"refresh-batch-transfer-secrets",`` + // ``tp[k][] = HKDF(n*sizeof(HashCode),`` + // ``"refresh-batch-transfer-priv",`` // ``bs[k])`` // - // An individual coin's transfer secret at kappa-index k and - // coin index i in the batch is then ``ts[k][i]``. + // An individual coin's transfer private key at kappa-index k and + // coin index i in the batch is then ``tp[k][i]``. The corresponding + // transfer _public_ keys are given in the field ``transfer_pubs``. master_refresh_seed: HashCode; // Master seed for the Clause-Schnorr R-value @@ -2359,15 +2360,17 @@ as proof that the age restriction was set correctly (if applicable). signatures: CoinSignature[kappa-1]; // @since vDOLDPLUS - // The seeds for the transfer secrets to reveal, as they - // were generated for the previous `MeltRequest`. - // That is, for the kappa many batches of n coin candidates, - // the seeds for _all_ kappa were are expanded via HKDF: + // The batch seeds for the transfer private keys to reveal, + // as they were generated for the previous `MeltRequest`. + // That is, assuming an honest client who had generated + // kappa many batch seeds via HKDF like this: + // // ``bs[] = HKDF(kappa*sizeof(HashCode),`` // ``"refresh-batch-seeds",`` // ``old_coin_priv,`` - // ``master_refresh_seed)`` - // This field contains the entries in ``bs[]`` for all the indeces + // ``master_refresh_seed)``, + // + // this field contains the entries in ``bs[]`` for all the indeces // *except* the ``noreveal_index``. batch_seeds: HashCode[kappa-1];