Update docs/pages/treasury-operations/transaction-verification.mdx

Co-authored-by: Elliot <34463580+ElliotFriedman@users.noreply.github.com>

Author: DicksonWu654

docs/pages/treasury-operations/transaction-verification.mdx

@@ -118,7 +118,9 @@ Request from sender:
 - **\<$10M**: Single transaction preferred (simpler, one confirmation cycle, cleaner records)
 - **\>$10M**: Consider 2-3 separate transactions (reduces single-transaction risk, allows staged confirmation, provides pause points to verify each step)
 - **\>$50M**: Multiple transactions strongly recommended with 30-minute intervals between each
+**Anti-Duress Protocols:**
 
+Since kidnapping and other forms of duress have been employed by criminals to steal cryptocurrency, organizations should prepare for this. Establish a duress word that indicates a transfer is not being made of your own free will. Once the duress word is mentioned during an exchange involving the transfer, law enforcement will be contacted and the transaction not processed. Procedures should be put in place with concrete run books for these situations. Safe words should not appear in run books or any digital format.
 **Anti-Social-Engineering Protocols:**
 
 Establish code phrase during initial verified meeting. Use this phrase to authenticate any address changes or unusual requests. Example: "What was the name of the restaurant where we finalized the agreement?" Exchange secondary contact numbers for key personnel - if primary contact requests changes, call secondary to confirm. Maintain out-of-band verification: if request comes via email, confirm via phone.