Author

Topic: NXT :: descendant of Bitcoin - Updated Information - page 1812. (Read 2761624 times)

newbie
Activity: 28
Merit: 0
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...

It is not clear to me (and possible to others). What is the difference between accounts with pubkey and without? My digits are also worried.

Accounts without a pubkey are only protected by 64bits. It is a first used, first gets basis. Basically even if you created the account by funding it, if you never associate a pubkey to the acct, ANYBODY who stumbles onto the 64bit key will control the account with their 256bit key.

The risk of keys being intercepted online is the usual reason people have for sending funds to an acct, but never using that acct. This backfires. Best to do one transaction. Any transaction and get 256 bit protection which is not projected to be cracked for at least another 8.957 years. Just kidding, 256 bit passwords with high entropy that new clients will enforce (hopefully) will be safe until further notice. Need some giant breakthroughs in crypto busting algorithms or hardware (quantum computers from the future) to even have a chance at breaking 256 bit keys. 64 bit keys, not so strong. Dedicated banks of ASICS could probably become a threat in as little as 5 years.

For significant holdings I recommend a fragmented wallet, eg. 10% in 10 different wallets each with different keys.

James

Im quoting you James as you have laid out a post that has the most elements for my questions. Thanks.

Ok been reading about this 'darknxt' in a few posts. Read some rather agitated post's wanting to ban them and others saying its accounts that have not sent nxt at all. Righteo got that when I tried to get my public key (local get public key)- didn't have one, but sent a nxt got a public key wonderful. I feel so secure.  

Enough background im curious. pubkey, the one I log in and out with I take it yes? I mean if I fly over to any one else running nxt say hi and bash my password in I would get my account? Is this correct? I am going to assume this the case and ask why it is insecure until I send a nxt so making a public key?

I am totally un-technical so im going to take a stab at trying to understand this. All accounts are in the blockchain. Unless you're account has a public id in the blockchain it has a vastly inferior encryption method (ie need to make a alias, transaction or mine a block to get this public id). This in beginning or middle even was never explained and im only hearing this recently (well as far as posts keep expanding rapidly). So was this a bug or a fault found, because it sounds like it. I am going to assume this is an attempt to stop people trying to mine/crack the blockchain (which is d/l by anybody) and was added in after the release? Because this sudden need for this makes it seem so. But..

As i say, I am not technical so if anyone could explain it in simple, start, why, because, manner I would be grateful, as to a layman when I read posts about people wanting to ban accounts that have made no transactions and not reading about any valid reasons to do so makes me question even more this concept.    

 




legendary
Activity: 2142
Merit: 1010
Newbie
Does transparent forging link your IP address to your Nxt balance?

No
legendary
Activity: 2142
Merit: 1010
Newbie
Bounty announcement

100'000 NXT will be paid for working JavaScript code that signs and verifies signatures using NRS algo.

- The licence must allow to use the code in any application
- Sign/verify speed must be not lower than 100 signatures per second on a 1 GHz CPU (1 core)
- All the code must be in a single non-obfuscated well-formatted .js file
- Input/output values must be strings like "8302504e4e57c6c65335289879c6915a273d3aae7bd086058e403fcd2bc18341"

The bounty is valid till the 20th of January, 2014 12:00:00 UTC. The complete code must be published in this thread.

There are already a bunch of JS crypto libraries: http://jsperf.com/nacl-vs-sjcl-sha256-hash/3

None of the existing ones satisfy your needs? There are already SHA256 and curve25519 implementations...

Just compose something working and get 100K.
legendary
Activity: 2142
Merit: 1010
Newbie
Yes, but you have to explicitly handle the json since it doesn't return a proper content type for JSON ('application/json'):

It used to return "application/json" but Unicode symbols didn't work properly in browsers.
legendary
Activity: 2142
Merit: 1010
Newbie
@cfb

how can i find the Blocks detail which one i just Generated

If it was empty - u can't (without API calls).
legendary
Activity: 2142
Merit: 1010
Newbie
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

There is no API for that yet.
newbie
Activity: 10
Merit: 0
How would you suggest targeting a single acct, vs mining against all accts in parallel?

Parallel of course. System is designed in a way that all 'darkNXT' accounts can be recovered with a single 2^64 'pass', there's no need to target accounts individually.
full member
Activity: 155
Merit: 100
so does anyone know about this account 2176239447854173275 sending 1Nxt to a lot of other random accounts?
is it something sneaky going on again? .... ;|
Or it is faucet.

