Pages:
Author

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

newbie
Activity: 41
Merit: 0
is there a slack channel or discord server somewhere i can join?

go8bit.slack.com - channel
https://join.slack.com/t/go8bit/shared_invite/MjE0ODE4NzU2NDA0LTE1MDA0NjU2MzAtZjU3MzIwMzVkYw -invite link
The telegram channels are almost dead but however
https://t.me/EightBitChat
https://t.me/eightbitcoin
member
Activity: 318
Merit: 10
is there a slack channel or discord server somewhere i can join?
full member
Activity: 219
Merit: 100
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.

What's your boost version?


1.62

Build has come a lot further along, but now I get this error:

$  make -f makefile.unix&&strip 8bitd&&sudo cp 8bitd /usr/bin
/bin/sh ../share/genbuild.sh obj/build.h
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -DUSE_SECP256K1 -I/home/r8st/8bit/src -I/home/r8st/8bit/src/obj -DUSE_UPNP=0 -DENABLE_WALLET -I/home/r8st/8bit/src/leveldb/include -I/home/r8st/8bit/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/darksend.d -o obj/darksend.o darksend.cpp
darksend.cpp: In member function ‘bool CDarkSendPool::IsCollateralValid(const CTransaction&)’:
darksend.cpp:978:29: error: cannot convert ‘bool’ to ‘bool*’ in initialization
     bool* pfMissingInputs = false;
                             ^~~~~
makefile.unix:201: recipe for target 'obj/darksend.o' failed
make: *** [obj/darksend.o] Error 1


Has anyone received this error while building 8bitd, and is there a known solution?

Change "bool* pfMissingInputs" to "bool fMissingInputs " in darksend.cpp line 978. On the next line change "pfMissingInputs" to "&fMissingInputs". I could have sent a patch, but I am on a touch screen right now, so... just do manually Smiley

That is just a stupid programming mistake done by the first dev (not 8-bit-party). Your compiler is too clever to digest that stupidity.

This code really needs to be refactored...  Undecided

Should we all apply this patch?
legendary
Activity: 2576
Merit: 1073
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.

What's your boost version?


1.62

Build has come a lot further along, but now I get this error:

$  make -f makefile.unix&&strip 8bitd&&sudo cp 8bitd /usr/bin
/bin/sh ../share/genbuild.sh obj/build.h
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -DUSE_SECP256K1 -I/home/r8st/8bit/src -I/home/r8st/8bit/src/obj -DUSE_UPNP=0 -DENABLE_WALLET -I/home/r8st/8bit/src/leveldb/include -I/home/r8st/8bit/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/darksend.d -o obj/darksend.o darksend.cpp
darksend.cpp: In member function ‘bool CDarkSendPool::IsCollateralValid(const CTransaction&)’:
darksend.cpp:978:29: error: cannot convert ‘bool’ to ‘bool*’ in initialization
     bool* pfMissingInputs = false;
                             ^~~~~
makefile.unix:201: recipe for target 'obj/darksend.o' failed
make: *** [obj/darksend.o] Error 1


Has anyone received this error while building 8bitd, and is there a known solution?

Change "bool* pfMissingInputs" to "bool fMissingInputs " in darksend.cpp line 978. On the next line change "pfMissingInputs" to "&fMissingInputs". I could have sent a patch, but I am on a touch screen right now, so... just do manually Smiley

That is just a stupid programming mistake done by the first dev (not 8-bit-party). Your compiler is too clever to digest that stupidity.

This code really needs to be refactored...  Undecided
full member
Activity: 179
Merit: 100
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.

What's your boost version?


1.62

Build has come a lot further along, but now I get this error:

$  make -f makefile.unix&&strip 8bitd&&sudo cp 8bitd /usr/bin
/bin/sh ../share/genbuild.sh obj/build.h
g++ -c -O2  -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -DUSE_SECP256K1 -I/home/r8st/8bit/src -I/home/r8st/8bit/src/obj -DUSE_UPNP=0 -DENABLE_WALLET -I/home/r8st/8bit/src/leveldb/include -I/home/r8st/8bit/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/darksend.d -o obj/darksend.o darksend.cpp
darksend.cpp: In member function ‘bool CDarkSendPool::IsCollateralValid(const CTransaction&)’:
darksend.cpp:978:29: error: cannot convert ‘bool’ to ‘bool*’ in initialization
     bool* pfMissingInputs = false;
                             ^~~~~
makefile.unix:201: recipe for target 'obj/darksend.o' failed
make: *** [obj/darksend.o] Error 1


Has anyone received this error while building 8bitd, and is there a known solution?
hero member
Activity: 2114
Merit: 619
Question:

How to speed up the synchronization process?

I just downloaded the windows wallet.
=> "Synchronizing with the network... "2years and 13weeks behind"

It takes quite some while !!

I have currently 70 active connections with the 8bit network.

A user posted a snapshot about 4 hours ago, download and replace those files in the wallet folder when roaming if you are on windows
(Prior to this eliminate what is inside 8bit, except for wallet.dat and 8bit.conf)

C: \ Users \ your user \ AppData \ Roaming

It is not recommended to synchronize from scratch or you will get a fork


Thanks for this help.
I followed your steps... now I get this error message, when opening the wallet:

EXCEPTION: St13runtime_error
init_blockindex(): error opening database
environment IO error: C:\...\AppData\Roaming\txleveldb\MANIFEST-9793949: The handle is not valid.

C:\Program Files\...\8bit\8bit-qt.exe in Runaway exception


=> What is required to fix this error message?
=> What needs to be adjusted ?


Thanks for your support!


I do not know if you understood the snapshots of the snapshot you should save them in

C: \ Users \ your user \ AppData \ Roaming \ 8bit \

There only copy this: the folder database, txleveldb and the file blk0001.dat

That error has come out because you use the incomplete path, you must note that the files must go inside the 8bit folder
full member
Activity: 179
Merit: 100
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.

What's your boost version?


1.62
newbie
Activity: 58
Merit: 0
Question:

How to speed up the synchronization process?

I just downloaded the windows wallet.
=> "Synchronizing with the network... "2years and 13weeks behind"

It takes quite some while !!

I have currently 70 active connections with the 8bit network.

A user posted a snapshot about 4 hours ago, download and replace those files in the wallet folder when roaming if you are on windows
(Prior to this eliminate what is inside 8bit, except for wallet.dat and 8bit.conf)

C: \ Users \ your user \ AppData \ Roaming

It is not recommended to synchronize from scratch or you will get a fork


Thanks for this help.
I followed your steps... now I get this error message, when opening the wallet:

EXCEPTION: St13runtime_error
init_blockindex(): error opening database
environment IO error: C:\...\AppData\Roaming\txleveldb\MANIFEST-9793949: The handle is not valid.

C:\Program Files\...\8bit\8bit-qt.exe in Runaway exception


=> What is required to fix this error message?
=> What needs to be adjusted ?


Thanks for your support!
legendary
Activity: 2576
Merit: 1073
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?

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

It is perfectly possible to run cold Windows wallet with remote Linux VPS, in case if you run just one masternode.

If you run more than one masternode, and plan to use "masternode.conf", you cannot have cold wallet on Windows, because the current Windows binary does not include the patch needed (I published that source code patch some pages back). But you can run local cold Linux wallet (with the patch included) + remote Linux VPS with multiple masternodes.


Drays apologize for my ignorance of what you mean with run local cold in linux?

I mean you can keep the 112 coins (masternode collateral) in your local wallet on your local Ubuntu machine, and have remote wallet on VPS running with zero coins. This is called cold/hot wallet setup.
hero member
Activity: 2114
Merit: 619
Question:

How to speed up the synchronization process?

I just downloaded the windows wallet.
=> "Synchronizing with the network... "2years and 13weeks behind"

It takes quite some while !!

I have currently 70 active connections with the 8bit network.

A user posted a snapshot about 4 hours ago, download and replace those files in the wallet folder when roaming if you are on windows
(Prior to this eliminate what is inside 8bit, except for wallet.dat and 8bit.conf)

C: \ Users \ your user \ AppData \ Roaming

It is not recommended to synchronize from scratch or you will get a fork
newbie
Activity: 58
Merit: 0
Question:

How to speed up the synchronization process?

I just downloaded the windows wallet.
=> "Synchronizing with the network... "2years and 13weeks behind"

It takes quite some while !!

I have currently 70 active connections with the 8bit network.
hero member
Activity: 2114
Merit: 619
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?

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

It is perfectly possible to run cold Windows wallet with remote Linux VPS, in case if you run just one masternode.

If you run more than one masternode, and plan to use "masternode.conf", you cannot have cold wallet on Windows, because the current Windows binary does not include the patch needed (I published that source code patch some pages back). But you can run local cold Linux wallet (with the patch included) + remote Linux VPS with multiple masternodes.


Drays apologize for my ignorance of what you mean with run local cold in linux?
sr. member
Activity: 506
Merit: 250
Seriously Windows wallet enabling setting up multiple nodes would be highly appreciated, i would like to subscribe for ubuntu vps while having all my coins on my windows wallet just as available on other MN coins please look into this!
newbie
Activity: 58
Merit: 0
Hello together,

I did want to download the 8BIT windows wallet - Link: https://www.dropbox.com/s/c3dx56aki99c83f/8bit-qt-2.1-win.zip?dl=0


but then I got the following error message:

"Error (429)
This link is temporarily disabled. The person who shared it hit their daily limit of traffic or downloads. Learn about traffic limits."


Will be there another link be provided for downloading the windows wallet ?


Thanks!
Roman



http://zalil.su/4290609


@d3nc3nd: Thanks a lot for your quick support! Link worked excellent, wallet installed. :-)
legendary
Activity: 2576
Merit: 1073
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?

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

It is perfectly possible to run cold Windows wallet with remote Linux VPS, in case if you run just one masternode.

If you run more than one masternode, and plan to use "masternode.conf", you cannot have cold wallet on Windows, because the current Windows binary does not include the patch needed (I published that source code patch some pages back). But you can run local cold Linux wallet (with the patch included) + remote Linux VPS with multiple masternodes.
member
Activity: 129
Merit: 10
Hello together,

I did want to download the 8BIT windows wallet - Link: https://www.dropbox.com/s/c3dx56aki99c83f/8bit-qt-2.1-win.zip?dl=0


but then I got the following error message:

"Error (429)
This link is temporarily disabled. The person who shared it hit their daily limit of traffic or downloads. Learn about traffic limits."


Will be there another link be provided for downloading the windows wallet ?


Thanks!
Roman



http://zalil.su/4290609
full member
Activity: 219
Merit: 100
Looks like things are really starting to stabilize!

I have us started off on getting a listing on masternodes.pro. We would have the number 1 spot in ROI there. Only $178 more needed to get listed. Come on people, lets get this 8Bit Party started!
newbie
Activity: 58
Merit: 0
Hello together,

I did want to download the 8BIT windows wallet - Link: https://www.dropbox.com/s/c3dx56aki99c83f/8bit-qt-2.1-win.zip?dl=0


but then I got the following error message:

"Error (429)
This link is temporarily disabled. The person who shared it hit their daily limit of traffic or downloads. Learn about traffic limits."


Will be there another link be provided for downloading the windows wallet ?


Thanks!
Roman


full member
Activity: 219
Merit: 100
Hello, I have just arrived. The block explorer & website will return this evening (UTC), I am syncing my nodes finally.


That's great 8-bit-Party!

It would be beneficial if there was standard api access to the block explorer like most have.
legendary
Activity: 1036
Merit: 1000
8b 16b DEMOSCENE FTW
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.

What's your boost version?
Pages:
Jump to: