What is this line in mnw command handling in main.cpp? Some sort of checking with hardcoded key?
4212 + if(!masternodePayments.CheckSignature(winner)){
4212 + if(!masternodePayments.CheckSignature(winner)){
You're welcome! I guess I should have tagged you..good to see it fixed!Fixed. Thanks!
correct :http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-12/gitian-win-darkcoin-bin/32/darkcoin-qt.exe
The latest link is still 15.7
guess so, on linux:correct :
{
"version" : 101507,
"protocolversion" : 70041,
"walletversion" : 60001,
"balance" : 1887.08700000,
"darksend_balance" : 0.00000000,
"blocks" : 46859,
"timeoffset" : -9,
"connections" : 5,
"proxy" : "",
"difficulty" : 0.08339494,
"testnet" : true,
"keypoololdest" : 1413021695,
"keypoolsize" : 1000,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"unlocked_until" : 0,
"errors" : ""
}
we need to be on protocol 70042 .. correct guys ?
Linux 64 daemon and qt are fine.}we need to be on protocol 70042 .. correct guys ?
Evan is learning the joys of CI-ServerLinks are fixed!
CI-builds for v0.10.15.8
Windows 32bit:
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-13/gitian-win-darkcoin-bin/32/darkcoin-qt.exe
http://bamboo.darkcoin.qa/artifact/...tian-win-darkcoin-bin/32/daemon/darkcoind.exe
http://bamboo.darkcoin.qa/artifact/...oin-bin/32/darkcoin-0.10.15.8-win32-setup.exe
Linux 32bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-10/gitian-linux-darkcoin-bin/bin/32/darkcoind
Linux 64bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-10/gitian-linux-darkcoin-bin/bin/64/darkcoind
There's a new type of node that's responsible for telling the network who will get paid. The algorithm is deterministic, but by just having a few of these nodes we'll ensure it can't be attacked. So there's a public key in the source for checking the signatures to make sure it's from one of the privileged nodes.What is this line in mnw command handling in main.cpp? Some sort of checking with hardcoded key?
Evan is learning the joys of CI-Server![]()
sounds analogous to a checkpointing node for mining networks. Who will operate these nodes?There's a new type of node that's responsible for telling the network who will get paid. The algorithm is deterministic, but by just having a few of these nodes we'll ensure it can't be attacked. So there's a public key in the source for checking the signatures to make sure it's from one of the privileged nodes.
These nodes are going to be responsible for monitoring the masternodes and could even do testing on ports, run darksend tests, etc. Just to make sure that the nodes are doing their job. Otherwise they won't be paid.
Good question. Is there any plan to remove the checkpointing that's done now? It seems we are creeping toward a central authority by checkpointing and using 'privileged nodes'. Essentially we are building trust into the DNA of the coin, and that's scary.sounds analogous to a checkpointing node for mining networks. Who will operate these nodes?
23.97.152.145 / mpMVevHGJCuBpqxFqbah1dgkSDnyi58nTb
$ darkcoind getinfo
{
"version" : 101508,
"protocolversion" : 70042,
"walletversion" : 60000,
"balance" : 19751.98471125,
"darksend_balance" : 0.00000000,
"blocks" : 46877,
"timeoffset" : 0,
"connections" : 19,
"proxy" : "",
"difficulty" : 0.10682378,
"testnet" : true,
"keypoololdest" : 1406001326,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
$ darkcoind masternode list
{
"178.62.203.249:19999" : 1,
"92.222.10.179:19999" : 1,
"107.170.168.162:19999" : 1,
"188.226.225.170:19999" : 1,
"198.50.148.87:19999" : 1,
"69.160.84.100:19999" : 1,
"107.170.157.216:19999" : 1,
"176.126.247.191:19999" : 1,
"108.61.198.220:19999" : 1
}
It's either a pubkey in the code that enables a centralized node to issue checkpoints, or it's checkpoints in the code that are also centralized. Aren't they both the same, really?Good question. Is there any plan to remove the checkpointing that's done now? It seems we are creeping toward a central authority by checkpointing and using 'privileged nodes'. Essentially we are building trust into the DNA of the coin, and that's scary.
What version are you running? Can you send me the debug log?i'm seeing 0.1 fees for self payments appearing..... not good.
Edit : Also i'm seeing messages about collateral not valid.
![]()
running V8 .. sent you the debug.log per emailCan I get everyone to do this that's running v8?
./darkcoind getblockhash 46877
00000008fa567018748da5939a55a88028f397529344eb4886b11c9e69805c26
My MN (108.61.198.220) matchesCan I get everyone to do this that's running v8?
./darkcoind getblockhash 46877
00000008fa567018748da5939a55a88028f397529344eb4886b11c9e69805c26
Can you see them now? Maybe it just took a while for them to get registered. I'm seeing all those servers you pasted + mine:If that's your MN list, that's not what I see at all:
Forked?Code:$ darkcoind getinfo { "version" : 101508, "protocolversion" : 70042, "walletversion" : 60000, "balance" : 19751.98471125, "darksend_balance" : 0.00000000, "blocks" : 46877, "timeoffset" : 0, "connections" : 19, "proxy" : "", "difficulty" : 0.10682378, "testnet" : true, "keypoololdest" : 1406001326, "keypoolsize" : 1001, "paytxfee" : 0.00000000, "mininput" : 0.00001000, "errors" : "" } $ darkcoind masternode list { "178.62.203.249:19999" : 1, "92.222.10.179:19999" : 1, "107.170.168.162:19999" : 1, "188.226.225.170:19999" : 1, "198.50.148.87:19999" : 1, "69.160.84.100:19999" : 1, "107.170.157.216:19999" : 1, "176.126.247.191:19999" : 1, "108.61.198.220:19999" : 1 }
[email protected]:~/.darkcoin# ./darkcoind getblockhash 46877
00000008fa567018748da5939a55a88028f397529344eb4886b11c9e69805c26
[email protected]:~/.darkcoin# ./darkcoind masternode list
{
"107.170.168.162:19999" : 1,
"188.226.225.170:19999" : 1,
"198.50.148.87:19999" : 1,
"92.222.10.179:19999" : 1,
"69.160.84.100:19999" : 1,
"107.170.157.216:19999" : 1,
"178.62.203.249:19999" : 1,
"176.126.247.191:19999" : 1,
"108.61.198.220:19999" : 1,
"23.97.152.145:19999" : 1,
"191.235.132.246:19999" : 1,
"137.135.13.83:19999" : 1,
"191.238.52.72:19999" : 1,
"138.91.1.101:19999" : 1,
"23.98.65.243:19999" : 1,
"168.63.151.85:19999" : 1,
"191.238.80.67:19999" : 1,
"202.171.65.13:19999" : 1,
"50.248.181.2:19999" : 1,
"202.171.65.14:19999" : 1
}
Could someone attack/bring down "these nodes" and by that cripple the Master nodes?There's a new type of node that's responsible for telling the network who will get paid. The algorithm is deterministic, but by just having a few of these nodes we'll ensure it can't be attacked. So there's a public key in the source for checking the signatures to make sure it's from one of the privileged nodes.
These nodes are going to be responsible for monitoring the masternodes and could even do testing on ports, run darksend tests, etc. Just to make sure that the nodes are doing their job. Otherwise they won't be paid.
Nope. There's a few of them on the network. they're anonymous and the network functions without them, just masternode payments wouldn't be as predictable.Could someone attack/bring down "these nodes" and by that cripple the Master nodes?
If these nodes are not running or down for some reason what affect will it have on the MN network?
All 8 of my tMNs respond the same thing:./darkcoind getblockhash 46877
My 2 tMNs (92.222.../198.50...) match.Can I get everyone to do this that's running v8?
./darkcoind getblockhash 46877
00000008fa567018748da5939a55a88028f397529344eb4886b11c9e69805c26
I suppose. Is there a way to empower the entire masternode network to implement a consensus style checkpoint? Sunny King referred to a wind down of checkpoints in PPC due to undesirable centralization (not sure if it ever came to pass). At the least, he did refer to a user enabled emergency checkpoint mode that would only be enabled by consensus if the coin ever came under a persistent 51% attack.It's either a pubkey in the code that enables a centralized node to issue checkpoints, or it's checkpoints in the code that are also centralized. Aren't they both the same, really?
My 2 MNs are okCan I get everyone to do this that's running v8?
./darkcoind getblockhash 46877
00000008fa567018748da5939a55a88028f397529344eb4886b11c9e69805c26