moli
Well-known member
Does your wallet have money? What it does: it takes .0.5 tDASH to pay the fee for you.I think it is because that address has no coins...
Does your wallet have money? What it does: it takes .0.5 tDASH to pay the fee for you.I think it is because that address has no coins...
Does your wallet have money? What it does: it takes .0.5 tDASH to pay the fee for you.
I did "mnbudget prepare" on two proposals one after another... But when I tried to submit, the system does not remember the fee of the first proposal. The second proposal got submitted and voted fine but the first one can't go through, it keeps saying:
"Proposal FeeTX is not valid - 4c9d45a3da59af8379c8b078b62227a1ca062e5387702cce2110262e33ab3482 - Can't find collateral tx %s"
So I guess we have to start and finish one proposal at a time before starting another one?
No, that should be an error, the system should remember the fee ID transaction.Probably, sort of makes sense... unless you realize 1rst proposal you prepared was incorrect and you'd rather prepare something different
mnbudget prepare DASH_2_THE_MOON http://www.dashpay.io/one.json 10 83600 yJExRGH5fig93n8EC7SauAs5G5ArzbSmN1 1000000
0f9f4458d9e8a1c0078aa61b22c7bb09427bbc816d763fdd50f8fba12df4de7d
mnbudget submit DASH_2_THE_MOON http://www.dashpay.io/one.json 10 83600 yJExRGH5fig93n8EC7SauAs5G5ArzbSmN1 1000000 0f9f4458d9e8a1c0078aa61b22c7bb09427bbc816d763fdd50f8fba12df4de7d
Proposal is not valid - 6e6eed56c84b26dbdf68bb531a8cd5d749177513dc2739918b20ee6176a60854 - Payment more than max
mnbudget submit DASH_2_THE_MOON http://www.dashpay.io/one.json 10 83600 yJExRGH5fig93n8EC7SauAs5G5ArzbSmN1 100000 0f9f4458d9e8a1c0078aa61b22c7bb09427bbc816d763fdd50f8fba12df4de7d
Proposal FeeTX is not valid - 0f9f4458d9e8a1c0078aa61b22c7bb09427bbc816d763fdd50f8fba12df4de7d - Couldn't find opReturn
Well I made this proposal
Code:mnbudget prepare DASH_2_THE_MOON http://www.dashpay.io/one.json 10 83600 yJExRGH5fig93n8EC7SauAs5G5ArzbSmN1 1000000
and got this id
Code:0f9f4458d9e8a1c0078aa61b22c7bb09427bbc816d763fdd50f8fba12df4de7d
then tried to submit
Code:mnbudget submit DASH_2_THE_MOON http://www.dashpay.io/one.json 10 83600 yJExRGH5fig93n8EC7SauAs5G5ArzbSmN1 1000000 0f9f4458d9e8a1c0078aa61b22c7bb09427bbc816d763fdd50f8fba12df4de7d
and got
Code:Proposal is not valid - 6e6eed56c84b26dbdf68bb531a8cd5d749177513dc2739918b20ee6176a60854 - Payment more than max
ok
tried to lower the value
Code:mnbudget submit DASH_2_THE_MOON http://www.dashpay.io/one.json 10 83600 yJExRGH5fig93n8EC7SauAs5G5ArzbSmN1 100000 0f9f4458d9e8a1c0078aa61b22c7bb09427bbc816d763fdd50f8fba12df4de7d
and now I get
Code:Proposal FeeTX is not valid - 0f9f4458d9e8a1c0078aa61b22c7bb09427bbc816d763fdd50f8fba12df4de7d - Couldn't find opReturn
So the fee I payed is forever lost?
Prepare checks for almost everything, it should have given you an error, but I missed that one :wink:
https://github.com/dashpay/dash/commit/e57f2d40037a3ce5391bed09c2bae1862651826a
But yeah, the fee is prepared for that exact proposal. If you change anything at all, the hash changes and you'll need to prepare a new fee
mnbudget submit DASH_2_THE_MOON_2 http://www.dashpay.io/one.json 10 83600 yJExRGH5fig93n8EC7SauAs5G5ArzbSmN1 100 2f9257ea79ac1d02f7c7926ce25e2420eb7422cf967cb4e939f2ecb7e4680295
Great!
I just submitted a proposal starting on a block in the past
Code:mnbudget submit DASH_2_THE_MOON_2 http://www.dashpay.io/one.json 10 83600 yJExRGH5fig93n8EC7SauAs5G5ArzbSmN1 100 2f9257ea79ac1d02f7c7926ce25e2420eb7422cf967cb4e939f2ecb7e4680295
Is this ok?
I think the prepare was before that block.
New Version : v0.12.0.16
Eduffield:
- Check IsValid when preparing proposal fee
Udjin:
- Merge upstream 10.0.2 changes from Bitcoin
- Fix CBudgetProposalBroadcast::IsBudgetCollateralValid log output
- lower mn reuse rate
- Start all ds, mnodeman, ix related checks and activate mn only after sync is over
- Major masternode broadcast/ping changes (incompatible with prev version on, proto bump required):
- Do not rely on local lastTimeSeen and requested fRequested anymore. Use last know (signed) ping instead and base all logic on that. Should reduce mn list difference between
nodes.
- Rework CActiveMasternode accordingly along with states, errorMessages, rpc etc.
- Clean some related code, move parts from public to private
- drop c_str in LogPrintf that were related to this functionality (todo: drop it for LogPrintf everywhere else)
Linux32:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux32.tar.gz
Linux64:
https://dashpay.atlassian.net/build...n-linux-dash-dist//dash-0.12.0-linux64.tar.gz
Mac:
https://dashpay.atlassian.net/build...n-osx-dash-dist//dash-0.12.0-osx-unsigned.dmg
Win32:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win32.zip
Win64:
https://dashpay.atlassian.net/build...1/gitian-win-dash-dist//dash-0.12.0-win64.zip
when I do mnbudget show, I see nothing. I'm pretty sure we have some budgets going, no?