[*] 8BIT [Dark Masternodes][Anon][Roadmap Stage 4]

[8bitproject]

I skipped through the pages since I crashed last night. " I needed some rest "
here is a few things you should know:

If your IP address is not static it will still work with your dynamic address until it changes,
if it does change then you can change it in the conf file and it will work again.

Use coin control to make sure your 112 coins in your node address are not used while
sending coins before the node is up. if your node is up the 112 coins will not be available
to send and break the node. When receiving coins use a different address in the wallet.

The payments coming in now are a percent of the 8% yearly PoS and sometimes
will be very small until block 11500 at which point they will be fixed.

The wallet needs time to connect with all the Masternodes so seeing different lists
in different wallets is normal, eventually if left running all wallets will connect.

Incorrectly configured node will appear in the list but will be kicked out when
it fails verification. Your node will take 5 to 10 minutes to appear in node list.

Your external IP address for conf file can be found by typing this in google search
" What is my IP "

A few community members are helping, I would like to thank everyone who
does.  Please ask your questions in the thread, I still have the 360 seconds limitation
and can not answer PM's quickly.

There is no such thing as a "stupid" question, try to get your answer in the thread,
so everyone can see that answer.

I need to clear my head and move on to stage 4, but will be around to help and
make sure the fork is smooth at block 11500.

* You can send to and receive coins from exchanges, however, after block 11500
you need to make sure the exchange updated the wallet

[racer2012]

I skipped through the pages since I crashed last night. " I needed some rest "
here is a few things you should know:

If your IP address is not static it will still work with your dynamic address until it changes,
if it does change then you can change it in the conf file and it will work again.

Use coin control to make sure your 112 coins in your node address are not used while
sending coins before the node is up. if your node is up the 112 coins will not be available
to send and break the node. When receiving coins use a different address in the wallet.

The payments coming in now are a percent of the 8% yearly PoS and sometimes
will be very small until block 11500 at which point they will be fixed.

The wallet needs time to connect with all the Masternodes so seeing different lists
in different wallets is normal, eventually if left running all wallets will connect.

Incorrectly configured node will appear in the list but will be kicked out when
it fails verification. Your node will take 5 to 10 minutes to appear in node list.

Your external IP address for conf file can be found by typing this in google search
" What is my IP "

A few community members are helping, I would like to thank everyone who
does.  Please ask your questions in the thread, I still have the 360 seconds limitation
and can not answer PM's quickly.

There is no such thing as a "stupid" question, try to get your answer in the thread,
so everyone can see that answer.

I need to clear my head and move on to stage 4, but will be around to help and
make sure the fork is smooth at block 11500.

* You can send to and receive coins from exchanges, however, after block 11500
you need to make sure the exchange updated the wallet

Can some1 create video on how to setup masternode
Please

[8bitproject]

* You can send to and receive coins from exchanges, however, after block 11500
you need to make sure the exchange updated the wallet

you are not going to ask them to update?
you need to send bittrex and the other exchanges a support ticket as the developer.

All exchanges have been informed, but some take longer to update.
I will mark exchanges that confirm update on OP.
At this time there is nothing to worry about. when we get close to
block 11500 make sure you use exchanges that confirmed the update.

[njs811]

Earlier someone said that a MN with the internal ip address 192.168.1.128 will not work. I am curious how this happened, how it can be fixed, and what will happen if it is not fixed.

[8bitproject]

Earlier someone said that a MN with the internal ip address 192.168.1.128 will not work. I am curious how this happened, how it can be fixed, and what will happen if it is not fixed.

You need to find your external IP and replace that 192.168.x.x in the conf file.
What will happen: the node with the internal IP will be kicked out from list.
To find your external IP search google for " What is my IP "

[stackoverflow]

Earlier someone said that a MN with the internal ip address 192.168.1.128 will not work. I am curious how this happened, how it can be fixed, and what will happen if it is not fixed.

The node with local address is broadcasted by your wallet as it can connect to it, but other nodes will reject it after failure to connect to it.

[dbt1033]

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.

[Peter80]

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 )

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.

[M8BWNNRFMNdak68c]

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..

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 )

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...

[Peter80]

[/quote]
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...
[/quote]

ok thanks, at least it's good to know that the config is ok. will try on my second pc if it's working - if not must look at the router.

[M8BWNNRFMNdak68c]

by the way.. i can confirm your port 9800 is working correctly.. the internet can access your rpc.. we also know your password ^^
but your coins are save, as long as you leave rpcallowip=127.0.0.1
we are not allowed to access:

HTTP/1.1 403 Forbidden
Date: Sat, 25 Apr 2015 15:58:14 +0000
Connection: close
Content-Length: 0
Content-Type: application/json
Server: 8bit-json-rpc/v2.0.0.0-g

but you should remove forewarding of 9800 !

[Peter80]

by the way.. i can confirm your port 9800 is working correctly.. the internet can access your rpc.. we also know your password ^^
but your coins are save, as long as you leave rpcallowip=127.0.0.1
we are not allowed to access:

HTTP/1.1 403 Forbidden
Date: Sat, 25 Apr 2015 15:58:14 +0000
Connection: close
Content-Length: 0
Content-Type: application/json
Server: 8bit-json-rpc/v2.0.0.0-g

but you should remove forewarding of 9800 !

thank you!

[Peter80]

by the way.. i can confirm your port 9800 is working correctly.. the internet can access your rpc.. we also know your password ^^
but your coins are save, as long as you leave rpcallowip=127.0.0.1
we are not allowed to access:

