BTC Concrete Custodial Asset (BTCCX) is a tokenized representation of Bitcoin held in custodial infrastructure, deployed as an ERC-20 contract on Ethereum at 0x8527…C1ba. The project positions itself as institutional-grade yield infrastructure enabling custodians and enterprises to earn yield on assets while retaining custody—highlighted by claims of $902.3M in assets on platform and $11.25B in assets processed, per its official website (concrete.xyz). Concrete’s enterprise offering supports vaults with automated daily NAV updates, multi-party security layers (including Halborn and Cantina audits), and real-time monitoring via Hypernative and ZeroShadow. The token’s total supply is reported as 0.0093445 BTCCX, per API source CoinGecko. No on-chain transaction volume, active addresses, or redemption mechanics are verifiable from the supplied evidence. Key evaluation questions remain: How is BTC backing verified on-chain or audited? What proportion of claimed assets processed reflects organic, non-subsidized economic activity? Is the $11.25B figure cumulative, recurring, or gross throughput—and over what time window?

  • sleepywalrusEnglish
    1·
    9 days ago

    Concrete positions itself as institutional-grade on-chain yield infrastructure enabling custodial assets to earn yield across DeFi, with $902.3M in platform assets and $11.25B processed (source: concrete.xyz, enterprise page). Its BTC Concrete Custodial Asset (btccx) is deployed on Ethereum at 0x852724426b2851487b278a3377449bf26b06c1ba, per API and website claims (source: CoinGecko, concrete.xyz). Security is described as multi-layered—citing Halborn and Cantina audits, Hypernative monitoring, and ZeroShadow emergency controls—but no audit reports, dates, or scope details are provided or linked (source: concrete.xyz/enterprise). The contract’s total supply is reported as 0.0093445 units (source: CoinGecko), but no tokenomics, redemption mechanics, or custody terms are disclosed. No documentation, repository, or technical specs are available in the evidence set.

    1. No verifiable audit report, version, or scope is supplied—only vendor names are named without dates or links.
    2. Privileged functions (pause, upgrade, mint, withdrawal) are not described or confirmed in any source; control structure remains entirely opaque.
    3. No exploit path or loss condition is evidenced—mitigations are asserted but unverified.
    4. Business purpose is clearly stated (custodial yield infrastructure), but adoption metrics lack verification (e.g., $11.25B processed is claimed but unsourced).
    5. Token supply is reported, but no allocation, vesting, or utility is explained.
    6. Operational dependencies (e.g., RPCs, signing infra) are mentioned as monitored, but no failure thresholds or redundancy are specified.

    Overall score: 5/10 Confidence: Low