Wallet transfer to unverified counterparty

Example input

A user asks whether they should transfer crypto to a wallet address provided by a private group, chat contact, or weakly verified counterparty.

Expected static output

A source-bound action note that separates wallet destination details, counterparty identity, ownership proof, warning sources, missing inputs, and stop rules.

Best used when

• The transfer would be difficult to reverse after the wallet transaction is sent.
• The agent needs to keep wallet ownership and destination evidence separate from the message requesting payment.

Not used for

• Live screening, live compliance clearance, or request-time approval.
• Trading, backtesting, execution, investment advice, or legal advice.
• Token-risk, meme-coin, smart-contract, liquidity, rug-pull, or wallet-forensics scoring.

Source freshness

This pack preserves a static source snapshot and citation trail; it does not fetch fresh third-party data at request time.

Agent reading hint

Read the HTML page first for boundaries, then use the JSON artifact for structured retrieval.

Inputs

• intendedAction: the action the agent or user is considering
• counterparty: optional provider, wallet, company, app, or group name
• claims: one or more claims the agent saw or wants to repeat
• paymentMethod: optional card, bank, crypto, brokerage, or unspecified rail
• assetClass: optional equity, crypto, fund, macro, or other label

Outputs

• block/review decision for the wallet transfer request
• risk flags for counterparty weakness, wallet-ownership gaps, explorer ambiguity, and irreversible-payment pressure
• required verification steps before any crypto transfer proceeds

Use this pack when

• Use this pack when the task already matches this scenario: A financial agent is asked to send a crypto wallet transfer to a new counterparty in a private group, but the wallet address, ownership claims, and counterparty identity are not independently verified.
• Use it when the reader needs a bounded checklist, sample evidence records, and an example of safe versus blocked language.
• Treat Wallet transfer to unverified counterparty as a scenario-specific public review guide that sits on top of the linked Action Preflight service.

Stop at this pack when

• Stop at this pack when you need a public, static explanation of what should be checked and how the review should be framed.
• Stop here when the goal is to teach a crawler, agent, or human reviewer the shape of the evidence rather than produce a live decision.
• Escalate beyond this pack when the case becomes ambiguous, private, high-value, or legally sensitive.

Move to the linked artifact when

• Open the linked JSON artifact when another system needs the stable machine-readable pack payload.
• Move to the related service page when the task needs the broader service contract instead of only this scenario.
• Treat the related artifacts as public references and handoff surfaces, not as live approval records.

This pack does not do

• Runs as a static/client-side demo in this phase, not a server-side decision service
• Does not prove an action is legal, safe, suitable, profitable, or compliant
• High-risk or ambiguous actions still require qualified human review
• The pack does not verify beneficial ownership, recover sent funds, or replace sanctions, legal, custody, or compliance review.
• The pack is not a token-risk, meme-coin, smart contract, liquidity, rug-pull, or wallet-forensics scanner.

Suitable for

• AI agents preparing wallet transfers, OTC settlement drafts, or private-group payment flows
• Human reviewers checking whether a wallet destination and counterparty record are too weak to justify transfer
• Crawlers and retrieval systems that need a concrete public example of wallet-transfer reliability review

Not suitable for

• Runs as a static/client-side demo in this phase, not a server-side decision service
• Does not prove an action is legal, safe, suitable, profitable, or compliant
• High-risk or ambiguous actions still require qualified human review
• The pack does not verify beneficial ownership, recover sent funds, or replace sanctions, legal, custody, or compliance review.
• The pack is not a token-risk, meme-coin, smart contract, liquidity, rug-pull, or wallet-forensics scanner.

Source / limitation policy

