Technically - probably not.
but increasing the number of gateways 3+n where 'n' is 1,2,3,4

At 3+0 with 3providers colluding you risk not detecting
At 3+n you have more opportunity of detecting collusion.
Or accept the risk
Or find another way

Problems starting the 0.8.3...

1) First... using "sh run.sh"

2) Second... using "java -cpmnt/nxt/nxt.jar:/mnt/nxt/lib/*:conf nxt.Nxt"

Any ideas?


EDIT: is Linux, not Windows!

@JL, CfB did you drop the 'numberOfUsers' field from the 'getState' request? It does not seem to appear there any more.. If not, what am I making wrong?

1 - numberOfPolls - 0<class 'int'>
2 - totalEffectiveBalance - 99482635500<class 'int'>
3 - maxMemory - 954728448<class 'int'>
4 - numberOfTrades - 0<class 'int'>
5 - version - 0.8.3<class 'str'>
6 - numberOfBlocks - 78803<class 'int'>
7 - availableProcessors - 4<class 'int'>
8 - freeMemory - 296162080<class 'int'>
9 - lastBlockchainFeeder - node1.nxtbase.com<class 'str'>
10 - numberOfOrders - 0<class 'int'>
11 - numberOfAssets - 0<class 'int'>
12 - cumulativeDifficulty - 2444760512653829<class 'str'>
13 - numberOfUnlockedAccounts - 0<class 'int'>
14 - numberOfAliases - 63141<class 'int'>
15 - numberOfVotes - 0<class 'int'>
16 - numberOfTransactions - 136664<class 'int'>
17 - totalMemory - 643301376<class 'int'>
18 - numberOfPeers - 180<class 'int'>
19 - time - 8463865<class 'int'>
20 - numberOfAccounts - 25927<class 'int'>
21 - lastBlock - 10042636691406560440<class 'str'>



Also,  - sorry to bother you with this - I am having a bit of a hard time switching over from GET to POST


On localhost - http://localhost:7876 - I can assemble the requests simply with POST instead of GET
 
        self.req = Request( method='GET', url = sessUrl, params = {"requestType" : "getState"  })

        self.req = Request( method='POST', url = sessUrl, params = {"requestType" : "getState"  })

And I get correct json() response object. On https://holms.cloudapp.net:6875/ I get the old javascript access, but I can't connect with python requests, because I haven't hit the proper port/scheme combe yet apparently.

Also, when I use POST, on localhost it does not seem to require 'auth', 'data', 'headers' - is this maybe needed when using a remote connection??

Please drop me a hint which scheme/port combo I have to use for the testnet and my raspi - I don't seem to be getting ahead there

what is running on what port

6874
6875
6876


thanks,
l8orre

Use this :

I work on a model for that.

Have you posted results with the penalty model? I may have missed them. Could you point me to them?


So, it will lead to a split network and that might open doors for an even bigger attack. Splitting the network into smaller and smaller chunks. Until new nodes only become part of a little branch of the DAG.

I need to go now.

for me when I say fairness I mean this:

100 Nxt account is forging every day not every 10 year


aprox 1,44 Blocs per day. 100 Nxt account is forging every day. receives fees in proportion to their funds every day!!!

1.000.000.000 Nxt Coin
1.000.000 Nxt Coin per pool (share fee group)
30.000 Nodes participate in forging. if there are only 30 accounts linked per pool (share fee group)

this means;

Extremely decentralized network (in the exemple 30.000 Nodes) and therefore very secure network
Small accounts motivated to participate in forging (In the exemple 100 Nxt account is forging every day not every 10 year)
rich and poor have the same chance to forge because everybody forge everyday!!!!

igmaca, please. we talk about security of nxt. if you want to talk about fairness, ok. but that has nothing to do with the change and implementation of TF right now.

I dropped this field because it has nothing to do with the server state. It is very specific to the NRS client UI only and represents the number of its user sessions. But it does not reflect users using clients that connect through the http API, or through the Java API.

As for the status of testnet and holms.cloudapp.net, CfB should know, I don't work on that.