This running topic will track the accomplished and remaining tasks of the Electrum Wallet and Server fork for BTG.
Electrum Server
Correct electrum header creation
Change chunksize
Make regtest compatible
Fix unittests
Bonus
Merge changes/fixes from upstream repository
Commit changes to upstream repository
Electrum Client
Block header sync with server
Make regtest compatible
Adopt equihash validation
Validate header solution
Adopt new difficulty algorithm by Zawy
Regtest
Testnet
Mainnet (New algorithm not deployed yet)
Fix transactions
Regtest
Testnet
Mainnet
Deal with parent->child chain hierarchy
Release beta version
Test and fix hardware wallet support
Trezor
Ledger
UI updates and fixes
Test all extra features
Check and fix unit tests (ongoing)
Release final version
Bonus
Implement scheduled automatic-update of blockchain_headers file
Merge changes/fixes from the upstream repository
Notes:
Adopting new header format required more work than initially anticipated; BTG version must handle different header sizes for pre-fork and post-fork, but much Electrum header-related info was hard-coded in many places; this required more rework in more code and therefore more debugging and testing.
The same applies to the code for chunked header requests. The code parts/constants were tied to the BTC-specific difficulty algorithm and are used in different places with different meanings. This slowed progress during the early stages, but that’s largely behind us, now.
Initial bootstrap using a compressed blockchain_headers download has been implemented (PR pending). This will get you up and running pretty quickly.
We also implemented a fallback to checkpoints (Pre-Fork headers only) and in case this fails we will fallback to sync from Genesis block (very slow).
It would amazing to setup using checkpoints only (would be the fastest method) but that’s simply not possible with BTG. Unlike BTC, our difficulty changes with every block. This means that our checkpoints would need to include every block header since the fork. This makes checkpoints pretty useless. Therefore we decided to provide a compressed blockchain_headers file for download which we will update periodically (interval not decided yet).
Update on Hardware wallets
Trezor
Everything is working fine so far. We tested all desktop platforms with all address types and didn’t encounter any problem.
Test on Linux with transfer from/to all address types
it’s been a while since the last update. Sorry for that.
We worked hard behind the scenes to get ElectrumG ready for it’s full release including HW Wallets, improved syncing, bugfixes, stabilizing and so on.
But sadly due to the 51% attack on multiple coins, including BTG, we had to switch priorities.
Priority number 1 is, has always been and will always be: Decentralization!
I guess you already read about the upcoming network upgrade. Not an easy task and everyone is currently working day and night to make all needed changes to every bit of software (including ElectrumG) of the whole ecosystem. And it’s a lot
This means that with the upcoming network upgrade we will release a new version of ElectrumG too, including some improvements and partial or even full HW wallet support. Depending on the time we have to work on it.
can I replenish my deposit on the stock exchange now?
I am a miner, I have the extracted coin for supernova … if they stay on my account at the supernova pool, after hardfork coins are burned on the pool of prey or for them you do not have to worry?
at the moment the bitrex exchange has suspended withdrawal and replenishment of funds, they are waiting for you to make decisions, please tell me when will there be a hard plug of the gold network?
I can not withdraw funds from the supernova mining to the bitrex exchange
Coins sitting in any wallet - whether at Suprnova, an exchange, or a private wallet - are at no risk during an upgrade or fork.
The devs continue to work hard, and we will provide a date as soon as we can possibly provide a date.
We need to ensure everything is tested and working on testnet before making the software available for all the services, and then we need to give at least a week of notice for all our partners to deploy the new software.
The original target was end of June… we are trying to advance it as much as possible, but we can’t yet say when that will be.