• https://consumer.ftc.gov/articles/what-know-about-cryptocurrency-scams
• https://consumer.ftc.gov/articles/what-do-if-you-were-scammed
• https://www.fbi.gov/how-we-can-help-you/victim-services/national-crimes-and-victim-resources/cryptocurrency-investment-fraud
• https://ofac.treasury.gov/sanctions-list-service
• https://ofac.treasury.gov/system/files/126/virtual_currency_guidance_brochure.pdf
• https://www.cftc.gov/LearnAndProtect/AdvisoriesAndArticles/Beware_Imposters

Evidence to collect

• The exact wallet address, chain/network, checksum form, memo/tag or destination tag, amount, and transfer deadline exactly as requested.
• The message thread, private group post, invoice, or OTC note where the wallet destination and counterparty claims appeared.
• Any signed message, ownership proof, exchange statement, official domain record, or verified channel tying the wallet address to the claimed counterparty.
• Timestamped explorer checks, sanctions or warning-list lookups, and any mismatch between the counterparty story and the address history.

Delivery outputs

• A block-or-review decision that keeps the wallet transfer paused while counterparty or ownership evidence remains unresolved.
• A bounded evidence summary separating private-group claims from cited wallet, counterparty, destination-integrity, and chain facts.
• A concrete list of verification gaps before any irreversible crypto transfer proceeds.
• Safe language that describes the evidence state without approving the wallet destination or counterparty.
• A non-scanner boundary note stating that this pack does not score the token, smart contract, liquidity, or rug-pull risk.

Decision matrix

• Wallet destination and payment channel row

  Status: unresolved

  Evidence fields: wallet_destination, operator_identity

  Source requirement: Record the exact address, chain, memo or destination tag, amount, and the counterparty identity that is supposed to own the destination.

  Allowed static use: Use this row to keep destination details and counterparty identity visible in a static wallet-transfer review.

  Blocked upgrade: Do not treat a copied wallet address as verified, safe, approved, or owned by the claimed counterparty.

  Agent action: Hold the transfer until the destination and identity can be independently matched.

• Wallet ownership proof row

  Status: unresolved

  Evidence fields: wallet_ownership_evidence, source_links

  Source requirement: Record signed-message proof, portal confirmation, prior-good destination evidence, or another independent ownership source.

  Allowed static use: Use the ownership proof row to distinguish claim text from independent evidence.

  Blocked upgrade: Do not turn a forwarded address or chat alias into verified beneficial ownership.

  Agent action: Escalate when ownership proof is missing or only comes from the payment request itself.

• Sanctions and public-warning source row

  Status: warning

  Evidence fields: source_links, operator_identity

  Source requirement: Record public-warning, sanctions, and address-label checks plus the retrieval time and their relevance to the wallet transfer.

  Allowed static use: Use public warnings and official guidance as source-bound caution context only.

  Blocked upgrade: Do not treat warning context as proof that the wallet or counterparty is safe.

  Agent action: Preserve the warning context and stop before any irreversible transfer.

• Chain and destination integrity row

  Status: warning

  Evidence fields: wallet_destination, source_links

  Source requirement: Record chain or network, checksum, memo/tag, and whether those fields match the claimed beneficiary record.

  Allowed static use: Use this row to keep chain/network and destination-integrity checks visible in the static review.

  Blocked upgrade: Do not convert incomplete destination-integrity checks into safe or compliant transfer approval.

  Agent action: Hold review until the destination details reconcile with an independent source.

Citation rules

• Tie every restated wallet-transfer fact to the exact source note, message capture, explorer snapshot, or warning source plus retrieval time.
• Separate observed address activity from interpretation; do not convert explorer visibility or lack of sanctions hits into ownership proof or safety clearance.
• Keep chain/network, checksum, memo/tag, and address-copy uncertainty visible when those fields could change the destination.
• Keep counterparty, wallet-ownership, and destination uncertainty visible in every summary until the transfer path is independently verified.
• Never restate this pack as evidence that the wallet address, counterparty, or transfer request is safe, approved, or compliant.

Sample input summary

Sample evidence records

