TAGGER

TAGGER dates its research, design and self-funded start to the fourth quarter of 2023. Its 2024 roadmap listed an authentication protocol, AI Copilot, collection tools and a marketplace, followed by hardware and agent services in 2025. Those entries record the team's intended sequence; they are not independent proof that each milestone reached production scale.

The public pitch joins jobs usually performed by different institutions. Workers would collect or annotate data, AI would assist them, reviewers would score the output, cryptography would track control, and a marketplace would sell ownership or permission. The GitBook names Trevor Xu as founder and Reagan Wu as development lead, but does not identify a legal issuer that contracts with every TAG holder.

That matters because labeling is not only a technical operation. Accuracy, consent, copyright, privacy and permitted use must survive outside the blockchain. A certificate can timestamp a claim; it cannot manufacture the right behind it.

At block 44,972,322 the BNB Smart Chain created 0x208bf3e7da9639f1eaefa2de78c23396b0682025. Calls identify Tagger, ticker TAG and 18 decimals. The exact address is the dossier's anchor against unrelated TAG tickers and Ethereum contracts.

The verified code is a direct contract rather than an EIP-1967 proxy. Launch released transfer restrictions, minted 300 billion units to a reserve recipient and 20 billion into a PancakeSwap V3 position funded with 70 BNB. The liquidity NFT was handed to a locker for 3,650 days; a lock constrains that position, not every reserve or market-making wallet.

The contract began with signer 0x6F3F71e803D5F59Af4C1D7dAE7d442EF548D4A0f. claim() accepted an address, amount and timestamp signed by that key, required the timestamp to be less than 90 seconds old and allowed each address to claim once. It then minted the signed amount. The chain verified authorization, not whether the claimant actually labeled a photograph.

The project describes a richer scoring system: base reward multiplied by a halving coefficient, account coefficient and quality measure. Account coefficient equals 1 + 0.01 times level; AI-assisted jobs use mask accuracy, manual jobs use pass proportion and review jobs use review accuracy. None of those inputs is calculated in the ERC-20.

The gap becomes visible in the supply constants. MAX_SUPPLY is 400 billion, yet claim() never checks it and current totalSupply is 405.3808 billion. Documentation calls that final figure the total and assigns 85.3808 billion to Tag-to-Pump. The allocation was enforced through signed decisions and distribution operations, not the named constant.

Today owner() returns the zero address, signer() returns zero and standard proxy implementation and admin slots are empty. Owner-only fee-collector and ETH-withdraw functions are therefore inaccessible through that owner path, while zero signer prevents new claims from passing signature verification.

But the code also creates ROLE_DEPLOYER and ROLE_OPERATOR. A deployer can replace the signer and administer operator membership; the operator performed launch. AccessControl does not enumerate members through a simple view. Without a complete current RoleGranted and RoleRevoked reconstruction, “ownership renounced” is narrower than “all privileged roles proven absent.”

TAGGER says clients pay a 5% listing fee for collection, cleaning or annotation tasks. Dataset sellers pay 1% to list; buyers pay another 1% handling fee. Workers receive task rewards and account progression changes their coefficient. These are the economics of an operated marketplace, not automatic rights embedded in a TAG balance.

The distribution page assigns 74.00449158% to Proof-of-Human-Work, 21.06187565% to Tag-to-Pump and 4.93363277% to liquidity. It says a preorder of 106,726 labeling tasks worth $50,000 supported the Tag-to-Pump experiment and that the liquidity tranche paired with $50,000 of BNB; the contract itself records 70 BNB at launch. Different valuation language should not be silently treated as the same fact.

The official token-contract page still says Coming Soon and the audits page contains no report. Without a published contract-to-platform architecture, independent service metrics or customer evidence, readers can verify token movement more strongly than the data business it is meant to finance.

Documentation calls TAG both native and governance token and lists staking, tasks, datasets, subscriptions and model customization as uses. The reviewed contract contains transfers, signed mint claims, role administration and liquidity-fee collection; it contains no voting weight, proposal threshold, quorum or timelocked executor.

A holder owns transferable units that the operated platform may accept. No reviewed holder instrument establishes equity, dataset title, guaranteed work, wages, profit share, redemption, privacy indemnity or a legal claim on marketplace fees simply through TAG ownership. Other independently arising legal claims are not ruled out. Rights behind product records require identified counterparties and enforceable terms.