cryptosnif
Across Protocol Token (ACX)
Documentary contract0x44108f0223a3c3028f5fe7aec7f9bb2e66bef82f
Unrated · 0% Evidence coverage
Operational strength remains unproven; unrated with 0% scoring coverage.
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.
Inspect the evidenceThe source review explains documented mechanisms. Independent network checks remain pending.
Promise
This dossier examines the documented purpose and mechanisms of Across Protocol Token (ACX) on the eip155:1 network. The objective is to explain the stated aims of the token as recorded in community-maintained registries, without verifying live network operation or investment outcomes.
Established facts
The pinned Trust Wallet Ethereum integration record identifies Across Protocol with symbol ACX and contract address 0x44108f0223a3c3028f5fe7aec7f9bb2e66bef82f. The record specifies 18 decimal places, a technical parameter for amount representation that does not measure supply or value. The entry is labeled ERC20 and active. ERC-20 refers to a standard interface for fungible tokens in smart contracts, defining functions for total supply, balance checks, transfers, and allowances. An allowance permits a named spender to use a specified amount; repeated approvals overwrite previous amounts. The registry description states that Across is a cross-chain token bridge secured by UMA's optimistic oracle, optimized for capital efficiency with a single liquidity pool and a no-slippage fee model. It claims the oracle verifies transfers optimistically to process them quickly. These statements are attributed registry claims from a community-maintained source, not independently verified issuer statements. The general ERC-20 specification defines interface requirements but establishes no independently checked compliance for this specific contract. The network context is identified as Ethereum, accompanied by project website and explorer links in the wallet repository. Inclusion in this registry does not imply a direct partnership with the listed projects, and inclusion does not constitute an exhaustive inventory of recent launches.
Unknowns
Present independent control, beneficial ownership, actual usage, client adoption, supply distribution, concentration, liquidity, and complete incident history remain unverified. No deployed implementation, rights, safety, or security audit has been established. The documentary mechanism alone cannot confirm actual network behavior.
Consequences
Documentary descriptions of bridge mechanics and oracle verification do not establish operational reality or investment safety. Without independent verification, the stated capital efficiency and speed claims remain theoretical. The lack of verified supply and control data prevents assessment of economic risk or governance stability.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage. Critical criteria including identity, supply, and control are unknown. This status reflects the absence of independent operational verification, not a determination of fraud or inherent unsafety.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence regarding control, supply, and usage would be required. Calibration and editorial review following such evidence could enable a scored assessment.
Each check earns its result.
| Check | Weight | Result |
|---|---|---|
| Exact asset identityEssential | 3% | Verification pending |
| Observable use | 15% | Verification pending |
| Economic role of the token | 10% | Verification pending |
| Supply mechanismsEssential | 10% | Verification pending |
| Ownership concentration | 8% | Verification pending |
| Value capture | 7% | Verification pending |
| Control powersEssential | 10% | Verification pending |
| Security verification | 7% | Verification pending |
| Decision process | 8% | Verification pending |
| Accountability | 7% | Verification pending |
| Incident history | 6% | Verification pending |
| Operational continuity | 4% | Verification pending |
| Execution conditions | 5% | Verification pending |
Family-specific checks: Observable usage, token necessity and dependencies.
Inspect the evidence
Sources behind this analysis
Trust Wallet: captured Ethereum record for Across Protocol
The pinned Trust Wallet Ethereum integration record names Across Protocol with symbol ACX, contract 0x44108f0223a3c3028f5fe7aec7f9bb2e66bef82f and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry ERC20 and active. Its community-maintained description states: "The Bridge Ethereum Deserves! Across is a cross-chain token bridge that is secured by UMA's optimistic oracle. It is optimized for capital efficiency with a single liquidity pool, a competitive relayer landscape, and a no-slippage fee model. Across is able to process cross-chain transfers quickly because its oracle verifies transfers optimistically." Every project, economic, partnership, performance, supply, date and adoption statement within this quoted description is an attributed registry claim, not an independently established issuer statement or operational observation. This dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The general ERC-20 specification is separate from this token implementation. Treat the generic application family as a documentary contract subject; its economic niche and scoring criteria remain unclassified and unknown.
Inspect the primary source ↗Trust Wallet Assets: blockchains/ethereum/info/info.json (bbe582d25a22)
The pinned wallet blockchain-information file names the network Ethereum, symbol ETH, and lists its project website and explorer. That named network context accompanies token records in the repository's Ethereum subtree. This identifies the documented integration network without reproducing its operation. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.
Inspect the primary source ↗Trust Wallet Assets: README.md (bbe582d25a22)
The Trust Wallet Assets README describes a community-maintained registry of token information and logos across blockchains, used by the wallet and other projects. It says additional token information is optional and unavailable on-chain. Anyone can submit assets, and inclusion does not imply a direct partnership with the listed projects. It also explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The README states that its scripts and documentation use the MIT license. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.
Inspect the primary source ↗Ethereum ERC-20: pinned token interface specification
The pinned ERC-20 specification describes a standard interface for fungible tokens in smart contracts. It defines totalSupply and balanceOf reads, transfers, third-party transfers after authorization, approval and remaining allowance. An allowance is the amount a named spender may use; a repeated approval overwrites that amount. The specification says callers must handle a false transfer result and describes Transfer and Approval events. Name, symbol and decimal-place metadata are optional in the standard. These interface requirements describe what a conforming implementation should do. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply or security. No token transaction was performed in this review. Copyright and related rights are waived under CC0.
Inspect the primary source ↗Only original summaries are distributed. Licensed raw market data stays private.