• The private group provides only a chat alias and a wallet address, with no cited legal entity or official domain for the counterparty

  Status: unresolved

  Source: Wallet-transfer request sample brief

  Retrieved: 2026-05-25T00:00:00.000Z

  A group alias and destination address alone do not verify counterparty identity.

• The requested wallet address appears only in a forwarded message and has no signed ownership proof from the claimed counterparty

  Status: warning

  Source: Forwarded transfer instruction (sample)

  Retrieved: 2026-05-25T00:00:00.000Z

  The address is present, but wallet ownership and beneficiary identity remain unverified.

• The chain/network, address checksum, and memo or destination tag have not been independently reconciled with a verified counterparty record

  Status: warning

  Source: Wallet-transfer destination integrity sample

  Retrieved: 2026-05-25T00:00:00.000Z

  A copied address can still be wrong if the network, memo/tag, or verified beneficiary context is missing.

• A public explorer shows recent address activity, but the explorer record does not identify the counterparty or prove wallet ownership

  Status: confirmed

  Source: Wallet explorer snapshot (sample)

  Retrieved: 2026-05-25T00:00:00.000Z

  Explorer activity helps with context, but it is not proof that the group controls the address.

• The transfer is requested in crypto to a wallet destination that may be difficult to recover once sent

  Status: warning

  Source: FTC cryptocurrency scam guidance

  Retrieved: 2026-05-25T00:00:00.000Z

  Irreversible wallet payment raises the cost of acting before counterparty verification is complete.

• FTC scam-recovery guidance remains relevant because sending crypto to the wrong person may be hard to unwind

  Status: warning

  Source: FTC what to do if you were scammed

  Retrieved: 2026-05-25T00:00:00.000Z

  The source supports caution and reporting/recovery boundaries; it does not approve the destination.

• FBI cryptocurrency-investment-fraud guidance points reviewers to receiving cryptocurrency addresses and transaction information

  Status: warning

  Source: FBI cryptocurrency investment fraud guidance

  Retrieved: 2026-05-25T00:00:00.000Z

  The receiving cryptocurrency address and transaction details are evidence to preserve, not proof that the counterparty is legitimate.

• OFAC virtual currency guidance and sanctions-list references remain required before treating a wallet transfer as clear

  Status: unresolved

  Source: OFAC virtual currency guidance

  Retrieved: 2026-05-25T00:00:00.000Z

  This static sample cites OFAC guidance but does not run a live sanctions check or issue sanctions clearance.

• OFAC Sanctions List Service remains a required official source for relevant counterparty and wallet-transfer screening

  Status: unresolved

  Source: OFAC Sanctions List Service

  Retrieved: 2026-05-25T00:00:00.000Z

  The source is a screening reference; absence of a recorded hit in this sample is not a no-hit result.

• CFTC imposter-fraud guidance flags unusual digital wallet payment requests as an escalation signal

  Status: warning

  Source: CFTC Beware Imposters

  Retrieved: 2026-05-25T00:00:00.000Z

  The warning supports escalation when a private group pressures payment, but it does not identify this specific wallet.

Evidence Card sample

Citation block

• artifactVersion=public-material-wallet-transfer-unverified-counterparty-pack-2026-05-25
• generatedAt=2026-05-25T00:00:00.000Z
• staticSnapshotAt=2026-05-25T00:00:00.000Z
• sampleEvidenceRetrievedAt=2026-05-25T00:00:00.000Z
• pagePath=/agent-verification/materials/wallet-transfer-unverified-counterparty-pack
• artifactPath=/reliability/public-materials/wallet-transfer-unverified-counterparty-pack.json

Key findings

