taler-docs

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

commit eafdf52131f8635b523163c35786e97101e1b871
parent d7ef2c1e7178bd48aea3111feab7f2ff9e720e2b
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sun, 24 Sep 2023 18:10:04 +0200

api update for batch-deposit signatures

Diffstat:
Mcore/api-auditor.rst | 10++++++----
Mcore/api-exchange.rst | 10+---------
2 files changed, 7 insertions(+), 13 deletions(-)

diff --git a/core/api-auditor.rst b/core/api-auditor.rst @@ -184,10 +184,12 @@ paid out first. // amount with fee and the fee from the deposit request. amount_without_fee: Amount; - // The coin's public key. This is the value that must have been - // signed (blindly) by the Exchange. The deposit request is to be - // signed by the corresponding private key (using EdDSA). - coin_pub: CoinPublicKey; + // Array of public keys of the deposited coins. + coin_pubs: EddsaPublicKey[]; + + // Array of deposit signatures of the deposited coins. + // Must have the same length as ``coin_pubs``. + coin_sigs: EddsaSignature[]; // The Merchant's public key. Allows the merchant to later refund // the transaction or to inquire about the wire transfer identifier. diff --git a/core/api-exchange.rst b/core/api-exchange.rst @@ -3249,15 +3249,7 @@ proof to the seller for the escrow of sufficient fund. // which signing key was used. exchange_pub: EddsaPublicKey; - // Array of deposit confirmation signatures from the exchange - // Entries must be in the same order the coins were given - // in the batch deposit request. - exchange_sigs: DepositConfirmationSignature[]; - } - - .. ts:def:: DepositConfirmationSignature - - interface DepositConfirmationSignature { + // Deposit confirmation signature from the exchange. // The EdDSA signature of `TALER_DepositConfirmationPS` using a current // `signing key of the exchange <sign-key-priv>` affirming the successful // deposit and that the exchange will transfer the funds after the refund