Call. Claim. Repeat..

Abstract

$MPAY turns a social ritual into a payout. A holder opens the $MPAY page on GMGN and posts a callout, or posts a thesis on fomo — either one counts as a "call". The wallet attached to that call becomes the payout address. The platform reads the public feeds on both platforms, verifies the call, and pays the reward in BNB.

The size of the reward is not fixed: it scales with the callout multiplier — the price multiple of the token measured from the moment the call was posted. A call that is up 3× earns — on a — base.

Mechanism

• Call. The holder posts a callout on the $MPAY GMGN page, or a thesis on the $MPAY fomo page, containing the phrase gm/gn. The platform records the account and wallet behind it — that wallet is the payout target.
• Scan. A watcher process reads both public feeds (GMGN callouts and fomo theses) every 5 minutes and stores every call it sees: wallet, handle, text, timestamp and multiplier.
• Verify. The first call per wallet is accepted; the call's multiplier is captured and the reward is computed.
• Pay. A payout worker takes queued rewards in order and sends BNB from the rewards wallet. It pauses automatically if the wallet balance falls below the reserve threshold and resumes on the next cycle.
• Record. Every step is written to a ledger: the raw callout, the multiplier used, the amount, the transaction hash and the confirmation status.

The multiplier

Each call carries a multiplier: the ratio of the token price at the moment of settlement to the price at the moment the call was posted. On GMGN it is the same number shown on the callout card.

Multipliers are read from the platform feed, not recomputed by us. If a feed read fails, the payout is retried on the next cycle rather than guessed.

Rewards & payouts

• Asset. BNB on BNB Smart Chain. The USD amount is converted at the payout moment.
• One per wallet. A wallet can only be paid once. If it calls several times, the earliest call is the one that counts; later calls are recorded and marked as duplicates.
• Queue. Verified calls enter a first-in-first-out payout queue.
• Reserve. If the rewards wallet holds less than the reserve threshold (0.1 BNB), the worker sends nothing that cycle and keeps the queue intact, then resumes in order.
• Confirmation. A payout is marked sent when broadcast and confirmed after the configured number of blocks. The transaction hash is always published in the dashboard.
• Ledger. The dashboard shows total allocated, total paid, pending amount, participant count and the token contract, and the full ledger can be exported as CSV.

Verification & anti-abuse

Revenue share & token

Rewards are funded by the token's revenue-share allocation: trading activity feeds a rewards treasury, and the payout worker distributes from it. The token contract will be published at launch and pinned in the dashboard, so the address in the app is always the official one.

Risks & disclaimer

• Platform dependency. Verification reads public data from GMGN and fomo. Platform changes or rate limiting can delay verification; affected calls are retried, not discarded.
• Market risk. Multipliers move with the market. A call can settle below 1× and pay less than the base reward.
• No cap means variable cost. Because rewards are uncapped, an extreme multiplier produces a larger payout. The treasury, not the user, carries that exposure.
• Smart-contract and chain risk. Transfers are irreversible. Always verify the recipient wallet before calling.
• Not investment advice. This document is not an offer, a solicitation, or investment advice.

Roadmap

Appendix

This whitepaper describes system version v0.1. Parameters and endpoints may change as the project ships; the version and date above are updated when they do.