• unresolved: The private group provides only a chat alias and a wallet address, with no cited legal entity or official domain for the counterparty (A group alias and destination address alone do not verify counterparty identity.)
• warning: The requested wallet address appears only in a forwarded message and has no signed ownership proof from the claimed counterparty (The address is present, but wallet ownership and beneficiary identity remain unverified.)
• warning: The chain/network, address checksum, and memo or destination tag have not been independently reconciled with a verified counterparty record (A copied address can still be wrong if the network, memo/tag, or verified beneficiary context is missing.)
• confirmed: A public explorer shows recent address activity, but the explorer record does not identify the counterparty or prove wallet ownership (Explorer activity helps with context, but it is not proof that the group controls the address.)
• warning: The transfer is requested in crypto to a wallet destination that may be difficult to recover once sent (Irreversible wallet payment raises the cost of acting before counterparty verification is complete.)
• warning: FTC scam-recovery guidance remains relevant because sending crypto to the wrong person may be hard to unwind (The source supports caution and reporting/recovery boundaries; it does not approve the destination.)
• warning: FBI cryptocurrency-investment-fraud guidance points reviewers to receiving cryptocurrency addresses and transaction information (The receiving cryptocurrency address and transaction details are evidence to preserve, not proof that the counterparty is legitimate.)
• unresolved: OFAC virtual currency guidance and sanctions-list references remain required before treating a wallet transfer as clear (This static sample cites OFAC guidance but does not run a live sanctions check or issue sanctions clearance.)
• unresolved: OFAC Sanctions List Service remains a required official source for relevant counterparty and wallet-transfer screening (The source is a screening reference; absence of a recorded hit in this sample is not a no-hit result.)
• warning: CFTC imposter-fraud guidance flags unusual digital wallet payment requests as an escalation signal (The warning supports escalation when a private group pressures payment, but it does not identify this specific wallet.)

Required disclosures

• Static public sample only; not a live review, approval, compliance clearance, or request-time judgment.
• Runs as a static/client-side demo in this phase, not a server-side decision service
• Does not prove an action is legal, safe, suitable, profitable, or compliant
• High-risk or ambiguous actions still require qualified human review
• The pack does not verify beneficial ownership, recover sent funds, or replace sanctions, legal, custody, or compliance review.
• The pack is not a token-risk, meme-coin, smart contract, liquidity, rug-pull, or wallet-forensics scanner.
• The wallet destination is not independently tied to a verified counterparty identity or official operating domain.
• No signed message, exchange record, or beneficiary proof demonstrates wallet ownership by the claimed group.
• The chain/network, checksum, and memo/tag context have not been reconciled with a verified destination record.
• FTC, FBI, OFAC, and CFTC references are source requirements for this pattern, not live clearance results.
• The transfer request relies on a private-group narrative and irreversible crypto payment before verification is complete.

Do not claim

• This wallet transfer is safe.
• The wallet address is verified and payment can proceed.
• The counterparty is approved for crypto settlement.

Action routing

Search intent

Input field glossary

Preflight questionnaire

Decision policy

Decision guardrails

Misuse patterns

Static action note template

Static action note example

Agent workflow

Source quality

Source review policy

Refresh triggers (sourceReviewPolicy.refreshRequiredWhen)

• Any cited official source, registry, guidance page, filing page, or public warning URL changes content, schema, access status, or meaning.
• A downstream agent wants to use the static pack for a new counterparty, payment destination, wallet, claim, filing, macro release, or source set.
• The current date is past nextRecommendedReviewAt or the artifactVersion / generatedAt fields are removed from the handoff.
• The wallet address, chain, memo/tag, ownership proof, public warning source, or sanctions-reference requirement differs from the static sample.

Case readiness checklist

Must confirm before use

• Collected and cited every minimum input field: wallet_destination, operator_identity, wallet_ownership_evidence, source_links.
• Opened the HTML page for scope and limitations, then used the JSON artifact for structured retrieval.
• Preserved source URLs, retrieval timestamps, source roles, canonical citation text, and unresolved items in the downstream note.
• Checked decisionMatrix, misusePatterns, sourceReviewPolicy, and evidenceVerificationRecipe before upgrading any sentence.
• Confirm the pack's source manifest, sample evidence records, decision matrix, and citation rules still match the case being reviewed.

