Anyone seeing a block higher than 51000 ?
Topic: NXT :: descendant of Bitcoin - Updated Information - page 1334. (Read 2761650 times)
Anyone seeing a block higher than 51000 ?
So nothing is fixed ... major stakeholders can still delay forging of blocks to get as much tx fees as they can. Lame!
Please, please please, get out of a PoW mindset when dealing with a PoS system...
Need to see some info from older clients, I've got 5.10, like most of us, anyone on 5.9 or older?
Code:
[2014-01-26 23:17:38.002] DEBUG: Error in milestone blocks processing thread
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@6c92658c rejected from java.util.concurrent.ThreadPoolExecutor@7f490203[Shutting down, pool size = 4, active threads = 1, queued tasks = 0, completed tasks = 90619]
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1372)
at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:132)
at Nxt$Peer.sendToSomePeers(Nxt.java:3511)
at Nxt$Block.pushBlock(Nxt.java:1839)
at Nxt$7.run(Nxt.java:6420)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
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:724)
So are we forking badly or not?
noob question but what happens when it forks???
Everyone engages "headless chicken mode" and runs around shouting.
We should have only one blockchain, that every node agrees on.
In a fork, some nodes seperate from the group and head off on an independent blockchain for some reason.
It could be that all of the older clients (ie 5.9) are on a side chain
Or that the newest clients (5.10) are.
Or that everything has come good:
51001 5154541454348994634 zondag 26 januari 2014 23:17:38
3 730 + 3 384 B
2 8360826299593841999 167 %
14 minutes on one block...there must have something going on there.
So are we forking badly or not?
noob question but what happens when it forks???
Every fork of a network is effectively a new network itself. If you get stuck on a new fork/network then the coins you have are newNXT coins, as opposed to originalNXT coins. And they are not usable on the main NXT network. So they are almost useless.
13 min interval between 51000 and 51001. Why?..
@ nexern https://bitcointalksearch.org/topic/counterparty-desktop-gui-bounty-thread-430998
Hurry , first to market + network effect plays a big role…we want to retain the lead in the 2nd gen market like bitcoin is in crypto
whats the approximate date for the GUI??
Hurry , first to market + network effect plays a big role…we want to retain the lead in the 2nd gen market like bitcoin is in crypto
whats the approximate date for the GUI??
Anyone seeing a block higher than 51000 ?
yea 50001
51001 5154541454348994634 Sun 26 Jan 2014 11:17:38 PM CET
3 730 + 3 384 B
2 8360826299593841999 167 %
\o/
Edit: haha, I could almost HEAR the collective sigh of relief!
3 730 + 3 384 B
2 8360826299593841999 167 %
\o/
Edit: haha, I could almost HEAR the collective sigh of relief!
51001 5154541454348994634 26/1/2014 17:17:38
Is this working? 10+ minutes and no new blocks on my node. 21 hours wait for my block...
https://forums.nxtcrypto.org/viewtopic.php?f=2&t=666
I created a vote here and it seems like the encrypted message won. So I will implement this. Right now I decided to use sha128. But I think there may be other crypto algorithms, which maybe are better. If you can deliver a source for a php implementation (I'm not a crypto guy (not now! :p), so I can't implement it. I can just handle the algorithms and create services with them) then I will think about choose this. If I can find a sha256 php implementation I will take this one.
I created a vote here and it seems like the encrypted message won. So I will implement this. Right now I decided to use sha128. But I think there may be other crypto algorithms, which maybe are better. If you can deliver a source for a php implementation (I'm not a crypto guy (not now! :p), so I can't implement it. I can just handle the algorithms and create services with them) then I will think about choose this. If I can find a sha256 php implementation I will take this one.
Take a look at the topic "Nxt encryption algorithm" posted by CfB:
https://nextcoin.org/index.php?topic=727.0
Thanks. But I don't know how this can help me? I'm talking about sending messages via the AMs.
Same for forging...why does DGEX get all the payoff for holding its users' NXT? Of course, if they lose that, expect higher fees charged to users for DGEX's services.
This. I see 100% POS as a system to prevent exchanges from taking fees. They get them by holding the users NXT. But aren't we all paying various exchange trading and withdrawal fees already? I would prefer that that the beneficial owner gets any NXT from forging. Of course, he can assign the right to receive forged NXT to the exchange for perhaps no or reduced exchange fees (and the arrangement can be enforced with a smart contract). I see this as similar to a right to receive dividends on stock held through a broker; the shares are in the broker's name, but only in name, and the beneficial owner is entitled to any dividends.
Maybe this all becomes moot with the NXT asset exchange?
so many news at few days.
Anyone seeing a block higher than 51000 ?
Im stuck at 51k blocks atm.. and also my forging timer went up from 2k days to 92k days..
51000 is now.....get ready for some forking.
51000 12292439833850569026 zondag 26 januari 2014 23:04:40
1 5'057 + 1 128 B
2 10814881392127211940 83.3 %
@sebastien256: snap.
51000 12292439833850569026 zondag 26 januari 2014 23:04:40
1 5'057 + 1 128 B
2 10814881392127211940 83.3 %
@sebastien256: snap.
So are we forking badly or not?
I bought NXT again from these BTCs. 
Probably from the same poor guy that bought your NXT at 3-e4
It might have been your NXT all along, just more now.
Jump to: