Standard

Minimum rules to turn dust into verifiable donations.

This page defines the DustEthic framework: bounded consent, batch grouping, visible fees, separated roles, public proof and applied standard version.

ZERO-OR-WAIT

No additional payment, otherwise wait.

User network fees and additional payment must be zero throughout the required journey. The external sponsor covers network costs, including required setup and failures. A missing sponsor never triggers a user-paid transaction.

Any commission deducted from the batch remains disclosed, capped and accepted before signing; it reduces the NGO net. Donation-funded gas reimbursement is not external sponsorship.

Read the draft profile and failure cases

Scope

DustEthic describes an open method. It does not collect funds.

A wallet, relayer or NGO may implement the standard. DustEthic must not become an opaque custody point or a brand used to hide fees.

Out of scope

no DustEthic token;
no yield;
no active fundraising by DustEthic;
no unlimited approval;
no impact claim without proof.

Mandatory rules

An implementation must pass these controls before any real funds.

Bounded intent

Asset, network, amount, beneficiary, duration, revocation and fee cap must be explicit.

Batch by NGO

Contributions are not mixed between beneficiaries without a public and readable rule.

Rational threshold

Execution starts only if the NGO net remains acceptable after gas and fees.

Exportable proof

Readable JSON or CSV with hash, network, amounts, fees, NGO net and version.

Calculation

The formula must be public and recalculable.

The final amount sent to the NGO is credible only if all deductions are separated. Fiat conversion can help readability, but the primary reasoning remains in crypto units.

gross collectedreal gascommissionoptional reserveNGO net

FormulaNGO net = gross collected - gas deducted from donation - relayer commission - optional technical reserve

Commission

The commission rule must be published before execution. Reasonable ranges can be discussed, but no fee should be hidden.

Version

Each batch states the standard version used for the calculation.

Proof schema

The standard must produce proof readable by an NGO and verifiable by a developer.

{
  "standard_version": "draft-2026-10-03",
  "wallet_profile_version": "0.1",
  "batch_id": "DE-2026-0042",
  "status": "educational_example_not_executed",
  "network": "arbitrum-one",
  "beneficiary": {
    "type": "ngo",
    "name": "Example NGO",
    "receiving_address": null
  },
  "economics": {
    "gross_collected": "128.40 USDC",
    "gas_reimbursed": "0.00 USDC",
    "relayer_commission": "6.42 USDC",
    "technical_reserve": "0.00 USDC",
    "ngo_net_amount": "121.98 USDC"
  },
  "fees": {
    "user_network_fee": "0",
    "additional_user_payment": "0",
    "sponsor": {"name": "Fictional sponsor", "network_asset": "ETH", "network_fee": "0.00024", "funding": "external"}
  },
  "public_proof": {
    "tx_hash": null,
    "reason": "No real-money batch during phase 0"
  }
}

Governance

A modified rule must leave a trace.

Version

The rules applied to a batch must remain identifiable after execution.

Audit

Contracts, relayers, fee schedules and signing interfaces must be reviewed before real funds.

Publish

Major changes must be publicly discussed with justification.