Quote from: dbt1033 on April 25, 2015, 03:18:44 PM

Ended up getting masternode 6 up last night on the same aws server...

Was going to set up another 6 at work today but I left the .pem file at home.

On 6 nodes, I probably received a total of 20 stakes. I can't imaging how profitable this will be once we make the switch.

then let's calculate..

every second there will be one block with 0.88 for all masternodes
= 1267 8Bit / day

let's say you have 12 masternodes ( 1344 8Bit ) and there will be 120 masternodes in the network.. ( 13440 8Bit in masternodes, ca 87000 stay in wallets and exchanges? )
so you will get 126.7 8Bit / day = 9% dailiy interest

but if this is really true, then there will be many more nodes.. you alone could afford one more masternode every day..

so let's see how this will behave..

Quote from: Peter80 on April 25, 2015, 03:34:36 PM

Hi,

first of all, Dev, fantastic work!!!

I would like to setup a masternode, but it's the first time an something went wrong.

I got this error:
not capable masternode: Could not connect to 213.47.7.54:9999

I'm using a cable modem with built in router.
The IP is correct, i have checked several times.

I used the Port forwarding function from my router to my local IP 192.168.0.2 and opend 9999 with TCP.
I tested with several Ports (9999, 9990, 9586, 9800...) I also restart the router etc.

For testing i turned Windows Firewall, Avast Antivir and Router Firewall to OFF.
Windows is Ver 8.1 Pro 64bit (--> maybe need 8bit Version Grin

)

This is my config file: (don't understand this rpc things, should i change something there?)
rpcallowip=127.0.0.1
rpcuser=YourUserName
rpcpassword=YourRPCPassword
rpcport=9800
server=1
daemon=1
listen=1
staking=0
port=9999
masternodeaddr=213.47.7.54:9999
masternode=1
masternodeprivkey= "myKey"

Someone an idea?
Thanks for help.

seems to be all correct! ( myKey without quotes! )
maybe your router is the problem.. so your local wallet can not access 213.47.7.54:9999, although the whole internet can...