Search content
Sort by
Showing 20 of 35 results by ricot
the site relies on client-side javascript being executed correctly... and it seems to not do any checks on the server side. so someone seems to have not taken web design 101.
I just gave myself a balance of 123.456 and there are others with way higher balances, would be really cool if it paid.
I just gave myself a balance of 123.456 and there are others with way higher balances, would be really cool if it paid.
they will probably see you didn't make high scores and deny your payment
Probably...
But it's also relatively simple to send a full, valid, and plausible history of a game that goes to 16384 because they don't transmit the seed for the random number generator, so you basically have free choice of placing the next tile. And even if they would transmit it, you could still calculate everything in advance and then choose the best strategy to have a high chance on 16384.
Also, if you just want to rely on AI without modifying the code on the site, you can easily get 8192 in a few seconds, if you're lucky also 16384 after a few tries.
So it remains: Never gonna work, best not waste time, there are websites with much fewer ads where you can play 2048 :p
[edit]
there are tons of strategies for 2048, google is your friend.
the site relies on client-side javascript being executed correctly... and it seems to not do any checks on the server side. so someone seems to have not taken web design 101.
I just gave myself a balance of 123.456 and there are others with way higher balances, would be really cool if it paid.
I just gave myself a balance of 123.456 and there are others with way higher balances, would be really cool if it paid.
We'll see a fork soon, some nodes run old NRS without AM support...
Could we please have an announcement on nxtcrypto.org that sais that an update is mandatory by ehm, tomorrow, and what version you need to have?
Otherwise there will be some very confused people
[edit]
Just checked:
You need to run at least NRS v0.5.4e from block 40,000 onwards!
Besides the automatic error correction, there are other advantages like branding (everyone can now see that it's an NXT address, even if they don't know, what exactly NXT is ), an obvious grouping that helps a lot with readability, and you just can't hit a wrong account number, practically.
), an obvious grouping that helps a lot with readability, and you just can't hit a wrong account number, practically.thx, ricot,
ok, understood. usefull for users typing in account numbers but this doesn't answer my question.
this doesn't help to prevent sending funds to hiberNXT, or does it and if, could you please explain how?
as said, i am currently on this, therefore i would like to understand the whole procedure.
from what i see the main problem is to copy or even type a number to send funds to
which is not the intended number and therefore the funds are lost in hiberNXT.
is this what we are talking about?
ok, understood. usefull for users typing in account numbers but this doesn't answer my question.
this doesn't help to prevent sending funds to hiberNXT, or does it and if, could you please explain how?
as said, i am currently on this, therefore i would like to understand the whole procedure.
from what i see the main problem is to copy or even type a number to send funds to
which is not the intended number and therefore the funds are lost in hiberNXT.
is this what we are talking about?
Well, the chance that, by randomly typing that new kind of identifier, you get to a valid account is 1 in 2 million. So money sent to the wrong address because a cat walked over my keyboard should be dealt with.
The only other option to send it to an unknown account is if someone logs into an account, gets the identifier from there and then looses his password. (Or he mistyped his password on the first try). This you can only avoid by making sure that the password is correct. That's a pure UI thing in the client and shouldn't influence account numbers.
So if someone logs into an account, and gives you the new identifier, it's very very hard for you to send it to another account.
nxt system should have a validation function to verify the account is available.
e.g:
acct: 209832084023840384023
MD5 & SHA Checksum: DfwSgeH
so the new account: DfwSgeH-209832084023840384023
Check the MD5 or SHA to verify the account available..
thanks for this example coolfish,
could you explain further please how this checksum approach can verify account available?
acct: 209832084023840384023
MD5 & SHA Checksum: DfwSgeH // from MD5("accountid")
so the new account: DfwSgeH-209832084023840384023 // from substr(MD5("accountid"),6)+ "- accountid"
//substr(MD5("209832084023840384023"),6)=="DfwSgeH"
if( substr(MD5("209832084023840384023"),6)==substr("DfwSgeH-209832084023840384023",6) ) it is available..
else unavailable.
Each new account is password and userid combination : password-userid
Please see my thread about that in the other forum: https://forums.nxtcrypto.org/viewtopic.php?f=17&t=524
We can do a lot better than merely detecting if the user made an error. With the method presented there, we can correct what the user typed. - That's 2nd gen. :p
I was asked what an encryption algo should be used in Arbitrary Messages. It's up to u. But u could use https://nextcoin.org/index.php/topic,727.0.html, it's quite simple.
What's current encryption method of AM ? Exactly as written here? https://nextcoin.org/index.php/topic,727.0.html
AM encrypts nothing. It's just a transport of raw bytes.
I'd prefer sticking with curve25519 for messages.
The public keys are already in the protocol, so you don't need to transamit new ones, it's save, it's easy because you have all the dependencies already there, and it fits the problem perfectly...
I just posted a proposal to fix the account number typo-problem over at the official forums:
https://forums.nxtcrypto.org/viewtopic.php?f=17&t=524 <- making NXT account numbers awesome!
What do you think about that?
https://forums.nxtcrypto.org/viewtopic.php?f=17&t=524 <- making NXT account numbers awesome!
What do you think about that?
Nice idea. Didn't CfB (or someone else?) mumbled something about "in the future we can make great things with account numbers" which would mean, a big adoption rate of your idea would interfere with this "great things"? Damn, can't find the post... and no clue what it meant...
I just read the post, that such a system should be done on client side. So I designed mine to be client-side and not interfere with the NXT protocol itself.
Why do some transactions, which are a week old, have only 3 confirmations (other 400, and other 2000)? And how many confirmations are needed to be 'safe'?
This for example:
http://87.230.14.1/nxt/nxt.cgi?action=2000&tra=9128967358451728434 (from dgex to an user #account)
That is just an error in displaying it.
You can click the "next block" link and see that there are a lot of next blocks, that is, a lot of confirmations.
10 confirmations is generally considered safe.
This might be a stupid question but...is there a way to tell how much NXT there is running among the online nodes and how much NXT in transaction fees is actually circulating? I am trying to figure out how much my NXT will forge for me and although I don't have millions of it I was looking forward to SOME kind of return. I have been funded for a little over an hour I would say and I know I need to wait longer but I would like to at least get an idea to I know what kind of return to expect.
Thanks to anyone who can help edumacate me!
Thanks to anyone who can help edumacate me!
The network is currently generating some 700ish blocks per day, out of 1440 which it would, if all accounts forged. So the forging amount should be somewhere in the range of 50%, i.e. 500M NXT.
Meaning, approx., with 1M you would generate every 500th block, so a little more than 1 per day on average.
[edit]
New accounts can start forging 1440 blocks after the first transaction to that account.
About a third of the blocks have fees, and the fees are usually single-digit.
So when you generate a block do you take ALL of the transaction fees? And when you say single digit, do you mean that, according to the above scenario, the person with 1M NXT will forge less than 10 NXT in transaction fees daily IFF he hits a block with transaction fees at all? That sounds...pretty brutal.
Yep, that's what it is...
You can get a lot of such statistics here: http://87.230.14.1/nxt/nxt.cgi?action=40
This might be a stupid question but...is there a way to tell how much NXT there is running among the online nodes and how much NXT in transaction fees is actually circulating? I am trying to figure out how much my NXT will forge for me and although I don't have millions of it I was looking forward to SOME kind of return. I have been funded for a little over an hour I would say and I know I need to wait longer but I would like to at least get an idea to I know what kind of return to expect.
Thanks to anyone who can help edumacate me!
Thanks to anyone who can help edumacate me!
The network is currently generating some 700ish blocks per day, out of 1440 which it would, if all accounts forged. So the forging amount should be somewhere in the range of 50%, i.e. 500M NXT.
Meaning, approx., with 1M you would generate every 500th block, so a little more than 1 per day on average.
[edit]
New accounts can start forging 1440 blocks after the first transaction to that account.
About a third of the blocks have fees, and the fees are usually single-digit.
I just posted a proposal to fix the account number typo-problem over at the official forums:
https://forums.nxtcrypto.org/viewtopic.php?f=17&t=524 <- making NXT account numbers awesome!
What do you think about that?
https://forums.nxtcrypto.org/viewtopic.php?f=17&t=524 <- making NXT account numbers awesome!
What do you think about that?
What web.xml options add most to stability of NXT server? The stability problems could simply be from suboptimal web.xml settings.
Does the 0.5.3 install use the most stable options in web.xml?
Are there any other files that need to be tweaked?
I am thinking that a lot of the problems in the field could be related to having a wrong set of settings. We are so close to a stable NXT server. I updated my peers list and now it is not going brain dead. Still need more time, but looking good so far.
The only thing that was changed was the list of peers, but I remember seeing a bunch of different tweaks. Has anybody tested the effect of the different tweaks on NXT server stability. So much work has been put into NXT, it would be a shame if a new NXT'er gets a bad experience due to suboptimal settings.
James
Does the 0.5.3 install use the most stable options in web.xml?
Are there any other files that need to be tweaked?
I am thinking that a lot of the problems in the field could be related to having a wrong set of settings. We are so close to a stable NXT server. I updated my peers list and now it is not going brain dead. Still need more time, but looking good so far.
The only thing that was changed was the list of peers, but I remember seeing a bunch of different tweaks. Has anybody tested the effect of the different tweaks on NXT server stability. So much work has been put into NXT, it would be a shame if a new NXT'er gets a bad experience due to suboptimal settings.
James
The problems we have been seeing were mostly due to one specific type of attack combined with a ddos. These attacks seem to have stopped now that they don't have the "desired" effect anymore.
The parameters are fine as they are, no need to adjust them. As are the peers, as soon as you see one peer, it will send you all it's other peers and you're good to go
I am using wesleyh's MaxNXT so not sure how to refresh browser in this context. I click lock and login again, but all the same orphans are there.
I can redownload the entire block chain, that is one option and it fixes it for a few hours, then goes bad again. At least it did the first time. I will do it again and see what happens
James
I can redownload the entire block chain, that is one option and it fixes it for a few hours, then goes bad again. At least it did the first time. I will do it again and see what happens
James
What's that? Why aren't you using the official client?
Well, if it's based on the official client before 0.5.3 (very likely), then you still have that bug...
Solution: Get the official client
My understanding is that MacNXT embeds the official client, it says it is using 0.5.3
All caught up:
36420 14571285356259793594 January 9, 2014 3:16:56 AM GMT+02:00
5 500'000 + 13 691 B
2 15607836971861154475 188 %
The problem seems to happen after a few hours. I did "update peers" before this redownload of blockchain, so I am hoping for better stability.
James
P.S. I did not change anything from default installation other than Update peers
Ah, ok, found a thread about it in some russian forum
Yes, it's basically just displaying a browser window in a different frame, so unless you refresh that browser window, it won't show correct results...
you can try apple+r, maybe that works, depends on how he implemented it.
I am using wesleyh's MaxNXT so not sure how to refresh browser in this context. I click lock and login again, but all the same orphans are there.
I can redownload the entire block chain, that is one option and it fixes it for a few hours, then goes bad again. At least it did the first time. I will do it again and see what happens
James
I can redownload the entire block chain, that is one option and it fixes it for a few hours, then goes bad again. At least it did the first time. I will do it again and see what happens
James
What's that? Why aren't you using the official client?
Well, if it's based on the official client before 0.5.3 (very likely), then you still have that bug...
Solution: Get the official client
There's a thread in this forum about bugs in the code release. After my client had been attacked, I analyzed, what exactly happened and figured out, how the attacker managed to get the clients to basically crash. JLP and CfB fixed that now mostly by 0.5.3, the only thing that is left is the actual browser page. So when you see negative blocks, just refresh the tab in your browser and everything will look normal again. On the server side (communicating with other NXT clients) the server now behaves normally, even if you don't refresh your browser window.
If you want to see what kind of bugs we're finding and that are getting fixed, jump over to https://bitcointalk.org/index.php?topic=397183.0
If you want to see what kind of bugs we're finding and that are getting fixed, jump over to https://bitcointalk.org/index.php?topic=397183.0
0.5.3 been running since released, so far so good. If it's still running OK in the morning that would a new record for me. Can't wait to find out.
Running 0.5.3 via NxtMac, on bad branch?
36406 14571285356259793594 January 9, 2014 2:27:28 AM GMT+02:00
2 0 + 3 305 B
2 5313834224092465353 74.3 %
2901 orphans, 8651 unconfirmed transactions
See if refreshing your browser window helps...
Nxt full source code (decompiled 0.5.2).
https://github.com/slothbag/nxt-decompiled
donations: 6683387465452189666
https://github.com/slothbag/nxt-decompiled
donations: 6683387465452189666
Updated to 0.5.3
or: go to google, search for "java decompiler", click the first hit, download the program, open the Nxt.class file that is in the NXT-client download
Do we know how to make the NXT server more stable. As it is each time it hangs, for personal use it is annoying, but not that big of a deal. Unless you are racing to the airport and can't send NXT!
What I'd like to know, what developers doing about this? Because if I know they are working on it, I can be patient, but I find it worrying that a few times this problem was bought up, it was simply brushed off as not important, or even nonexistent.
New features are important, some of them I'm very much looking forward to, but these stability issues absolutely should take priority.
There's a thread in this forum about bugs in the code release. After my client had been attacked, I analyzed, what exactly happened and figured out, how the attacker managed to get the clients to basically crash. JLP and CfB fixed that now mostly by 0.5.3, the only thing that is left is the actual browser page. So when you see negative blocks, just refresh the tab in your browser and everything will look normal again. On the server side (communicating with other NXT clients) the server now behaves normally, even if you don't refresh your browser window.
If you want to see what kind of bugs we're finding and that are getting fixed, jump over to https://bitcointalk.org/index.php?topic=397183.0
Re: Anon136's NXT Giveaway Thread (weighted by forum notoriety)
Hi,
trying to build some stuff using the (slightly undocumented) client API and in need of some NXT to do some test transactions...
My buy in is stuck between dgex and me, so a little help until that arrives would be very much appreciated!
9808033577554903596
Thanks!
trying to build some stuff using the (slightly undocumented
) client API and in need of some NXT to do some test transactions...My buy in is stuck between dgex and me, so a little help until that arrives would be very much appreciated!
9808033577554903596
Thanks!