PUBLIC · ON-CHAIN · VERIFIABLE
The VargaMesh Ecosystem Treasury.
A single public VMESH pot for voluntary ecosystem contributions. Balances, verified contributions, contributor shares and distributions are designed to be independently auditable on-chain.
LIVE TREASURY
VMESH · Mainnet
Last refresh: —. A positive reconciliation delta can represent direct/unattributed inflows; it is never assigned to a nickname without verification.
CONTRIBUTE
Support VargaMesh transparently
Register a pseudonymous contributor identity if you want your contribution attributed to a nickname. You can remain public or appear anonymously.
Save your contributor secret
This secret is shown only once. It stays in this browser and is required to manage your nickname and create attributed contribution requests.
ID:
YOUR CONTRIBUTOR IDENTITY
—
—
SEND VMESH
Create an attributed contribution
Create a payment request first. The service adds a tiny unique verification tag to the amount so another person cannot claim your TXID. Direct transfers without a request still increase the public pot balance, but are not attributed to a nickname.
Send exactly—
—Request expires: —Automatic payment detectionCreate an exact amount and send it to the treasury. This page will look for the matching on-chain output and continue checking until the required confirmations are reached.
MINE TO TREASURY
Point SHA-256d work directly at the pot
Your contributor code is embedded in the worker name. Only a confirmed block that actually pays VMESH to the pot counts as a mining contribution. Hashrate and submitted shares alone never increase Contribution Share.
URL
—Username
—Password
xThe current public VMESH pool uses the VMESH payout address before the first dot. The treasury collector cross-checks the solved block and credits only the amount actually received by the pot wallet.
POLICY BUCKETS
Transparent planning allocation
These percentages are bookkeeping policy for one wallet — not separate wallets, liabilities or promises.
Loading…
Community / Airdrop ReserveA policy bucket may be reserved for future community rewards, testnet/mining campaigns or airdrops. Every campaign must publish its own eligibility rules, snapshot/block height and distribution record before execution. No current contributor is automatically entitled to a future airdrop.
Future liquidity ≠ price backing.
Future liquidity reserve means only that this portion may be considered for legitimate future ecosystem liquidity after exchange availability and regulatory review. It is not price support, market making, a listing promise or a minimum-price commitment.
Future liquidity reserve means only that this portion may be considered for legitimate future ecosystem liquidity after exchange availability and regulatory review. It is not price support, market making, a listing promise or a minimum-price commitment.
INTEGRITY
Snapshot & VargaProof trail
Treasury snapshots can be SHA-256 hashed and anchored with VargaProof. That proves the published snapshot data existed in that form; it is not an audit, solvency opinion or price guarantee.
No published treasury snapshot yet.
MESHPROOF COMMUNITY REWARDS
A published infrastructure-reward program
MeshProof is the first concrete community-reward use of the Treasury: useful public VargaMesh nodes can qualify through verifiable P2P uptime and ownership checks.
Published caps
Current operating policy: at most 100 VMESH per completed UTC day across the program and at most 10 VMESH per eligible node per day. Unused budget remains in the reward wallet.
Separated from consensus
Rewards come from existing Treasury-funded VMESH staged through a limited-balance meshproof-rewards wallet. MeshProof does not mint VMESH and does not change block rewards or mining-pool payouts.
Eligibility is evidence-based
Ownership verification, repeated P2P probes, uptime, chain synchronization, node age and advertised full-node service determine eligibility and Mesh Score. Latency is displayed but not scored.
Public payout record
Completed epochs expose allocation data and, when payouts are enabled and sent, the payout transaction ID. A reward is not guaranteed merely by registering or holding VMESH.
COMMUNITY CONTRIBUTIONS
Contribute to VargaMesh
Open community contribution areas for documentation, mining validation, node operations, language review and development. Scope and any reward are agreed before work starts.
Opening or completing a task does not by itself create a payment claim. Scope, acceptance criteria and any reward must be agreed before work begins. Approved payouts are discretionary project treasury distributions and should be published with purpose and TXID.
VERIFIED CONTRIBUTORS
Contribution leaderboard
The percentage uses cumulative verified attributed contributions. Treasury spending never rewrites historical Contribution Share.
| # | Contributor | Sent | Mined | Total | Share |
|---|---|---|---|---|---|
| Loading… | |||||
TOP DONATIONS
Largest verified individual donations
Ranked by the amount of each verified attributed donation. Mining contributions remain in the contributor leaderboard above and are not mixed into this list.
| # | Contributor | Donation | Date | Transaction |
|---|---|---|---|---|
| Loading… | ||||
PUBLIC LEDGER
Verified treasury activity
Attributed inflows and operator-recorded on-chain distributions. The blockchain transaction remains authoritative.
| Date | Type | Contributor / purpose | Amount | Block | Transaction |
|---|---|---|---|---|---|
| Loading… | |||||
TREASURY POLICY v1.0
What this pot is — and what it is not
Voluntary ecosystem contributions
VMESH sent or mined to the treasury supports the VargaMesh ecosystem. Attributed contributions are final after on-chain confirmation.
Contribution Share has no financial rights
The displayed share is only a transparency metric. It does not grant ownership of the wallet, project equity, repayment, dividends, profits, redemption rights, voting rights or guaranteed future distributions.
One public wallet, operator spending authority
This is a project-operated treasury, not a DAO escrow. The public address makes holdings and movements inspectable; spending authority remains with the treasury operator and distributions should be documented with purpose and TXID.
Mining is credited from confirmed outputs
Mining hashrate or pool shares do not count as VMESH contributions. A contributor is credited only when a solved, sufficiently confirmed block actually pays the treasury wallet and the worker code can be verified.
Reconciliation is explicit
The on-chain wallet balance and the attributed ledger are intentionally separate. Unattributed direct transfers appear as reconciliation delta rather than being assigned to somebody without proof.
Community rewards and airdrops require published rules
The operator may later designate part of the treasury for community rewards or airdrops. Any such campaign should define eligibility, snapshot or block height, amount or allocation method and distribution TXIDs before or when it is executed. Holding VMESH or contributing to the treasury does not by itself create a guaranteed right to a future distribution.
No price or listing promise
The treasury does not back a fixed VMESH price. The future-liquidity policy bucket is only a possible ecosystem use after separate legal and operational review.
PRIVACY & NICKNAMES
Pseudonymous by design
The treasury ledger stores a contributor ID, nickname/public-display choice, hashed management secret and verified blockchain references. It does not require an email address. The treasury application does not persist IP addresses in its ledger; normal web-server and security logs may still process connection metadata. Do not use a nickname that impersonates another person or organization.
PUBLIC ADDRESS
VMESH Treasury
vm1qmh7cnjshtxyrqdfefzs2k7g6r7pd7ma9ntrleg