btcgpu / btcgpu

Current work on BTCGPU

BTG Core (Bitcoin Gold Core)

BTG Core (aka Bitcoin Gold Core, BTCGPU) is the original BTG client and it builds the backbone of the network. It is based on Bitcoin Core. BTG began as a fork of Bitcoin after block height 491406 on Tue, 24 Oct 2017 01:17:35 GMT and began being mined as a separate chain at block height 491407 on Sun, 12 Nov 2017 13:34:01 GMT.

This project began out of the desire to create a variant of Bitcoin that is more decentralized by using an ASIC-resistant Proof of Work algorithm, removing barriers to entry for new miners around the world and reducing the concentration of power in the hands of massive-scale mining operations.

BTG preserves and implements Bitcoin features such as SegWit, which enables advanced scaling technologies like Lightning Network. Significant differences at launch time included:

• ASIC-resistant GPU-minable PoW algorithm (Equihash)
• Per-block difficulty adjustment algorithm
• Replay protection (SIGHASH_FORK_ID)
• Unique wallet addresses (prefixes of G and A, to avoid user confusion with Bitcoin)

Although BTG was bootstrapped on 12 Nov to create an entirely new network, it contains the entire Bitcoin blockchain until block 491406. This means BTG was a full fork at that time, with all Bitcoin transaction history since 2009. Any Bitcoin wallet address which held Bitcoin in BTC block 491406 before the fork held an equal number of Bitcoin Gold in BTG block 491407 after the fork, and those funds are accessible through the original private keys.

Releases

This is the staging tree of Bitcoin Gold. For release version, please switch to 0.17 branch or release page.

To compile from source, please check the build documentations under doc.

Documentation

• Usage
  • macOS
  • Windows
• Configuration and system service

Responsible Disclosure

At the Bitcoin Gold, we consider the security of our systems a top priority. But no matter how much effort we put into system security, there can still be vulnerabilities present.

If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our users and our systems.

Please check our Responsible Disclosure page for more details.

Links

• Website: https://bitcoingold.org
• Tech Spec: https://github.com/BTCGPU/BTCGPU/wiki/Technical-Spec
• Twitter: https://twitter.com/bitcoingold
• Facebook: https://www.facebook.com/bitcoingoldofficial/
• Forum: https://forum.bitcoingold.org
• Discord: invitation
• Telegram (Global): https://t.me/BitcoinGoldHQ

btcgpu's Issues

Can't compile the code.

Code doesn't even compile....

Your own build says it's failing...

Aren't you forking in roughly 27 hours? What's the deal?

Start at block #1 instead of having to DL entire blockchain to date

I think what needs to be done is instead of forking-off the original Bitcoin blockchain is to simply just include all the coins in existence with a premine and just start with the Genesis block. All addresses would be credited exact BTG as the snapshot time.

There are way too many of these Bitcoin forks and its annoying to download and sync. Especially with the coin so new and lack of nodes. Downloading 150GB is really unneccessary.

Which PoW algorithm does the project utilize?

I'm considering to add support for BTG to our pool but - correct me if I'm wrong here - that the PoW algorithm to be used is not set in stone yet. I've seen this PR point to Equihash. What's the current situation here?

Testnet

Is there a testnet on new algo already?

Code audit link?

Hi,

Can you please provide the link to the audit results of your code, if the code is audited?
I couldn't find it anywhere on your website.

If it's not audited, when it will be? The deadline is approaching.

Thank you

Peer Connections Misbehaving, Receiving Bad Headers, Client will not Sync

I've downloaded the bitcoin blockchain: https://getbitcoinblockchain.com/

Then when starting the client on the splash screen stated it was upgrading the UTXO, which completed and the wallet opened, showing the syncing process. However the connections never stay constant, and a lot of peers are banned. and no synchronization seems to be occurring (5 weeks behind), ran this for a few hours, and it never progressed past the block it's "stuck" at.

Debug log:

https://gist.github.com/D3m0nKingx/26dfb18dfa89c6d3f910ede006322e20

