The 2020 whitepaper describes content-addressed files in distributed storage, hashes managed on a blockchain, identity through SKC, device registration through Smart Guardian, and company access after user permission. Current PDL pages and manuals show concrete account, access-history and data-provision settings. The PDL terms also say the platform belongs to Jasmy or providers, the service may use data under specified consent, and users bear backup and account responsibilities.
JASMY’s verified contract is much simpler. Its constructor minted 50,000,000,000 tokens with 18 decimals to the deployer on 26 December 2019. The public ABI exposes ordinary ERC-20 transfer and allowance functions. It has no external mint, burn, pause, blacklist, owner or upgrade function and is not a proxy. Code therefore fixes supply mechanics, while treasury distribution and product rules remain off-chain organizational choices.
The whitepaper’s allocation plan divides supply into business companies 30%, business financing 20%, developer program 18%, listing 14%, airdrop 13% and incentives 5%. Those are planned categories, not a live proof of beneficial ownership. The reviewed primary sources do not provide a current wallet-labelled treasury ledger, release schedule reconciled to all transfers, or binding lock contracts.
BITPOINT began Japanese trading on 26 October 2021 and displayed the domestic code JMY; the Ethereum token uses JASMY. This was an exchange listing inside Japan’s registered-provider framework, not state certification of value or technology. The FSA explicitly says assets in registered-provider lists are not guaranteed or endorsed and need not have backing.
Jasmy describes tokens as payment or reward instruments for data and services. The contract itself contains no staking, voting, dividend, redemption, data-license or fee-sharing logic. Any reward depends on a specific application or agreement; a market purchase alone grants only possession and transfer of JASMY.