opticalcarrier
|
|
January 06, 2014, 10:23:09 PM |
|
P.S. My guess is that a lot of the 250 million(!) darkNXT is founder or large early adopter NXT put into "savings" accts, without realizing (or caring) about the "weak" 64 bit security
You forget about probability of huge transfer made accidentally by stakeholder to wrong account number because of NXT Client freeze, like many other users who had such issue before but with less amounts. I don't think that is a huge issues. The 250m are most likely from people that don't even know that you have to make a transaction to create a public key. Hell i didn't know until 7 days ago and i have 6 digits of them... As far as we all are concerned (those of use with no access to those accts with no published public keys) they are the same scenario and are subject to cracking. Ive already reached out to counterra and asked them to look into curve25519 performance of their terraminer IV 2THps sha256 asics
|
|
|
|
etlase3
Newbie
Offline
Activity: 28
Merit: 0
|
|
January 06, 2014, 10:25:28 PM |
|
As far as we all are concerned (those of use with no access to those accts with no published public keys) they are the same scenario and are subject to cracking.
Ive already reached out to counterra and asked them to look into curve25519 performance of their terraminer IV 2THps sha256 asics
I don't know how these nxt accounts are being secured, but a sha256 asic is going to have a performance of 0 for curve25519...
|
|
|
|
martismartis
Legendary
Offline
Activity: 1162
Merit: 1005
|
|
January 06, 2014, 10:27:55 PM |
|
Jean-Luc, You're been asking for the error I have in not lucky to generate a block. That happens again, except client still working. Text from command prompt:
2014-01-06 17:33:32.751:INFO:oejs.Server:main: jetty-9.1.0.v20131115 2014-01-06 17:33:32.767:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/D:/nxt/webapps/] at interval 0 [2014-01-06 17:33:32.932] Nxt 0.5.0 started. [2014-01-06 17:33:32.933] "blockchainStoragePath" = "blockchain.nrs" [2014-01-06 17:33:32.933] "myPlatform" = "PC" [2014-01-06 17:33:32.933] "myScheme" = "http" [2014-01-06 17:33:32.933] "myPort" = "7874" [2014-01-06 17:33:32.933] "myAddress" = "" [2014-01-06 17:33:32.933] "shareMyAddress" = "true" [2014-01-06 17:33:32.933] "myHallmark" = "" [2014-01-06 17:33:32.933] "wellKnownPeers" = "87.230.14.1; 46.19.137.116; 95.85. 22.142; node18.nxtbase.com; node10.nxtbase.com; vps1.nxtcrypto.org; vps2.nxtcryp to.org; vps3.nxtcrypto.org; vps4.nxtcrypto.org; vps5.nxtcrypto.org; node16.nxtba se.com; node09.nxtbase.com; node29.nxtbase.com; 162.243.214.183; 162.243.213.115 ; 78.46.63.221; 95.85.46.233; 162.243.140.133; 146.185.129.54; 162.243.143.15; 1 09.230.224.65; 46.165.208.107:32151; 54.249.101.252; 37.209.120.192; 84.112.39.2 4; 78.46.63.221; 69.163.47.173; 95.85.46.233; 162.243.140.133; 146.185.129.54; 1 62.243.117.63; 192.241.155.44; 162.243.214.68; 95.85.46.164; 162.243.216.55; 162 .243.143.15; 95.85.46.249; 93.190.92.74; 37.209.120.192; 93.190.92.75; 85.25.134 .59; 93.190.92.76; nxtwallet.com; 31.220.50.208; nxt.ddos.me; 203.174.12.25; 88. 198.142.92; 66.197.138.90; 64.120.180.106; 109.230.224.65; 80.86.92.50; node1.ne xtcoin.it; node2.nextcoin.it; node3.nextcoin.it; node4.nextcoin.it; node5.nextco in.it; nxt.homer.ru; 31.204.130.123; 209.222.0.194; 209.222.16.10;" [2014-01-06 17:33:32.941] "maxNumberOfConnectedPublicPeers" = "200" [2014-01-06 17:33:32.942] "connectTimeout" = "2000" [2014-01-06 17:33:32.942] "readTimeout" = "5000" [2014-01-06 17:33:32.943] "enableHallmarkProtection" = "true" [2014-01-06 17:33:32.943] "pushThreshold" = "0" [2014-01-06 17:33:32.943] "pullThreshold" = "0" [2014-01-06 17:33:32.944] "allowedUserHosts" = "127.0.0.1; localhost; 0:0:0:0:0: 0:0:1;" [2014-01-06 17:33:32.944] "allowedBotHosts" = "127.0.0.1; localhost; 0:0:0:0:0:0 :0:1;" [2014-01-06 17:33:32.945] "blacklistingPeriod" = "300000" [2014-01-06 17:33:32.945] "communicationLoggingMask" = "0" [2014-01-06 17:33:32.946] Loading transactions... [2014-01-06 17:33:35.214] ...Done [2014-01-06 17:33:35.214] Loading blocks... [2014-01-06 17:33:37.273] ...Done [2014-01-06 17:33:37.273] Scanning blockchain... [2014-01-06 17:33:38.439] ...Done 2014-01-06 17:33:38.484:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppCo ntext@49c342bd{/,file:/D:/nxt/webapps/root/,AVAILABLE}{D:\nxt\webapps\root} 2014-01-06 17:33:38.525:INFO:oejs.ServerConnector:main: Started ServerConnector@ 2318ac57{HTTP/1.1}{0.0.0.0:7874} 2014-01-06 17:33:38.714:INFO:oejs.ServerConnector:main: Started ServerConnector@ 6a46661e{SSL-http/1.1}{0.0.0.0:7875} [2014-01-06 17:34:25.446] Generated an incorrect block. Waiting for the next one ... [2014-01-06 17:34:28.968] Generated an incorrect block. Waiting for the next one ... [2014-01-06 17:34:40.588] Generated an incorrect block. Waiting for the next one ...
End of story.
|
|
|
|
utopianfuture
Sr. Member
Offline
Activity: 602
Merit: 268
Internet of Value
|
|
January 06, 2014, 10:31:09 PM |
|
P.S. My guess is that a lot of the 250 million(!) darkNXT is founder or large early adopter NXT put into "savings" accts, without realizing (or caring) about the "weak" 64 bit security
You forget about probability of huge transfer made accidentally by stakeholder to wrong account number because of NXT Client freeze, like many other users who had such issue before but with less amounts. We would have heard about it by now if someone did lose millions of $ due to the client freeze. Besides, what mechanism can a freeze make a right account number become a wrong one ? Unfortunately, this has not been reliably replicated, so all we have are some anecdotal evidences.
|
|
|
|
jl777
Legendary
Offline
Activity: 1176
Merit: 1134
|
|
January 06, 2014, 10:42:24 PM |
|
Looking to buy 10BTC worth at above market price, .00006 BTC
James
|
|
|
|
mcjavar
|
|
January 06, 2014, 10:44:49 PM |
|
Looking to buy 10BTC worth at above market price, .00006 BTC
James
Hi! I am selling for 2 BTC.Pls PM me if interested!
|
|
|
|
salsacz
|
|
January 06, 2014, 10:45:00 PM |
|
Now I see why Nxt has so decentralized PR support I’m a one of those who are against the launch of The Bitcoin Foundation. The most danger that comes from TBF existence, from my point of view, is a chance that Bitcoin will lose its decetralized non-regulated nature and become just yet another digital fiat currency.
|
|
|
|
jl777
Legendary
Offline
Activity: 1176
Merit: 1134
|
|
January 06, 2014, 11:03:21 PM |
|
CfB (or anybody that knows)
I remember somewhere there was a way to forge using API, just from running the java server.
1. How exactly can you start forging for an account from API. 2. How can you verify that it is indeed forging
James
|
|
|
|
trl55238
Newbie
Offline
Activity: 55
Merit: 0
|
|
January 06, 2014, 11:05:30 PM |
|
I like the original phrase DarkNXT.
Maybe I'm alone with this association, but when I hear DarkNXT, I immediately think of Darknet and the gloomy parts of the Internet. I know that this is not correct, with Darknet technically being just an anonymizing network - but I think the public perception is like that. +1
|
|
|
|
davethetrousers
|
|
January 06, 2014, 11:08:04 PM |
|
Meanwhile at Nextcoin.org:
Table './nxt/sessions' is marked as crashed and should be repaired
|
|
|
|
|
klee
Legendary
Offline
Activity: 1498
Merit: 1000
|
|
January 06, 2014, 11:18:36 PM |
|
|
|
|
|
nexern
|
|
January 06, 2014, 11:26:17 PM |
|
hmm, just ran the hiberNXT script here and the numbers seems way to high. i guess an additional filter makes sense. to approximate i think an account with more than one transaction without a key could be consider as a cold wallet.
accounts without key total: 5.509 - nxt : 164.006.650 without key and only 1 trans.: 3.626 - NXT : 26.635.400
any other idea how to filter, doesn't this makes sense at all? to be sure i am testing my db and script again.
|
|
|
|
relm9
|
|
January 06, 2014, 11:27:52 PM |
|
I can't seem to get my client synced up with the blockchain. Fresh install and it stalls on around 12/31/2013 every time. Any ideas? Have 17 active peers...
Can someone post an up to date blockchain?
|
|
|
|
opticalcarrier
|
|
January 06, 2014, 11:32:50 PM |
|
hmm, just ran the hiberNXT script here and the numbers seems way to high. i guess an additional filter makes sense. to approximate i think an account with more than one transaction without a key could be consider as a cold wallet.
accounts without key total: 5.509 - nxt : 164.006.650 without key and only 1 trans.: 3.626 - NXT : 26.635.400
any other idea how to filter, doesn't this makes sense at all? to be sure i am testing my db and script again.
CfB said 250M was hibernating at this point
|
|
|
|
|
nexern
|
|
January 06, 2014, 11:39:02 PM |
|
hmm, just ran the hiberNXT script here and the numbers seems way to high. i guess an additional filter makes sense. to approximate i think an account with more than one transaction without a key could be consider as a cold wallet.
accounts without key total: 5.509 - nxt : 164.006.650 without key and only 1 trans.: 3.626 - NXT : 26.635.400
any other idea how to filter, doesn't this makes sense at all? to be sure i am testing my db and script again.
CfB said 250M was hibernating at this point well, who knows but it is unlikely that a user/s sends again to the same wrong account. if my script hasn't any fundamental error i would say there are ~26m nxt hibernating.
|
|
|
|
relm9
|
|
January 06, 2014, 11:54:33 PM |
|
Thanks it finally started downloading a few blocks, going real slow though - guess the nodes must be under heavy load or something.
|
|
|
|
salsacz
|
|
January 07, 2014, 12:00:03 AM |
|
|
|
|
|
intel
Member
Offline
Activity: 98
Merit: 10
|
|
January 07, 2014, 12:01:43 AM |
|
P.S. My guess is that a lot of the 250 million(!) darkNXT is founder or large early adopter NXT put into "savings" accts, without realizing (or caring) about the "weak" 64 bit security
You forget about probability of huge transfer made accidentally by stakeholder to wrong account number because of NXT Client freeze, like many other users who had such issue before but with less amounts. We would have heard about it by now if someone did lose millions of $ due to the client freeze. Besides, what mechanism can a freeze make a right account number become a wrong one ? Unfortunately, this has not been reliably replicated, so all we have are some anecdotal evidences. This is not anecdote, but a bug hardly to reproduce (happened to me), just imagine you have a corrupted memory in your laptop
|
|
|
|
|