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.
VMESH · Mainnet
Last refresh: —. A positive reconciliation delta can represent direct/unattributed inflows; it is never assigned to a nickname without verification.
Support VargaMesh transparently
Register a pseudonymous contributor identity if you want your contribution attributed to a nickname. You can remain public or appear anonymously.
This secret is shown only once. It stays in this browser and is required to manage your nickname and create attributed contribution requests.
—
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.
—Request expires: —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.
——xTransparent planning allocation
These percentages are bookkeeping policy for one wallet — not separate wallets, liabilities or promises.
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.
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.
Contribution leaderboard
The percentage uses cumulative verified attributed contributions. Treasury spending never rewrites historical Contribution Share.
| # | Contributor | Sent | Mined | Total | Share |
|---|---|---|---|---|---|
| Loading… | |||||
Verified treasury activity
Attributed inflows and operator-recorded on-chain distributions. The blockchain transaction remains authoritative.
| Date | Type | Contributor / purpose | Amount | Block | Transaction |
|---|---|---|---|---|---|
| Loading… | |||||
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.
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.
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.