• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

V12 Testing Thread

SPORK_10_MASTERNODE_PAY_NEWEST_NODES

Just an observation might be completely wrong but if we pay newest node first what's to stop people just sending 1000 coins to new address and setting up new nodes and being paid more regularly would it be better to put them to the back of the list .

Just a thought
 
Quick quiz question. Testing lowest of lowest spec servers for an idea I'm developing. Is it KVM or openvz that even if you allocate HDD swap it wont use it?

Sorry for the side track, setting up another tMN
 
TanteStefana said:
Questions, if I may:

"TScherryfarm" : {
"URL" : "http://www.dashpay.io/ts.json",
"Hash" : "678333ef5ee35e7d13b531eae9a0ca0ab250a77493c7f3d9dcc54d74ee8a6f29",
"FeeHash" : "238a5a8e9f7d3ed957fd8177bac5f4bed63f3e8f8c3557e23a5f66959a91481a",
"BlockStart" : 89000,
"BlockEnd" : 89775, How are the payments doled out. I chose 500 coins and 15 payment counts. It should be 500/15 per payment, but how often will I get paid? Every block between these two blocks? There are 775 blocks between start and end, which blocks will have a payment? What determines the spread?
Click to expand...
On testnet, payments happen every 50 blocks. So we're on a very accelerated version of the mainnet implementation.

TanteStefana said:
"TotalPaymentCount" : 15,
"RemainingPaymentCount" : 31, Why is this different from total payment count?
Click to expand...

RemainingPaymentCount definitely had a bug, thanks for pointing it out!
https://github.com/dashpay/dash/commit/f727b2dbd714c9fdaf336db1d9ae4522c759a3ed

TanteStefana said:
"PaymentAddress" : "yL7WTtehXs7w5wsyqGMpkdESM9W1ejHRvi",
"Ratio" : 1.00000000,
"Yeas" : 3, I am highly disappointed in you all, your not voting for me! I thought you were my friends!!!
Click to expand...
Voted!
TanteStefana said:
"Nays" : 0,
"Abstains" : 0,
"TotalPayment" : 7500.00000000, Ooops, I see here it's 500 * 15 = 7500
"MonthlyPayment" : 500.00000000, If this is to be a monthly payment, then shouldn't my BlockEnd be way farther away than 89775?
"IsValid" : true,
"fValid" : true

I only show 3 votes, and I voted 3 times, LOL. So could some of you please vote so I can see this in action?

dash-cli mnbudget vote 678333ef5ee35e7d13b531eae9a0ca0ab250a77493c7f3d9dcc54d74ee8a6f29yes
Click to expand...
 
dark-sailor said:
SPORK_10_MASTERNODE_PAY_NEWEST_NODES

Just an observation might be completely wrong but if we pay newest node first what's to stop people just sending 1000 coins to new address and setting up new nodes and being paid more regularly would it be better to put them to the back of the list .

Just a thought
Click to expand...
Hey... My testnet masternodes got plenty of payments due to this... but Evan just fixed it... lol

https://dashpay.atlassian.net/builds/browse/DASHW-DEV-168

Actually, i don't think ""SPORK_10_MASTERNODE_PAY_NEWEST_NODES" : true," is the issue, it's some other code... I think..
 
I've never been this excited since I managed to set up my very first tMN last year following chaeplin's "el presidente" newb-painful tutorial.

Submitted my first proposal !!

eduffield see if you can spot it hehe :wink:

.
 
Last edited by a moderator:
88337

edit: rebuilding chain now

88599 now
and mix'n 500/2 @24%
 
Last edited:
88625 ... what was the command to find the block hash? Can't find it listed in the command line option list
 
And old persisting bug got the best of me again today. cold/remote setup

- Set up local and remote configs
- On remote, masternode=0 so I can issue "genkey", which I copy to an excel for safe keep, and proceed with local config etc
- Configured local with masternodeprivkey and flag masternode=1. Configure remote with masternodeprivkey but forgot tochange masternode=0 to 1
- tried to start node from QT, gave me error saying something like "can't find the coins" ... its a new message I haven't seen before
- Check configs and notice my lapse, edit, save remote config all fine.
- On the QT I try to start, gives the same mistake. Check configs, all fine, thinking very very low end server with connection problems, but no.
- "masternode debug" give back same error about unallocated coins
- Restart the QT and do "masternode debug" and "successfully started masternode" pops up
- Check remote, yup, I had previously successfully started it.

It seems on Masternode Start, if it errors out, you need to restart the client to clear the memory of that state. This is a long standing behaviour since my ultra-noob days. I've done this config mistake often, getting error messages and ignoring them as checking server side returns node did successfully start.

.
 
yidakee said:
And old persisting bug got the best of me again today. cold/remote setup

- Set up local and remote configs
- On remote, masternode=0 so I can issue "genkey", which I copy to an excel for safe keep, and proceed with local config etc
- Configured local with masternodeprivkey and flag masternode=1. Configure remote with masternodeprivkey but forgot tochange masternode=0 to 1
- tried to start node from QT, gave me error saying something like "can't find the coins" ... its a new message I haven't seen before
- Check configs and notice my lapse, edit, save remote config all fine.
- On the QT I try to start, gives the same mistake. Check configs, all fine, thinking very very low end server with connection problems, but no.
- "masternode debug" give back same error about unallocated coins
- Restart the QT and do "masternode debug" and "successfully started masternode" pops up
- Check remote, yup, I had previously successfully started it.

It seems on Masternode Start, if it errors out, you need to restart the client to clear the memory of that state. This is a long standing behaviour since my ultra-noob days. I've done this config mistake often, getting error messages and ignoring them as checking server side returns node did successfully start.

.
Click to expand...
I don't know what it was like for the MN pioneers during the early days of creating MNs.. but i've had fun setting up MNs with scratchy 's cloud service... When i had to change something in the configs and to make it in effect, all i had to do was restart the wallets... Maybe we're going Microsoft way? "if your MN wallet doesn't work, restart it!" ? lol
 
moli said:
I don't know what it was like for the MN pioneers during the early days of creating MNs.. but i've had fun setting up MNs with scratchy 's cloud service... When i had to change something in the configs and to make it in effect, all i had to do was restart the wallets... Maybe we're going Microsoft way? "if your MN wallet doesn't work, restart it!" ? lol
Click to expand...

I am a bit surprised to have not noticed this service by myself. Granted, I've been a bit away from the forums as of late. Mind linking me to his service? I'd like to check it out, it's the second time this week I've heard of scratchy - don't think I even recognise his handle. Is he new around here? Great to see new guys enter the scene and gain community respect!

.
 
yidakee said:
I am a bit surprised to have not noticed this service by myself. Granted, I've been a bit away from the forums as of late. Mind linking me to his service? I'd like to check it out, it's the second time this week I've heard of scratchy - don't think I even recognise his handle. Is he new around here? Great to see new guys enter the scene and gain community respect!

.
Click to expand...
He's working on his server so it's down for now, but his website is here: http://masternodecloud.com/
poiuty also got a new MN service: https://dashtalk.org/threads/dash-org-ru-masternode-hosting.5723/

And you probably already know about the rest of other mn services.
 
moli said:
He's working on his server so it's down for now, but his website is here: http://masternodecloud.com/
poiuty also got a new MN service: https://dashtalk.org/threads/dash-org-ru-masternode-hosting.5723/

And you probably already know about the rest of other mn services.
Click to expand...

That's what i heard, that the service is a bit flaky. But BIG UP to him for running a free service (for the time being)!

An excellent compromise for a service stress-test while benefitting the community. And quite a responsible and bold approach to figure out back-end quirks on their business model. Very happy to see this. Will keep an eye on it, thanks moli!

.
 
Last edited by a moderator:
yidakee said:
88625 ... what was the command to find the block hash? Can't find it listed in the command line option list
Click to expand...
Code: 
getblockhash index

Returns hash of block in best-block-chain at index provided.

Arguments:
1. index         (numeric, required) The block index

Result:
"hash"         (string) The block hash

Examples:
> dash-cli getblockhash 1000
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getblockhash", "params": [1000] }' -H 'content-type: text/plain;' http://127.0.0.1:9998/
 (code -1)
 
New Version - v0.12.0.27

This should fix a few bugs that we've seen popup such as syncing issues, client hanging on quit and some display issues.

@evan82
do not sync while IBD
delete comment
protocol bump
Various improvements …
Check for existing budget hash before submitting
inc min peer version to 70094 for testing
Fixed RemainingPayments display bug …
New masternodes must wait till end of queue
Disable multisig proposals / IsScheduled read ahead 8 blocks
Fixed mnbudget suggestion
Submit finalized budget 2 days before payment
Fix sync-spork logic

@Udjin
fix resync
do not sync while IBD
small fixes for rpc
active masternode fixes


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
 
You must log in or register to reply here.
Back
Top