Cannot connect to any peers

Cloned the repo, compiled it on a clean Ubuntu 16.04 server and started the process but I get no connections.

In the logs, I see several occurrences of the following:
2017-10-09 21:44:47 Misbehaving: xxx.xxx.xxx.xxx:8333 peer=12 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-10-09 21:44:47 ERROR: invalid header received
2017-10-09 21:44:47 ProcessMessages(headers, 135597 bytes) FAILED peer=12
...
2017-10-09 21:49:45 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000000000bd23f1e0ac2383fe48b53e169c0bee7a1f6411bdb3a8a3, bad-diffbits, incorrect proof of work (code 16)
...

Perhaps I am too early for this but I thought I should be able to synchronize in preparation for the fork.
What am I doing wrong?

Duration of premine if DIFF=1 could be a couple of minutes?

With 5.000 Zol/s (about 12x Nvidia 1070) and a diff=1 we would be able to reward 659.180 BTCG per day. This will translate to 52734 Blocks if reward=12.5.

If you want to only premine 16.000 blocks , this will roughly be 0.61blocks per second!.

First it's curios to see how your network (mainnet doesnt even exist) will keep up the pace but then the question is: If fork 25th and premine starts 25th, then we can jump in on 25th aswell?

When do you really start the premine (UTC)? how long you expect it to be?

BTCGPU BTG Wallet

Hi,

I can't deposit to any exchanges and there are no wallets that let me withdraw the funds. When can we expect a wallet for trading?

-mini

This issue tracker is only for technical issues related to bitcoin-core.

General bitcoin questions and/or support requests and are best directed to the Bitcoin StackExchange.

For reporting security issues, please see the official Bitcoin Gold website.

Describe the issue

No way to withdraw / sell / deposit funds

BTG price down

The biggest mistake was to launch this coin without a working wallet!

Regards,
François

Regtest network bug with wrong values in K,N

Regtest network have init K and N params different from mainnet and testnet.
On mainnet and testnet K, N
const size_t N = 200, K = 9; // Same as mainchain.
BOOST_STATIC_ASSERT(equihash_parameters_acceptable(N, K));
nEquihashN = N;
nEquihashK = K;
On regtest K, N (chainparams.cpp:344)
const size_t N = 48, K = 5;
BOOST_STATIC_ASSERT(equihash_parameters_acceptable(N, K));
nEquihashN = N;
nEquihashK = K;

With public miners on mainnet and testnet all works fine, but if you make regtest network (for some test) daemon reject all shares from public miners. (this problem have all forks of zerocash).

Please make regtest params same mainnet and make genesis block for regtest with K,N 200,9 and not with K,N 48,5

How to participate during the pre-mine stage?

i have 155 k/zol that i would like to contribute to make the network bigger. how to do?

when can we start up the first pools?

Bitcoin Gold Decentralization Problem

How will Bitcoin Gold make Bitcoin Decentralized again? There doesn't seem to be a specific directive or feature that insures that this is the case (other than what already exists in Bitcoin) other than the PoW algorithm.

The mining algorithm is only 1/3 of the problem. The nodes are another 1/3 of the problem. Development is the other 1/3.

To be more decentralized, there should be some incentive to proliferate full nodes as much as possible. Maybe by adding some features that incentivize full nodes, etc.. Not necessarily like the way that dash is setup where full nodes get handouts; but; something that incentivizes users to actually run legitimate full nodes.

A handful of servers on a few continents isn't decentralized at all. Equihash is much more accessible to average people than SHA256; I'll give you that. What about the development team(s) and the network nodes? Is there a plan to make them more accessible to average people?

slack invitation link doesnt work

Hi

Can you please fix the slack invitation link @Readme.md

Best
-s

LoadBlockIndexGuts: failed to read value. Error loading block database.

Describe the issue

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

1. run bitcoin core 0.15 node in pruning mode
2. wait until all blocks are synced
3. stop bitcoin core
4. copy ~/.bitcoin to ~/.bitcoingold
5. start bgoldd

Expected behaviour

Daemon should be able to open block database

Actual behaviour

2017-10-23 15:03:33 Bitcoin version v0.15.0.1-g3180ead18
2017-10-23 15:03:33 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-10-23 15:03:33 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
2017-10-23 15:03:33 Prune configured to target 20480MiB on disk for block and undo files.
2017-10-23 15:03:33 Using the 'standard' SHA256 implementation
2017-10-23 15:03:33 Using RdRand as an additional entropy source
2017-10-23 15:03:33 Default data directory /home/bitcoin/.bitcoingold
2017-10-23 15:03:33 Using data directory /home/bitcoin/.bitcoingold
2017-10-23 15:03:33 Using config file /home/bitcoin/.bitcoingold/bitcoin.conf
2017-10-23 15:03:33 Using at most 125 automatic connections (1024 file descriptors available)
2017-10-23 15:03:33 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2017-10-23 15:03:33 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2017-10-23 15:03:33 Using 0 threads for script verification
2017-10-23 15:03:33 Binding RPC on address 0.0.0.0 port 8332 failed.
2017-10-23 15:03:33 HTTP: creating work queue of depth 16
2017-10-23 15:03:33 HTTP: starting 4 worker threads
2017-10-23 15:03:33 init message: Verifying wallet(s)...
2017-10-23 15:03:33 Using BerkeleyDB version Berkeley DB 5.3.28: (September  9, 2013)
2017-10-23 15:03:33 Using wallet wallet.dat
2017-10-23 15:03:33 CDBEnv::Open: LogDir=/home/bitcoin/.bitcoingold/database ErrorFile=/home/bitcoin/.bitcoingold/db.log
2017-10-23 15:03:33 scheduler thread start
2017-10-23 15:03:33 Cache configuration:
2017-10-23 15:03:33 * Using 2.0MiB for block index database
2017-10-23 15:03:33 * Using 8.0MiB for chain state database
2017-10-23 15:03:33 * Using 440.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-10-23 15:03:33 init message: Loading block index...
2017-10-23 15:03:33 Opening LevelDB in /home/bitcoin/.bitcoingold/blocks/index
2017-10-23 15:03:33 Opened LevelDB successfully
2017-10-23 15:03:33 Using obfuscation key for /home/bitcoin/.bitcoingold/blocks/index: 0000000000000000
2017-10-23 15:03:33 ERROR: LoadBlockIndexGuts: failed to read value
2017-10-23 15:03:33 : Error loading block database.
Please restart with -reindex or -reindex-chainstate to recover.
2017-10-23 15:03:33 Aborted block database rebuild. Exiting.
2017-10-23 15:03:33 scheduler thread interrupt
2017-10-23 15:03:33 Shutdown: In progress...
2017-10-23 15:03:33 Shutdown: done

What version are you using?

bitcoin-gpu-master-3180ead18bcb6471bf6dd3ae18bbaf30bb344602-xenial
selfcompiled from github .zip download via:

./configure --with-incompatible-bdb

Machine specs:

• OS: Ubuntu Xenial 16.04 with libsodium 1.0.13 from Ubuntu Artful (17.01)
  • Please see #43 (comment) regarding the libsodium stuff

Testnet

Describe the issue

No BTG testnet exists

Can you reliably reproduce the issue?

Always

If so, please list the steps to reproduce below:

1. Observe
2. No
3. Testnet

Expected behaviour

A freaking awesome testnet.

Actual behaviour

No testnet 😿

Bounty

650 BTG

Reclaim unused coins

did the fork happen? statement?

did you keep the snapshot?
statement pls.

Include libsodium check in configure.ac

It is required to do check about the libsodium version because currently many people are having problems with this.

Minor improvements to the difficulty algorithm

There's an asymmetry in the algorithm, allowing for a max +32% to -16% rise and fall per block in the difficulty. I would change the 32% to 16%. But the current asymmetry will not hurt anything like the asymmetry of BCH because these limits are rarely reached.

