From 1f4e38c27fe552834aef7490f035f13d835f8c4e Mon Sep 17 00:00:00 2001 From: simsbluebox Date: Mon, 30 Dec 2024 13:46:58 -0300 Subject: [PATCH] meta-peg-out technical documentation: @tenuki review - minor fix --- developers/contracts/meta-peg-out-endpoint-v2-03.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developers/contracts/meta-peg-out-endpoint-v2-03.md b/developers/contracts/meta-peg-out-endpoint-v2-03.md index ab0cd71..e9611ed 100644 --- a/developers/contracts/meta-peg-out-endpoint-v2-03.md +++ b/developers/contracts/meta-peg-out-endpoint-v2-03.md @@ -89,7 +89,7 @@ Key validations include: - The request must exist. - The token pair must be approved and operational (not paused for peg-out). - The transaction cannot be indexed to a time before the contract deployment. -- The transaction's metaprotocol token (BRC-20) must match the requested details (`tick` and `amount`). Additionally, the `from` address must correspond to the `fulfilled-by address`, and the `to` address must match the `peg-out-address`. +- The transaction's metaprotocol token (BRC-20) must match the requested details (`tick` and `amount`). Additionally, the `from` address must correspond to the `fulfilled-by` address, and the `to` address must match the `peg-out-address`. - The request must not be revoked or already finalized. The procedure is as follows, based on who finalizes it: