More good info. Would you please answer these questions?
After the outgoing server has sent out the randomized NAVcoins to the intended recipient, the incoming server will join together any NAVcoins that have been processed and on the next transaction cycle send it to the outgoing server to replenish the pre-loaded pool of NAVcoins for future transactions.
What is the size of the preloaded pool of NAVcoins?I'll look into the other parts But I can answer the last one.
1. The server admin sets this I have 50K set in my soon to be completed server right now.
2. When your wallet is looking for an anon server to randomly pick from it starts with the list entered in the navcoin.conf file
addanonserver=95.183.52.55:3000
addanonserver=95.183.53.184:3000
addanonserver=95.183.52.28:3000
addanonserver=95.183.52.29:3000
these are the nav devs servers
the wallet rejects servers that do not have enough NAV in the pool for your transaction right now.
the pool is reduced when nav is being sent from outgoing to end receiver. so If I'm processing 15k NAV in other transactions my server will only report 35K in the pool.
As far as I can tell nothing is closed. part of the server uses forever.js to restart processes if they crash just checked that is open source
https://github.com/foreverjs/foreverthe actual code for the wallets and the server script are at
https://github.com/navcoindev