gobytecoin / gobyte

GoByte Core - GBX

GoByte Core v0.16.2.2 (GBX)

https://www.gobyte.network

What is GoByte?

GoByte (GBX) is an innovative cryptocurrency. A form of digital currency secured by cryptography and issued through a decentralized and advanced mining market. Based on GoByte, it's an enhanced and further developed version, featuring the masternode technology with 50% Reward, near-instant and secure payments as well as anonymous transactions. GoByte has great potential for rapid growth and expansion. Based on a total Proof of Work and Masternode system, it is accesible to everyone, it ensures a fair and stable return of investment for the Graphics Processing Units (GPUs) miners and the Masternode holders.

Additional information, wallets, specifications & roadmap: https://bitcointalk.org/index.php?topic=2442185.0

License

GoByte Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of GoByte Core.

The contribution workflow is described in CONTRIBUTING.md.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

The Travis CI system makes sure that every pull request is built for Windows and Linux, OS X, and that unit and sanity tests are automatically run.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

gobyte's Issues

Libevent issue

Hello,
I am getting an error message after typing command ./configure

checking for EVENT... no
configure: error: libevent not found.

any solution?

Network is dead

Is the network is dead ??

No peers and network confirmation down.. But token pump on exchange, WTF ?!

V

how do i run the linux wallet

i cloned the repo. ran ./autogen.sh , ./configure and make now what?

Offer build which runs on latest stable Ubuntu

The current build v0.12.1.3 does not run on the current version of Ubuntu, which is 17.10. The problem is the version of libboost. Gobyte was build with libboost version 1.58, while Ubuntu ships with version 1.62. Please fix this so that users can run the wallet on latest stable Ubuntu.

Also, version 18.04 of Ubuntu, which is coming up in April, will ship with libboost version 1.65. So please also offer a bulid for that version.

I know there are tricks to build all this yourself on Ubuntu, but that is for most users way too difficult or cumbersome. Offering these build will increase the user base and improve the image for this wallet.

libtool for -rpath problems

./autogen.sh

libtoolize: copying file 'build-aux/m4/lt~obsolete.m4'
configure.ac:52: installing 'build-aux/compile'
configure.ac:25: installing 'build-aux/missing'
Makefile.am:5: warning: user variable 'GZIP_ENV' defined here ...
/usr/share/automake-1.15/am/distdir.am: ... overrides Automake variable 'GZIP_ENV' defined here
Makefile.am:58: warning: user target 'distcleancheck' defined here ...
/usr/share/automake-1.15/am/distdir.am: ... overrides Automake target 'distcleancheck' defined here
src/Makefile.am: installing 'build-aux/depcomp'
src/Makefile.am:516: warning: user target '.mm.o' defined here ...
/usr/share/automake-1.15/am/depend2.am: ... overrides Automake target '.mm.o' defined here

./configure

checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating pc/libunivalue.pc
config.status: creating pc/libunivalue-uninstalled.pc
config.status: creating univalue-config.h
config.status: univalue-config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
Fixing libtool for -rpath problems.

make

Making all in src
make[1]: Entering directory '/home/devjs/gobyte/gobyte/src'
make[2]: Entering directory '/home/devjs/gobyte/gobyte/src'
CXX crypto/libbitcoinconsensus_la-hmac_sha512.lo
CXX crypto/libbitcoinconsensus_la-ripemd160.lo
CXX crypto/libbitcoinconsensus_la-sha1.lo
CXX crypto/libbitcoinconsensus_la-sha256.lo
CXX crypto/libbitcoinconsensus_la-sha512.lo
CXX libbitcoinconsensus_la-hash.lo
CXX primitives/libbitcoinconsensus_la-transaction.lo
CXX libbitcoinconsensus_la-pubkey.lo
CXX script/libbitcoinconsensus_la-bitcoinconsensus.lo
CXX script/libbitcoinconsensus_la-interpreter.lo
CXX script/libbitcoinconsensus_la-script.lo
CXX libbitcoinconsensus_la-uint256.lo
CXX libbitcoinconsensus_la-utilstrencodings.lo
make[3]: Entering directory '/home/devjs/gobyte/gobyte/src/secp256k1'
gcc -I. -g -O2 -Wall -Wextra -Wno-unused-function -c src/gen_context.c -o gen_context.o
gcc gen_context.o -o gen_context
./gen_context
CC src/libsecp256k1_la-secp256k1.lo
CCLD libsecp256k1.la
/usr/bin/ar: u' modifier ignored since D' is the default (see U') make[3]: Leaving directory '/home/devjs/gobyte/gobyte/src/secp256k1' CXXLD libbitcoinconsensus.la /usr/bin/ar: u' modifier ignored since D' is the default (see U')
make[2]: *** No rule to make target 'gobyted.cpp', needed by 'gobyted-gobyted.o'. Stop.
make[2]: Leaving directory '/home/devjs/gobyte/gobyte/src'
Makefile:9080: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/devjs/gobyte/gobyte/src'
Makefile:652: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

i'm using ubuntu 16.04 and also tried with Debian 9.3 getting same error.

Gobyte pool showing wrong price compared to btc

Expected behavior

Gobyte asia pool is expected to show the btc value in pool stats correctly.

Actual behavior

Gobyte asia pool is showing wrong btc value.

How to reproduce

1. Visit: https://asia1.gobyte.network/
2. Check out the "Pool Stats (neoscrypt)" tab

• Browser: Brave Browser v0.21.16
• Operating system: Windows 10

Problem with libboost_system.so.1.58.0 (Ubuntu 18.04.4)

Ubuntu 18.04.4. Once I found that gobyted can't be started anymore. Because of

./gobyted: error while loading shared libraries: libboost_system.so.1.58.0: cannot open shared object file: No such file or directory

So after I created a bunch of symbolic links to many of newer libraries as the problems were appearing, finally I've got this error:

./gobyted: symbol lookup error: ./gobyted: undefined symbol: _ZN5boost11this_thread5hiden9sleep_forERK8timespec

p2pool for this coin

i seach a p2pool for this coin.
can anyone help me?

give gbx.xyz to your company

I have a domain,which is gbx.xyz
If you company have interesting, I can sale you , only 1bsv
My email is [email protected]
looking forward to you replay

depends folder outdated and resulted segfaults on ubuntu 16.04

Using the depends folder from the master results in segfaulted binarys on ubuntu 16.04.
compiling directly with the systemlibs works. (but all is shared then...)

After short checking the used versions in depends folder i will suggest to update the version numbers and patches, especialy openssl, zmq, boost and qt to a more actual version.

Further more the libsodium package is missing and needs to be added. version 14 or 15 is an open question. by using a never qt5-version the package zlib needs to be added. A good base is the depends folder from latest bitcoin-core or btcgold.

Compile error with boost-libs 1.66

On Arch Linux I got compile errors after upgrading boost to version 1.66.
To fix them I did changes in txmempool.h like described here:
bitcoin/bitcoin@1ec0c0a01c31

Did not need to fix anything in miner.h

Not sure what changes do but maybe some developer can check it.

Solo mining?

how do i solo mine this coin? any tips? stratum package available? on click docker file?

Deleted

Deleted.

EXCEPTION: St9bad_alloc std::bad_alloc

---

EXCEPTION: St9bad_alloc
std::bad_alloc
gobyte in ProcessMessages()

I get this then the wallet stops working

cannot run Linux wallet, missing libraries

Your Linux binary appears to depend on a very specific Linux version, and it will not run elsewhere.

I'm trying to run your Linux wallet on Ubuntu 16.04. First it gave me this error:

./gobyte-qt: error while loading shared libraries: libqrencode.so.3: cannot open shared object file: No such file or directory

I was able to fix it by installing libqrencode3.

Then it produced this error:

./gobyte-qt: error while loading shared libraries: libdb_cxx-4.8.so: cannot open shared object file: No such file or directory

I could not fix it. Ubuntu 16.04 does not appear to include that library.

It would be great if you could do static linking on your Linux binaries. This way they will not depend on specific libraries being installed on the system - as long as the kernel is not extremely old they will run just fine on any distribution.

Also, currently your statement that you're providing a "Linux wallet" is a bit misleading. You're providing a wallet that only runs on a specific Linux distribution.

Masternode status "WATCHDOG_EXPIRED" ??

I updated my wallet this am.
The masternode status is "Watchdog Expired" What do I do to get back to enabled status?

Genesis block!

Hello!
How did you create block genesis?
I can not check your result =(

Guide] Setup the GoByte Sentinel

Step #1
Login to you VPS client, and execute the following command in order to update your VPS and install python virtual environment.

sudo apt-get update
sudo apt-get -y install python-virtualenv
Step #2
The sentinel installation. First we will have to clone the repository of the sentinel using the commands below.

— Here we might an error mentioning that virtualenv is not installed. If it says that, simply run the command: “apt install virtualenv” it will ask for your approval [Y/n], hit Y and enter.

git clone https://github.com/gobytecoin/sentinel.git && cd sentinel
apt install virtualenv
virtualenv ./venv
./venv/bin/pip install -r requirements.txt
Step #3
Setup the crontab entry to call the sentinel every minute using the following command.

crontab -e
It should ask you to select the editor you want to use in order to edit the crontab. Chose “2” the “nano” editor as it is easier.

Now scroll all the way down on that file until the last line is:

m h dom mon dow user command

Under that line add this line

• • • • • cd /root/sentinel && ./venv/bin/python bin/sentinel.py >/dev/null 2>&1
          The one above is the default path for the sentinel if you login as “root”, if you have other user on that VPS then use the following:
• • • • • cd /home/YOURUSERNAME/sentinel && ./venv/bin/python bin/sentinel.py >/dev/null 2>&1
          Edit according to the path to your sentinel folder.

Step #4
The configuration. You have to edit the “sentinel.conf” file inside the “sentinel” folder in order to point it to your “gobyte.conf” file inside your “.gobytecore” folder

Inside the sentinel folder do the command

nano sentinel.conf
Now edit the line

#gobyte_conf=/home/YOUR HOME DIRECTORY/.gobytecore/gobyte.conf
to

gobyte_conf=/root/.gobytecore/gobyte.conf
If you are using another user than root, then edit according to the path to your gobyte.conf file

gobyte_conf=/home/YOUR HOME DIRECTORY/.gobytecore/gobyte.conf

WATCHDOG_EXPIRED - but without any changes to MN configuration

My Gobyte MN was working for many months completely OK. But now with no changes to MN configuration I only see a WATCHDOG_EXPIRED message in my Gobyte wallet, and I can't start my MN. Sentinel is installed and configured.

Ubuntu 16.04.6 LTS

High CPU usage

We run a shared masternode service, hosting for many various coins. One of the coins we host is gobyte which consistently uses around 150-165% cpu (of one core). I'm not sure what the cause is of the high cpu usage, it seems there may be some inefficiencies in the masternode code.

bitcoin nBits used in scriptSig of first block

gobyte/src/chainparams.cpp

Line 27 in f1aa274

txNew.vin[0].scriptSig = CScript() << 486604799 << CScriptNum(4) << std::vector<unsigned char>((const unsigned char*)pszTimestamp, (const unsigned char*)pszTimestamp + strlen(pszTimestamp));

see 486604799 . it's 1D00FFFF , bitcoin first block difficulty ,where should be 1e0ffff0