some previous posts say that the account belongs to someone trying to get more Nxt by sending 1nxt high balance accounts with the hope that the bagholders will send back more..the aliases registered under that account suggests the same thing, but noone has confirmed it.

however is there any possibility that this is a scam or theft attempt or something?
legendary
Activity: 1110
Merit: 1000

When 64bit key space is brute forced offline, it doesn't matter which type of darkNXT it is. All of them will be cracked wide open. Even if someone has a key for a darkNXT acct, if the brute force robot cracks the 64bit code first, it will obtain control of the acct and lock out the original funder of the acct.

People who think they are being safer by never going online are doing the exact opposite. We really need to tell people about this. Currently tens of millions of dollars is up for grabs. My understanding is that bitcoin terahash asics can do part of the offline decoding, but the curve25... doesn't have any asics yet, so it will be a very long time before 64 bit space is cracked. However, if NXT price goes up significantly, specialized NXT miner asics won't be too far behind

James

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

+1 Totally right !
hero member
Activity: 784
Merit: 501
so does anyone know about this account 2176239447854173275 sending 1Nxt to a lot of other random accounts?
is it something sneaky going on again? .... ;|
Or it is faucet.
member
Activity: 98
Merit: 10
34839   id  8693426962330810557    408 %

if someone needs a reference.
hero member
Activity: 910
Merit: 1000
and why is gex down?

reminds me of good ol' gox days...
full member
Activity: 155
Merit: 100
so does anyone know about this account 2176239447854173275 sending 1Nxt to a lot of other random accounts?
is it something sneaky going on again? .... ;|
hero member
Activity: 910
Merit: 1000
no clue  Huh
hero member
Activity: 784
Merit: 500
Are we stuck again?

34779      11731960900805566730 1737 %

Nop. You will need to restart client.

Last block:

34794      11731960900805566730      7/1/2014 05:26:17   
0      0 + 0      0 B   
2      13481557620332621774      339 %

Thanks dude.

No new comment for 1,5 hours? Something must have been happened...
full member
Activity: 193
Merit: 100
Are we stuck again?

34779      11731960900805566730 1737 %

Nop. You will need to restart client.

Last block:

34794      11731960900805566730      7/1/2014 05:26:17   
0      0 + 0      0 B   
2      13481557620332621774      339 %

Thanks dude.
legendary
Activity: 1190
Merit: 1001
Are we stuck again?

34779      11731960900805566730 1737 %

Nop. You will need to restart client.

Last block:

34794      11731960900805566730      7/1/2014 05:26:17   
0      0 + 0      0 B   
2      13481557620332621774      339 %
sr. member
Activity: 252
Merit: 250
Not sure if this has been reported, but I got this exception twice today. Content inside blocks widget disappeared, block count negative. Orphaned blocks = tens of thousands, account balance = negative.
Restarted NRS, everything fine. Same NRS 0.5.0 that has been running fine over the past few days.

Code:
[2014-01-07 15:13:46.695] Generated an incorrect block. Waiting for the next one...
[2014-01-07 15:14:01.446] Generated an incorrect block. Waiting for the next one...
[2014-01-07 15:14:28.786] Generated an incorrect block. Waiting for the next one...
2014-01-07 15:22:58.990:WARN:oejs.HttpChannel:Scheduler-1090289695: Commit failed
java.util.concurrent.TimeoutException: Idle timeout expired: 5020/5000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
2014-01-07 15:22:59.212:WARN:oejs.ServletHandler:qtp79296087-241: /nxt
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 5020/5000 ms
at org.eclipse.jetty.util.BlockingCallback.block(BlockingCallback.java:101)
at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:734)
at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:307)
at java.io.OutputStream.write(OutputStream.java:75)
at Nxt.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1568)
at org.eclipse.jetty.servlets.DoSFilter.doFilterChain(DoSFilter.java:457)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:326)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:299)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1539)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:524)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:568)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1110)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:453)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1044)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:199)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:459)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:280)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:229)
at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java:505)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
at java.lang.Thread.run(Thread.java:744)
Caused by:
java.util.concurrent.TimeoutException: Idle timeout expired: 5020/5000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
full member
Activity: 193
Merit: 100
Are we stuck again?

34779      11731960900805566730 1737 %
full member
Activity: 238
Merit: 100
Does transparent forging link your IP address to your Nxt balance?

Cfb claimed no when i asked same question about an atacker tracking and ddosing next forger
Jump to: