Are you having trouble with Bter?  If so, have you tried to go to http://bter.com/myaccount/myfunds and hitting the "sync" option for your NXT account?

This has to be solved anyway, two blockchain explorers, with different results.

http://www.mynxt.info/blockexplorer/details.php?action=tx&tx=17232427939066065628

Nexern please what is the issue with your blockchain explorer?

http://87.230.14.1/nxt/nxt.cgi?action=2000&tra=17232427939066065628

thank you

Would you be so kind as to educate me on how using double precision is being cavalier? I have used floating point a lot, even for iterative computations. For a gateway, all user facing operations have a very short length, eg. one maybe two operations. How will errors in the 14th decimal place matter when 1 satoshi is 12 decimal place even for 1000 deposit.

I am all for super precision, so once I understand the actual problem I will do what it takes to make it precise.

Please help me understand the issue. I read https://bt.irlbtc.com/view/13837.0 and nothing in here convinces me that doing a single subtract will change the value of any deposit or withdrawal, down to 1 satoshi.

Also, the gateway code will be run in controlled environments and I will specify compiler, options, etc.

Again, please provide a specific example of precision problem that a gateway doing deposits and withdrawals will run into. What if I used 128bit floating point?

James

exchanges using thier own instance to verify transactions for sure. blockexplorer is currently polling the NRS api and buffers the result
into a local database, therefore the very quick query and response times you see when using the explorer. the new NRS supports now direct
database access, which means blockexplorer can query all data in realtime soon. since the buffering can be skipped, the confirmations
will be always realtime too. atm you see a snapshot from that moment the old api was polled and therefore the confirmation gap but
this doesn't mean the data is not acurate. the confirmation gap is currently filled by an additional cron job refreshing the snapshot from time
to time. if you check this specific transaction later you will see the confirmation increased.

ps: the blockexplorer is special built to run on minimal hardware to handle even millions of records without any greater latency by query.
this means even if the nxt blockchain grows extremly the response time will remain the same. compared to other tools (e.g. php/mysql)
blockexplorer won't break later due to heavy load or terrabyte dbs.

Speak the Devil's name and he shall appear.

Start here: http://en.wikipedia.org/wiki/Floating_point#Accuracy_problems

There is lack of support for people that want to use and implement NXT, that way we miss opportunities.

Apparently implementing NXT is not that straight forward, look at cryptsy, mintpal, atomic-trader, etc… none of them succeed without any help to implement NXT.

We cannot expect mass adoption if above persist, and nobody steps forward to either make some kind of procedure or help people out.

Another remark is that I have the impression interest in NXT is decreasing in favor of new alt-coins/clones.

How can we reestablish interest in NXT?

Announcing a client that almost everyone is going to use.

+ Public giveaway to promote that client. So people can play with the coins they receive with the new client.

But I have a feeling that we have to wait for Nexern.

no need to wait, there are many good clients out now, supporting AE too.
anyway, of course i am adding additional value to nxt soon.