You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: packages/runtime/client/rest/src/contract/header.ts
+2-2
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ import { TxStatus } from "./transaction/status.js";
22
22
* Use {@link index.RestClient#getContractById} to get full contract details
23
23
*
24
24
* @see The {@link https://github.com/input-output-hk/marlowe-cardano/blob/b39fe3c3ed67d41cdea6d45700093e7ffa4fad62/marlowe-runtime-web/src/Language/Marlowe/Runtime/Web/Types.hs#L502 | The backend definition } of this type
* Configure Roles using tokens previously Minted. These Role Tokens are already defined (via an NFT platform, cardano-cli, another Marlowe Contract Created, etc.. )
198
+
* @param policyId The policy Id of All the token roles defined in the Marlowe Contract DSL
199
+
* @param openRoleNames defines all the Roles to be Open (Others will be Closed)
200
+
* @remarks
201
+
* It is under the user's responsability to create and distribute properly these role tokens
202
+
* - Make sure all the Token Name are minted and match all the Role Names defined in the contract
203
+
* - Depending on the Marlowe Contract logic, make sure the tokens are distributed to the right wallet
204
+
* When using Open Role Tokens
205
+
* - Thread Role Token needs to me minted when using Open Roles (by default threadRoleName = "")
* Build an unsigned transaction (sign with the {@link @marlowe.io/wallet!api.WalletAPI#signTx} procedure) which withdraws available payouts from a contract (when applied with the {@link @marlowe.io/runtime-rest-client!index.RestClient#submitWithdrawal} procedure).
167
155
* @see {@link https://docs.marlowe.iohk.io/api/withdraw-payouts | The backend documentation}
168
156
*/
157
+
// TODO: Jamie, remove the `s from the end of the endpoint name in the docs site
158
+
// DISCUSSION: @Jamie, @N.H: Should this be called `buildWithdrawPayoutsTx` instead? As it is not withdrawing the
159
+
// payout, rather it is creating the transaction to be signed
169
160
withdrawPayouts(
170
161
request: Withdrawals.WithdrawPayoutsRequest
171
162
): Promise<Withdrawals.WithdrawPayoutsResponse>;
@@ -257,14 +248,21 @@ export function mkRestClient(baseURL: string): RestClient {
* Role Token Configuration for the new contract passed in the `contract` field.
61
+
*
62
+
* <h4>Participants</h4>
63
+
* <p>
64
+
* Participants ({@link @marlowe.io/language-core-v1!index.Party | Party}) in a Marlowe Contract can be expressed in 2 ways:
65
+
*
66
+
* 1. **By Adressses** : When an address is fixed in the contract we don't need to provide further configuration.
67
+
* 2. **By Roles** : When the participation is done through a Role Token, we need to define if that token is minted as part of the contract creation transaction or if it was minted beforehand.
68
+
*
69
+
* </p>
70
+
*
71
+
* <h4>Configuration Options</h4>
72
+
* <p>
73
+
*
74
+
* - **When to create (mint)**
75
+
* - **Within the Runtime** : At the contrat creation, these defined Roles Tokens will be minted "on the fly" by the runtime.
76
+
* - **Without the Runtime** : before the creation, these Role Tokens are already defined (via an NFT platform, `cardano-cli`, another Marlowe Contract Created, etc.. )
77
+
* - **How to distribute**
78
+
* - **Closedly** (Closed Roles) : At the creation of contract or before, the Role Tokens are released to the participants. All the participants are known at the creation and therefore we consider the participation as being closed.
79
+
* - **Openly** (Open Roles) : Whoever applies an input (IDeposit or IChoice) on the contract `contract` first will be identified as a participant by receiving the Role Token in their wallet. In that case, participants are unknown at the creation and the participation is open to any meeting the criteria.
80
+
* - **With or without Metadata**
81
+
* - **Quantities to create(Mint)** : When asking to mint the tokens within the Runtime, quantities can defined as well.
82
+
*
83
+
* Smart Constructors are available to ease these configuration:
0 commit comments