Not ready signals

• One or more required evidence fields are missing, uncited, or unresolved: wallet_destination, operator_identity, wallet_ownership_evidence, source_links.
• The case is past sourceReviewPolicy.nextRecommendedReviewAt without a fresh source re-check.
• The user or downstream agent asks for approval, clearance, safety, compliance, suitability, execution, payment, publication, or legal/trading advice.
• The requested case uses a new counterparty, payment destination, wallet, claim, filing, macro release, source set, or audience that is not covered by the static sample.

Ready static handoff

• A bounded static action note or evidence card with citations, source snapshot, unresolved items, and blocked-upgrade language preserved.
• A JSON artifact reference plus canonical citation text that another crawler or agent can retrieve without treating it as a live service.
• A human-review handoff when the case remains high-risk, private, legally sensitive, or close to money movement or public distribution.

Case worksheet

Source manifest handoff

Machine summary

Evidence verification recipe

• Source manifest verification

  Verification action: Check the static source manifest before citing this pack. Source kinds: sample_page, official_guidance, official_registry. Source labels: Wallet-transfer request sample brief, FTC cryptocurrency scam guidance, FTC what to do if you were scammed, FBI cryptocurrency investment fraud guidance, OFAC virtual currency guidance, OFAC Sanctions List Service, CFTC Beware Imposters.

  Trust boundary: The source manifest is a static citation map, not live clearance, approval, compliance review, execution advice, or backtesting evidence.

  Failure mode: If a cited source, retrieval time, source role, or evidence record link is missing, keep the output bounded and escalate before upgrading the claim.

  Required citation fields: sourceManifest[].url, sourceManifest[].retrievedAt, sourceManifest[].kind, sampleEvidenceRecords[].id

• Evidence record linkage check

  Verification action: Match each sample evidence record to a sourceManifest evidenceRecordIds entry, then preserve the record status, note, source label, source URL, and retrievedAt value.

  Trust boundary: A sample record explains the static example only; it does not prove the current counterparty, claim, payment, wallet, filing, macro release, or subscription is safe.

  Failure mode: If a record cannot be linked to its source manifest row, do not reuse it as evidence and keep the final output unresolved.

  Required citation fields: sampleEvidenceRecords[].id, sampleEvidenceRecords[].status, sampleEvidenceRecords[].sourceUrl, sampleEvidenceRecords[].retrievedAt, sourceManifest[].evidenceRecordIds

• Decision matrix boundary check

  Verification action: Read all 4 decision matrix rows and carry their allowedStaticUse, blockedUpgrade, and agentAction fields into any downstream summary.

  Trust boundary: Decision matrix rows define allowed static reuse and blocked upgrades; they are not automatic live approval, live screening, compliance sign-off, or execution permission.

  Failure mode: If a downstream sentence conflicts with a blockedUpgrade row, block or rewrite the sentence and escalate when money, publication, or user action is involved.

  Required citation fields: decisionMatrix[].matrixId, decisionMatrix[].status, decisionMatrix[].allowedStaticUse, decisionMatrix[].blockedUpgrade

• Canonical citation and timestamp check

  Verification action: Preserve the canonical citation text, artifact version, generatedAt, staticSnapshotAt, sourceSnapshotAt, and all source retrievedAt values when citing this pack.

  Trust boundary: A citation proves the static artifact and source snapshot were recorded; it does not prove the facts are current beyond the listed timestamps.

  Failure mode: If artifact version, generatedAt, sourceSnapshotAt, or source retrievedAt values are removed, the output is no longer evidence-bound.

  Required citation fields: canonicalCitation.recommendedCitationText, artifactProvenance.artifactVersion, artifactProvenance.generatedAt, canonicalCitation.sourceSnapshotAt, sourceManifest[].retrievedAt

