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
@@ -80,13 +82,13 @@ The following code demonstrates how to reserve collateral by calling the [`reser
80
82
81
83
## Generate Proof with Flare Data Connector
82
84
83
-
Use the [FDC Payment](/fdc/guides/hardhat/payment) script to generate a Merkle proof by providing the XRP transaction details.
84
-
85
-
FDC returns an attestation response with the required proof structure to execute minting.
85
+
Use the [FDC Payment](/fdc/guides/hardhat/payment) script to validate the XRP payment and generate a Merkle proof.
86
86
87
87
## Execute Minting
88
88
89
-
Once you have the proof, call [`executeMinting()`](/fassets/reference/IAssetManager#executeminting) to mint FAssets.
89
+
Once the XRP payment is validated, you can retrieve the FDC proof from the [Data Availability Layer](/fdc/overview#data-availability-layer) and call the [`executeMinting()`](/fassets/reference/IAssetManager#executeminting) function on the AssetManager contract.
90
+
91
+
This script demonstrates how to retrieve the FDC proof and execute minting.
@@ -98,7 +100,7 @@ Once you have the proof, call [`executeMinting()`](/fassets/reference/IAssetMana
98
100
2. Declare the constant `ASSET_MANAGER_ADDRESS` pointing to the FXRP AssetManager on the Songbird Testnet (Coston network).
99
101
100
102
3. Set the collateral reservation ID to the previously reserved minting request.
101
-
4. Set the Flare Data Connector (FDC) round ID to retrieve the proof for.
103
+
4. Set the Flare Data Connector (FDC) round ID to retrieve the proof.
102
104
5. Prepare the FDC request payload data.
103
105
6. Function to get the proof from the FDC. It sends a POST request to the [Flare Data Availability Layer](/fdc/overview#data-availability-layer) and returns a Merkle proof and attestation response from FDC.
104
106
7. Retrieve the FDC proof from the Data Availability Layer.
0 commit comments