PUB-007 — POLÍTICA DE ACTIVOS Y REDES NO SOPORTADOS Unsupported Asset / Network Policy
- Entidad / Entity
- BLIIM GLOBAL LLC — Delaware, United States
- Documento / Document
- Política de Activos y Redes No Soportados / Unsupported Asset / Network Policy
- ID
- PUB-007
- Versión / Version
- V1.2
- Fecha de vigencia / Effective date
- 7 de octubre de 2026 / 7 October 2026
- Estado / Status
- PUBLICATION FINAL — ACTIVATION CONDITIONAL
- Ámbito / Scope
- App, web y flujos de activos digitales expresamente habilitados / App, web and expressly enabled digital-asset flows Soporte / Support [email protected] Legal [email protected]
- PRINCIPIO CENTRAL / CENTRAL PRINCIPLE
- Solo se consideran soportados los activos, token contracts, representaciones, redes y rutas que Bliim muestre expresamente como habilitados para el producto y usuario aplicables. Un ticker, logo, dirección sintácticamente válida, token visible públicamente o existencia de una blockchain no significa que Bliim lo soporte. Enviar un activo o utilizar una red no soportados puede causar falta de acreditación o pérdida permanente. Cualquier recuperación es excepcional y no está garantizada.
Only assets, token contracts, representations, networks and routes expressly displayed by Bliim as enabled for the applicable product and user are supported. A ticker, logo, syntactically valid address, publicly visible token or the existence of a blockchain does not mean Bliim supports it. Sending an unsupported asset or using an unsupported network may result in non-crediting or permanent loss. Any recovery is exceptional and is not guaranteed.
ALCANCE PREVISTO DE ACTIVOS Y REDES / INTENDED ASSET & NETWORK SCOPE Activo / Asset Red / Network Estándar / Standard Regla de soporte / Support rule USDT BNB Smart Chain BEP-20 Solo si la combinación exacta aparece habilitada en la app / Only if the exact combination is enabled in the app USDT Polygon Polygon PoS Solo si la combinación exacta aparece habilitada en la app / Only if the exact combination is enabled in the app USDC BNB Smart Chain BEP-20 Solo si la combinación exacta aparece habilitada en la app / Only if the exact combination is enabled in the app USDC Polygon Polygon PoS Solo si la combinación exacta aparece habilitada en la app / Only if the exact combination is enabled in the app
1. Purpose
This Policy defines what it means for a digital asset, token, representation, blockchain, Layer 2, bridge or deposit/withdrawal route to be supported by Bliim and sets out the general treatment of transfers made using unsupported assets, contracts or networks.
This Policy does not create a general obligation to recover incorrectly sent assets.
2. Scope
It applies to on-chain deposits and withdrawals, wallet and stablecoin flows, digital-asset conversions, cross-border transfers with a blockchain leg and any transaction in which the user selects or depends on an asset/network combination.
It also applies where an asset reaches a technically valid address but the representation or network is not enabled.
3. Meaning of “Supported”
An asset or network is supported only when Bliim expressly displays it as available for the applicable product and user and the exact representation matches the enabled configuration.
A ticker, commercial name or logo is not sufficient to determine support.
4. Intended Assets and Networks
Bliim intends to enable functionality involving USDT and USDC on BNB Smart Chain (BEP-20) and Polygon, subject to the applicable production configuration.
The existence of USDT or USDC on other networks, bridges or representations does not mean those versions are supported.
5. Contract Address and Exact Representation
Where an asset is a token, the supported representation depends on the exact contract address or applicable technical identifier.
Two tokens may share a ticker and name while having different contracts, issuers, bridges, rights or risks.
6. Correct Network
Users must select the exact network indicated by Bliim. BNB Smart Chain (BEP-20) and Polygon are different networks and must not be treated as interchangeable.
Sending through a network different from the one displayed may result in non-crediting or loss.
7. Unsupported Networks
A blockchain may exist and be technically compatible with a wallet without being supported by Bliim.
Networks, Layer 2s, sidechains, testnets or forks not displayed as enabled should be treated as unsupported.
8. Unsupported Tokens
A token sent to a valid address may not be credited if Bliim or the provider does not support that token or representation.
The fact that a token is visible on a block explorer does not obligate Bliim to credit or recover it.
9. Native, Bridged and Wrapped Assets
A bridged, wrapped, synthetic or third-party-issued representation may differ materially from the native asset or another version using the same ticker.
Users must use only the exact representation indicated in the flow.
10. Bridges and Cross-Chain Routes
Bliim does not presume support for bridges or cross-chain routes merely because an asset exists on multiple networks.
Sending an asset through an unapproved bridge may produce an unsupported representation.
11. Wrong Network
If a user selects the wrong network, the transaction may fall outside the technical reach of the provider that manages the route or keys.
In such cases, recovery may be impossible even where the address format is valid.
12. Wrong Contract
Sending a token with the same ticker but a different contract address may result in an unsupported asset.
Bliim does not treat ticker matching as technical or legal equivalence.
13. Wrong Address
Users are responsible for reviewing the destination address. A valid address belonging to another person or service may prevent recovery.
Blockchain irreversibility may limit available remedies.
14. Memo, Tag or Additional Identifiers
Where a network or provider requires a memo, tag, destination tag, reference or other identifier, users must include it exactly.
Missing or incorrect information may cause delay, non-crediting or manual review.
15. Testnets and Non-Production Environments
Assets sent through testnets, devnets or other non-production environments are not supported unless expressly stated.
Visually similar addresses across environments do not guarantee interoperability.
16. Airdrops, Forks and Derived Assets
Bliim is not required to support airdrops, forks, new tokens, redenominations or derived assets unless expressly communicated.
A user's economic exposure to an asset does not create an automatic right to any new token.
17. Delisting or Suspension
Bliim may suspend deposits, withdrawals or support for an asset or network because of maintenance, incidents, regulatory changes, risk, liquidity, partner termination or technical changes.
A temporary suspension does not necessarily mean permanent delisting.
18. Token Migrations
An issuer or protocol may migrate contracts, networks or versions. Bliim may require a support update before accepting the new representation.
Users should not assume that an external migration will automatically be reflected in Bliim.
19. Scam and Impersonation Risk
Fraudsters may create tokens that imitate the name, ticker or logo of recognized assets. Visual similarity does not verify authenticity.
Users must use only the assets and networks presented by Bliim.
20. Incoming Deposits
A deposit may be visible on-chain before it is credited. Bliim or the partner may require confirmations, screening, asset validation and network-status review.
On-chain visibility does not equal final credit.
21. Withdrawals
Withdrawals should only use enabled assets, networks and routes. Bliim may block combinations that are unsupported or present elevated risk.
Users must verify compatibility with the external recipient before confirmation.
22. Stablecoins
Where USDT or USDC is used, the Stablecoin Risk Disclosure, Blockchain Finality Disclosure and Network Fee Disclosure also apply.
An issuer depeg, freeze function or smart-contract incident is different from an unsupported-network issue.
23. Finality and Irreversibility
An on-chain transaction may reach a point at which it is no longer technically cancellable. Blockchain finality does not guarantee that the transferred asset is supported by Bliim.
A finalized transfer involving the wrong asset or network may still be uncreditable.
24. Network Fees and Recovery Fees
A transaction may consume gas or network fees even if it fails or is not credited. Those charges may be non-refundable.
If an exceptional recovery requires technical or partner costs, any applicable fee should be communicated before recovery is performed where practicable.
25. Recovery Is Not Guaranteed
Bliim may assess a recovery request but does not guarantee that recovery is technically, legally or operationally possible.
Recovery capability depends on factors including custody, key control, architecture, partner, network, token contract, amount, security, compliance and cost.
26. Non-Recoverable Cases
Recovery may be unavailable where Bliim or the partner does not control the relevant keys, the asset was sent through an incompatible network, the transaction is technically irreversible, security or compliance risk exists, or recovery is not viable.
Bliim is not required to build new infrastructure or assume disproportionate risk to attempt recovery.
27. Support Process
Users should contact [email protected] with the transaction hash, asset, network, address, date, amount and any other available information.
Bliim may request additional evidence before determining whether the case can be investigated.
28. Investigation Timing
Unsupported-asset or network cases may require technical and partner review and do not have a universal resolution time.
Receipt of a request does not mean that recovery has been accepted.
29. AML, Sanctions and Security
A recovery may be subject to KYC/KYB, sanctions screening, fraud review, ownership verification, security review and other controls.
Bliim may decline recovery where there is a legal, contractual, security or compliance reason.
30. User Responsibility
Users must review the asset, network, address, contract, memo/tag and any warning before confirmation.
Any mandatory legal protections that apply are not eliminated by this duty of care.
31. Brazil
In Brazil, treatment of virtual assets depends on the product and the entity performing the relevant function. Availability of a network or stablecoin does not mean Bliim is an authorized Brazilian virtual-asset service provider.
Use of Pix, if present in a related flow, does not make Bliim a Pix participant.
32. United States, Colombia, Mexico and Spain/EEA
User rights, responsibilities, recovery and error treatment may vary by jurisdiction, provider and nature of the service.
This Policy applies as a general framework without replacing mandatory rights or product-specific terms.
33. Changes in Support
Bliim may add, suspend or remove assets and networks. The app or website should be used as the operational reference for combinations enabled at the time of a transaction.
Historical support does not guarantee future support.
34. Contact
To report a transfer involving an unsupported asset or network, contact [email protected]. For legal questions about this Policy, contact [email protected].