All scheduled amounts represent maximum release eligibility. Reaching an eligibility date does not automatically distribute tokens. Actual release may be zero, partial, or up to the currently available eligible amount. Unused eligibility can accumulate within the contract limits. No automatic distribution or mandatory catch-up occurs.
Zero release means no release transaction. A successful release(uint256 amount) requires a positive amount. Treasury use remains subject to the allocation’s purpose and genuine project needs.
Fixed-duration timing
1 month
30 days
6 months
180 days
12 months
360 days
24 months
720 days
48 months
1440 days
MDC Treasury / Vesting contracts use fixed-duration periods, not a natural-calendar month/year model. One day is 86,400 seconds. Calendar dates drift relative to these fixed periods by design; all timing is enforced by Ethereum block.timestamp.
Every schedule is derived from this Genesis. Deployment of an individual Vault, publication of this page or later document updates do not reset its schedule. The first tranche is eligible at its startTime, not one interval later.
Seven allocations. One fixed supply.
54,000,000 MDC · 100% total allocation
Founder
5,000,000 MDC9.26%
H1 · FOUNDER RELEASABLE VAULT
4,000,000 MDC
Initial lock: 720 days from Genesis. At startTime, 50,000 MDC becomes eligible; another maximum 50,000 MDC becomes eligible every 30 days. There are 80 tranches, capped at 4,000,000 MDC. Eligibility only, not automatic distribution.
Founder schedule parameters
startTime · Genesis + 720 days
1850928515 2028-08-26 18:48:35 UTC
interval / amountPerInterval
2592000 seconds / 50,000 MDC
Final tranche
Period 80 = startTime + 79 × 30 days
H2 · FOUNDER PERMANENT LOCK
1,000,000 MDC
Permanently and irreversibly locked. This is not ordinary vesting or a time-lock awaiting an unlock date. There is no beneficiary or Treasury.
Already deployed historically and accounted separately. Actual original LP contribution: 4,999,999.9999999999761456 MDC. This is a historical amount, not the current LP composition.
Historical Batch 1 is not included in the H7 Vault or the 49M production Vault/Lock funding.
H7 · REMAINING LIQUIDITY RESERVE VAULT
8,500,000 MDC
Batch 2: 5,000,000 MDC eligibility at Genesis + 180 days. Batch 3: an additional 3,500,000 MDC at Genesis + 360 days. H7’s final maximum eligibility is 8,500,000 MDC.
These are eligibility limits, not mandatory liquidity deployment. The full 13.5M is not held in one Vault.
Liquidity batch parameters
batch2Time / batch2Amount
1804272515 / 5,000,000 MDC 2027-03-05 18:48:35 UTC
batch3Time / batch3Amount
1819824515 / 3,500,000 MDC 2027-09-01 18:48:35 UTC
Security / Bug Bounty
5,000,000 MDC9.26%
H3 · SECURITY VAULT
10,000 MDC every 30 days
Maximum eligibility begins at Genesis and accumulates up to the allocation. For genuine, validated security research, vulnerability reports, fixes and qualifying security contributions.
If no valid security contribution exists, actual distribution may be 0. It is not automatically distributed.
Security schedule parameters
startTime · Genesis
1788720515
interval / amountPerInterval
2592000 seconds / 10,000 MDC
Community Promotion
1,000,000 MDC1.85%
H4 · PROMOTION VAULT
1,000 MDC every 30 days
Maximum eligibility begins at Genesis and accumulates up to the allocation. For genuine community building, early user testing, reasonable promotion and participation.
Not automatically distributed. Actual use may be 0 when there is no reasonable need. Small test distributions should retain date, amount, purpose and transaction records.
Promotion schedule parameters
startTime · Genesis
1788720515
interval / amountPerInterval
2592000 seconds / 1,000 MDC
Development / App
5,000,000 MDC9.26%
H5 · DEVELOPMENT VAULT
10,000 MDC every 30 days
Maximum eligibility begins at Genesis and accumulates up to the allocation. Only for genuine development, infrastructure, future MDC App needs, developer contributions and necessary technical services.
Actual use may be 0 when there is no genuine need. Unused amounts remain in the Development Vault or Treasury.
Development schedule parameters
startTime · Genesis
1788720515
interval / amountPerInterval
2592000 seconds / 10,000 MDC
Team & Contributors
5,000,000 MDC9.26%
H6 · TEAM VAULT
500,000 MDC every 180 days
Initial lock: 360 days from Genesis. The first 500,000 MDC becomes eligible at startTime, followed by one tranche every 180 days. 10 tranches total, capped at 5,000,000 MDC.
Not automatic salary. Not automatic distribution. Actual use depends on genuine, identifiable contribution and can be partial or 0.
Team schedule parameters
startTime · Genesis + 360 days
1819824515 2027-09-01 18:48:35 UTC
interval / amountPerInterval
15552000 seconds / 500,000 MDC
Final tranche
Period 10 = startTime + 9 × 180 days = Genesis + 1980 days
Community / Ecosystem Reserve
19,500,000 MDC36.11%
Two independent 9,750,000 MDC reserves with separate schedules. The same tokens are never counted in both parts. Each tranche is maximum eligibility, not mandatory distribution.
H8 · ECOSYSTEM PART I
9,750,000 MDC
Initial lock: 1080 days from Genesis. The first 750,000 MDC becomes eligible at startTime. Every 360 days, the next tranche increases by 50,000 MDC, for 10 periods.
Part I · maximum eligibility per tranche
Period
MDC
1 · startTime
750,000
2
800,000
3
850,000
4
900,000
5
950,000
6
1,000,000
7
1,050,000
8
1,100,000
9
1,150,000
10
1,200,000
Total
9,750,000 MDC
Part I schedule parameters
startTime · Genesis + 1080 days
1882032515 2029-08-21 18:48:35 UTC
interval
31104000 seconds / 360 days
initialAmount / stepAmount / periodCount
750,000 MDC / 50,000 MDC / 10
H9 · ECOSYSTEM PART II
9,750,000 MDC
The first 4,875,000 MDC becomes eligible at Genesis + 2880 days. Thereafter, every 1440 days, the next tranche is half the previous tranche, rounded down in integer base units.
Part II · first five eligibility tranches
Period
MDC
1 · startTime
4,875,000
2
2,437,500
3
1,218,750
4
609,375
5
304,687.5
83 non-zero tranchesFinal maximum cumulative eligibility: allocation − 23 base units
23 base units remain permanently ineligible for release inside H9’s allocation. This is not a burn, not an extra lock contract and not the Funding Source residual. No final sweep or rounding catch-up exists.
Part II schedule and exact integers
startTime · Genesis + 2880 days
2037552515 2034-07-26 18:48:35 UTC
interval / initialAmount
124416000 seconds / 4,875,000 MDC
Integer floor-halving
nextTranche = floor(previousTranche / 2) Amounts use 18-decimal base units, never floating-point arithmetic.
Terminal cumulative eligibility
9749999999999999999999977 base units
Final non-zero tranche
Period 83: 1 base unit at 12239664515 startTime + 82 × interval. All later tranches are 0; cumulative eligibility stays unchanged.
Permanently ineligible amount
23 base units = 0.000000000000000023 MDC
How release works
release(uint256 amount) requires an explicit Ethereum transaction. It does not happen automatically.
Any address can call it. The caller cannot choose the destination and does not receive tokens merely by calling.
Tokens always go to the fixed Treasury for that Vault.
The amount must be positive and cannot exceed either remaining eligibility (releasable) or the actual Vault balance.
availableToReleaseNow is the smaller of those two limits, not an amount already released.
State is updated before transfer; a transfer failure reverts the transaction.
Immutable destination. Safe-managed Treasury.
Each releasable Vault has an immutable Treasury address. Treasury funds are managed by the corresponding Safe. Safe signer and threshold configuration is operational governance, not the same as the immutable Vault Treasury address. Signers, threshold, modules, guard and fallback handler can change under valid Safe rules; changes require separate review and recording.
Treasury spending and distribution are separate from release into the Treasury. Unused resources may remain in the Vault or Treasury; reaching eligibility does not require a sale or forced distribution.
Historical accounting: two different residuals
The Funding Source accounting residual is 23,854,400 base units (0.0000000000238544 MDC), the difference between the nominal 5M Batch 1 allowance and the actual historical LP contribution. The Production Registry records it at the Funding Source in snapshot S1. It is not a new allocation and is not added to H7 or another Vault.
H9’s 23 permanently ineligible base units are already inside H9’s allocation and the 49M funding total. They are completely separate from the Source residual.
49,000,000 MDC production funding + 4,999,999.9999999999761456 MDC historical Batch 1 + 0.0000000000238544 MDC Source residual = 54,000,000 MDC. This is historical funding reconciliation, not a formula for the sum of future current Vault balances.
From rules to production
Production Implementation
9 production Treasury / Vesting instances are deployed on Ethereum Mainnet, with 49,000,000 MDC in completed production funding. H1–H9 map to the allocations above; Historical Liquidity Batch 1 is separate. Current balances and eligibility must be read at a named snapshot, not inferred from these original allocations.
These are read-only public transparency tools. Operational checks and source/runtime/parameter conformity verification are not a third-party security audit, formal verification or a security guarantee.
Liquidity Transparency
Initial MDC / ETH Liquidity Locked On-Chain
The first official MDC / ETH liquidity position was created on Uniswap V4 and locked through UNCX. The liquidity remains active in the Uniswap pool while the position principal cannot be withdrawn before the unlock date.
Position
NFT #396442
UNCX Lock
#106
Initial MDC
~5,000,000
Initial ETH
~0.1122
Fee Tier
0.25%
Unlock
Sep 8, 2028 17:30 UTC
Pool ID 0x0951b427016a3fc5c7c8ca7217af4ac5b86b76ef2c5cdd20f1caaf6de22b3ff3
Liquidity locking limits withdrawal of the locked position until the stated unlock time. It does not eliminate smart-contract, protocol, market, or other digital-asset risks.
Swap MDC
Swap MDC on Uniswap
MDC is available through the official MDC / ETH liquidity pool on Uniswap V4. A successful swap sends MDC directly to your connected Ethereum wallet.
Always verify the official MDC contract address before swapping. Never rely only on a token name or symbol.
0xd6b160672Fad1376943F1E6d60C41adb103aED33
Step 1
Open Uniswap
Use the official pool link above.
Step 2
Connect Wallet
Connect an Ethereum-compatible wallet and keep ETH for the swap and network gas.
Step 3
Swap ETH → MDC
Review the token address, amount, price impact and transaction details before confirming.
Step 4
Hold in Your Wallet
After confirmation, MDC is held directly at your wallet address. Some wallets may require importing the token contract to display it.
Uniswap is a third-party decentralized protocol. MDC does not guarantee execution price, liquidity, availability, or future token value. Digital assets can be volatile.
Always verify the website domain and contract address before connecting a wallet, buying, sending, or receiving MDC.
MDC will never ask you to reveal your recovery phrase or private key.
Vision
A Simpler Digital Experience
MDC aims to explore ways to make digital value easier to use in everyday life.
Today, blockchain can still feel complicated. Wallets, networks, and gas fees can create friction for everyday users.
The long-term MDC vision is to develop tools and applications that simplify the experience, so people can focus on sending, receiving, and managing MDC without needing to understand every technical layer behind it.
Future development may explore technologies that reduce complexity around transaction fees and network configuration.
Future Product
The Future MDC App
Send
Simple Transfers
Receive
Easy Access
Manage
User-Friendly Experience
Connect
Community Ecosystem
Roadmap
The Journey Ahead
Completed
Phase 1 — Foundation
Ethereum deployment, contract verification, official website, first Uniswap V4 liquidity position, and initial on-chain liquidity lock.
In Progress
Phase 2 — Community Growth
Expand awareness, strengthen official channels, and grow participation around the MDC community.
Planned
Phase 3 — Ecosystem Development
Explore useful tools, accessibility improvements, and practical community-focused use cases.
Planned
Phase 4 — MDC App
Explore application development focused on making sending, receiving, and managing MDC easier.
Long Term
Phase 5 — Long-Term Growth
Continue building the MDC ecosystem as technology, community needs, and opportunities evolve.
Community
Join the Journey
MDC is only at the beginning of its journey. Follow the official channels and verify information through the official website and contract address.