Topic: NXT :: descendant of Bitcoin - Updated Information - page 2296. (Read 2761629 times)
yeah the client caught up, i'm now at 22322
One quick question: How is the client supposed to know when I can and cannot generate blocks? E.g., You can generate the next block in "9 hours 16 minutes 15 seconds".
Isn't that supposed to be a random distribution, with the fraction of my stake vs the overall coin count times average minutes per block?
P.S.: Last block 22269, looking healthy from here.
Isn't that supposed to be a random distribution, with the fraction of my stake vs the overall coin count times average minutes per block?
P.S.: Last block 22269, looking healthy from here.
thanks anonyous donor! now hopefully we'll see if that ransaction is in the resulting winning chain...
There is no "correct" chain. Longest chain wins but u don't know which one.
Ok, this one seems longest, I am on block 22322 now, id 14177751551286266419
anyone seen any longer, let me know? )
I think i understand most of the features now.
BUT!
If i open my wallet on several computers, each running the node. does this make the forging faster?
BUT!
If i open my wallet on several computers, each running the node. does this make the forging faster?
No, sorry for that
I am still stuck with block 6149600228563548577 at 22310
Put hosts listed in lastBlockchainFeed about into "wellKnownPeers". Set other parameters to:
connectTimeout = 2000
readTimeout = 2000
pushThreshold = 1
pullThreshold = 1
pushThreshold = 500000
pullThreshold = 500000
in order to use only Hallmarked nodes? to diminish the attack ?
Forum off for ages (nextcoin one). Bitcointalk seems to also be under attack. Whats going on on there?
seems better now,
http://87.230.14.1/nxt/nxt.cgi?action=10
22318 12678226736354368369 22.12.2013 19:24:16 13 2094.71 18 0 2584657662098653454
ps: high target...
http://87.230.14.1/nxt/nxt.cgi?action=10
22318 12678226736354368369 22.12.2013 19:24:16 13 2094.71 18 0 2584657662098653454
ps: high target...
My nodes eventually found a chain with 22318 blocks (target = 2095 %)
yes, it's the correct chain?
There is no "correct" chain. Longest chain wins but u don't know which one.
block 22310 still
Pin
Let us know when u catch us, plz.
My nodes eventually found a chain with 22318 blocks (target = 2095 %)
yes, it's the correct chain?
block 22310 still...
Pin
I think i understand most of the features now.
BUT!
If i open my wallet on several computers, each running the node. does this make the forging faster?
BUT!
If i open my wallet on several computers, each running the node. does this make the forging faster?
I suggest that the source code is released earlier if at all possible. Some stakeholders won't run it otherwise.
What id does block 22311 have?
15409522258630801652
22315, 0 unconfirmed
22317 988823525772914505 So 22 Dez 2013 19:21:31 CET
4 0 + 6 575 B
1 9268012222682756536 1047 %
block 22310 still
Pin
My nodes eventually found a chain with 22318 blocks (target = 2095 %)
Is this a problem money can solve? Because some of the founders are really rich now... would make sense for them to protect their investment by running a load of nodes? Or am I looking at this wrong.
Aye, money could easily solve this problem.
so wtf is happening? someone is ddos attacking or some peer is just trying to fuck up all?
My 32Gb 8 core node on 1 Gbps connection hardly manages to process requests, I wouldn't say this is just some peer.
It's 100 mb/s ddos according to the bandwidth graph, and that's just to my server.
Hehe, 200mb/s and that's only coz hoster limited my bandwidth
Jump to: