Closed nyusternie closed 4 years ago
So I ran the meep command through meep and it looks like your tx.hashOutputs
do not exactly match the outputs of the transaction. Note that the CashScript SDK automatically adds a change output for the leftover money in the contract, which might be a source of error here. You can disable this change output by calling withMinChange(Number.MAX_VALUE)
when building the transaction.
If that is not the cause of the error, try to double check if the outputs you added using the to()
function exactly match the expected output of the smart contract.
Note that the CashScript SDK automatically adds a change output for the leftover money in the contract, which might be a source of error here
hmmm, yeah that sounds about right, considering the inconsistency came with varying UTXO amounts for the same Script .. ugh! likely NOT gonna go back and re-test this right now .. really determined to get the Mecenas contract fully tested (w/ all edge cases) so I can launch Causes Cash asap..
withMinChange(Number.MAX_VALUE)
if I hit this issue again, I'll definitely give this a try..
appreciate you making the time to sort me out 🙏
I have a contract that's having some inconsistencies I can't explain .. I've tried searching for the error, but none of the hits offered a solution..
for some reason, I'm unable to install meep to run this and "maybe" shed some light on the issue .. could someone that has a "working" version of meep, run this and post the results??
~I have a few workarounds to this issue that so far HAVE been consistent, but they would degrade the effectiveness of this contract.~ fyi, I have SEVERAL versions of this contract, but I can post one or more if that would help in resolving the issue..
thanks!
edit: here's the error when I try to
make
meep .. alsogo get github.com/gcash/meep
is hanging, probably for the same reason