Is DigiDollar's $1 minimum output intentional and permanent? (agent / machine payments)

[eps8sap]

Also raised in the oracle Gitter — posting here for a durable answer, and because I filed a related RPC issue at #424.

Building an agent-payments integration on DigiDollar, I ran into these in src/consensus/digidollar.h:

CAmount minMintAmount = 10000; // $100 minimum mint
CAmount minOutputAmount = 100; // $1 minimum output

minOutputAmount is enforced in consensus validation (digidollar/validation.cpp:826), so a sub-$1 DD output is invalid to the network, not merely refused by the wallet.

Why I'm asking

The emerging AI-agent payment standards (x402, AP2) settle fractions of a cent per API call, and today that's almost all USDC-on-Base — an asset with an issuer-level blacklist, on an L2 with a single sequencer. DigiDollar is the obvious decentralized alternative: collateral-backed, no freeze function, PoW settlement. But the $1 floor rules out per-call metering.

I've routed sub-dollar cases to raw DGB in my tools (no floor there), but that loses the stable pricing that makes DD attractive for machine payments in the first place.

The question

1. Is the $1 output floor dust / UTXO-bloat protection, or does it serve the collateral accounting in a way I'm not seeing?
2. I notice minMintAmountActivationHeight exists, which suggests these params were designed to be adjustable at a block height. Is there appetite to revisit the floor later?
3. Or is DigiDollar deliberately scoped to ≥$1 settlement, with DGB carrying the micro tier?

Any of these is a fine answer — I mainly want to document it accurately in the tools I'm publishing rather than guess.

Context: https://github.com/dgb-tools (testnet only)