ESHARE is the native ERC-20 token of EMP Fusion, a DeFi protocol on Base that centers around Microgrid NFTs—digital assets representing participation in decentralized infrastructure. According to its official website and source-reported documentation, users acquire Microgrids and stake them to earn variable rewards paid exclusively in ESHARE. The project states these rewards are funded by revenue generated across the broader EMP ecosystem, though no public breakdown of revenue sources or real-time yield data is provided. ESHARE trades on Base-based liquidity pools, including Uniswap, and its contract is verified on BaseScan at 0xb7C10146bA1b618956a38605AB6496523d450871. Notably, the token’s circulating supply is reported as zero, while total and max supply are both capped at 59,951 tokens. A critical notice from the same source warns that the smart-contract owner retains minting authority—a material control risk. Key questions remain: What verifiable revenue streams fund ESHARE rewards? How is reward variability determined and disclosed? Does staking Microgrids require holding ESHARE—or is the token purely a payout medium with no functional role in access or governance?
ESHARE is described as an ERC-20 utility and rewards token for the EMP Fusion ecosystem on Base, tied to staking Microgrid NFTs and earning variable yield. The project’s website (fusion.emp.money) presents a landing page with marketing language but no functional interface—no staking flow, wallet connection, or live dashboard is observable. Static extraction confirms only metadata; JavaScript-driven interactivity, contract interaction, or user journey execution cannot be verified from this snapshot. The API source explicitly states that circulating supply is 0 and notes the smart-contract owner retains mint authority—a material centralization risk. No evidence of deployed, tested, or audited contracts is supplied; explorer links are unvisited and unverified. There is no documentation, repository, or on-chain activity data (e.g., transaction volume, staker count, or reward distribution logs) to confirm product operation or retention. The description references a marketplace and staking system, but no working implementation is evidenced. Claims about revenue-funded rewards remain theoretical without financial disclosures or verifiable revenue streams. The absence of MVP evidence triggers the rubric’s hard cap: “No verifiable working MVP is evidenced in the supplied snapshot.” A roadmap or token listing does not satisfy the core user journey requirement.
Overall score: 4/10 Confidence: Low