NXT :: descendant of Bitcoin - Updated Information

[SZZT]

Can we please stop wasting time with emule and focus on improving nxt so we can make money? The last 5 pages have had nothing but emule talk. Get off his d*** everyone, guy is annoying and unfunny and is being succesfull on derailing an important project

take it easy mate!
a bar is where people get to relax a bit after work )

Can a brother get a beer in here?

[apenzl]

[Daedelus]

Sorry guys...

(Soon to be taken) from the Nxt Glossary...

****

Elmo
See Emule.


Emule
Emule is a Nxt user who is, and always has been, extremely pessimistic about the future of Nxt. He/She can often be seen predicting a large fall in the price of NXT, which predictably do not occur when He/She claims they will. When the NXT price invariably falls, Emule will claim it was due to his/her selling action. On many, many occasions (25+ by some estimates) it has been shown that Emule's predictions don't come true and many have pointed out the poor logic behind telling people you are about to sell a large amount before you actually do (you could get better prices if you don't). But Emule remains a tenacious member of the Nxt community. Emule is adamant that he/she is an original Founder who has millions of NXTs to Dump. Or sometimes that they are just a trader out to make a killing. All evidence so far suggests they are just a FUDster but only time will tell. Despite his/her stance and sometimes unbecoming behaviour (i.e. making claims about the sexual orientation of other users mothers), he has become a lovely rogue and pantomime villain of the Nxt Pub threads, earning the nickname Elmo and often receiving a tickle behind the ears when he makes an appearance.

****

Bookmark the Nxt Glossary here >>>>> http://wiki.nxtcrypto.org/wiki/Glossary 

[starik69]

Someone broke the blockchain!  

Code:

[2014-03-26 17:50:47.266] DEBUG: block 0
[2014-03-26 17:50:47.427] DEBUG: Error in block generation thread
[2014-03-26 17:50:50.086] DEBUG: block 5000
[2014-03-26 17:50:53.050] DEBUG: block 10000
[2014-03-26 17:50:55.985] DEBUG: block 15000
[2014-03-26 17:50:56.187] DEBUG: Invalid transaction attachment:
{"alias":"IWE","uri":"SZ"}
[2014-03-26 17:50:56.188] DEBUG: Dropping invalid transaction
[2014-03-26 17:50:56.194] DEBUG: Invalid transaction attachment:
{"alias":"IWA","uri":"SZ"}
[2014-03-26 17:50:56.194] DEBUG: Dropping invalid transaction
[2014-03-26 17:50:56.201] DEBUG: Invalid transaction attachment:
{"alias":"IWD","uri":"SZ"}
[2014-03-26 17:50:56.202] DEBUG: Dropping invalid transaction
[2014-03-26 17:50:56.208] DEBUG: Invalid transaction attachment:
{"alias":"IVX","uri":"SZ"}
[2014-03-26 17:50:56.209] DEBUG: Dropping invalid transaction
[2014-03-26 17:50:56.215] DEBUG: Invalid transaction attachment:
{"alias":"IWB","uri":"SZ"}
[2014-03-26 17:50:56.216] DEBUG: Dropping invalid transaction
[2014-03-26 17:50:56.222] DEBUG: Invalid transaction attachment:
{"alias":"IVZ","uri":"SZ"}
[2014-03-26 17:50:56.222] DEBUG: Dropping invalid transaction
[2014-03-26 17:50:56.228] DEBUG: Invalid transaction attachment:
{"alias":"IWG","uri":"SZ"}
[2014-03-26 17:50:56.230] DEBUG: Dropping invalid transaction

Client continuously rescaning it and balance became mad

[DrearyUrbanite]

Sorry guys...

(Soon to be taken) from the Nxt Glossary...

****

Elmo
See Emule.


Emule
Emule is a Nxt user who is, and always has been, extremely pessimistic about the future of Nxt. He/She can often be seen predicting a large fall in the price of NXT, which predictably do not occur when He/She claims they will. When the NXT price invariably falls, Emule will claim it was due to his/her selling action. On many, many occasions (25+ by some estimates) it has been shown that Emule's predictions don't come true and many have pointed out the poor logic behind telling people you are about to sell a large amount before you actually do (you could get better prices if you don't). But Emule remains a tenacious member of the Nxt community. Emule is adamant that he/she is an original Founder who has millions of NXTs to Dump. Or sometimes that they are just a trader out to make a killing. All evidence so far suggests they are just a FUDster but only time will tell. Despite his/her stance and sometimes unbecoming behaviour (i.e. making claims about the sexual orientation of other users mothers), he has become a lovely rogue and pantomime villain of the Nxt Pub threads, earning the nickname Elmo and often receiving a tickle behind the ears when he makes an appearance.

****

Bookmark the Nxt Glossary here >>>>> http://wiki.nxtcrypto.org/wiki/Glossary 

I love it 

[yassin54]

Someone broke the blockchain!  

Code:

[2014-03-26 17:50:47.266] DEBUG: block 0
[2014-03-26 17:50:47.427] DEBUG: Error in block generation thread
[2014-03-26 17:50:50.086] DEBUG: block 5000
[2014-03-26 17:50:53.050] DEBUG: block 10000
[2014-03-26 17:50:55.985] DEBUG: block 15000
[2014-03-26 17:50:56.187] DEBUG: Invalid transaction attachment:
{"alias":"IWE","uri":"SZ"}
[2014-03-26 17:50:56.188] DEBUG: Dropping invalid transaction
[2014-03-26 17:50:56.194] DEBUG: Invalid transaction attachment:
{"alias":"IWA","uri":"SZ"}
[2014-03-26 17:50:56.194] DEBUG: Dropping invalid transaction
[2014-03-26 17:50:56.201] DEBUG: Invalid transaction attachment:
{"alias":"IWD","uri":"SZ"}
[2014-03-26 17:50:56.202] DEBUG: Dropping invalid transaction
[2014-03-26 17:50:56.208] DEBUG: Invalid transaction attachment:
{"alias":"IVX","uri":"SZ"}
[2014-03-26 17:50:56.209] DEBUG: Dropping invalid transaction
[2014-03-26 17:50:56.215] DEBUG: Invalid transaction attachment:
{"alias":"IWB","uri":"SZ"}
[2014-03-26 17:50:56.216] DEBUG: Dropping invalid transaction
[2014-03-26 17:50:56.222] DEBUG: Invalid transaction attachment:
{"alias":"IVZ","uri":"SZ"}
[2014-03-26 17:50:56.222] DEBUG: Dropping invalid transaction
[2014-03-26 17:50:56.228] DEBUG: Invalid transaction attachment:
{"alias":"IWG","uri":"SZ"}
[2014-03-26 17:50:56.230] DEBUG: Dropping invalid transaction

Client continuously rescaning it and balance became mad

mee too
continuously rescaning
why?
bug blockchain?

[Buratino]

i predict 500K dump before the end of the day!

Pessimistic scenario is more realistic. I am afraid that NXT rate will stuck around 4000 satoshi for a very long time (until next NY). Emule may be right in his (her) prediction.
Other strong competitors will be there. NXT can sink into oblivion.

[ChuckOne]

One remark:
Right now, a forger only has one variable (accounts) to tweak until it suits his needs.
Just imagine the bad guy forges the last block in that (1440-X)-row (e.g. accidentally). He now has two variables (accounts, transactions) to tweak.

Yup - (that's why I wrote X rather than 1 for starters) - I think an approach that would require being in control of forging multiple blocks in a row would be the best strategy for defense here.

For example if we included # of transactions until X - 3 then balance of txs until X - 2 then say number of even account numbers used until X - 1 (or some other such ideas spreading perhaps over 10 blocks or more) then might have something with just "too many variables" to be cheated unless you control that vast majority of forging power.

Maybe, there is a misunderstanding here: The variables are in favor of the attacker not against him. More possibilities are not bad. They do not necessarily increase the difficulty.

First of all, transactions of the past are just a constant factor. So, the bad guy simply needs to tweak the current block (the (1440-X)-th block) to get what he want. He he find it easier to simply tweak the account variable, it okay for him. He can simply leave the block empty. The other way round is also possible.

[Daedelus]

i predict 500K dump before the end of the day!

Pessimistic scenario is more realistic. I am afraid that NXT rate will stuck around 4000 satoshi for a very long time (until next NY). Emule may be right in his (her) prediction.
Other strong competitors will be there. NXT can sink into oblivion.

Maybe. Their track record suggests otherwise  but who knows. Even a stopped clock is right twice a day 

[mthcl]

Version 0.4.1 of the math-of-forging paper (now also with a randomization algorithm): http://www.docdroid.net/ahms/forging0-4-1.pdf.html

[ChuckOne]

Version 0.4.1 of the math-of-forging paper (now also with a randomization algorithm): http://www.docdroid.net/ahms/forging0-4-1.pdf.html

Great. Thank you for acknowledging CfB, CIYAM, BloodyRookie and me.

Thank you also for including additional ideas like accounts splitting and randomization.

[salsacz]

It's a month since BCNext left Nxt and started with collecting trains again https://bitcointalk.org/index.php?action=profile;u=14881

[redsn0w]

Goodmorning people  .

[CIYAM]

First of all, transactions of the past are just a constant factor. So, the bad guy simply needs to tweak the current block (the (1440-X)-th block) to get what he want. He he find it easier to simply tweak the account variable, it okay for him. He can simply leave the block empty. The other way round is also possible.

So let's to the heart of the matter - a forger can always decide *not to forge* and we simply cannot stop that (sure the account can be penalised but of course that forger will probably have other accounts so it doesn't really hurt them much if the have divided up their stake amongst many accounts).

We *can't* fix that - all I am trying to stop anyone from being able to "predict their lottery ticket value" but calculating the expected TF results.

By including some other information we can add a small amount of entropy which will make that future prediction impossible so at least no-one can "time the purchase of their ticket" to get an advantage.

Of course when it comes to the block when your ticket is going to "appear" that forger *can* affect the ticket values (for everyone who bought a ticket 1440 blocks ago) so a "nefarious forger" can always *stop you from getting a winning ticket* if they want to (unless you can see a way to prevent that) but at least that doesn't guarantee that they *will* have the winning ticket (the main reason to even try and game it).

[talkingnonstop]

Goodmorning people  .

good evening dude, i am going to sleep right now.
have a good day , hail to all NXT stakeholders.

[ChuckOne]

So let's to the heart of the matter - a forger can always decide *not to forge* and we simply cannot stop that (sure the account can be penalised but of course that forger will probably have other accounts so it doesn't really hurt them much if the have divided up their stake amongst many accounts).

True. They simply forge nonsense and we cannot check that.

By including some other information we can add a small amount of entropy which will make that future prediction impossible so at least no-one can "time the purchase of their ticket" to get an advantage.

Including other information will not help. Excluding will.

If you include information, one can game the system.
If you exclude information, one cannot.

[CIYAM]

It seems that I hadn't paid proper attention about the idea of the random numbers that were being suggested (they are actually hashes of random numbers with the *actual* numbers being delivered later).

I am now starting to warm to the idea (provided that the range of these numbers is large enough - say 64 bit at least).

[etlase3]

It's a month since BCNext left Nxt and started with collecting trains again https://bitcointalk.org/index.php?action=profile;u=14881

Ukigo is not BCNext, he was hosting a wiki and communicating with me about decrits.

[salsacz]

well.. and who are you?

[Come-from-Beyond]

well.. and who are you?

He is the inventor of Decrits concept.