[ edit: I recommend changing 16% and 32% both to 12% with nPowAveragingWindow = 40 and the deletion of the tempering equation. ]

BTCGPU/src/chainparams.cpp

Line 102 in 574a6e5

consensus.nPowMaxAdjustDown = 32; // 32% adjustment down

The algorithm "tempers" the measurements, but this slows the response down rather than basing the change on data. It looks at only the past 17 blocks in the averaging window, but the tempering makes it so slow that it takes over 63 blocks to reach the correct difficulty. It would be better to make the measuring window N=63 blocks and not temper it. N=40 blocks without the tempering would make it respond a bit faster, with slightly larger difficulty swings. To remove the tempering delete:

BTCGPU/src/pow.cpp

Line 55 in 574a6e5

nActualTimespan = params.AveragingWindowTimespan() + (nActualTimespan - params.AveragingWindowTimespan())/4;

The current N=17 without tempering responds probably faster than people want (unless you're a small coin), causing 2x swings in difficulty on occasion based on random chance. So N=40 here would be safer, closer to the current slow response. For comparison, small coins have to hard fork to fix it if they use cryptonote's default N=300.

BTCGPU/src/chainparams.cpp

Line 100 in 574a6e5

consensus.nPowAveragingWindow = 17;

There's also a 5-block delay in responding due to using MTP, but fixing that would require code changes in several places to prevent damage from bad timestamps.

Add libsodium check in configure script

Describe the issue

configure script lacks a check for libsodium and libsodim-dev

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

1. download BTCGPU zip file from github
2. unzip file
3. apt-get purge libsodium-dev libsodium18
4. ./autogen.sh && ./configure && make

Expected behaviour

configure complains about missing libsodium/libsodium-dev

Actual behaviour

configure runs fine, make crashes with:

  CXX      crypto/libbitcoinconsensus_la-aes.lo
In file included from crypto/aes.cpp:6:0:
./crypto/common.h:16:20: fatal error: sodium.h: No such file or directory
compilation terminated.

What version of are you using?

bitcon-gpu-master-2f5fe4c15bb88596e7edbbda5ad702d8c075c4b7

Machine specs:

Ubuntu Xenial (16.04 LTS) on AWS EC2 instance type t2.small

Stratum spec

Since BTCGPU utilises equihash it's wise to follow zcash stratum spec, will make existing miners compatible. https://github.com/str4d/zips/blob/77-zip-stratum/drafts/str4d-stratum/draft1.rst

Timelock mechanism not implemented

Timelock mechanism must be implemented for the launch of the project.

As discussed 60% of the premine must be released on a fixed period of time, proportionately on the next 3 years.
This is being used for the development of the project.

Exact method of fork

There is great discussion about how will the fork be done. You guys already have a exact block to execute the snapshot. But when exactly?

In the very second that the block is found? Or at the end of the period of this block?

Build Error

Describe the issue

Followed the build instructions 1:1 on ubuntu 16.04 64bit. ran autogen and afterwards config, then this error occured:
configure error: Could not link against boost_system
solution:
instead of ./configure , use:
./configure --with-boost-libdir=/usr/lib/x86_64-linux-gnu

Can you reliably reproduce the issue?

1.Followed the build instructions on ubuntu 16.04 64 bit
2.ran ./autogen.sh
3.ran ./configure

Expected behaviour

build bitcoin gold

Actual behaviour

error message

Just wanted to clear things up in case someone else got the same problem :)

Bitcoin private keys data file is recognised by Bitcoin gold

Describe the issue

Upon starting the daemon there is an error message that says "Error loading wallet.dat: Wallet requires newer version of Bitcoin Gold"

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

1. Build source
2. start bitcoind

Expected behaviour

Tell us what should happen
Wallet.dat must be different that Bitcoin's wallet.dat

What version of bitcoin-core are you using?

• 4f33ac1

Machine specs:

• OS: MacOS

Support multiple PoW

Same chain, different PoW on each block - each one with different difficulty depending how often it is used (are there ASIC out there), hijack 1 byte from e.g. version to state which hashing algorithm use to verify. It could also allow some support from desperate SHA256 miners, before GPU pools will kick in.

Wallet crashes right after launch with assertion failed

Crashes right after launch:

src/bgoldd -daemon
bgoldd: crypto/common.h:138: int init_and_check_sodium(): Assertion `crypto_sign_verify_detached(sig, message, sizeof(message), pk) != 0' failed.
Segmentation fault (Core dumped)

Core Dump error

On Ubuntu 16.04 after configure make seems to make the daemon fine.

Once you go to execute the daemon the following issues occurs.

bgoldd: crypto/common.h:138: int init_and_check_sodium(): Assertion `crypto_sign_verify_detached(sig, message, sizeof(message), pk) != 0' failed.
Aborted (core dumped)

no testnet nodes

there aren't any public testnet nodes to connect to, the dnsseed nodes are not working

The fork date should be postponed

Clearly with so many work-in-progress features, including the one perceived as mandatory for most supporters - 2-way replay protection - it seems most reasonable to postpone the fork until:

• you have a 2-way replay protection implemented so that users can easily split their coins,
• you have a testnet developers can play with,
• you have presented exact way the premine and timelocks will be executed,
• you have a client people could actually run,
• there is a public block explorer.

Right now there are only a few hours till the fork.

Without replay protection BTG loses most of it's value since Bitcoin holders will not be able to send BTG coins without the risk of losing their BTC coins and vice versa.

Moreover, lack of replay protection makes it really difficult for services like exchanges to credit their users with BTG coins.

If you really want BTG to have any value for its holders you should definitely postpone the launch until all the issues are resolved. Otherwise you risk jeopardizing your whole project.

There is nothing wrong in saying "we have a few more issues we need to work on to make sure your coins are safe". But lauching a coins that is only half-baked is a sure way to lose most of your credibility and make BTG useless.

Cheers,
Ethan (from YOLOdice)

building static files under linux without the needs of system-boost-files, etc. failed

One simple question, not answered between all the (mostly async and/or outdated) doc-files:

What are the exact ./configure commands and FLAGs to just build EVERYTHING static
under Ubuntu 16.04? Means: No dependencies to system-boost-libs and other libs ?
...by using the stock (system+dev-)files that comes with ubuntu 16.04

Simple things like "--disable-shared --enable-static" results only in "half" static binarys, where boost
and other libs are still needed...

Is it scam?

• Firstly, the website https://btcgpu.org/ is down at 8:22 UTC.
• Secondly, the BTCGPU reported (has implemented) three main features in comparison with BTC and BCH. But these features are not working now.
• Thirdly, the fork time is changed, the developers are not strong enough, someone just joins the project 2 weeks ago.

From these points, I sure that this fork is just scam.

Change address version

I suggest to change the address version to something different, so it is obvious the address is a Bitcoin Gold address. (It can start with G for example). Don't forget to change also address version for P2SH!

Tons of compile warnings in equihash.cpp (comparison between signed and unsigned integer expressions)

crypto/equihash.cpp: In instantiation of ‘bool Equihash<N, K>::BasicSolve(const eh_HashState&, std::function<bool(std::vector<unsigned char>)>, std::function<bool(EhSolverCancelCheck)>) [with unsigned int N = 96u; unsigned int K = 3u; eh_HashState = crypto_generichash_blake2b_state]’:

crypto/equihash.cpp: In instantiation of ‘bool Equihash<N, K>::IsValidSolution(const eh_HashState&, std::vector<unsigned char>) [with unsigned int N = 200u; unsigned int K = 9u; eh_HashState = crypto_generichash_blake2b_state]’:
crypto/equihash.cpp:785:111:   required from here
crypto/equihash.cpp:741:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
crypto/equihash.cpp: In instantiation of ‘bool Equihash<N, K>::IsValidSolution(const eh_HashState&, std::vector<unsigned char>) [with unsigned int N = 96u; unsigned int K = 5u; eh_HashState = crypto_generichash_blake2b_state]’:
crypto/equihash.cpp:795:110:   required from here
crypto/equihash.cpp:741:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
crypto/equihash.cpp: In instantiation of ‘bool Equihash<N, K>::IsValidSolution(const eh_HashState&, std::vector<unsigned char>) [with unsigned int N = 48u; unsigned int K = 5u; eh_HashState = crypto_generichash_blake2b_state]’:
crypto/equihash.cpp:805:110:   required from here
crypto/equihash.cpp:741:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
crypto/equihash.cpp: In instantiation of ‘FullStepRow<WIDTH>::FullStepRow(const FullStepRow<W>&, const FullStepRow<W>&, size_t, size_t, int) [with long unsigned int W = 22ul; long unsigned int WIDTH = 38ul; size_t = long unsigned int]’:
crypto/equihash.cpp:425:91:   required from ‘bool Equihash<N, K>::BasicSolve(const eh_HashState&, std::function<bool(std::vector<unsigned char>)>, std::function<bool(EhSolverCancelCheck)>) [with unsigned int N = 96u; unsigned int K = 3u; eh_HashState = crypto_generichash_blake2b_state]’
./crypto/equihash.h:220:67:   required from here
crypto/equihash.cpp:233:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
     for (int i = trim; i < len; i++)
                          ^

Never had this many compile warnings with Bitcoin Core or Bitcoin Cash.

Build Error

N/A

Stuck at block 366836 while syncing: ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader bad-height, incorrect block height

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

1. start btcgpu daemon
2. sync begins until block 366836

Expected behaviour

New blocks being downloaded. My understanding is, that bitcoin gold should sync from any core client until block 491406.

Actual behaviour

2017-10-25 08:40:02 ERROR: invalid header received
2017-10-25 08:40:02 ProcessMessages(headers, 18064 bytes) FAILED peer=1
2017-10-25 08:40:05 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000000000e5438564434edaf41e63829a637521a96235adf4653e1b, bad-height, incorrect block height (code 16)

What version of bitcoin-core are you using?

bitcoin-gpu-master-3180ead18bcb6471bf6dd3ae18bbaf30bb344602-xenial
selfcompiled from github .zip download

Any extra information that might be useful in the debugging process.

Node is well connected:

% bitcoin-cli getpeerinfo | grep subver
    "subver": "/Satoshi:0.15.0.1/",
    "subver": "/Satoshi:0.15.0.1/",
    "subver": "/Bitcoin Gold:0.15.0.1/",
    "subver": "/Satoshi:0.15.0.1/",
    "subver": "/Satoshi:0.13.2/",
    "subver": "/Satoshi:0.14.2/",
    "subver": "/Satoshi:0.14.2/",
    "subver": "/Satoshi:0.15.0.1/",
    "subver": "/Bitcoin Gold:0.15.0.1/",

The connected Bitcoin Gold nodes are at block 491406 and thus don't signal "new block found" since there are no new blocks public right now. That's why my node doesn't download new blocks from the Bitcoin Gold nodes.

Implement two-way replay protection

This is necessary in order not to cause havoc.

Bitcoin Cash implemented this by using SIGHASH_FORKID and I recommend you doing the same, as it would be trivial to implement your coin into other wallets that already support Bitcoin Cash.

More info:

• Bitcoin-ABC/bitcoin-abc#24
• bitcoincashorg/spec#17

Change our ClientID

Suggested by @daira here #16 (comment) and a very good idea, to differentiate our client

Update the magic numbers in order to diff from Bitcoin.

Replay Protection Implementation

Two-way replay protection must be provided in Bitcoin Gold
Refer to #18

The solution must feature:

• two-way SIGHASH_FORK_ID replay protection
• clean and readable code
• automated tests

Bounty: 250 BTG
Bonus 50 BTG if the task is finished before 25.10.2017 12:00 UTC

Vote for a new logo design

All the exchange platform, coinmarketcap and other news website are going to take the logo from the official website. If you think that the current logo gives a bad image to Bitcoin Gold thank you for voting or propose a new design.

