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

[8bitfan]

Ok, sure. Which version of PIVX are you looking for?

v3.0 and higher they have been experiencing a lot of problems. After the implementation of zerocoin protocol.

v2.3.1 and earlier were a lot more stable

Bah, recently I jumped into v3 and I more and more convinced we should proceed with the newer version. v2 is abandoned and no longer maintained (last commit almost 3 months ago).

Anyone against?

This sounds good.  v3 running a lot better now with constant upgrades.

Also having 8bit with zerocoin features would be very cool 

[1714608620]

1714608620

[1714608620]

1714608620

[1714608620]

1714608620

[8-bit-Party]

Yeah, also we can always introduce feature flags for smelly stuff like zerocoin implementation and enable them once they mature. Win-win

[aestrum]

I tried to build masternode, took sources from here: https://github.com/8bit-dev/8bit
But in order to get it running I had to actually edit sources and call dead code that is responsible for reading masternode.conf.
Is it supposed to be like that, or I am missing something?

[Pon13]

sup guys ??

i have two instances of the 8bit wallet running one for staking and one masternode (different data dirs).

i decided to make a second masternode but when i try to start the third instance i get the following error "Unable to bind 0.0.0.0:18888 on this computer. 8bit is probably already running.
Failed to linsten on any port. use -listen=0 if you want this."

If i put -listen=0 the third instance is running without problems. However i dunno what this command (-listen) does and for the masternode you have to have it at 1.

Any suggestions? There are people running 5 - 10 mns at one machine. How you managed to do it after the second (wallet) instance ??

THANKS IN ADVANCE !!

[8bitfan]

Yeah, also we can always introduce feature flags for smelly stuff like zerocoin implementation and enable them once they mature. Win-win

Nice, this makes sense.  Sounds like a good approach

[8bitfan]

I tried to build masternode, took sources from here: https://github.com/8bit-dev/8bit
But in order to get it running I had to actually edit sources and call dead code that is responsible for reading masternode.conf.
Is it supposed to be like that, or I am missing something?

Hello

Yes there are some unusual parts to current codebase, there is currently a major 8bit upgrade under development and soon to be launched. New wallets, new features etc.

If you've got any suggestions or pull requests in the meantime though, I'm sure the community would be happy with the input.

[Marijn]

Hi Guys,

Can somebody help me out with fixing a compiling error i get? I get a few of about the same (just a different number) and then no joy.

chainparams.cpp:143:53: error: ambiguous overload for ‘operator=’ (operand types are ‘std::vector<unsigned char>’ and ‘boost::assign_detail::generic_list<int>’)
         base58Prefixes[PUBKEY_ADDRESS] = list_of(111);

I did all steps that need to be done before building. I am at Ubuntu 17, so maybe some version conflict?

Something to do with boost? I'm at V1.62

Thanks!

[mainconcept]

I tried to build masternode, took sources from here: https://github.com/8bit-dev/8bit
But in order to get it running I had to actually edit sources and call dead code that is responsible for reading masternode.conf.
Is it supposed to be like that, or I am missing something?

Hello

Yes there are some unusual parts to current codebase, there is currently a major 8bit upgrade under development and soon to be launched. New wallets, new features etc.

If you've got any suggestions or pull requests in the meantime though, I'm sure the community would be happy with the input.

So are you doing a upgrade of the current codebase to the PIVX codebase on the current chain? Or do you plan to do a coin swap?

[Marijn]

Hi Guys,

Can somebody help me out with fixing a compiling error i get? I get a few of about the same (just a different number) and then no joy.

chainparams.cpp:143:53: error: ambiguous overload for ‘operator=’ (operand types are ‘std::vector<unsigned char>’ and ‘boost::assign_detail::generic_list<int>’)
         base58Prefixes[PUBKEY_ADDRESS] = list_of(111);

I did all steps that need to be done before building. I am at Ubuntu 17, so maybe some version conflict?

Something to do with boost? I'm at V1.62

Thanks!

Ok, this was a boost version error. I did some copy/paste work in "chainparams.cpp" to fix this.
Now having a darksend.cpp error and trying to fix at at the same manor. Going to "borrow" some code from another git ;-)

[Pon13]

Hi Guys,

Can somebody help me out with fixing a compiling error i get? I get a few of about the same (just a different number) and then no joy.

chainparams.cpp:143:53: error: ambiguous overload for ‘operator=’ (operand types are ‘std::vector<unsigned char>’ and ‘boost::assign_detail::generic_list<int>’)
         base58Prefixes[PUBKEY_ADDRESS] = list_of(111);

I did all steps that need to be done before building. I am at Ubuntu 17, so maybe some version conflict?

Something to do with boost? I'm at V1.62

Thanks!

Ok, this was a boost version error. I did some copy/paste work in "chainparams.cpp" to fix this.
Now having a darksend.cpp error and trying to fix at at the same manor. Going to "borrow" some code from another git ;-)

man do you use the correct git version?? the only thing that needs to be edited in order to compile the wallet is the following:

Most likely, there will be an error in the assembly.
Therefore, you will need to fix ~/8bit/src/rpcrawtransaction.cpp
search for this line
                     const CScriptID& hash = boost::get<const CScriptID&>(address);
It should work after changed to
                       const CScriptID& hash = boost::get<CScriptID>(address);


Here is the complete guide for CLI and GUI. If you make it pat yourself in da back and smoke a spliffy.

Once I wrote for myself the installation instructions, maybe it will come in handy.

1. Setting dependencies:

Code:

sudo apt-get install -y libminiupnpc-dev autoconf automake build-essential libssl-dev libdb++-dev libboost-all-dev libqrencode-dev

1.5 sudo apt-get install git (if you dont have it)

2. Installation secp256k1

Code:

cd ~&&git clone http://www.github.com/bitcoin/secp256k1&&cd  secp256k1&&git checkout a1d5ae1&&./autogen.sh&&./configure&&make&&sudo make install&&cd ..

3. Installing 8bit

Code:

cd ~&&git clone https://github.com/8bit-dev/8bit&&cd 8bit/src&&cp crypto obj/crypto -rR

Most likely, there will be an error in the assembly.
Therefore, you will need to fix ~/8bit/src/rpcrawtransaction.cpp
search for this line
                     const CScriptID& hash = boost::get<const CScriptID&>(address);
It should work after changed to
                       const CScriptID& hash = boost::get<CScriptID>(address);

Code:

make -f makefile.unix&&strip 8bitd&&sudo cp 8bitd /usr/bin

If everything went well and without errors, then you will have a console version of the wallet.
If you need the GUI (ATTENTION IF YOU COMPILED THE CLI VERSION YOU NEED TO RENAME THE 8bit Folder to something else e.g. 8bitCLI and the continue with the procedure below):
1. Setting dependencies:

Code:

sudo apt-get install -y qt5-default qt5-qmake qtbase5-dev-tools qttools5-dev-tools build-essential libboost-dev libboost-system-dev libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev libssl-dev libdb++-dev libminiupnpc-dev

2. Installing 8bit-qt

Code:

cd ~&&git clone https://github.com/8bit-dev/8bit&&cd 8bit/src&&cp crypto obj/crypto -rR

Then again you have to edit the rpcrawtransaction.cpp (as you did for the CLI version) and then compile

Code:

qmake&&make

I install 8bitd on Raspberry Pi 3
8bit-qt install on Linux Mint 18.1

I apologize for the bad english.

[Marijn]

man do you use the correct git version?? the only thing that needs to be edited in order to compile the wallet is the following:

I thankfully used that guide and did use the git source. I think it is due to my fully upgraded Ubuntu version. I had some problems compiling other wallets also due to this.

[Pon13]

man do you use the correct git version?? the only thing that needs to be edited in order to compile the wallet is the following:

I thankfully used that guide and did use the git source. I think it is due to my fully upgraded Ubuntu version. I had some problems compiling other wallets also due to this.

hmmm you should downgrade to 16.4. it works like a charm

[8bitfan]

sup guys ??

i have two instances of the 8bit wallet running one for staking and one masternode (different data dirs).

i decided to make a second masternode but when i try to start the third instance i get the following error "Unable to bind 0.0.0.0:18888 on this computer. 8bit is probably already running.
Failed to linsten on any port. use -listen=0 if you want this."

If i put -listen=0 the third instance is running without problems. However i dunno what this command (-listen) does and for the masternode you have to have it at 1.

Any suggestions? There are people running 5 - 10 mns at one machine. How you managed to do it after the second (wallet) instance ??

THANKS IN ADVANCE !!

hey Pon13, are you using a different port number for each masternode instance?

You can edit the port number for each masternode in the 8bit.conf file.   The following line:

masternodeaddr=0.0.0.0:9999   << this port number needs to be different for each MN

[8bitfan]

sup guys ??

i have two instances of the 8bit wallet running one for staking and one masternode (different data dirs).

i decided to make a second masternode but when i try to start the third instance i get the following error "Unable to bind 0.0.0.0:18888 on this computer. 8bit is probably already running.
Failed to linsten on any port. use -listen=0 if you want this."

If i put -listen=0 the third instance is running without problems. However i dunno what this command (-listen) does and for the masternode you have to have it at 1.

Any suggestions? There are people running 5 - 10 mns at one machine. How you managed to do it after the second (wallet) instance ??

THANKS IN ADVANCE !!

hey Pon13, are you using a different port number for each masternode instance?

You can edit the port number for each masternode in the 8bit.conf file.   The following line:

masternodeaddr=0.0.0.0:9999   << this port number needs to be different for each MN

*also in the .conf file for each masternode you can use the line:

port=9999  << different for each MN

[Marijn]

man do you use the correct git version?? the only thing that needs to be edited in order to compile the wallet is the following:

I thankfully used that guide and did use the git source. I think it is due to my fully upgraded Ubuntu version. I had some problems compiling other wallets also due to this.

hmmm you should downgrade to 16.4. it works like a charm

Maybe you are right, or the wallet needs to be upgraded 
I have multiple masternodes running on 3 different servers already. Downgrading means a lot of work and some downtime.
It would be cheaper for me to just skip 8bit masternode, but I don't like to give up.

I upgraded some files and the daemon is running now. Just no connection yet (connection failures). Don't know if that is my upgraded config or missing something else.
Trying to figure that one out. I will get there somehow 

[Pon13]

sup guys ??

i have two instances of the 8bit wallet running one for staking and one masternode (different data dirs).

i decided to make a second masternode but when i try to start the third instance i get the following error "Unable to bind 0.0.0.0:18888 on this computer. 8bit is probably already running.
Failed to linsten on any port. use -listen=0 if you want this."

If i put -listen=0 the third instance is running without problems. However i dunno what this command (-listen) does and for the masternode you have to have it at 1.

Any suggestions? There are people running 5 - 10 mns at one machine. How you managed to do it after the second (wallet) instance ??

THANKS IN ADVANCE !!

hey Pon13, are you using a different port number for each masternode instance?

You can edit the port number for each masternode in the 8bit.conf file.   The following line:

masternodeaddr=0.0.0.0:9999   << this port number needs to be different for each MN

*also in the .conf file for each masternode you can use the line:

port=9999  << different for each MN

hey man thanks for the reply !! the port command worked perfect !!

[aestrum]

I have 4 masternodes running, but when I issue "masternode count" command, each of them shows different number:
213
230
242
280

Also, my masternodes sometimes are not in the each other lists.

Is there any reliable way to determine if masternode is actually on the network, and will be participating in the payout?

[r8st]

I have 4 masternodes running, but when I issue "masternode count" command, each of them shows different number:
213
230
242
280

Also, my masternodes sometimes are not in the each other lists.

Is there any reliable way to determine if masternode is actually on the network, and will be participating in the payout?

This happens to me too. Sometimes even my mn will be alone in the list of masternodes... but still receive payment. Others have mentioned this phenomena as well so we're not unique.

Best advice I could give you to start would be to fill out an excel sheet or something like it with the balance in each mn at the end of each day. After a few days, you can look at the changes in balances to make sure all of your mns are receiving rewards. Make sure your nodes are fully synced before issuing "masternode start" command... and usually everything is peachy even though the list function is a bit buggy.

If a node goes a few days with no payment I usually issue a "masternode stop" command, followed by a check to make sure the node is fully synced, followed again by the "masternode start" command. Usually this is enough but occassionally the node needs to be restarted.

When I receive the message "Masternode started succesfully"... I estimate the mn does in fact start successfully 99.9% of the time... you can be pretty confident once you receive this message, but it is wise to track it via excel or whatever as well.

As a sidenote, since I started running 8bitd on ubuntu server rather than desktop, I have had very very few errors compared to on desktop. Running 12 currently on one machine with more than enough ram, my processor seems to be the limiting factor.

These issues should be non-existent on the new chain/codebase, I think pivx for instance has a list on the web somewhere of an updated list of active mns, maybe we'll have something like that soon.

[8-bit-Party]

These issues should be non-existent on the new chain/codebase, I think pivx for instance has a list on the web somewhere of an updated list of active mns, maybe we'll have something like that soon.

Yes, we will have similar public ledger.

[bakra]

Yeah, also we can always introduce feature flags for smelly stuff like zerocoin implementation and enable them once they mature. Win-win

I think that will be the best option