MemeCore

MemeCore mainnet exposes Ethereum-style RPC endpoints under chain ID 4352 and uses M for fees. Its public Gmeme client is a fork of go-ethereum. The repository describes PoSA, a single-layer engine where stake selects authorities and scheduled signers take turns. That is the machinery that produces blocks.

The product language is broader. Validator pages label the system Proof of Meme, while the dedicated PoM page says PoM is not a conventional consensus model but an evolution framework for a meme token's lifecycle. Both statements can coexist if PoSA is the signing engine inside PoM. They should not be collapsed into the claim that social virality itself validates blocks.

The validator guide says the seven highest-ranked candidates form the active set and that the list refreshes every 10 blocks, roughly 70 seconds at the target cadence. Registration is open to an externally owned account, but it currently requires at least 7,000,000 M. Delegated M and whitelisted meme tokens feed ranking and reward formulas.

This is rotation within a narrow set, not permissionless participation at equal weight. Official consensus docs also leave two different clocks in view: an epoch explanation that initially suggests a day and a newer validator page that says 10 blocks. The operational page and live explorer support fast rotation, but the documentation should reconcile the terms.

The system contract matters as much as the ranking formula. Address 0x1234000000000000000000000000000000000002 manages validators; the explorer labels it a genesis proxy and records a July 2025 implementation upgrade with role events. Governance can adjust registration fees and lists. Token staking chooses candidates, while privileged contract roles maintain the rules of the election.

At launch-era settings, Gmeme emitted 112.5 M per block. RewardTree cut that to 30 M at mainnet block 2,300,000 in July 2025. The client mints the reward and routes it to system contracts, which split value among block producers, M delegators and approved meme-token delegators. These are protocol emissions, not revenue generated by meme commerce.

PoM adds a second loop. Each MRC-20 is meant to receive a Meme Vault; 5% of its supply goes to reserves, split as 1% for M stakers and 4% for that meme token's stakers. Another 10% of block rewards goes to Viral Grants for qualifying vaults. Yet qualification still depends on Meme 2.0 evaluation criteria marked TBA. Words such as fair, sustainable and lasting remain the project's desired outcomes until the rules and results can be tested.

Official documentation states 5 billion M at TGE and a 10 billion maximum, with the additional supply mined through block rewards. The initial split is 58% Community, 15% Foundation, 13% Core Contributor, 12% Investor and 2% Meme Treasury. Those labels describe intended purpose, not custody, unlock timing or enforceable spending constraints.

The Foundation and Meme Treasury together account for 17% of the initial allocation, while contributors and investors account for another 25%. The reviewed official allocation page supplies no vesting wallets or release calendar. That gap matters because validator entry, delegation and future governance all turn M balances into influence.

M's present rights are narrower than the brand story. It pays fees and can enter staking and delegation. The MiCA paper prepared for Kraken in July 2025 described on-chain governance as not live and denied holders ownership, dividends, profit sharing, asset claims and redemption. A stake reward is protocol issuance; it is not a legal share of MemeCore Foundation.

CertiK's dashboard lists 16 findings across MemeCore reviews: no critical findings, but one acknowledged major issue and two partially resolved centralization findings tied to upgrade and privilege. It also shows no formally verified properties and no listed bug bounty. This is more informative than an audit badge alone because it preserves unresolved scope.

The node software supplied a second lesson in February 2026. Gmeme v1.15.3 backported fixes for a high-severity P2P denial-of-service flaw and a medium node-key leakage flaw, warning that keys may already have been partly exposed and recommending regeneration. The response was concrete. It also shows that inheriting from geth brings upstream maintenance obligations to every validator.

MemeCore's strongest verifiable story is therefore smaller than 'virality becomes value.' It operates a public chain, rotates seven stake-ranked signers, publishes client releases and encodes several reward pools. Whether unpublished cultural criteria can resist gaming, whether token holders gain real rule-setting power and how concentrated allocations unlock are still open chapters.