Querying many accounts at once will be slow even if done on the server side, it will be better to have a way to subscribe for notifications when the balance of an account changes. Currently this is not possible with the http API, only with the direct Java API (i.e., you would need to write Java code to talk to the server).

Also not sure what he means by "all of the accounts held by the node" - each node has information about all existing accounts on the blockchain, so it is not a very useful query.

plz send me any coins in testnet 8934589681199444737
thanks guys

you send btc*1 to bob. bob sends BobsBtcToken*1 to you. you go onto the orderbook for BobsBtcTokens and fill a buy order. Nxt appears in your account. Now you find a ltc gateway. Say betty seems the most trustworthy. Fill a sell order for BettysLtcTokens. Receive BettysLtcTokens*X. Send BettysLtcTokens*X to Betty's nxt address with a message containing your ltc address. Wait for ltc to arrive.

It seems overly complicated now but it'll feel natural once it gets rolling and everyone gets used to it. All steps serve their purpose, these extra steps are the cost of decentralization.

I still say trying to tie the fee to some FIAT is the wrong direction.  Ill say it again - a transactions's fee should be tied to its byte size on the blockchain.  So lets say a NXT transfer is 128bytes, and its fee is .1NXT, so then an AM or alias of size 256bytes should cost .2NXT.
But no one likes my idea. 

This proposal will require a bit more code; but for the moment I think a straight .1 NXT for all works, as it will encourage more use for now.

If I read this right - 'No escrow' or atomic completion?
so buyer beware....

OK, this is my cue to update status of community gateways. Keep in mind I am talking about the first step along the path toward fully automated DAC solution. No need to wait for that if we can get a more traditional solution in the meantime.

I have a job offer out to a fulltime dev who will help code my ideas, both crazy and not so crazy. The first task is to create reference code for automated gateways and clients along the lines of my post about this yesterday.

In parallel, I am working with traditional gateway providers to create a federation of gateways that users can choose between. We will create requirements to be part of the gateway and the community will need to help do the due diligence on each of the gateways as I have little expertise in data center security, etc.

NXT community gateway federation requirements:

A) we need source code of the automated gateway functionality, this way the smart guys can make sure that all the error cases are properly handled and if a database is used, that proper database techniques are used, etc. It is expected that all the federation members will work together to create best practices for deposit/withdrawal handling. No more bter funny business!

B) There needs to be an automatically updated balance of Assets issued and a corresponding account that can be checked using blockchain.info, trust but verify. This ensures that there is 100% backing of all the Assets issued into AE and people can trade it without worrying about fractional reserve.

C) There needs to be a publicly posted information about any and all fees charged. There will also be the option of the gateway provider to put up a bond against deposit flight risk. This allows even gateways run by an unknown newbie to have a chance, especially if they put up a bond big enough to cover all their deposits. Any reductions in bond will require enough time for adjustments to be made by holders of gateway's assets. [I need a place to host this information and also someone to keep it updated, maybe nxtcrpto.org?]

D) There needs to be an agreement to exchange gateway assets of the same denomination with the community asset at 1:1, this is something that ripple never achieved and it fragments the trading for all gateways to this day. By pooling all assets for the same thing, it reduces confusion for the user and also creates more liquidity and tighter spreads. Imagine if the highest bid and lowest ask for DOGE was always available within AE!

D) Anything else that is missing?

I cannot stress how important it is that we unite all the Assets for the same crypto, otherwise it will be a giant confusing mess. In ripple right now, anybody can issue anything, but there are no standards or requirements to be able to do this. Buyer beware. I am hopeful that each federation gateway will either start with enough credibility or be able to find a sponsor/partner that will be able to put up a big enough bond to allow for true interchangeability among all Assets for the same thing.

Getting the tech to achieve this is actually not new, having the community that can achieve freely interchangeable Assets among a federation of gateways, that is what is new here.

James