Update Verifier section transaction examples to use `intents.near`

[thisisjoshford]

Problem

The "Real transaction examples" tables across the Verifier Contract docs contain transaction links that reference the old deprecated defuse contract address. These should be replaced with current transactions that use the intents.near contract to avoid confusing integrators.

Current state

integration/verifier-contract/account-abstraction.mdx

Operation	Transaction	Line(s)
Add public key	FBTRk6jRUSW3E1SjBfYbA71DhN5xTX1yE2foy98TafrM	57, 143
Remove public key	69XiJcRtipZ2i8bkHHgCaSAkswd8Lt6VxiJuM8dKq9qn	144

integration/verifier-contract/deposits-and-withdrawals/deposits.mdx

Operation	Transaction	Line
Deposit tokens	DWv4AkrLxnbJV6paqSFR3Tt42SdVAtunBbEi2XATdXTW	136
Deposit + execute intents	Bn3iC9B1uUJrX59x7cfxngY1E159HspzTCyyDVwx5DMJ	137
Deposit + swap + withdraw	BMFcWFReAzbH8okweUio2nNTuVXtMr1hXeaaNR4UhEzS	138

integration/verifier-contract/deposits-and-withdrawals/withdrawals.mdx

Operation	Transaction	Line
Withdraw by transaction	3E8TDSLq2Xn8JZEAdbeX8NGS7Ps6f1EwLeoFxhT7YY3G	101
Deposit + swap + withdraw	BMFcWFReAzbH8okweUio2nNTuVXtMr1hXeaaNR4UhEzS	102
Execute intents	FxpbspXjRQg3gDii18ibp3w7yvbe7MWaDHQfVqVfq7xN	103

What needs to happen

1. Find replacement transactions — For each operation listed above, find a recent, successful mainnet transaction that interacts with the intents.near contract.

2. Update account-abstraction.mdx — Replace both the inline example link (line 57) and the table entries (lines 143–144) with new intents.near transactions.

3. Update deposits.mdx — Replace table entries (lines 136–138).

4. Update withdrawals.mdx — Replace table entries (lines 101–103).

5. Verify all links — Confirm each NearBlocks link resolves correctly and shows the expected operation against intents.near.

Files to update

• integration/verifier-contract/account-abstraction.mdx
• integration/verifier-contract/deposits-and-withdrawals/deposits.mdx
• integration/verifier-contract/deposits-and-withdrawals/withdrawals.mdx

Selection criteria for new transactions

• Must interact with intents.near (not the deprecated defuse contract)
• Should be recent (within the last few months)
• Should be successful transactions
• Should clearly demonstrate the labeled operation
• Prefer transactions with straightforward, easy-to-follow execution traces

Notes

• The BMFcWFRe... transaction (Deposit + swap + withdraw) appears in both deposits.mdx and withdrawals.mdx — use the same replacement in both places
• The FBTRk6jR... transaction (Add public key) appears twice in account-abstraction.mdx — once inline (line 57) and once in the table (line 143)