Idea 1 : Bitcoin is leaning on one side, and Bitcoin cash is leaning on the other side, Bitcoin version Gold will have his letter R I G H T

Block explorer

Please make sure you set up a block explorer for you Testnet and Mainnet.

Add Bitcoin Gold to Electrum

Describe the issue

Electrum does not support Bitcoin Gold.

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

1. Observe
2. No
3. Support

Expected behaviour

Electrum should support Bitcoin Gold.

Actual behaviour

No support.

Details

Add Bitcoin Gold to Electrum, which requires changing both the ElectrumX client, which supports multiple cryptocoins (not the horrible BCH fork stuff which doesn't work) and the Electrum server to talk to the correct BTG nodes and make any protocol changes. This will include a test suite, developer documentation and end user documentation for using BTG via Electrum.

Bounty

250BTG

Bonus Bounty: 50BTG if this is merged before the launch of mainnet (currently planned for Nov 1st)

Bitcoin Gold daemon must have different name than Bitcoin daemon

Bitcoin Gold daemon has name bitcoind that overlaps with Bitcoin daemon. They must be different.

Problem with BTC WALLET compiling in Windows

I try to follow the info on github for compiling the BTC GOLD Wallet but i have this iusse.
CXX libbitcoinconsensus_la-utilstrencodings.lo
make[3]: ingresso nella directory "/home/vrminer2/BTCGPU/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
libtool: link: warning: undefined symbols not allowed in x86_64-w64-mingw32 shared libraries
make[3]: uscita dalla directory "/home/vrminer2/BTCGPU/src/secp256k1"
CXXLD libbitcoinconsensus.la
crypto/.libs/libbitcoinconsensus_la-equihash.o:equihash.cpp:(.text+0x196): undefined reference to crypto_generichash_blake2b_update' crypto/.libs/libbitcoinconsensus_la-equihash.o:equihash.cpp:(.text+0x1a4): undefined reference to crypto_generichash_blake2b_final'
/usr/bin/x86_64-w64-mingw32-ld: crypto/.libs/libbitcoinconsensus_la-equihash.o: bad reloc address 0x0 in section `.data'
collect2: error: ld returned 1 exit status
make[2]: *** [libbitcoinconsensus.la] Errore 1
make[2]: uscita dalla directory "/home/vrminer2/BTCGPU/src"
make[1]: *** [all-recursive] Errore 1
make[1]: uscita dalla directory "/home/vrminer2/BTCGPU/src"
make: *** [all-recursive] Errore 1
vrminer2@DESKTOP-C6LEM3D:~/BTCGPU$
How i can solve this iusse ? Some one already compiled the Wallets ?

Change default port number

to something else than 8333 so it will not collide with Bitcoin.

Exact fork date?

If I understand correctly, from this file:

https://github.com/BTCGPU/BTCGPU/blob/master/src/chainparams.cpp#L82

It seems like the fork already happened, at block 487427. The website however says Bitcoin Gold won't launch until October 25. How will this work exactly?

System Tray Icon Menu not Appearing

Describe the issue

Bitcoin Gold's System Tray Icon's Menu is not working

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

1. Open Bitcoin Gold Wallet
2. Right-Click On System Tray Icon

Expected behaviour

Appmenu should be displayed with various wallet operations that can be performed, (show/hide, receive/send, sign/verify message, options..., debug window, exit)

Actual behaviour

Blank narrow box appears

Screenshots.

What version of bitcoin-core are you using?

Version: v0.15.0.1-b195fa2
Compiled locally

Machine specs:

Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial

Any extra information that might be useful in the debugging process.

Both appmenu-qt and appmenu-qt5 packages are installed:

 appmenu-qt:amd64      0.2.7+14.04.20140305-0u amd64         application menu for Qt
 appmenu-qt5           0.3.0+16.04.20170216-0u amd64         application menu for Qt5

Yobit starting BTG trading prior to launch date

https://yobit.net/en/bitcoingold/timer/

How is this so?