Hashnote

Internal linkages

  • Alias note for legacy project placement: hashnote.
  • Useful adjacent company / issuer reads: circle, opentrade, and paxos.
  • Useful adjacent operator / issuer comparison when the question is who packages the fund, custody, and redemption shell around tokenized Treasury exposure: openeden.

Protocol / company boundary

  • Hashnote is better kept as an entity note than as a standalone projects/ note because the practical dependency is a named operator running investor admission, allowlisting, entitlement management, redemption workflow, fund structuring, and collateral-market packaging.
  • There is no especially useful neutral Hashnote protocol boundary doing separate work here. USYC’s smart-contract surface matters, but it only becomes usable through the company-run compliance, teller, and fund-administration shell.
  • Keep [[../projects/hashnote]] only as an alias so legacy links continue to resolve without pretending Hashnote is a protocol peer to more autonomous onchain systems.

Control surface

  • Practical leverage sits in investor eligibility, wallet whitelisting, sanctions screening, entitlement issuance, teller access, subscribe/redeem workflow, custody and fund-service-provider composition, and the post-acquisition way Circle can package USYC alongside USDC and related collateral flows.

  • Read Hashnote here as a regulated operator boundary around a permissioned yield-bearing collateral product, not as a neutral token primitive.

  • Last reviewed: 2026-08-10 UTC