HTTP/1.1 403 Forbidden
Date: Sat, 25 Apr 2015 15:58:14 +0000
Connection: close
Content-Length: 0
Content-Type: application/json
Server: 8bit-json-rpc/v2.0.0.0-g

but you should remove forewarding of 9800 !

thank you!

ok, wasn't a good idea to take this pw^^ -> now i think i understand this rpc things

tested all with another pc, same problem with "not capable masternode: Could not connect to"

all ports closed now - but it worked from WAN to LAN as you tested and not in the other direction.

So, should this be rly a problem with the router?

This options i can change on the router, but i think it's ok?
WAN-Sperrung -> Not Active   
IPSec Forward -> Active
PPTP Forward -> Active
Multicast -> Active
UPnP -> Active

Firewall was off for testing.
Both PCs configured with static ip - and on both everything else is running without any problems, so i think it's also not a problem with the windows config?

...so anybody an idea what's wrong with my router?

thanks for help - special this security problem!

[Wintermute420]

What is the meaning of Rank on the Masternode page?

[dbt1033]

by the way.. i can confirm your port 9800 is working correctly.. the internet can access your rpc.. we also know your password ^^
but your coins are save, as long as you leave rpcallowip=127.0.0.1
we are not allowed to access:

HTTP/1.1 403 Forbidden
Date: Sat, 25 Apr 2015 15:58:14 +0000
Connection: close
Content-Length: 0
Content-Type: application/json
Server: 8bit-json-rpc/v2.0.0.0-g

but you should remove forewarding of 9800 !

thank you!

ok, wasn't a good idea to take this pw^^ -> now i think i understand this rpc things

tested all with another pc, same problem with "not capable masternode: Could not connect to"

all ports closed now - but it worked from WAN to LAN as you tested and not in the other direction.

So, should this be rly a problem with the router?

This options i can change on the router, but i think it's ok?
WAN-Sperrung -> Not Active   
IPSec Forward -> Active
PPTP Forward -> Active
Multicast -> Active
UPnP -> Active

Firewall was off for testing.
Both PCs configured with static ip - and on both everything else is running without any problems, so i think it's also not a problem with the windows config?

...so anybody an idea what's wrong with my router?

thanks for help - special this security problem!

I was having the same bullshit problems.

Just get an AWS instance and save yourself the trouble.

[stackoverflow]

What is the meaning of Rank on the Masternode page?

The rank refers to the nodes rank to get the next stake from what i see

[Arie22]

by the way.. i can confirm your port 9800 is working correctly.. the internet can access your rpc.. we also know your password ^^
but your coins are save, as long as you leave rpcallowip=127.0.0.1
we are not allowed to access:

HTTP/1.1 403 Forbidden
Date: Sat, 25 Apr 2015 15:58:14 +0000
Connection: close
Content-Length: 0
Content-Type: application/json
Server: 8bit-json-rpc/v2.0.0.0-g

but you should remove forewarding of 9800 !

thank you!

ok, wasn't a good idea to take this pw^^ -> now i think i understand this rpc things

tested all with another pc, same problem with "not capable masternode: Could not connect to"

all ports closed now - but it worked from WAN to LAN as you tested and not in the other direction.

So, should this be rly a problem with the router?

This options i can change on the router, but i think it's ok?
WAN-Sperrung -> Not Active   
IPSec Forward -> Active
PPTP Forward -> Active
Multicast -> Active
UPnP -> Active

Firewall was off for testing.
Both PCs configured with static ip - and on both everything else is running without any problems, so i think it's also not a problem with the windows config?

...so anybody an idea what's wrong with my router?

thanks for help - special this security problem!

You can check your IP and PORT via http://www.canyouseeme.org/

If success you can start your maternode 

[M8BWNNRFMNdak68c]

...so anybody an idea what's wrong with my router?

thanks for help - special this security problem!

i think you shhould use a service like dyndns..
you would set a name like "8bit.dyndns.org:9999"
this redirects to your ip ( set it up in your router, so you will be reachable after IP change! )

then you define in your windows hosts-file: 8bit.dyndns.org = 127.0.0.1

[racer2012]

Simple guide on how to create a masternode:

Start your 8BIT wallet
Send exactly 112 8BITS to an address in your wallet

Go to Help/Debug/Console
type the following and hit Enter:

Code:

masternode genkey

Copy the result and place that in the 8bit.conf file below:

Code:

rpcallowip=127.0.0.1
rpcuser=YourUserName
rpcpassword=YourRPCPassword
rpcport=any_valid_port EX: 9228
server=1
daemon=1
listen=1
staking=0
port=9999
masternodeaddr=YOUR_IP:9999
masternode=1
masternodeprivkey=KEY GENERATED BY COMMAND masternode genkey

Port 9999 must be open.

Restart your wallet and go back to Help/Debug/Console
Type the following and hit enter:

Code:

masternode start

* Give your Masternode a few minutes, and check if it's up in the Masternode list

how to create multiple masternodes in the same wallet?

You need to run multiple instances of the wallet with different ports.

So the address that's shows up in masternode Gen key must be copied and paste inside 8bit.conf? ??
And where should we sent 112 8bit
To that address from masternode???

[MALCOM X X X]

Sometimes ISP blocking certain PORT, you can try this..

-Download Security kiss tunnell, RUN it.. klick CONNECT..
-Now look on http://www.canyouseeme.org/ that your IP.. you can see PORT on Security kiss app -> change server..
-Put Security kiss tunnell PORT on http://www.canyouseeme.org/ PORT then klick check port..
-If success copy IP and PORT change your 8bit.conf masternodeaddr=YOUR_IP:YOUR_PORT,  restart wallet
-Go to consol type masternode start