{
  "url": "https://blockindex.ai/coin/osak",
  "name": "Osaka Protocol",
  "links": {
    "github": null,
    "website": "https://osaka.win/",
    "whitepaper": null
  },
  "dScore": 53,
  "market": {
    "priceUsd": 1.6480777861530583e-8,
    "marketCapUsd": 12374917.365311537,
    "volume24hUsd": 66405.83140318,
    "priceChange7dPct": -5.81944147,
    "priceChange24hPct": -2.44323168
  },
  "source": "BlockIndex.AI",
  "supply": {
    "max": 1000000000000000,
    "circulating": 750869738630302,
    "circulatingPct": 75.08697386303021
  },
  "ticker": "OSAK",
  "founder": null,
  "vcFunded": false,
  "updatedAt": "2026-06-19T06:00:37.101942+00:00",
  "fairLaunch": false,
  "launchYear": null,
  "description": "Osaka Protocol (OSAK) is presented in the supplied source fragments as an ERC-20 token deployed on the Ethereum mainnet. The available material is sparse and primarily driven by market-data snapshots, contract metadata and exchange/wallet listings. The token is tracked by market aggregators and carries a token contract hash (0xa21af1050f7b26e0cff45ee51548254c41ed6b5c) in the extracted fragments. Project-level disclosures such as a team roster, founder biographies, a mission statement, or a published and dated whitepaper are not included in the provided files. What can be stated from the extracted material is that OSAK has substantial nominal supply metrics recorded on aggregator snapshots and a measurable holder base, and it is represented across several centralized exchanges and widely used wallets, which provide on-ramps and custody options for users.\n\nTechnically, the snapshots and contract snippets indicate that OSAK is an Ethereum-native token; as such its security and settlement are inherited from the Ethereum mainnet and its consensus (PoS) rather than from an independent validator set or native chain mechanics. No project-provided technical specification or repository link was included in the provided data, so precise details about token utilities, smart-contract modules, upgradeability patterns, or any bespoke infrastructure cannot be confirmed from the supplied fragments alone. The data does show circulating supply and max supply figures and a contract address; these on-chain identifiers are sufficient for typical aggregate tracking and exchange listing processes but do not substitute for a formal technical whitepaper or audited code repository when assessing architecture-level risks.\n\nFrom an adoption and ecosystem perspective, the available material emphasizes market visibility: OSAK is present in CoinMarketCap/CryptoCompare-style snapshots and appears on multiple centralized exchanges (identified in the verified wallet/exchange dataset). Wallet support in the high-confidence extraction includes hardware and desktop/browser extension wallets such as Ledger, Electrum, MetaMask and Phantom, which indicates practical accessibility for a broad set of end users. Holder counts and circulating supply snapshots are provided in the aggregated content and show a substantial holder base (71.30K holders) with a circulating supply of 750.86T OSAK representing roughly 75.09% of the stated max supply. There are market milestones recorded in the scraped data — an all-time low on 2023-04-23 and an all-time high with timestamp 2024-04-08 — which speak to historical price volatility and tracking across data providers.\n\nTokenomics, governance and roadmap information are not documented in the supplied files. Allocation details such as premine percentages, PIP (pre-issued percentage), vesting schedules, or team/treasury allocations are absent from the extracted fragments; the DScore extraction explicitly marked these items as unknown. Likewise, no corporate entity or CEO was identified in the data, and there is no high-confidence statement asserting on-chain DAO governance or a community treasury mechanism. Given the limited disclosure in the source fragments, risk assessments must rely on the available quantitative snapshots (supply, holders, price, exchange listings) while treating governance, distribution and security questions as open items requiring direct project documentation or on-chain trace analysis for validation. Absent a published whitepaper or public repository in the provided material, due diligence should prioritize contract verification, token-holder distribution inspection, and audit history checks before any trust assumptions are made.",
  "methodology": "https://blockindex.ai/dscore",
  "classification": {
    "layer": "Layer 1",
    "isToken": true,
    "consensus": "PoS",
    "parentChain": "ETH"
  },
  "dScoreComponents": {
    "autonomy": 5,
    "ageHistory": 7,
    "governance": 16,
    "nodeDistribution": 0,
    "initialDistribution": 25
  },
  "decentralizationVerdict": "Moderately Decentralized"
}