v0.10.15.x Testing

Status
Not open for further replies.
DrkMiner said:
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
Click to expand...

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 ?
 
qwizzie said:
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 ?
Click to expand...

guess so, on linux:

"version" : 101508,
"protocolversion" : 70042,
 
 
 
GilAlexander said:
What is this line in mnw command handling in main.cpp? Some sort of checking with hardcoded key?
Click to expand...

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.
 
flare said:
Evan is learning the joys of CI-Server :)
Click to expand...
:)

note :

i'm getting the 0.001 fees for Darksend self payments too now.. has this changed ? (in my options ''pay transaction fees'' are set to 0.00000000 so i was exspecting 0 Darksend self payments fees too)

Edit : Darksend denominate transactions are coming in.. so this new update looks promising.
 
Last edited by a moderator:
eduffield said:
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.
Click to expand...
sounds analogous to a checkpointing node for mining networks. Who will operate these nodes?
 
i'm seeing 0.1 fees for self payments appearing..... not good.
Edit : Also i'm seeing messages about collateral not valid.

EdX3eSX.jpg
 
Last edited by a moderator:
kryptofoo said:
sounds analogous to a checkpointing node for mining networks. Who will operate these nodes?
Click to expand...
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.
 
eduffield said:
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-13/gitian-win-darkcoin-bin/32/darkcoin-qt.exe
Click to expand...

23.97.152.145 / mpMVevHGJCuBpqxFqbah1dgkSDnyi58nTb
191.235.132.246 / mpCjmn7rKUs6TcXeXxTKoBK1wtkC1Qsune
191.238.52.72 / n43UCKkMybVQ7bFBfyZ2wJciHTetheyuc1
137.135.13.83 / mrtY9qopFHzyqcXju13xFSE2Py6gVUWL6S
168.63.151.85 / moQgMKbaQAZKCCwAqCZvHt6ijouXCNGpYy
23.98.65.243 / myKtKKwAnQWXR78QndMu5sjGoovPbu4jkC
138.91.1.101 / mtohxUb85JwGutcg7y3UoAXhEDKQYkPop9
191.238.80.67 / mkkc3ac6PFKax1AzK7SeqHJUMUhwnHT5sj

Updated to v0.10.15.8
 
If that's your MN list, that's not what I see at all:
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
}
Forked?
 
HinnomTX said:
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.
Click to expand...

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?
 
Can I get everyone to do this that's running v8?

./darkcoind getblockhash 46877
00000008fa567018748da5939a55a88028f397529344eb4886b11c9e69805c26
 
eduffield said:
Can I get everyone to do this that's running v8?

./darkcoind getblockhash 46877
00000008fa567018748da5939a55a88028f397529344eb4886b11c9e69805c26
Click to expand...

running V8 .. sent you the debug.log per email

ran getblockhash 46877 :

00000008fa567018748da5939a55a88028f397529344eb4886b11c9e69805c26
 
eduffield said:
Can I get everyone to do this that's running v8?

./darkcoind getblockhash 46877
00000008fa567018748da5939a55a88028f397529344eb4886b11c9e69805c26
Click to expand...

My MN (108.61.198.220) matches

$ ./darkcoind getblockhash 46877
00000008fa567018748da5939a55a88028f397529344eb4886b11c9e69805c26
 
HinnomTX said:
If that's your MN list, that's not what I see at all:
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
}
Forked?
Click to expand...

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:

"92.222.10.179:19999" : 1,
"178.62.203.249: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,
"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
 
Status
Not open for further replies.
Back
Top