V12 Release
- Thread starter eduffield
- Start date
moli
Well-known member
I think the devs are sleeping....
Defacto
Member
after so good job they have right to do that :smile:
moli
Well-known member
"SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT" : 1440246078,
eduffield
Core Developer
V12 Update
Everything looks stable now, so we're locking down v12 development and moving on to v12.1 We'll be making announcements soon about the direction of the project. I'm currently doing a lot of research so it could take a bit.
- 12.0.47 has resolved most of the issues that we were having with CPU load and consensus of masternode payment winners
- It's also really nice to see CPU usage and bandwidth are both much lower than v11
A note on queue reset:
When a masternode joins the network it gets in the queue, then waits, usually a few days for a payment. However, what would happen if you dropped out of the masternode list and then rejoined 5 days later? You would receive your payment in about 15 minutes.
To stop this type of attack, whenever you join the masternode pool, you will automatically move to the back of the list. This means that you shouldn't do a cold "masternode start" unless you're trying to bring a specific masternode back online.
This also has a couple nice side effects:
- When people do a mass start-many, they are giving up privacy because their masternodes can be grouped by the signature times. So we will increase the privacy of anyone using start-many frequently.
- SigTime is also intended to represent when the masternode first joined the masternode pool. This will allow us to better determine the average uptime of the masternodes and their level of service.
Everything looks stable now, so we're locking down v12 development and moving on to v12.1 We'll be making announcements soon about the direction of the project. I'm currently doing a lot of research so it could take a bit.
- 12.0.47 has resolved most of the issues that we were having with CPU load and consensus of masternode payment winners
- It's also really nice to see CPU usage and bandwidth are both much lower than v11
A note on queue reset:
When a masternode joins the network it gets in the queue, then waits, usually a few days for a payment. However, what would happen if you dropped out of the masternode list and then rejoined 5 days later? You would receive your payment in about 15 minutes.
To stop this type of attack, whenever you join the masternode pool, you will automatically move to the back of the list. This means that you shouldn't do a cold "masternode start" unless you're trying to bring a specific masternode back online.
This also has a couple nice side effects:
- When people do a mass start-many, they are giving up privacy because their masternodes can be grouped by the signature times. So we will increase the privacy of anyone using start-many frequently.
- SigTime is also intended to represent when the masternode first joined the masternode pool. This will allow us to better determine the average uptime of the masternodes and their level of service.
moli
Well-known member
Could you elaborate on this? What do you mean "giving up privacy"? Thank you.
eduffield
Core Developer
Each masternode has a sigTime, which was when the original message was signed and propagated. So if you sign and propagate 10 at once, they will have the same sigTime, which means that they are probably all owned by the same person.
M
MangledBlue
Guest
So do you think you can 'gap' the start-many's by "random timing" of 5s-30s
[just a thought]
M
MangledBlue
Guest
yep
SPORK INFO
{
"SPORK_2_INSTANTX" : true,
"SPORK_3_INSTANTX_BLOCK_FILTERING" : false,
"SPORK_5_MAX_VALUE" : true,
"SPORK_7_MASTERNODE_SCANNING" : true,
"SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT" : true, <<<<<<<<<<<<<<<<<<<<<<<<<<<<
"SPORK_9_MASTERNODE_BUDGET_ENFORCEMENT" : false,
"SPORK_10_MASTERNODE_PAY_UPDATED_NODES" : true,
"SPORK_11_RESET_BUDGET" : true,
"SPORK_12_RECONSIDER_BLOCKS" : true,
"SPORK_13_ENABLE_SUPERBLOCKS" : false
camosoul
Well-known member
All my 128/128 nodes were managing to parse the chain, but all the "new stuff" that happened afterwards was looping. I bumped to 512 just for the hell of it and it's fine now.
I have a good relationship with my VPS provider becasue I monitor for problems and make sure I keep my actual usage well below what the VPSes are set to do. For this, he hooks me up super cheap since I rare occupy more than half of the footprint, and way less in many categories.
CPU exceeds 2% maybe for a few hours every year.
Bandwidth is a fraction of allowed.
I monitor and catch runaway problems before it causes havoc on his server.
I use about 1/3 of the allowed RAM that I'm paying for.
HD footprint is also super tiny...
Trying to get him hooked up with crypto payments.
Be nice to your host, they'll return the favor.
I've noticed that it tends to sit at ~34% of the 512MB I have now. V11 often expanded to fill whatever it could get. Seems to self-regulate RAM occupation better, as previously it only limited itself when it had no choice... 256 would probably do fine, but since it was so cheap, I went with some wiggle room.
Now I can use my VPSes to goof around doing other stuffs.
Last edited by a moderator:
So if everything is settled, are we going to have enforcement on? Or are we waiting until September 5th?
flare
Well-known member
Enforcement is on since 2015-08-22 12:00 GMT
Icebucket
Active member
uugh, I have another problem, saw that pablo was having the same issue, but did not find any fix for it. my local wallet freezes while sync, restarted several times and always the same problem, goes to 100% of synchronizing budgets but crashes then, im on linux and running the.47 
I keep sitting back down at the computer, LOL.uugh, I have another problem, saw that pablo was having the same issue, but did not find any fix for it. my local wallet freezes while sync, restarted several times and always the same problem, goes to 100% of synchronizing budgets but crashes then, im on linux and running the.47
Are your --reindexing each time? Try just restarting.
Awesome, flare , thanks!
Icebucket
Active member
nope Im not reindexing just restarting.
Edit: and now i just get sync failed :sad:
Last edited by a moderator:
moli
Well-known member
Sometimes it says "failed" but if you just let it sit for a while, it syncs again. But if it doesn't, shut it down, delete the peers.dat and try to run it again.