Local scan
The wallet detects candidate balances and excludes risky, illiquid or too costly assets.
Technical - developer version
Reference architecture for wallets, relayers and batch proofs.
DustEthic technology is useful only if it reduces fees, limits consent and makes results verifiable. Web3 primitives are possible building blocks, not automatic guarantees.
Lifecycle
An implementation must separate local scan, signed intent, execution and proof.
Intent
The user signs a bounded intent. No unlimited approval, no ambiguous message.
Batch
The relayer batches only if published thresholds and caps are respected.
Proof
The result publishes amounts, fees, commission, NGO net, network, hash and version.
Technical radar
Building blocks to prototype, monitor or exclude.
L2-firsteconomic base
Low-fee networks are prioritized so the NGO net remains rational.
EIP-5792wallet UX
Wallet API for batched calls and status tracking, potentially useful for bounded and verifiable donation flows.
Read the EIPERC-4337account abstraction
Smart accounts, UserOperations and paymasters may help mutualize some costs, with infrastructure dependencies to document.
Read the EIPEIP-7702delegation
Enables batching scenarios for existing accounts, but must be treated as sensitive for signatures and phishing.
Read the EIPERC-7677paymaster
Paymaster service interface. Relevant for gas sponsorship, but to monitor before normative use.
Read the EIPERC-7683long term
Cross-chain intents and solvers. Exploratory track, not a minimum base for the first prototype.
Read the EIPPrototype
The first prototype must validate the model without handling real funds.
The correct order is: simulator, intent schema, proof schema, security review, then only afterwards a possible legally framed NGO pilot.
Simulator
Generate fictitious dust, select a fictitious NGO, calculate a batch and produce exportable proof.
Intent schema
Define asset, network, amount, recipient, expiry, maximum fees and revocation.
Proof schema
Publish a JSON/CSV format readable by an NGO and verifiable by a developer.
Do not do: unlimited approval, vague signature, opaque relay, beneficiary mixing, free-gas promise or proof reduced to a hash.
Entry criterion for the standard
A technical building block enters DustEthic only if it improves safety, readability, cost or verifiability. Otherwise it remains a research track.