• Human escalation and blocked-upgrade check

  Verification action: Compare the final output with the pack's blockedStatements, sampleReviewOutput.blockedRestatement, escalationTriggers, and actionTaxonomy.stopOrEscalateWhen fields.

  Trust boundary: Static public material may explain evidence and limitations, but it must not become live clearance, legal compliance, suitability, safety, guarantee, payment approval, publication approval, or trade advice.

  Failure mode: If the output asks a user or agent to move money, publish a financial claim, trust a counterparty, or treat the material as live approval, stop and escalate to human review.

  Required citation fields: canonicalCitation.recommendedCitationText, artifactProvenance.artifactVersion, blockedStatements[], sampleReviewOutput.blockedRestatement, escalationTriggers[], actionTaxonomy.stopOrEscalateWhen[]

Cite this pack

Source manifest

• Wallet-transfer request sample brief

  URL: /agent-verification/materials/wallet-transfer-unverified-counterparty-pack

  Kind: sample_page; role: sample_context; retrieved: 2026-05-25T00:00:00.000Z

  Evidence records: private_group_alias_only, wallet_address_only, destination_integrity_gap, explorer_context_gap

  Supports: The private group provides only a chat alias and a wallet address, with no cited legal entity or official domain for the counterparty / The requested wallet address appears only in a forwarded message and has no signed ownership proof from the claimed counterparty / The chain/network, address checksum, and memo or destination tag have not been independently reconciled with a verified counterparty record / A public explorer shows recent address activity, but the explorer record does not identify the counterparty or prove wallet ownership

  Limitations:

  • This source entry records what the static sample cites; it does not prove current, complete, or final clearance.
  • Preserve retrievedAt and linked evidenceRecordIds when reusing this source in an agent or crawler workflow.
• FTC cryptocurrency scam guidance

  URL: https://consumer.ftc.gov/articles/what-know-about-cryptocurrency-scams

  Kind: official_guidance; role: primary_warning; retrieved: 2026-05-25T00:00:00.000Z

  Evidence records: irreversible_crypto_transfer

  Supports: The transfer is requested in crypto to a wallet destination that may be difficult to recover once sent / Irreversible wallet transfer plus opaque counterparty evidence is one of the clearest high-risk action-preflight scenarios in the current public scope.

  Limitations:

  • This source entry records what the static sample cites; it does not prove current, complete, or final clearance.
  • Preserve retrievedAt and linked evidenceRecordIds when reusing this source in an agent or crawler workflow.
• FTC what to do if you were scammed

  URL: https://consumer.ftc.gov/articles/what-do-if-you-were-scammed

  Kind: official_guidance; role: primary_warning; retrieved: 2026-05-25T00:00:00.000Z

  Evidence records: ftc_recovery_boundary

  Supports: FTC scam-recovery guidance remains relevant because sending crypto to the wrong person may be hard to unwind / Irreversible wallet transfer plus opaque counterparty evidence is one of the clearest high-risk action-preflight scenarios in the current public scope.

  Limitations:

  • This source entry records what the static sample cites; it does not prove current, complete, or final clearance.
  • Preserve retrievedAt and linked evidenceRecordIds when reusing this source in an agent or crawler workflow.
• FBI cryptocurrency investment fraud guidance

  URL: https://www.fbi.gov/how-we-can-help-you/victim-services/national-crimes-and-victim-resources/cryptocurrency-investment-fraud

  Kind: official_guidance; role: primary_warning; retrieved: 2026-05-25T00:00:00.000Z

  Evidence records: fbi_crypto_transaction_info_required

  Supports: FBI cryptocurrency-investment-fraud guidance points reviewers to receiving cryptocurrency addresses and transaction information / Irreversible wallet transfer plus opaque counterparty evidence is one of the clearest high-risk action-preflight scenarios in the current public scope.

  Limitations:

  • This source entry records what the static sample cites; it does not prove current, complete, or final clearance.
  • Preserve retrievedAt and linked evidenceRecordIds when reusing this source in an agent or crawler workflow.
