Skip to content

Commit 02b7d4b

Browse files
Update develop/interoperability/best-practices-for-teleporting-assets.md
Co-authored-by: Nicolás Hussein <[email protected]>
1 parent 25ebdda commit 02b7d4b

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

develop/interoperability/best-practices-for-teleporting-assets.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -230,7 +230,12 @@ For dealing with non-sufficient assets and fees, there are different fee payment
230230

231231
## Comprehensive Dry Run Testing
232232

233-
Dry run testing represents the most critical step in preventing asset loss during teleportation. Execute dry runs on both the source and destination chains to validate every aspect of the transfer before committing to the actual transaction. Local dry runs on the source chain validate transaction construction correctness, sufficient balance for transfer and fees, and proper XCM message generation. Remote dry runs on the destination chain verify that the XCM message will execute successfully, including asset reception and processing, account creation or balance updates, and proper fee deduction. This two-phase validation approach catches the majority of potential issues before they can cause problems in production.
233+
Dry run testing represents the most critical step in preventing asset loss during teleportation. Execute dry runs on both the source and destination chains to validate every aspect of the transfer before committing to the actual transaction. You can perform local dry runs or remote dry runs:
234+
235+
- Local dry runs on the source chain validate transaction construction correctness, sufficient balance for transfer and fees, and proper XCM message generation.
236+
- Remote dry runs on the destination chain verify that the XCM message will execute successfully, including asset reception and processing, account creation or balance updates, and proper fee deduction.
237+
238+
This two-phase validation approach catches the majority of potential issues before they can cause problems in production.
234239

235240
### Example Dry Run Implementation
236241

0 commit comments

Comments
 (0)