taler-docs

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

commit 730a10804d3dd23aa3f5d74ae0520fb732f493d2
parent 50222a7ea8436b6e7210d7c67807e5d61400899e
Author: Christian Grothoff <christian@grothoff.org>
Date:   Mon, 22 Dec 2025 22:22:54 +0100

vDOLDPLUS == v32

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

diff --git a/core/api-exchange.rst b/core/api-exchange.rst @@ -1987,7 +1987,7 @@ and prove that the age restriction was set correctly. The request body is a `RevealWithdrawRequest`. - This endpoint was introduced in this form in protocol **vDOLDPLUS**. + This endpoint was introduced in this form in protocol **v32**. :http:statuscode:`200 OK`: The coin's' secret material matched the commitment and the original request was well-formed. @@ -2111,7 +2111,7 @@ Melt exchange. The exchange MUST return a 307 or 308 redirection to the correct base URL if this is the case. - This endpoint was introduced in this form in protocol **vDOLDPLUS**. + This endpoint was introduced in this form in protocol **v32**. :http:statuscode:`200 OK`: The request was successful. The response body is `MeltResponse` in this case. @@ -2164,10 +2164,10 @@ Melt value_with_fee: Amount; // @since v27 - // @deprecated vDOLDPLUS + // @deprecated **v32** // Seed from which the nonces for the n*κ coin candidates are derived from. // - // @since vDOLDPLUS + // @since **v32** // The ``refresh_seed`` is an opaque value to the exchange. // It is provided by the client and is verified with the ``coin_sig`` below. // Its purpose is to ensure that the honest owner of the old coin @@ -2214,7 +2214,7 @@ Melt // each matching the respective entries in ``denoms_h``. coin_evs: CoinEnvelope[kappa][]; - // @since vDOLDPLUS + // @since **v32** // ``kappa`` arrays of ``n`` entries of transfer public keys each. // These are ephemeral ECDHE keys that allow the owner of a coin // to (re-)obtain the derived coins from a refresh operation, f.e. should @@ -2309,7 +2309,7 @@ as proof that the age restriction was set correctly (if applicable). The request body is a `RevealMeltRequest`. - This endpoint was introduced in this form in protocol **vDOLDPLUS**. + This endpoint was introduced in this form in protocol **v32**. :http:statuscode:`200 OK`: The coin's' secret material matched the commitment and the original request was well-formed. @@ -2340,14 +2340,14 @@ as proof that the age restriction was set correctly (if applicable). rc: HashCode; // @since v27 - // @deprecated vDOLDPLUS + // @deprecated **v32** // The disclosed kappa-1 signatures by the old coin's private key, // over Hash1a("Refresh", Cp, r, i), where Cp is the melted coin's public key, // r is the public refresh nonce from the metling step and i runs over the // _disclosed_ kappa-1 indices. signatures: CoinSignature[kappa-1]; - // @since vDOLDPLUS + // @since **v32** // 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 @@ -2787,7 +2787,7 @@ became minted, and proof ownership of the coin itself. Note that the original withdrawal fees will **not** be recouped. - .. note:: This endpoint still Work-in-Progress. It will be implemented in **vRECOUP**, sometime after **vDOLDPLUS**. + .. note:: This endpoint still Work-in-Progress. It will be implemented in **vRECOUP**, sometime after **v32**. **Request:** @@ -2935,7 +2935,7 @@ became minted, and proof ownership of the coin itself. Note that the original refresh fees will **not** be recouped. - .. note:: This endpoint still Work-in-Progress. It will be implemented in **vRECOUP**, sometime after **vDOLDPLUS**. + .. note:: This endpoint still Work-in-Progress. It will be implemented in **vRECOUP**, sometime after **v32**. **Request:** @@ -3586,7 +3586,7 @@ The GET request should come with the following HTTP headers: // Hash over the age commitment of the coin. Optional. old_age_commitment_h?: AgeCommitmentHash; - // @since vDOLDPLUS + // @since **v32** // This value is opaque to the exchange. It was provided by the client // as part of the original refresh request, and was therefore verified // with the confirm_sig below. @@ -3596,22 +3596,22 @@ The GET request should come with the following HTTP headers: // refresh request and replay it refresh_seed: HashCode; - // @since vDOLDPLUS + // @since **v32** // The kappa*n list of transfer public keys that were provided by the // old coin owner during the melt request. transfer_pubs: EddsaPublicKey[kappa][]; - // @since vDOLDPLUS + // @since **v32** // The n denomination public keys for the fresh coins // that the coin owner had requested. denoms_h: HashCode[]; - // @since vDOLDPLUS + // @since **v32** // The ``noreveal_index`` value that was returned by the exchange as response // to the melt request. noreveal_index: Integer; - // @since vDOLDPLUS + // @since **v32** // If the reveal step was successfully peformed by the coin owner, // this field contains the blind coin signatures that were returned // by the exchange for the chosen batch of coins.