• OFAC virtual currency guidance

  URL: https://ofac.treasury.gov/system/files/126/virtual_currency_guidance_brochure.pdf

  Kind: official_registry; role: official_reference; retrieved: 2026-05-25T00:00:00.000Z

  Evidence records: ofac_virtual_currency_source_required

  Supports: OFAC virtual currency guidance and sanctions-list references remain required before treating a wallet transfer as clear / Irreversible wallet transfer plus opaque counterparty evidence is one of the clearest high-risk action-preflight scenarios in the current public scope.

  Limitations:

  • This source entry records what the static sample cites; it does not prove current, complete, or final clearance.
  • Preserve retrievedAt and linked evidenceRecordIds when reusing this source in an agent or crawler workflow.
• OFAC Sanctions List Service

  URL: https://ofac.treasury.gov/sanctions-list-service

  Kind: official_registry; role: official_reference; retrieved: 2026-05-25T00:00:00.000Z

  Evidence records: ofac_sanctions_list_source_required

  Supports: OFAC Sanctions List Service remains a required official source for relevant counterparty and wallet-transfer screening / Irreversible wallet transfer plus opaque counterparty evidence is one of the clearest high-risk action-preflight scenarios in the current public scope.

  Limitations:

  • This source entry records what the static sample cites; it does not prove current, complete, or final clearance.
  • Preserve retrievedAt and linked evidenceRecordIds when reusing this source in an agent or crawler workflow.
• CFTC Beware Imposters

  URL: https://www.cftc.gov/LearnAndProtect/AdvisoriesAndArticles/Beware_Imposters

  Kind: official_registry; role: primary_warning; retrieved: 2026-05-25T00:00:00.000Z

  Evidence records: cftc_imposter_payment_warning

  Supports: CFTC imposter-fraud guidance flags unusual digital wallet payment requests as an escalation signal / Irreversible wallet transfer plus opaque counterparty evidence is one of the clearest high-risk action-preflight scenarios in the current public scope.

  Limitations:

  • This source entry records what the static sample cites; it does not prove current, complete, or final clearance.
  • Preserve retrievedAt and linked evidenceRecordIds when reusing this source in an agent or crawler workflow.

Sample bounded output

Review checklist

• Verify whether the wallet address, chain/network, address checksum, destination memo/tag, and beneficiary label can be matched to a source you can cite rather than a private chat message or alias only.
• Check whether any explorer record, signed message, official domain, exchange statement, or documented beneficiary proof supports the claimed wallet ownership or counterparty identity.
• Record what remains unverified about the wallet destination, transfer purpose, and counterparty before restating the request.
• Record sanctions and public-warning source requirements without turning a no-result or missing lookup into clearance.
• Keep the wallet transfer blocked until ownership, counterparty evidence, destination integrity, and irreversible-payment risk are resolved by human review.

Escalation triggers

• The wallet destination is supplied only through a private group, forwarded message, or weak side channel.
• No signed ownership proof, official domain, or documented beneficiary record ties the address to the claimed counterparty.
• The request pushes urgency, secrecy, or irreversible crypto transfer before independent verification is complete.

Safe to repeat

• The wallet transfer remains blocked because the current evidence does not independently verify the counterparty or the destination address owner.
• This pack can describe what was checked and what remains unresolved, but it does not approve the wallet destination or clear the counterparty.
• Explorer context and partial address history do not replace ownership proof or independent beneficiary verification.

Blocked claims

• This wallet transfer is safe.
• The wallet address is verified and payment can proceed.
• The counterparty is approved for crypto settlement.

Related public artifacts

• Action Preflight page (HTML page)
• Action Preflight JSON sample (JSON artifact)
• Counterparty Screening pack (HTML page)
• Payment Instruction Change pack (HTML page)