Proposal: cantonsim
RejectedPR- SIG
- needs-SIG
- Champion
- —
- Author org
- pixelplex
- Ask
- source pending
Abstract
Canton developers, application operators and wallets cannot find out what a command will do before submitting it: who will receive which part of the transaction, what it will cost, and why it is being refused. The participant computes most of this during submission and returns almost none of it — routing rejections arrive as one unstructured string, and a CreateAndExerciseCommand passes preparation only to be refused at execute, after it has been signed.
Milestones
No milestones recorded.
Budget impact
- % of approved-to-date
- —
- % if all RFV pass
- —
RFV scenario unavailable — using approved-to-date as denominator (degraded mode).
- Ask (CC)
- amount pending
Comments by org
No public reasons documented.
View discussion on GitHub