Hey everyone - we are building using Silverscript covenants (KCC20 tokens) on testnet-10. The covenant compiles and the transaction builds/signs correctly with WASM SDK v2.0.1, but we hit a blocker at submission.
We send a v1 transaction with sigOpCount: 0 and compute_budget: 10 (tried many values) through the REST API, but the node responds with:
“script units exceeded the amount committed in the input: used=100000, limit=9999”
The limit=9999 corresponds to ComputeBudget(0). The compute_budget field is silently dropped in the REST to RPC mapping - the same tx works when bypassing the REST API.
We noticed VidaWallet deployed a Silverscript AMM covenant to testnet-10 successfully.
Questions:
- Are you submitting through the community REST API or directly to a kaspad node?
- Is there a known workaround or API version that passes compute_budget through?
- Could the REST API at api-tn10.kaspa.org be updated to forward compute_budget?
Any help would be hugely appreciated!