Topic: NXT :: descendant of Bitcoin - Updated Information - page 1748. (Read 2761645 times)

Btw, Nxt has some kind of the event horizon. It's determined by the rate of new transactions. At some rate a person who is trying to catch recent blocks will be downloading them at the same speed as new blocks r being forged.

Actually has been done 15 times and still no black hole has opened...

I'm off to audition for a part in the NXT episode of Dr Who.

The very 1st transaction was sent from an account with 0 NXT. The rest 72 went when it was negative.

You can just change it in the source code!
Of course, getting jean-luc to agree to sign it as official release, that would be a problem

that doesn't count, not actual transactions, just initialization hardcoded in the source code

if people didn't know you are joking you could create mass panic

Sorry, but there are already 72 outgoing transactions from an account with negative balance.

Try it the other way around: Send NXT to the anti-NXT account and see what happens... ;-)

must have positive balance to send NXT

Can you send anti-NXT from the genesis account to normal accounts?  

what would such a collision of NXT and anti-NXT produce?

Exactly. He mentioned that at some moment in the future he would disappear completely. U'll get the secret phrase that opens the genesis account, everyone will be able to play a role of "BCNext".

I think client and/or java process lost blockchain somehow and this is not the refresh browser problem. The same problem I mentioned in my previous posts. I have the same problem, refresh of browser didn't help, needed to restrt everything. After restart everything works, but it shouldn't be the way.

I think you're right. It's "ec2-user" for some including Amazon Linux, RHEL, and CentOS. Well, one of admin/ec2-user/ubuntu/root should work

EDIT: fix typo, it's "ec2-user" not "ec-2user" (thanks EmoneyRu).

With a single leader we have a centralized system. I would imagine, given BCNext's views on centralization he/she/they are slowly contributing less and less as others do more and more.

If I'm not mistaken, Debian user is "admin"

New thread on API 2: https://bitcointalksearch.org/topic/nxt-api-2-brainstorming-406839

Looking closer, the timestamps on the actual transactions are different and are all after the duplicates.

December 30, 2013 7:50:26 AM GMT+02:00      2269220637361284198   90'000   90      10+   
December 30, 2013 7:41:53 AM GMT+02:00      2269220637361284198   10'000   10      10+   
December 30, 2013 7:41:53 AM GMT+02:00      2269220637361284198   11      1      10+   
December 30, 2013 5:26:31 AM GMT+02:00      2269220637361284198   2      1      10

Wait.

Definitely something strange, the transaction IDs are the same!
90000: 2908061711788780811 vs 2908061711788780811
10000: 11922435045177123841 vs 11922435045177123841
11:       8324684714258161869 vs 8324684714258161869
2:         11874188389536146018 vs 11874188389536146018

So definitely a bug of some sort. The same transaction ids are duplicated in the display. They are listed at the top of My transactions, with 0 confirmations but having identical transaction ids as the real transactions. To confuse things even more, the timestamps are different, each actual transaction is in the future relative to the unconfirmed ones.

additonally, I also remember sending a lot more smaller test transactions and they just disappeared without warning, probably due to the system clock being wrong. All during this timeframe. We need a warning when that happens

The client could just not display transactions without confirmations, or only display one with unique transaction ID, but I think this indicates some sort of lower level confusion that needs to be investigated.

James

Or, for non-Ubuntu OS, "ec2-user".

hiberNXT or darkNXT account

I would love to have a group like this exist. It would really show how difficult (or easy ) it is to crack a NXT account.

I would gladly raise a funding for a project like this even just for research purpose.