NXT :: descendant of Bitcoin - Updated Information

[wesleyh]

What is the format for account id's in aliases again?

Is it

acc:23232323 ?

[xcn]

What is the format for account id's in aliases again?

Is it

acc:23232323 ?

It should be cleared in NXT wiki, i think.

[mikesbmw]

[2014-02-17 21:22:23.586] DEBUG: Failed to accept block 13734259069497850723 at
height 68803 received from node55.nxtbase.com, blacklisting
[2014-02-17 21:22:26.391] DEBUG: Failed to accept block 13734259069497850723 at
height 68803 received from miasik.no-ip.org, blacklisting
[2014-02-17 21:22:50.345] DEBUG: Failed to accept block 209947979157787352 at he
ight 68804 received from nxt.homer.ru, blacklisting
[2014-02-17 21:23:02.295] DEBUG: Failed to accept block 209947979157787352 at he
ight 68804 received from node10.nxtbase.com, blacklisting

a
I don't understand why it keeps happening to your node, but again those two block ids are from the correct blockchain - at least on the nodes I run.

I am still not sure, who determines what is the correct chain?

i did a video interview with tai zen about how the network discovers the right chain. i cant make any promises but it may be helpful. http://www.youtube.com/watch?v=ZzKyXzZJJA8

Okay, let me ask you some questions. I put these ones on the table some time ago in my analysis of 'Transparent Forging' and CfB haven't answered it, yet. So, maybe you can.

You said: "The higher the stake involved in forging a block the 'better' the block."

So, how should a node (not the network as every node decides on their own) decide when two blocks are forged: one from account A and one from account B.

Now, there are several cases:
1) A comes first, TF says A is before B => A is on top of chain, B gets rejected when arriving (and vice versa)
2) B comes first, TF says A is before B => A didn't forge => B is on top of chain (and vice versa)

3) 2) happend; A arrived late; what happens? Will B get popped off?

3) ok so im not sure specifically how the client handles this situation. you could in theory have all of the nodes reject a as punishment for being late. there would be some advantages to this. personally though i think what you described in 3) would be wiser. ask a dev for specifics. 

IIRC, TF includes something like a penalty to accounts that were too late forging. From the perspective of a node, not forging and the forged block arrived too late are indistinguishable.
That penalty is supposed to prevent selfish mining.

Okay, let's go deeper:

Let's assume, one part of the network underwent 1) and the other part underwent 2) (because of network latency). We now have a partition of the network in nodes (say N1) having A on top and in nodes (say N2) having B on top.

How do we solve that?

Subtract all of the targets on chain a, subtract all of the targets on chain b, see which number is larger.

Sorry to ask again...

Two simple questions: can this be safely disregarded? All is well? (the non-technical answer please  )

[ChuckOne]

Subtract all of the targets on chain a, subtract all of the targets on chain b, see which number is larger.

Subtract from what?

technically it doesn't matter but probably zero would be the most strait forward.

Err, so what about summing them up and see what number is smaller? Sounds easier to explain to most people.

CfB said the next block will decide; still waiting for the how.

According to Wiki TF decides the next forger dependent on the previous block. So, if there is a partition of the network N1 and N2, then the nodes in these two different partitions have different TF outputs.

So, there are two cases: (next blocks/accounts are C, C' (part of N1) and D (part of N2); TF1 and TF2 are the output of TF of N1 and N2 respectively)
1) TF1 says C; TF2 says D => branches will get longer as foreign blocks get rejected
2) TF1 says C; TF2 says C' => C will get accepted; C' will get rejected as N1 expects C => What does N2? I would say: penalize C', ignore C and move on on its branch.

Still don't see how this conflict can be resolved. I need some idea for that.

bump

[abctc]

- so, it is definitely something wrong with the consensus mechanism now ...  because you need to manually recover your nodes from the fork.

I agree.

AFAIK, it was always this way.
https://bitcointalk.org/index.php?topic=303898.msg3375569#msg3375569

- there is no reference to "consensus" on this link.

[superresistant]

Nxt on bitcoinwisdom NOW !

NXT is added.
http://bitcoinwisdom.com/markets/bter/nxtbtc
http://bitcoinwisdom.com/markets/bter/nxtcny

[instacalm]

Nxt on bitcoinwisdom NOW !

NXT is added.
http://bitcoinwisdom.com/markets/bter/nxtbtc
http://bitcoinwisdom.com/markets/bter/nxtcny

Great news!

[xyzzyx]

What is the format for account id's in aliases again?

Is it

acc:23232323 ?

There doesn't seem to be a standard yet.

I'm in favor of the "acct" scheme as defined in this IETF standards draft: http://tools.ietf.org/html/draft-ietf-appsawg-acct-uri-07

Using this proposed standard, a Nxt account would be specified by acct:1234567890@nxt

The Android app by yueye000 uses a custom scheme of "nact". 

Using this custom scheme, a Nxt account would be specified by nact:1234567890

There's another custom scheme I've seen, but I forget what exactly it is and which client uses it.

[marcus03]

Nxt on bitcoinwisdom NOW !

NXT is added.
http://bitcoinwisdom.com/markets/bter/nxtbtc
http://bitcoinwisdom.com/markets/bter/nxtcny

I've asked to add NXT in their thread like 4 or 5 weeks ago and I think others, too. Very cool to now see it added!

[italovers]

Nxt on bitcoinwisdom NOW !

NXT is added.
http://bitcoinwisdom.com/markets/bter/nxtbtc
http://bitcoinwisdom.com/markets/bter/nxtcny

http://bitcoinwisdom.com/markets/bter/nxtbtc
good

[mikesbmw]

Nxt on bitcoinwisdom NOW !

NXT is added.
http://bitcoinwisdom.com/markets/bter/nxtbtc
http://bitcoinwisdom.com/markets/bter/nxtcny

Wow! Very cool!

[McDoxy]

Nxt on bitcoinwisdom NOW !

NXT is added.
http://bitcoinwisdom.com/markets/bter/nxtbtc
http://bitcoinwisdom.com/markets/bter/nxtcny

Wow! Very cool!

OMG Finally!

You can't select it under "Markets" yet though.

[bitmadaboutcoin]

Nxt on bitcoinwisdom NOW !

NXT is added.
http://bitcoinwisdom.com/markets/bter/nxtbtc
http://bitcoinwisdom.com/markets/bter/nxtcny

Wow! Very cool!

OMG Finally!

You can't select it under "Markets" yet though.

do you think it will be long before you can?

[pandaisftw]

Nxt on bitcoinwisdom NOW !

NXT is added.
http://bitcoinwisdom.com/markets/bter/nxtbtc
http://bitcoinwisdom.com/markets/bter/nxtcny

Very nice! Finally a real-time graph I can watch!

[xchrix]

do you think it will be long before you can?

i think they will show it in the main menu when there is more data to show. maybe in some days. otherwise the 1d time period is looking bad. very good news for NXT. but i dont think its realtime because bter isnt providing an API for this. maybe data every 30 seconds?

[mezzovide]

Nxt on bitcoinwisdom NOW !

NXT is added.
http://bitcoinwisdom.com/markets/bter/nxtbtc
http://bitcoinwisdom.com/markets/bter/nxtcny

OMG... finally!

[stereotype]

do you think it will be long before you can?

i think they will show it in the main menu when there is more data to show. maybe in some days. otherwise the 1d time period is looking bad. very good news for NXT. but i dont think its realtime because bter isnt providing an API for this. maybe data every 30 seconds?

Wisdom updates within a second or two of Bter.

Well done to those who badgered Wisdom. 

[Hegemon]

only 3 votes to eat PKR :

https://www.mintpal.com/voting

[sussex]

Reposted because I originally put this in an old thread.

Ok, I wonder if you guys can help?

I bought 500+ NXT through DGEX a few nonths ago, transfered them to my account and have not touched it for a couple of weeks.

Now, when I enter my password, it shows zero balance, zero transactions, nada.

I am sure the password is correct, I use keepass and have checked it against old backups, but it must still be logging me into the wrong account.

I have checked the account number against the explorer and that shows no information at all for the account number.

I'm guessing that my password must be wrong, but I am at a complete loss to explain how it could have happened. It was a randomly generated 30 character password.

Would it be possible for DGEX to trace the receiving account number of the transfers I made, to help me confirm if I am looking at the right account or not? There is no historical detail at all on DGEX, no txids, nothing, just dates.

Anyway, all help is appreciated, but I suspect the NXT has gone.

This is the first time I will have lost coins in this way, I'm a fairly experienced crypto geek, so if this can happen to me, it will happen to noobs. There's got to be a better way.

It's certainly put me off the NXT system.

EDIT:

I have just remembered that I saw my NXT in my account a few weeks ago when I was totting-up all my accounts.

EDIT EDIT:

I am trying to get the client to run on a Raspberry PI, this is the only reason I noticed the problem. If my client has downloaded a corrupt blockchain, would my password then log me into the wrong account? I ask because I am trying to reconcile the reason behind there being nothing shown in the block explorer.

 

[wesleyh]

If it shows zero transactions it probably means you are on a fork or something. Make sure you update to latest NRS 0.7.5