GuidesGeneralMyDaogs

MyDaogs is an on-chain ecosystem built on the Binance Smart Chain. It connects multiple micro-SaaS products and routes their revenue on-chain through registered product contracts and a central RevenueRouter.

This guide covers the MYG token, revenue epochs, staking mechanics, governance, and the path to deployment. For Web3 basics, see the Web3 guide. For platform features, see the Platform guide.

What MyDaogs is

MyDaogs is a BSC ecosystem of micro-SaaS products. Each product registers its revenue on-chain, and the protocol distributes that revenue to stakeholders without off-chain intermediaries.

The architecture is designed for transparency: product revenue is routed on-chain so holders, stakers, and contributors can verify flows directly on BscScan.

MYG token

The MYG token has a fixed supply of 100,000,000 tokens minted at genesis. There is no post-genesis minting. The protocol follows a deflationary buyback-and-burn path: a portion of revenue is used to buy back MYG from the market and burn it, permanently reducing totalSupply.

MYG is traded on decentralized exchanges such as PancakeSwap.

Revenue and epochs

Each registered product sends revenue to the RevenueRouter. Revenue is measured in 30-day epochs. At the end of each epoch, the protocol determines a payout token for that epoch and distributes accordingly. Claims are made in the payout token directly; there are no claim-side swaps.

This design keeps gas costs low and removes slippage risk from the claim process.

Distribution

Revenue distribution follows a strict order:

1. Bounty deducted first paid to the finalizeEpoch caller.
2. Default split: 65% stakers, 25% treasury, 10% buyback.

The treasury allocation funds ongoing development and operations. The buyback allocation is burned, reducing totalSupply and making the token deflationary over time.

Staking

Staking rewards come only from revenue. There is no inflationary emission. A user may have one active staking position at a time.

• Unstaking is full— you withdraw the entire position.
• A 7-day unbonding period applies before funds become liquid.
• Rewards are weighted by per-day epoch weight— the longer you are staked within an epoch, the higher your share.

Governance and safety

Governance is based on staked-MYG voting. Proposals pass through timelocks so participants have time to review before execution.

• Developer vote cap: 20%. No single team or founder wallet can exceed this threshold.
• A 3-of-5 guardian multisig can pause only— it cannot upgrade contracts, change parameters, or withdraw funds.

For questions about safety and operations, visit the FAQ.

Dev compensation

Developer compensation is revenue-indexed, capped, and health-gated. If health gates are not met, payments are deferred in FIFO order until the gates pass.

This aligns the team with protocol health and prevents excessive drain during low-revenue periods.

Sales and readiness

Token distribution includes a presale, private sale, public sale, and a Merkle airdrop for early community participants.

Before any deployment candidate is proposed, the protocol goes through an internal review and test matrix covering unit tests, integration tests, and staging simulation. External security audits are recommended before high-TVL expansion.

Learn more

Explore the Motherhunt app to see how the platform connects agencies, scouts, and models on-chain.