Tokenized assets and blockchain services involve risks. Review the asset, issuer, documented rights, network and any service involved. This overview introduces questions to consider; it does not establish the safety or suitability of a particular asset.

Reading asset and service risks

1. Price movements

A price observation describes one asset, market and point in time. Later values can differ sharply, and a quoted figure does not establish an available execution price. Read the source and timing alongside factors such as:

• Changes in demand and market expectations.

• New rules or regulatory information.

• Wider economic conditions and events.

2. Regulatory context

Regulatory treatment depends on the asset, activity, entity and jurisdiction. Review current official information for the specific context, including:

• Whether a claim is supported by an authoritative record.

• Whether a change affects the asset or service being considered.

3. Account security

A blockchain record does not establish the security of every wallet, website or service used to access it. Relevant risks include:

• Deceptive messages and unauthorized access.

• Harmful software affecting accounts or signing tools.

4. Transfer finality

A completed blockchain transfer can be difficult or impossible to recover. Check the exact asset, network, address and any required memo or tag before authorizing an instruction.

5. Available liquidity

A displayed price does not show how much can be traded at that level. Review available size, market depth and the effect of the proposed amount on execution.

6. Technical understanding

A transaction involves an account, an authorization method and a network. Misunderstanding access, destination details or the requested operation can lead to an unintended outcome.

7. Distorted market signals

Trading activity and promotional claims need independent context. A misleading market picture can involve:

• Coordinated promotion followed by concentrated selling.

• Reported activity that does not reflect genuine demand.

8. Service counterparties

When another organization controls assets or performs part of a process, its role needs to be understood. Read the custody arrangement, access conditions and treatment of an interruption. A familiar interface alone does not establish how assets are protected.

9. Deceptive requests

A convincing message can combine a familiar name with an unsupported claim. Examine what the sender asks you to do, how the request can be verified and what evidence supports it.

Recognizing misleading requests

1. Promises of easy returns

Treat the structure of an offer as a question to investigate, especially when it includes:

• A claimed profit without a credible explanation of risk.

• An extra payment demanded before funds can be released.

• An unverified person offering to control an account.

Review steps:

• Ask what evidence supports the promised outcome.

• Check the exact entity and activity against authoritative sources.

• Read current service terms and regulatory records.

2. False identity claims

A sender can copy a company name, official title or profile image. Establish the sender through an independent source before acting on a request for access, information or payment.

Review steps:

• Find the official channel independently of the message.

• Keep recovery phrases, passwords and access codes private.

• Use a verified website to check an unexpected request.

3. Copied sites and apps

A copied design or familiar logo can conceal a different operator. Check the exact domain or application source before relying on the interface.

Warning signs:

• A changed spelling or unexpected domain ending.

• A familiar design that does not match the verified domain.

4. Payment-first offers

An offer to return more assets after an upfront transfer needs scrutiny. A promotional image or familiar profile does not verify the promise.

Review steps:

• Examine why the offer requires an advance transfer.

• Trace the announcement to an independently verified source.

• Treat screenshots and endorsements as claims to check.

5. Threats and payment demands

A demand can pair a threat with an urgent request for cryptocurrency. The threat itself does not prove that the sender holds the information claimed.

Review steps:

• Preserve evidence and avoid engaging with the demand.

• Use an appropriate official reporting channel.

6. Unverified sellers

A storefront does not establish that a seller will deliver. Review the seller’s identity, terms and available evidence.

Review steps:

• Check the seller’s identity beyond its own testimonials.

• Examine unusually large discounts and payment conditions.

7. Unverified support

A claimed support role can conceal a request for access or payment. Verify the person and channel before following instructions.

Review steps:

• Locate support details through the service’s verified site.

• Do not give an unverified support contact access to your device.

8. Unsolicited token activity

An unsolicited transfer can attract attention or reveal address activity. Its presence does not establish a legitimate opportunity.

Review steps:

• Do not treat an unexpected token as an instruction to act.

• Review wallet documentation and the exact transaction being requested.

Building a careful review

1. Understand the activity: Identify the asset, the service and the operation being proposed.

2. Review access controls: Understand who can authorize activity and how account access is protected.

3. Check the source: Confirm the exact domain, sender and document behind a statement.

4. Understand Exposure: Identify the amount, asset, issuer and counterparties involved in a position.

5. Read the documentation: Read primary documentation, identify the issuer and verify the claims relevant to the asset.

DTCC Trading focuses on Stellar tokenization and multichain interoperability. Asset identity, network context and documented rights are separate checks. Keep those records together and resolve unclear claims before relying on an asset description.