Organisation in the french community
Avis à toute la communauté francophone de NXT, je lance l'idée d'un comité francophone pour NXT (NXT French comity and fund). Je vous propose de participer au débat et la discussion sur nextcoin.org : https://nextcoin.org/index.php/topic,4492.0.html
Toutes les bonnes volontés et idées sont bienvenues.
For the english speakers : I want to have a discussion with the french speaking community of NXT (France, Belgium, Switzerland, Canada, french Africa, etc.). I propose to make a comity and a NXT fund to :
- have referents people for the french media ;
- help the french speaking project (marketing, stores, economics project, etc.) ;
- communicate the french projects to the world community.
Topic: NXT :: descendant of Bitcoin - Updated Information - page 220. (Read 2761645 times)
isnt there an chat box for traders on nxt?
Anyway. The generationSignature does not depend on the content.
The forging queue does depend on the generationSignature and therefore does not depend on the content of the blocks as well.
So, the only why of gaming the system is to create accounts that is a legitimate forger in the future.
Because the probability of forging decreases when splitting accounts, that might seems highly unlikely.
The forging queue does depend on the generationSignature and therefore does not depend on the content of the blocks as well.
So, the only why of gaming the system is to create accounts that is a legitimate forger in the future.
Because the probability of forging decreases when splitting accounts, that might seems highly unlikely.
You were talking about the Generation signature of previous block.
Not the next one.
Not the next one.
Ok
what is a panicsell on bter??
This might explain that panicsell: http://www.reddit.com/r/Bitcoin/comments/20znt2/the_news_about_china_banning_bitcoin_is_false/
Generation signature of previous block and public key of the account that attempts to forged this block.
FIFY?
We assume that current block is not generated yet and millions of other accounts r trying to generate it.
You were talking about the Generation signature of previous block.
Not the next one.
Probability of that is very-very small. But, anyhow, the number of blocks generated by this 50% account will be strongly reduced, so this would encourage splitting.
Yes - so I think what are looking for is some sort of balance between "encouraging account splitting" and "how much advantage that would give you" whilst at the same time having as much "randomness" as we can get.
Generation signature of previous block and public key of the account that attempts to forged this block.
FIFY?
We assume that current block is not generated yet and millions of other accounts r trying to generate it.
Just a few more days until I come back. Is there anyone willing to pay the money for NXT.org?
I canceled 7 domains regarding the Nxt-Ecosystem. After I come back I will concentrate on quality work. Because this is what Nxt needs right now. So please respond to the question above.
Also I want to redirect NXTarea.com to http://mynxt.org/, Mario is that okay for you? After a few months I would also cancel this domain then, at this point the users should know that mynxt.org is the new landing page.
wesleyh, I'm not following everything right now. But you mentioned something like client-side-verification at http://nxtra.org/nxt-client-trustless/ . Is that also possible for tipNXT.com (not working right now, because I don't have a server for the client)?
So that someone can type in the wallet password to send the money, but it won't get send to the server. Sure there need to be HTTPS then. But will this makes tipNXT 100% secure?
What if someone hack the server and change the code. Is it possible to create a hash or checksum (with php and crojobs!) of the critical .php files and upload them somewhere on an external site?
I canceled 7 domains regarding the Nxt-Ecosystem. After I come back I will concentrate on quality work. Because this is what Nxt needs right now. So please respond to the question above.
Also I want to redirect NXTarea.com to http://mynxt.org/, Mario is that okay for you?
After a few months I would also cancel this domain then, at this point the users should know that mynxt.org is the new landing page. wesleyh, I'm not following everything right now. But you mentioned something like client-side-verification at http://nxtra.org/nxt-client-trustless/ . Is that also possible for tipNXT.com (not working right now, because I don't have a server for the client)?
So that someone can type in the wallet password to send the money, but it won't get send to the server. Sure there need to be HTTPS then. But will this makes tipNXT 100% secure?
What if someone hack the server and change the code. Is it possible to create a hash or checksum (with php and crojobs!) of the critical .php files and upload them somewhere on an external site?
Looking forward to having you back Passion_ltc definitely miss your web projects, they were all good!
Thanks.
I hope I can achieve something regarding NXT.org! Generation signature of previous block and public key of the account that attempts to forged this block.
FIFY?
there is 1 really solid solution that you arnt going to want to hear
What is it?
Let me guess, proof of work?
Not sure. The next forging queue (that one 100 blocks in the future when each of the 100 forgers forge) might not favor our 50% account.
Probability of that is very-very small. But, anyhow, the number of blocks generated by this 50% account will be strongly reduced, so this would encourage splitting. This is, essentially, about breaking the cryptography, right?
No - not breaking cryptography - just trying to work out the right balance between "predicting the next forger" and "knowing 100% the next forger" (if you can predict say 2 or 3 then you broadcast your tx to those and you should get an almost instant result but if there is "very little doubt" about who is next then apart from making it easier to *attack* the next node you have a problem with getting "random" things like "tickets for a lottery").
What does it depend on then?
Generation signature of previous block and public key of the account that attempts to forge this block.
Are saying you have basically achieved a way to do trustless, peer to peer cross asset trading?
Yes - I am.
+1 for understatement
I do not see, why penalty worsens the situation when trying out 100000000000000000000000000 combinations of raw transactions and potential blocks?
Why does one need "100000000000000000000000000 combinations of raw transactions"? Block generation signature doesn't depend on content of the block.
What does it depend on then?
Why does one need "100000000000000000000000000 combinations of raw transactions"? Block generation signature doesn't depend on content of the block.
Exactly - this seems to have been misunderstood.
But I still don't understand, what advantage the attacker obtains by creating these smaller accounts? Why not just sit on his big account and wait?
Creating blocks in a row is the major threat, if I understand it correctly.
The point is that an attacker might find a clever combination (trying enough of them out) to control a large enough row.
Probably, this could be beaten by introducing some extra randomness (e.g., take some quantity that the attacker does not control as a seed, etc.).
1) each block has its own forging queue
2) the network draws from the queue until it is depleted and creates a new one
3) the network considers all accounts of the queue as equally good
Then, if we decide on all queue at once, the algorithm should be changed, because this way you'll not obtain the "correct" forging probabilities (all ki's are different, right?). Think of a situation when there is an account with 50% of all NXT, and limit=100. Normally this account would forge every second block, but under this approach, it will only forge every 100th.2) the network draws from the queue until it is depleted and creates a new one
3) the network considers all accounts of the queue as equally good
Quote
Do you mean 2) or 3) ?
2Not sure. The next forging queue (that one 100 blocks in the future when each of the 100 forgers forge) might not favor our 50% account.
I do not see, why penalty worsens the situation when trying out 100000000000000000000000000 combinations of raw transactions and potential blocks?
Why does one need "100000000000000000000000000 combinations of raw transactions"? Block generation signature doesn't depend on content of the block.
Jump to: