Pages:
Author

Topic: [*] 8BIT [Dark Masternodes][Anon][Roadmap Stage 4] - page 48. (Read 379550 times)

newbie
Activity: 41
Merit: 0
Yesterday while setupping my vps I made this (I take part of the text from an old Post here but there was some errors). It was was written very quickly sorry for the Grammar error but the code works perfectly. Feel free to take, repost and modify it

....

Thanks for putting this together John. I am getting a hang up however on building 8-bit, following your instructions. I am on ubuntu 16.04, getting the following error during the build:

... /usr/local/include -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -Ibuild -Ibuild -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o build/bitcoin.o src/qt/bitcoin.cpp
In file included from src/qt/walletmodel.h:9:0,
                 from src/qt/bitcoin.cpp:9:
src/instantx.h:34:1: error: reference to ‘int64_t’ is ambiguous
 int64_t CreateNewLock(CTransaction tx);
 ^~~~~~~
...

I get hundreds of these "int64_t is ambiguous" errors, and the build fails.

Did this issue arise for you?

Seems the only solution is to go through and append "::" to every instance of int64_t declaration in the code.

I have tried this, but screwed something up, ended up wasting hours of time. Any help much appreciated.

mmm i don't know, i tried now to reinstall all on a fresh droplet (Ubuntu 16.04.3 64bit) only with the command of the post and it worked, except for the command 'apt-get update' and 'apt-get upgrade' missing, that i added now. Sorry, maybe the community here could be more helpfull
full member
Activity: 179
Merit: 100
Yesterday while setupping my vps I made this (I take part of the text from an old Post here but there was some errors). It was was written very quickly sorry for the Grammar error but the code works perfectly. Feel free to take, repost and modify it

....

Thanks for putting this together John. I am getting a hang up however on building 8-bit, following your instructions. I am on ubuntu 16.04, getting the following error during the build:

... /usr/local/include -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -Ibuild -Ibuild -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o build/bitcoin.o src/qt/bitcoin.cpp
In file included from src/qt/walletmodel.h:9:0,
                 from src/qt/bitcoin.cpp:9:
src/instantx.h:34:1: error: reference to ‘int64_t’ is ambiguous
 int64_t CreateNewLock(CTransaction tx);
 ^~~~~~~
...

I get hundreds of these "int64_t is ambiguous" errors, and the build fails.

Did this issue arise for you?

Seems the only solution is to go through and append "::" to every instance of int64_t declaration in the code.

I have tried this, but screwed something up, ended up wasting hours of time. Any help much appreciated.
full member
Activity: 179
Merit: 100
Hello, I have just arrived. The block explorer & website will return this evening (UTC), I am syncing my nodes finally.


Alright now we're talkin'
newbie
Activity: 63
Merit: 0
during the transaction of 112 coin to myself i have a fee of 0.0001, so i need to send myself 112.0001 right? the masternode started sucessfully with only 112 but i don't know if does it really works...

I think you should exactly send 112 coins and paying the fee from the wallet you are sending.
Try to send exactly 112 coins, then probably a pop up window will show up for the option of paying the fee from the sender wallet.
newbie
Activity: 41
Merit: 0
during the transaction of 112 coin to myself i have a fee of 0.0001, so i need to send myself 112.0001 right? the masternode started sucessfully with only 112 but i don't know if does it really works...
newbie
Activity: 41
Merit: 0
Hello, can someone share how many masternodes are online and how many coins are delivered as reward to each masternode in a day?
And also is it possible to have a cold windows wallet to get the rewards while using remote linux vps?

I think that the cold wallet is not possible, i saw time ago a post in this forum that said that there was no mention of a masternode.conf file in the source of the wallet. For the other questions idk
newbie
Activity: 63
Merit: 0
Hello, can someone share how many masternodes are online and how many coins are delivered as reward to each masternode in a day?
And also is it possible to have a cold windows wallet to get the rewards while using remote linux vps?
newbie
Activity: 41
Merit: 0
Here is the chain syncronized (using ubuntu the wallet works) https://mega.nz/#!m0423Jha!my3ZTm6Qh9HMQTwsFEmMiGJpxCtFXxcxMFsa463PTYg
legendary
Activity: 1036
Merit: 1000
8b 16b DEMOSCENE FTW
Hello, I have just arrived. The block explorer & website will return this evening (UTC), I am syncing my nodes finally.
newbie
Activity: 41
Merit: 0
Yesterday while setupping my vps I made this (I take part of the text from an old Post here but there was some errors). It was was written very quickly sorry for the Grammar error but the code works perfectly. Feel free to take, repost and modify it

I'm still syncronizing the wallet but if no one will upload the chain in the meantime I'll do

 GUIDE for Linux wallet setup 8BIT (tested on Ubuntu 16.04.3 64bit)
1. Setting dependencies:----------------------------------------------------------
Code:
apt-get update
apt-get upgrade
sudo apt-get install  nano -y libminiupnpc-dev autoconf automake build-essential libssl-dev libdb++-dev libboost-all-dev libqrencode-dev
apt-get update
apt-get upgrade
2. Installation secp256k1:----------------------------------------------------------
Code:
cd ~&&git clone http://www.github.com/bitcoin-core/secp256k1&&cd  secp256k1&&git checkout a1d5ae1&&./autogen.sh&&./configure&&make&&sudo make install&&cd ..
cp ../usr/local/lib/[libsecp256k1]* ../usr/lib
(optional 2.b Make swap to build the 8bit wallet-if you have less than 1gb ram)----------------------------------------------------------
Code:
sudo fallocate -l 1G /swapfile&&sudo chmod 600 /swapfile&&sudo mkswap /swapfile&&sudo swapon /swapfile
(the swap is only temporary after the reboot it will disappear, but if you want to know more about it:
https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-16-04  )
3. Installing 8bit----------------------------------------------------------
Code:
cd ~&&git clone https://github.com/8bit-dev/8bit&&cd 8bit/src&&cp crypto obj/crypto -rR
(optional 3.b Fix an error in the code)----------------------------------------------------------
Most likely, there will be an error in the assembly.Therefore, you will need to fix ~/8bit/src/rpcrawtransaction.cpp
Code:
nano ~/8bit/src/rpcrawtransaction.cpp
    search for this line
                     const CScriptID& hash = boost::get(address);
    It should work after changed to
                       const CScriptID& hash = boost::get(address);
[CTRL+O to save CTRL+X to exit]
3.c BUILD--------------------------------------------------------------------------------------------------
        (only console interface)
Code:
make -f makefile.unix&&strip 8bitd&&sudo cp 8bitd /usr/bin
             (GUI interface)
Code:
qmake&&make

_______________________COMMON ERRORS and FIX____________________________
https://bitcointalksearch.org/topic/m.20960275
________________________________________________________________________

--------------------------------------------------------------------------------------------------
Now you can start your wallet with the command " 8bitd " and execute debug command with " 8bitd -cli "
Example: " 8bitd -cli stop "        to stop the wallet
(It will give you an error because you conf file is not configured so continue the guide to configure it)
4. Configure the conf file
Code:
cd ../..&&nano ./.8bit/8bit.conf
Now paste and change the field user(not important), pw(not important), port:
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
[CTRL+O to save CTRL+X to exit]
--------------------------------------------------------------------------
Now you can start your wallet with the command above " 8bitd ", check the actual block height at https://www.cryptopia.co.nz/CoinInfo/?coin=8BIT
and with "8bitd -cli getinfo" check your, and wait the sync, you need to reach the same block as on cryptopia.
(optional set the firewall)
Code:
apt-get install ufw
ufw allow ssh/tcp&&ufw allow 9999/tcp&&ufw enable
--------------------------------------------------------------------------
                    CREDITS
my BTC wallet if you want to donate 3D6RKbFv2G78CYvrGZzFvpdUJgiGSVhod7
hero member
Activity: 2114
Merit: 619
After two days of failed attempts on linux, Today I have managed to configure several masternodes in Ubuntu 16.04, debian jessie gave me problems to do it, applying the same steps, and this thanks to the patch that shared Drays several weeks ago
legendary
Activity: 1778
Merit: 1000
Yes, most probably the most synchronisation problems come from people using wallet on Windows.

As I have wrote many-many times here in the thread - I do not recommend using Windows wallet with this specific coin! Use Ubuntu on virtual machine on your PC, or use VPS.
I used Win wallet back then, but abandoned it, as it caused too many issues. It seems to be not able to handle orphans easily, and 8bit chain is full of orphans.

Regarding one more snapshot.. well I think there is no big sense in producing snapshots every day, if people cannot sync further than the snapshot itself.
Folks, move to Linux first , then we'll see if snapshots are needed or not Smiley

Confirmed Drays the problem is in windows, I went to ubuntu. LOL...

So how easy is this to do for the average person who is used to just using windows wallets?

How can people with windows wallet swap to Ubuntu?

Is there any guide somewhere?
It is not fair. The Dev team needs to sort out windows wallet, so that 8bit can have wider adoption
full member
Activity: 394
Merit: 100
Yes, most probably the most synchronisation problems come from people using wallet on Windows.

As I have wrote many-many times here in the thread - I do not recommend using Windows wallet with this specific coin! Use Ubuntu on virtual machine on your PC, or use VPS.
I used Win wallet back then, but abandoned it, as it caused too many issues. It seems to be not able to handle orphans easily, and 8bit chain is full of orphans.

Regarding one more snapshot.. well I think there is no big sense in producing snapshots every day, if people cannot sync further than the snapshot itself.
Folks, move to Linux first , then we'll see if snapshots are needed or not Smiley

Confirmed Drays the problem is in windows, I went to ubuntu. LOL...

So how easy is this to do for the average person who is used to just using windows wallets?

How can people with windows wallet swap to Ubuntu?

Is there any guide somewhere?
hero member
Activity: 2114
Merit: 619
Yes, most probably the most synchronisation problems come from people using wallet on Windows.

As I have wrote many-many times here in the thread - I do not recommend using Windows wallet with this specific coin! Use Ubuntu on virtual machine on your PC, or use VPS.
I used Win wallet back then, but abandoned it, as it caused too many issues. It seems to be not able to handle orphans easily, and 8bit chain is full of orphans.

Regarding one more snapshot.. well I think there is no big sense in producing snapshots every day, if people cannot sync further than the snapshot itself.
Folks, move to Linux first , then we'll see if snapshots are needed or not Smiley

Confirmed Drays the problem is in windows, I went to ubuntu. LOL...
legendary
Activity: 2576
Merit: 1073
Yes, most probably the most synchronisation problems come from people using wallet on Windows.

As I have wrote many-many times here in the thread - I do not recommend using Windows wallet with this specific coin! Use Ubuntu on virtual machine on your PC, or use VPS.
I used Win wallet back then, but abandoned it, as it caused too many issues. It seems to be not able to handle orphans easily, and 8bit chain is full of orphans.

Regarding one more snapshot.. well I think there is no big sense in producing snapshots every day, if people cannot sync further than the snapshot itself.
Folks, move to Linux first , then we'll see if snapshots are needed or not Smiley
legendary
Activity: 2576
Merit: 1073
Not sure what this means exactly, but my log is constantly filling up with:

connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused


Is this someone on the wrong chain or something else wrong? If so, can we ban them or something?

That may be because that specific machine had too many connections, and is refusing newer ones. That is harmless, no reason to ban that node.
hero member
Activity: 2114
Merit: 619
Here is my latest snapshot, taken about 8:40am PST Aug 14, 2017

https://drive.google.com/file/d/0B-PuR_0fZVNrLWZ5V3czYWpWckk/view?usp=sharing

Thanks robert, you know I think I have confirmed that the problem of synchronization is with the wallet in windows. I appreciate your help, the block where the wallet in windows is stuck in linux, has it over
full member
Activity: 219
Merit: 100
Not sure what this means exactly, but my log is constantly filling up with:

connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused
connect() to 136.243.147.46:18888 failed after select(): Connection refused


Is this someone on the wrong chain or something else wrong? If so, can we ban them or something?
full member
Activity: 219
Merit: 100
Here is my latest snapshot, taken about 8:40am PST Aug 14, 2017

https://drive.google.com/file/d/0B-PuR_0fZVNrLWZ5V3czYWpWckk/view?usp=sharing
hero member
Activity: 2114
Merit: 619
I'm using the Linux wallet and am able to sync pretty well.

Am working on putting a snapshot together.

I've also noticed that it eats a LOT of memory which I think is very unusual.

@8-Bit-Party

Can you look into why the daemon uses so much memory (at times on my Linux system it wants over 1 GB of memoy)? Other mn coins like DAS use as little as 50 mb.

I sent you MP
Pages:
Jump to: