Problem
A service integrating a buyer lifecycle needs to verify purchase -> use -> terminal settlement -> withdrawal -> Season points without trusting browser input, local history, or wallet material.
At v0.0.15 / 8065ac6a3a728338289ae3a2bd6140aaf6d1f8f6:
dexdo status <deal> --json is an unsigned status/accounting snapshot; it has no terminal receipt, withdrawal result/link, or points evidence.dexdo export --deal is a local unsigned audit snapshot.dexdo withdraw-shell is a seller-signed money-moving operation.
Therefore an integrator cannot treat finalized_owed or a local export as authoritative proof of settlement, withdrawal, or rewards.
Request
Add a read-only, versioned and independently verifiable terminal-settlement receipt/protocol (CLI JSON and/or documented chain/indexer schema), bound to:
- deal/token contract and participant role;
- terminal sequence/finality;
- settled amount and asset, when applicable;
- withdrawal transaction/link/result, when it exists;
- Season-points event/receipt, or an explicit separate authoritative reward query;
- generation time/freshness and cryptographic or independently verifiable provenance.
The output must not require or expose wallet keys, Note material, or private data, and must distinguish not-final, not-withdrawn, and no-points states.
Why
This lets products project settlement and points truthfully only after objective proof, rather than making false claims from unsigned accounting or local history.
Problem
A service integrating a buyer lifecycle needs to verify
purchase -> use -> terminal settlement -> withdrawal -> Season pointswithout trusting browser input, local history, or wallet material.At
v0.0.15/8065ac6a3a728338289ae3a2bd6140aaf6d1f8f6:dexdo status <deal> --jsonis an unsigned status/accounting snapshot; it has no terminal receipt, withdrawal result/link, or points evidence.dexdo export --dealis a local unsigned audit snapshot.dexdo withdraw-shellis a seller-signed money-moving operation.Therefore an integrator cannot treat
finalized_owedor a local export as authoritative proof of settlement, withdrawal, or rewards.Request
Add a read-only, versioned and independently verifiable terminal-settlement receipt/protocol (CLI JSON and/or documented chain/indexer schema), bound to:
The output must not require or expose wallet keys, Note material, or private data, and must distinguish
not-final,not-withdrawn, andno-pointsstates.Why
This lets products project settlement and points truthfully only after objective proof, rather than making false claims from unsigned accounting or local history.