V12 Testing Thread

v0.12.0.12

*** Please delete mnbudget.dat, budget.dat and restart with --reindex . Thanks! ***

Proposal Security Overhaul
Submissions to the network now require a fee to be paid to the network (mining fee) using a special transaction with a OP_RETURN && ProposalHash in one of the outputs. This allows the network to filter spam quickly, while also allowing anyone to submit a proposal to the network.

To implement these changes we've introduced a few new commands:

mnbudget prepare PROPOSAL-NAME URL PAYMENT_COUNT BLOCK_START DASH_ADDRESS DASH_AMOUNT YES|NO|ABSTAIN [USE_IX(TRUE|FALSE)]
- To create the special transaction

mnbudget submit PROPOSAL-NAME URL PAYMENT_COUNT BLOCK_START DASH_ADDRESS DASH_AMOUNT YES|NO|ABSTAIN FEE_TX
- After the transaction is accepted by the network and has 3 confirmations, you can submit the transaction to the network here

mnbudget show
- Get the proposal hash from here

mnbudget vote PROPOSAL-HASH YES|NO|ABSTAIN
- You can now simply vote by hash using this command

Udjin:

- Temporary unlock MN coins locked by -mnconflock on masternode start-a… …
- make masternode.conf parsing more verbose on errors / translate strings
- fix alternative units in send dialog


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
 
Great to see we are incorporating a submission (miners) fee; I would suggest making it more than a few cents, at least 1 USD to better secure the app. Still playing with the new version so this may be moot.

It occurs to me we will really start to gain some traction once we get a GUI on this baby; that's gonna be my first proposal :).

Pablo.
 
This is not something new for my windows 32 bit wallet (on 64 bit win7) but when I start the wallet up, I go to debug console, and type "masternode debug" I get the following:
not capable masternode: Can't detect external address. Please use the Masternodeaddr configuration option.

When I then enter "masternode start", all is well. Successfully started Masternode

masternode status

{
"vin" : "CTxIn(COutPoint(91b17eb9dabd77c01021724a4218145d254924d8502734e8720ada7017e572c7, 1), scriptSig=)",
"service" : "104.00.00.000:19999",
"status" : 1,
"pubKeyMasternode" : "y5TG2vPD93xwtGTWMCBwbWjJu3ZCoEJ6HG",
"notCapableReason" : ""
}

Just wonderinf if the message "not capable masternode:etc" is coming up falsely or simply incorrectly worded or if there are any problems with my masternode? I get regular payments.

It's been happening, and still happening in v12
 
crowning said:
That's already on my long-term ToDo-list :smile:

But I'll wait until the the (technical) proposal-interface stabilizes...doesn't make sense to start now and throw most of it away when Evan needs to change things...
Click to expand...

Don't you be going anywhere, we need you! No getting a new job that makes you too busy, no having new kids, NOTHING! You understand me? LOL
 
updated my testnet nodes. :)

Code: 
ubuntu@node-master:~/testnet$ seq -w 001 069 | p 'cd testnet ; ./dash-cli -datadir=. getinfo | egrep "(\"version|protocolversion)" | tr "\n" " " ; CURRENT=`./dash-cli -datadir=. getblockcount` ; echo -n "$CURRENT "; ./dash-cli -datadir=. getblockhash `./dash-cli -datadir=. getblockcount` | tr "\n" " " ; ./dash-cli -datadir=. masternode debug'
001     "version" : 120012,     "protocolversion" : 70086, 82181 0000003a88ca0a452a78773d7b98dca949adaf8a4eadf4fb251beda9eba7a559 successfully started masternode
---snip---
069     "version" : 120012,     "protocolversion" : 70086, 82181 0000003a88ca0a452a78773d7b98dca949adaf8a4eadf4fb251beda9eba7a559 successfully started masternode
 
eduffield or UdjinM6 - what did i do wrong here:
19:39:56

mnbudget prepare COOLEST_APP http://www.dashpay.io/one.json 10 82300 y31PMspnaW57Q1WT1ZfNqpgLYYzYHgCNZK 500 yes




19:39:56

Correct usage of vote-many is 'mnbudget prepare PROPOSAL-NAME URL PAYMENT_COUNT BLOCK_START DASH_ADDRESS DASH_AMOUNT YES|NO|ABSTAIN [USE_IX(TRUE|FALSE)]' (code -1)
Click to expand...
EDIT: I just realized i have to pay a fee first, but the post doesn't say how much the fee's supposed to be? And where do we pay this fee?
 
