|
TheRealSteve
|
 |
June 17, 2014, 12:35:40 PM |
|
Regarding to the BURN address the only way I see to make sure that the dev doesn't has the private key is to show us exactly how was generated or to generate a new. One way is to use the string you like (avoid forbidden characters), prefix with the necessary prefix, and vary further prefixes/suffixes/checksum until you get an address that passes the address checks. This would give you a valid address without ever having the keys that belong to it - or even knowing whether it ever could be derived from valid keys; can't find the stackoverflow / stackexchange discussion, but I think the consensus was that as long as the address validates, then in theory there should be keys to match it. But yes, as mentioned several times, generating keys to match the address would be extremely difficult. |
|
|
|
|
sandor111
|
|
June 17, 2014, 12:35:55 PM |
|
There are some anomalies in the blockchain, look at block 1000, 4000 and 11000 for example.
...
Maybe that's a PoB block mislabeled as PoW?
Because the hash is just a random hash, and the block reward doesn't adhere to reward = 50/((diff*4096)^(1/4))
50/(0.02457705*4096)^(1/4)) = 15.78...
There actually is no label for PoB, check the code. An easy way to identify them from the getblock() response is to check if the nonce == 0 (as is the case in the example you give). I'm not sure that's 100% foolproof, but it held in the first 12,345 blocks at least. Oh ok, that just got me confused.  |
|
|
|
|
yang5034
|
|
June 17, 2014, 12:53:46 PM |
|
what happend i can get sync now ,and block is 17144 now.
|
|
|
|
|
|
TheRealSteve
|
|
June 17, 2014, 01:02:42 PM |
|
There actually is no label for PoB
Oh ok, that just got me confused. Yeah, hopefully that's one of the things that could be addressed while things are being poked at anyway |
|
|
|
|
sleepdog
|
|
June 17, 2014, 01:15:38 PM |
|
what happend i can get sync now ,and block is 17144 now.
Ha, yeah. Just started my wallet up and it's synced to 17151. I think this is irrelevant though as it seems we're going to be re-launching from 16000. Can we get a definitive statement from the dev about this if possible? |
|
|
|
|
|
sandor111
|
|
June 17, 2014, 01:32:08 PM |
|
what happend i can get sync now ,and block is 17144 now.
Ha, yeah. Just started my wallet up and it's synced to 17151. I think this is irrelevant though as it seems we're going to be re-launching from 16000. Can we get a definitive statement from the dev about this if possible? The hard fork is at block 15934. |
|
|
|
ynyjl
Member
 Offline
Activity: 86
Merit: 10
|
|
June 17, 2014, 01:46:05 PM
Last edit: June 17, 2014, 02:02:43 PM by ynyjl |
|
{
"blocks" : 17182,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00025813,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00001066,
"pooledtx" : 0,
"testnet" : false
}

{
"blocks" : 17191,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00026683,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00001135,
"pooledtx" : 0,
"testnet" : false
}
|
|
|
|
|
|
sleepdog
|
|
June 17, 2014, 02:19:44 PM |
|
what happend i can get sync now ,and block is 17144 now.
Ha, yeah. Just started my wallet up and it's synced to 17151. I think this is irrelevant though as it seems we're going to be re-launching from 16000. Can we get a definitive statement from the dev about this if possible? The hard fork is at block 15934. The dev has confirmed this then? There's absolutely no point in anyone having their wallet running at the moment is there? Likewise for mining? |
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
June 17, 2014, 02:28:11 PM |
|
Dev has not confirmed anything yet. There are doubts he has skills to fix the current issues.
No date for re-launch confirmed
No list of bugfixes confirmed
|
|
|
|
|
ynyjl
Member
Offline
Activity: 86
Merit: 10
|
|
June 17, 2014, 02:37:19 PM |
|
Have the ability to join the development, form a team.
|
|
|
|
|
|
rfcdejong
|
|
June 17, 2014, 03:46:52 PM |
|
what happend i can get sync now ,and block is 17144 now.
Ha, yeah. Just started my wallet up and it's synced to 17151. I think this is irrelevant though as it seems we're going to be re-launching from 16000. Can we get a definitive statement from the dev about this if possible? Dev should put it on the OP as soon as possible, new people don't always read the last posts (pages!). |
|
|
|
|
|
sandor111
|
|
June 17, 2014, 06:37:59 PM |
|
DNS Seeder is up : dnsseed.slimcoinpool.com
|
|
|
|
|
|
|
sandor111
|
|
June 17, 2014, 07:01:20 PM |
|
No idea, that's just some random node. o_0 |
|
|
|
|
|
|
|
exarena
Newbie
Offline
Activity: 50
Merit: 0
|
|
June 17, 2014, 08:14:41 PM |
|
No idea, that's just some random node. o_0 i can confirm that our wallets are out of sync, can you please give me nodes so i can make connectable super node |
|
|
|
|
|
sp00lin9
|
|
June 17, 2014, 08:22:39 PM |
|
No idea, that's just some random node. o_0 i can confirm that our wallets are out of sync, can you please give me nodes so i can make connectable super node My wallet only gets to 15157, I believe some other people can get higher but this is what im using. addnode=144.76.139.111
addnode=23.92.86.148
addnode=68.3.131.174
addnode=77.237.251.163
addnode=92.222.27.45
addnode=114.34.15.168
addnode=63.141.232.170
addnode=50.116.56.210
addnode=108.7.224.149
addnode=85.25.195.74
addnode=72.252.176.12
addnode=213.82.213.152
addnode=144.76.142.47
addnode=77.237.251.163
addnode=84.198.182.60
addnode=76.127.202.17
addnode=96.237.174.192
addnode=107.181.250.216
addnode=107.181.250.217
addnode=144.76.142.47
addnode=144.76.142.49 |
|
|
|
|
|
mumus
|
|
June 17, 2014, 08:26:05 PM |
|
DNS Seeder is up : dnsseed.slimcoinpool.com
I was also planning to open a dns seeder. Got to the point of having a serer online and compiling the seeder from https://github.com/pooler/litecoin-seederCould you please help me with the configuration? Thanks. |
|
|
|
|
|
|
|