Last edited by a moderator:
Can you clarify what each of these commands are for?


mnbudget prepare : how is this different from the following:

mnbudget submit :

And how do you submit the transaction to the network? I mean, isn't it automatically submitted when you enter, above, as the last item, Fee_TX? The following note is confusing:
- After the transaction is accepted by the network and has 3 confirmations, you can submit the transaction to the network here

Oh, I think I get it. You submit a payment, a fee, to an account. Wait 3 confirmations, and enter the TX number for that fee as the last item in the mnbudget submit, right?

I just don't understand this sentence: Submissions to the network now require a fee to be paid to the network (mining fee) using a special transaction with a OP_RETURN && ProposalHash in one of the outputs. This allows the network to filter spam quickly, while also allowing anyone to submit a proposal to the network.

How do you find your transaction #?

Finally, can that fee go to the foundation? I know people are down on foundations, but it is a legal entity that can submit things (like our trademark) and eventually fight for legislation that protects crypto currencies and advise us all in general on what to do when there is a question. These small fees could be donations to the foundation, help keep it going.
 
Last edited by a moderator:
I did the first part, like so:
mnbudget prepare TSmoneymaker http://www.dashpay.io/ts.json 15 83000 yL7WTtehXs7w5wsyqGMpkdESM9W1ejHRvi 500 yes USE_IX FALSE

But I can't figure out how to see my transaction number, what is the command. I'm using dashd not qt.

In the above case, and the following mnbudget submit, the dash address is the one you want funds deposited into, right? How is the fee paid? From the same account number? Perhaps my account number doesn't have the funds... also, I used an account number from a different wallet, I suppose that wouldn't work? Or?

When I do dash-cli listtransactions I don't see anything except the transactions from my masternode payments?? Is there a way to see the last tx?
 
Last edited by a moderator:
It's just that, if you can get an old ding dong like myself to do this, then anyone can do it. And I will write a how to for the tutorial section (one of many, I'm sure!)
 
eduffield UdjinM6 - Could you give an example how to use "mnbudget prepare" please. So far it's not working for me either I use the console or dash-cli (win32).

From the console:
00:54:56

mnbudget prepare COOLEST_APP http://www.dashpay.io/one.json 10 82500 y31PMspnaW57Q1WT1ZfNqpgLYYzYHgCNZK 500 yes USE_IX true


00:54:56

Correct usage of vote-many is 'mnbudget prepare PROPOSAL-NAME URL PAYMENT_COUNT BLOCK_START DASH_ADDRESS DASH_AMOUNT YES|NO|ABSTAIN [USE_IX(TRUE|FALSE)]' (code -1)


00:55:15

mnbudget prepare COOLEST_APP http://www.dashpay.io/one.json 10 82500 y31PMspnaW57Q1WT1ZfNqpgLYYzYHgCNZK 500 yes USE_IX false


00:55:15

Correct usage of vote-many is 'mnbudget prepare PROPOSAL-NAME URL PAYMENT_COUNT BLOCK_START DASH_ADDRESS DASH_AMOUNT YES|NO|ABSTAIN [USE_IX(TRUE|FALSE)]' (code -1)
Click to expand...
From command-line:
C:\DASH_QT>dash-cli.exe -datadir=C:\TESTNETMN2 mnbudget prepare COOLEST_APP http://www.dashpay.io/one.json 10 82500 y31PMspnaW57Q1WT1ZfNqpgLYYzYHgCNZK 500 yes USE_IX TRUE
error: {"code":-1,"message":"Correct usage of vote-many is 'mnbudget prepare PROPOSAL-NAME URL PAYMENT_COUNT BLOCK_START DASH_ADDRESS DASH_AMOUNT YES|NO|ABSTAIN [USE_IX(TRUE|FALSE)]'"}
Click to expand...
 
UdjinM6 's TODO list: :wink:
Note: I could only send 585,065: a61ea13b35a7d47713f1f0e75ffdc30eda346cd527ed84eff14ef1bdfbabf0b1

upload_2015-7-12_2-29-5.png
 
  • Like
Reactions: AjM
You must log in or register to reply here.
Back
Top