Why do you Americans put up with these state differences anyway? The idea of moving up the road and having to change your driving licence and pay hideous amounts more tax seems very silly.
Shape up over there.
Are there not similar differences in laws between the states that make up the European Union? The US is a federation of states, not a single monolithic state. |
|
|
|
This problem has finally been identified and should be fixed in a revision release shortly. Please see the discussion that occurred in today's development meeting for details.
Just to be sure that we got the right issue, did everyone experiencing this have the "at least" fee option set in 0.14 (efficient has since been removed in 0.15)?
I do not remember ever changing that option. [EDIT: The only option I ever change from the default in bitcoin-qt is to enable coin-control features.] |
|
|
|
Damn - downloaded Core 15.0 for my Mac, went through all loading OK, then crashed just after it said 'done loading'. Tried a few times, restarted, tried again. Gave up.
Now back on 14.2 and need to totally download whole blockchain (since old one re-org'd by 15.0).
Grrrr.... Maybe wait for 15.x if you're on a 64Bit Mac?
If it is crashing consistently at the point where the main GUI window should open, you should try restarting with the '-resetguisettings' switch. Thanks, but I confess I have no idea how to do that! It would require me getting into terminal and using CLI, which I am not sure how to do. Well, I don't know anything about using MacOS so I can't give you a step-by-step... In Windows, you can right-click on the icon for a program and select properties, and there is a place where the command that will be executed when you click on the icon is, and you can add arguments to that line, just like you would in a CLI. I'm sure MacOS must have something similar. Another possibility would be to edit your 'bitcoin.conf' file and add a line with "resetguisettings=1". I think that should work, but you should remember to remove that line afterwards so it doesn't reset the GUI on every restart. GL  |
|
|
|
Damn - downloaded Core 15.0 for my Mac, went through all loading OK, then crashed just after it said 'done loading'. Tried a few times, restarted, tried again. Gave up.
Now back on 14.2 and need to totally download whole blockchain (since old one re-org'd by 15.0).
Grrrr.... Maybe wait for 15.x if you're on a 64Bit Mac?
If it is crashing consistently at the point where the main GUI window should open, you should try restarting with the '-resetguisettings' switch. |
|
|
|
Yeah there better not be a full reindex with 0.15.0 - I really can't be doing with that, I went through that process a few times in earlier releases when I had a power cut in my house.
Just loaded 0.15.0 rc3 on my laptop and no re-indexing was required. I hate to tell you, but...
Who am I supposed to believe here  If it's the former, I'm going to hold off on downloading the latest version for a good while. I did not have to re-index when upgrading from 0.14.2 to 0.15.0rc2 - but it does do a full rebuild of the UTXO database (format changed) which takes a while. Not nearly as long as a full re-index, though. From the release notes: Upgrade notice
One of the performance optimizations in Bitcoin Core 0.15.0 is an update to the format of the database that tracks spendable bitcoins. The first time you start Bitcoin Core 0.15.0 (or a later version), it will automatically begin this update, which will take from about 5 minutes to 30 minutes depending on the speed of your computer.
Graphical users can monitor the progress of the update on the Bitcoin Core splash screen; bitcoind users can monitor it in the debug.log file in their data directory.
If you later decide to downgrade to an earlier version of Bitcoin Core, please see the instructions in the release notes.
|
|
|
|
Problem solved! Running bitcoin-qt with the '-resetguisettings' switch fixed it. Thanks to MeshCollider on github for the fix! |
|
|
|
Most likely the developers did not even test the new version on Windows 7
Look at whether you have updated the NET Framework 2, 3 and 4 versions, if there is no update required and check again.
The affected machine has all available Windows 7 updates applied. Looking at the windows log files, I see the crash is definitely an access violation, so probably a null-pointer thing. I need to install a debugger I can attach to the process so I can see what's happening and where... I will try that after I get home from work tonight if I can make time. Thanks to all who have helped so far |
|
|
|
Judging by the logs, you use the TOR to connect the bitcoins client's
Turn off the TOR and try to start the client without it
And then show me the logs.
I do not use TOR. Bitcoin uses TOR by default if it's available, that's what accounts for the attempts to use TOR that you see in the log. |
|
|
|
Thanks for looking into this, Achow101 |
|
|
|
Install a more recent version of Windows. You immediately get rid of many problems, such as drivers. Alternatively, you can run a virtual machine with Windows 10. To create a virtual machine, use this software https://www.virtualbox.orgThanks for the advice, but I think the devs would probably want Bitcoin to work on Windows 7 also. [EDIT: I guess I should add that this has not been shown to necessarily be a Windows 7 problem. No one else seems to be reporting the issue, but no one on this thread has claimed to have it working on Win7 either, so it's still unclear. The problem may be unique to my personal situation for all I know. All I am sure of is that 0.14.2 release worked fine on this machine, and the 0.15.0 rc's have not worked.] |
|
|
|
Yes, I tried that... The only thing I saw that looked like an error was this, at the tail end:
Can you please post the entire thing? What you posted are not errors that matter. Yeah, I know - those were the only 'errors' I saw, but seemed harmless. Below is the full debug output from my latest attempt to start rc3: 2017-08-29 19:37:52 Bitcoin version v0.15.0rc3
2017-08-29 19:37:52 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-08-29 19:37:52 Assuming ancestors of block 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a have valid signatures.
2017-08-29 19:37:52 Using the 'standard' SHA256 implementation
2017-08-29 19:37:53 RandAddSeedPerfmon: 240344 bytes
2017-08-29 19:37:53 GUI: requestInitialize : Requesting initialize
2017-08-29 19:37:53 GUI: initialize : Running initialization in thread
2017-08-29 19:37:53 Default data directory C:\Users\djm\AppData\Roaming\Bitcoin
2017-08-29 19:37:53 Using data directory F:\Bitcoin
2017-08-29 19:37:53 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2017-08-29 19:37:53 Using config file F:\Bitcoin\bitcoin.conf
2017-08-29 19:37:53 Using at most 125 automatic connections (2048 file descriptors available)
2017-08-29 19:37:53 Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2017-08-29 19:37:53 Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2017-08-29 19:37:53 Using 4 threads for script verification
2017-08-29 19:37:53 scheduler thread start
2017-08-29 19:37:53 Allowing HTTP connections from: 127.0.0.0/8 ::1/128 10.0.0.0/24
2017-08-29 19:37:53 Binding RPC on address :: port 8332
2017-08-29 19:37:53 Binding RPC on address 0.0.0.0 port 8332
2017-08-29 19:37:53 Initialized HTTP server
2017-08-29 19:37:53 HTTP: creating work queue of depth 16
2017-08-29 19:37:53 Starting RPC
2017-08-29 19:37:53 Starting HTTP RPC server
2017-08-29 19:37:53 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2017-08-29 19:37:53 Registering HTTP handler for / (exactmatch 1)
2017-08-29 19:37:53 Registering HTTP handler for /wallet/ (exactmatch 0)
2017-08-29 19:37:53 Starting HTTP server
2017-08-29 19:37:53 HTTP: starting 4 worker threads
2017-08-29 19:37:53 Entering http event loop
2017-08-29 19:37:53 init message: Verifying wallet(s)...
2017-08-29 19:37:53 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2017-08-29 19:37:53 Using wallet wallet.dat
2017-08-29 19:37:53 CDBEnv::Open: LogDir=F:\Bitcoin\database ErrorFile=F:\Bitcoin\db.log
2017-08-29 19:37:53 Cache configuration:
2017-08-29 19:37:53 * Using 2.0MiB for block index database
2017-08-29 19:37:53 * Using 8.0MiB for chain state database
2017-08-29 19:37:53 * Using 290.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-08-29 19:37:53 init message: Loading block index...
2017-08-29 19:37:53 Opening LevelDB in F:\Bitcoin\blocks\index
2017-08-29 19:37:53 Recovering log #548
2017-08-29 19:37:53 Level-0 table #550: started
2017-08-29 19:37:53 Level-0 table #550: 179 bytes OK
2017-08-29 19:37:53 Delete type=0 #548
2017-08-29 19:37:53 Delete type=3 #546
2017-08-29 19:37:53 Opened LevelDB successfully
2017-08-29 19:37:53 Using obfuscation key for F:\Bitcoin\blocks\index: 0000000000000000
2017-08-29 19:37:58 LoadBlockIndexDB: last block file = 979
2017-08-29 19:37:58 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=28, size=27978569, heights=482183...482210, time=2017-08-27...2017-08-27)
2017-08-29 19:37:58 Checking all blk files are present...
2017-08-29 19:37:59 LoadBlockIndexDB: transaction index disabled
2017-08-29 19:37:59 Opening LevelDB in F:\Bitcoin\chainstate
2017-08-29 19:37:59 Recovering log #871312
2017-08-29 19:37:59 Level-0 table #871322: started
2017-08-29 19:37:59 Level-0 table #871322: 308 bytes OK
2017-08-29 19:37:59 Delete type=2 #870302
2017-08-29 19:37:59 Delete type=2 #870303
2017-08-29 19:37:59 Delete type=2 #870304
2017-08-29 19:37:59 Delete type=2 #870305
2017-08-29 19:37:59 Delete type=2 #870306
2017-08-29 19:37:59 Delete type=2 #870311
2017-08-29 19:37:59 Delete type=0 #871312
2017-08-29 19:37:59 Delete type=3 #871310
2017-08-29 19:37:59 Opened LevelDB successfully
2017-08-29 19:37:59 Using obfuscation key for F:\Bitcoin\chainstate: c15290b8f7b37d9d
2017-08-29 19:37:59 Loaded best chain: hashBestChain=000000000000000000e725b7df7ae4d183a9146f9ac3a0eb0ecd1aa0b152abda height=482210 date=2017-08-27 13:31:20 progress=0.997589
2017-08-29 19:37:59 init message: Rewinding blocks...
2017-08-29 19:38:00 Writing final batch of 0.00 MiB
2017-08-29 19:38:00 Committed 0 changed transaction outputs (out of 0) to coin database...
2017-08-29 19:38:00 init message: Verifying blocks...
2017-08-29 19:38:00 Verifying last 6 blocks at level 3
2017-08-29 19:38:00 [0%]...Compacting 1@0 + 1@1 files
2017-08-29 19:38:00 Generated table #871324@0: 1 keys, 207 bytes
2017-08-29 19:38:00 Compacted 1@0 + 1@1 files => 207 bytes
2017-08-29 19:38:00 compacted to: files[ 0 1 45 252 1025 0 0 ]
2017-08-29 19:38:00 Delete type=2 #871313
2017-08-29 19:38:00 Delete type=2 #871322
2017-08-29 19:38:01 [16%]...[33%]...[50%]...[66%]...[83%]...[99%]...Expanding@3 1+1 (2176269+2175089 bytes) to 5+1 (10877150+2175089 bytes)
2017-08-29 19:38:04 Compacting 5@3 + 1@4 files
2017-08-29 19:38:04 [DONE].
2017-08-29 19:38:04 No coin database inconsistencies in last 7 blocks (10964 transactions)
2017-08-29 19:38:04 block index 11290ms
2017-08-29 19:38:04 Reading estimates: 98 buckets counting confirms up to 25 blocks
2017-08-29 19:38:04 init message: Loading wallet...
2017-08-29 19:38:04 Generated table #871325@3: 38554 keys, 2174677 bytes
2017-08-29 19:38:04 Generated table #871326@3: 39065 keys, 2175256 bytes
2017-08-29 19:38:04 nFileVersion = 150000
2017-08-29 19:38:04 Keys: 0 plaintext, 228 encrypted, 0 w/ metadata, 228 total
2017-08-29 19:38:04 wallet 220ms
2017-08-29 19:38:04 setKeyPool.size() = 97
2017-08-29 19:38:04 mapWallet.size() = 633
2017-08-29 19:38:04 mapAddressBook.size() = 33
2017-08-29 19:38:04 mapBlockIndex.size() = 482235
2017-08-29 19:38:04 nBestHeight = 482210
2017-08-29 19:38:04 torcontrol thread start
2017-08-29 19:38:04 AddLocal([2601:190:580:93ac::559f]:8333,1)
2017-08-29 19:38:04 Discover: djm-PC - 2601:190:580:93ac::559f
2017-08-29 19:38:04 AddLocal([2601:190:580:93ac:b502:1772:28c5:87ea]:8333,1)
2017-08-29 19:38:04 Discover: djm-PC - 2601:190:580:93ac:b502:1772:28c5:87ea
2017-08-29 19:38:04 AddLocal([2601:190:580:93ac:c4:120b:881e:39d3]:8333,1)
2017-08-29 19:38:04 Discover: djm-PC - 2601:190:580:93ac:c4:120b:881e:39d3
2017-08-29 19:38:04 Bound to [::]:8333
2017-08-29 19:38:04 Bound to 0.0.0.0:8333
2017-08-29 19:38:04 init message: Loading P2P addresses...
2017-08-29 19:38:04 Generated table #871327@3: 39070 keys, 2174944 bytes
2017-08-29 19:38:05 Generated table #871328@3: 39113 keys, 2175622 bytes
2017-08-29 19:38:05 Generated table #871329@3: 39444 keys, 2176163 bytes
2017-08-29 19:38:05 Generated table #871330@3: 38780 keys, 2175602 bytes
2017-08-29 19:38:05 Compacted 5@3 + 1@4 files => 13052264 bytes
2017-08-29 19:38:05 compacted to: files[ 0 1 45 247 1030 0 0 ]
2017-08-29 19:38:05 Delete type=2 #869962
2017-08-29 19:38:05 Delete type=2 #869963
2017-08-29 19:38:05 Delete type=2 #869964
2017-08-29 19:38:05 Delete type=2 #869965
2017-08-29 19:38:05 Delete type=2 #869966
2017-08-29 19:38:05 Delete type=2 #869971
2017-08-29 19:38:05 Loaded 68037 addresses from peers.dat 361ms
2017-08-29 19:38:05 init message: Loading banlist...
2017-08-29 19:38:05 ERROR: DeserializeFileDB: Failed to open file F:\Bitcoin\banlist.dat
2017-08-29 19:38:05 Invalid or missing banlist.dat; recreating
2017-08-29 19:38:05 Flushed 0 banned node ips/subnets to banlist.dat 10ms
2017-08-29 19:38:05 init message: Starting network threads...
2017-08-29 19:38:05 net thread start
2017-08-29 19:38:05 addcon thread start
2017-08-29 19:38:05 init message: Done loading
2017-08-29 19:38:05 opencon thread start
2017-08-29 19:38:05 dnsseed thread start
2017-08-29 19:38:05 msghand thread start
2017-08-29 19:38:05 GUI: initializeResult : Initialization result: true
2017-08-29 19:38:05 GUI: Platform customization: "windows"
2017-08-29 19:38:05 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" ("Microsoft Authenticode(tm) Root Authority") () ()
2017-08-29 19:38:05 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" () () ("Copyright (c) 1997 Microsoft Corp.", "Microsoft Time Stamping Service Root", "Microsoft Corporation")
2017-08-29 19:38:05 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "4a:19:d2:38:8c:82:59:1c:a5:5d:73:5f:15:5d:dc:a3" () () ("NO LIABILITY ACCEPTED, (c)97 VeriSign, Inc.", "VeriSign Time Stamping Service Root", "VeriSign, Inc.")
2017-08-29 19:38:05 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "3f:8b:c8:b5:fc:9f:b2:96:43:b5:69:d6:6c:42:e1:44" ("Microsoft Root Certificate Authority 2011") () ()
2017-08-29 19:38:05 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "03:c7:8f:37:db:92:28:df:3c:bb:1a:ad:82:fa:67:10" () () ("VeriSign Commercial Software Publishers CA")
2017-08-29 19:38:05 GUI: PaymentServer::LoadRootCAs: Loaded 56 root certificates
2017-08-29 19:38:05 GUI: TransactionTablePriv::refreshWallet
2017-08-29 19:38:05 trying connection 172.104.78.159:8333 lastseen=57.2hrs
2017-08-29 19:38:05 tor: Error connecting to Tor control socket
2017-08-29 19:38:05 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect
2017-08-29 19:38:06 Added connection peer=0
2017-08-29 19:38:06 sending version (102 bytes) peer=0
2017-08-29 19:38:06 send version message: version 70015, blocks=482210, us=[::]:0, peer=0
2017-08-29 19:38:06 received: version (102 bytes) peer=0
2017-08-29 19:38:06 sending verack (0 bytes) peer=0
2017-08-29 19:38:06 sending getaddr (0 bytes) peer=0
2017-08-29 19:38:06 receive version message: /Satoshi:0.14.1/: version 70015, blocks=482519, us=73.119.168.246:6576, peer=0
2017-08-29 19:38:06 added time data, samples 2, offset -205 (-3 minutes)
2017-08-29 19:38:06 received: verack (0 bytes) peer=0
2017-08-29 19:38:06 sending sendheaders (0 bytes) peer=0
2017-08-29 19:38:06 sending sendcmpct (9 bytes) peer=0
2017-08-29 19:38:06 sending sendcmpct (9 bytes) peer=0
2017-08-29 19:38:06 sending ping (8 bytes) peer=0
2017-08-29 19:38:06 received: sendheaders (0 bytes) peer=0
2017-08-29 19:38:06 initial getheaders (482209) to peer=0 (startheight:482519)
2017-08-29 19:38:06 sending getheaders (997 bytes) peer=0
2017-08-29 19:38:06 sending feefilter (8 bytes) peer=0
2017-08-29 19:38:06 received: sendcmpct (9 bytes) peer=0
2017-08-29 19:38:06 received: sendcmpct (9 bytes) peer=0
2017-08-29 19:38:06 received: ping (8 bytes) peer=0
2017-08-29 19:38:06 sending pong (8 bytes) peer=0
2017-08-29 19:38:06 received: addr (31 bytes) peer=0
2017-08-29 19:38:06 trying connection 176.9.133.154:8333 lastseen=59.8hrs
2017-08-29 19:38:07 received: getheaders (997 bytes) peer=0
2017-08-29 19:38:07 Ignoring getheaders from peer=0 because node is in initial block download
2017-08-29 19:38:07 received: feefilter (8 bytes) peer=0
2017-08-29 19:38:07 received: feefilter of 0.00001000 BTC/kB from peer=0
2017-08-29 19:38:07 received: pong (8 bytes) peer=0
2017-08-29 19:38:07 Added connection peer=1
2017-08-29 19:38:07 sending version (102 bytes) peer=1
2017-08-29 19:38:07 send version message: version 70015, blocks=482210, us=[::]:0, peer=1
2017-08-29 19:38:07 trying connection 81.92.107.72:8333 lastseen=142.2hrs
2017-08-29 19:38:07 received: headers (25113 bytes) peer=0
|
|
|
|
Has anyone else had this problem? I tried installing RC2 on a Windows 7 machine, and after initialization, at the point where you would expect it to open the main GUI window, it just exits. I installed RC3 and it exhibits the same behavior.
The 0.14.2 client was running with no problems before I tried the release candidate... It's painful to revert now because 0.15.0 upgrades the UTXO database to a new format during installation.
I have installed. On Windows 10, works without errors. Try to run with: bitcoin-qt.exe -debug=<category> (Output debugging information (default: 0, supplying <category> is optional). If <category> is not supplied or if <category> = 1, output all debugging information.<category> can be: addrman, alert, bench, cmpctblock, coindb, db, http, libevent, lock, mempool, mempoolrej, net, proxy, prune, rand, reindex, rpc, selectcoins, tor, zmq, qt. ) After run & crash, look at the debugging information in the file debug.logThanks. Yes, I tried that... The only thing I saw that looked like an error was this, at the tail end: 2017-08-27 14:00:58 GUI: PaymentServer::LoadRootCAs: Loaded 56 root certifica
es
2017-08-27 14:00:58 tor: Error connecting to Tor control socket
2017-08-27 14:00:58 tor: Not connected to Tor control port 127.0.0.1:9051, tryi
g to reconnect
2017-08-27 14:00:58 GUI: TransactionTablePriv::refreshWallet
2017-08-27 14:00:59 trying connection 79.195.178.192:8333 lastseen=366.6hrs
2017-08-27 14:00:59 Added connection peer=0
2017-08-27 14:01:00 tor: Error connecting to Tor control socket
2017-08-27 14:01:00 tor: Not connected to Tor control port 127.0.0.1:9051, tryi
g to reconnect
2017-08-27 14:01:03 tor: Error connecting to Tor control socket
2017-08-27 14:01:03 tor: Not connected to Tor control port 127.0.0.1:9051, tryi
g to reconnect
2017-08-27 14:01:04 connection to 79.195.178.192:8333 timeout
2017-08-27 14:01:04 trying connection 81.163.206.173:8333 lastseen=175.4hrs
2017-08-27 14:01:04 connection from 213.5.31.38:54224 accepted
2017-08-27 14:01:04 Added connection peer=1
2017-08-27 14:01:04 connection from 52.192.180.114:40814 accepted
2017-08-27 14:01:04 connection from 54.191.174.46:38180 dropped (banned)
2017-08-27 14:01:04 received: version (106 bytes) peer=1
2017-08-27 14:01:04 sending version (102 bytes) peer=1
2017-08-27 14:01:04 send version message: version 70015, blocks=482210, us=[::]
0, peer=1
2017-08-27 14:01:04 sending verack (0 bytes) peer=1
2017-08-27 14:01:04 receive version message: /bitcoin-seeder:0.01/: version 600
0, blocks=350000, us=73.119.168.246:8333, peer=1
2017-08-27 14:01:04 added time data, samples 2, offset -209 (-3 minutes)
2017-08-27 14:01:04 sending alert (168 bytes) peer=1
2017-08-27 14:01:05 received: verack (0 bytes) peer=1
2017-08-27 14:01:05 sending ping (0 bytes) peer=1
2017-08-27 14:01:05 socket closed
2017-08-27 14:01:05 disconnecting peer=1
|
|
|
|
|
Has anyone else had this problem? I tried installing RC2 on a Windows 7 machine, and after initialization, at the point where you would expect it to open the main GUI window, it just exits. I installed RC3 and it exhibits the same behavior.
The 0.14.2 client was running with no problems before I tried the release candidate... It's painful to revert now because 0.15.0 upgrades the UTXO database to a new format during installation.
|
|
|
|
Instead of re-posting this FUD here, why didn't you just reply to this: https://bitcointalk.org/index.php?topic=2040221.msg21238565#msg21238565Note that Blockstream offer all their software patents under the DPL, (modified) IPA, individual licences and have a defensive pledge and that patent is only for sidechains and only in the US. Basically anyone can use that patent but if another group tries to litigate against someone then Blockstream can use it to protect the group(s) using it, if Blockstream ever tried to use that patent "offensively" it would not hold up in court.
Thats very high level because law is not simple but ultimately they are doing as much as they can to keep software development as open and protected from trolls as possible but there will always be people bringing half truths to sell a point like "ermahgerd patent means dey be trying to take ova Bitcoin!!!"
|
|
|
|
So if I have an old satellite cable dish I could theoretically use it to receive blocks from the satellite?
If yes, is there any tutorials you guys are aware of to set that up?
The README from the git repository should tell you pretty much everything you need to know: https://github.com/Blockstream/satellite |
|
|
|
Does this mean that my node is storing both blockchains in my files?
No. The BCH client was designed to fully separate from the BTC chain. If a client is designed to prevent "replay attacks" then that new client is actually a separate chain, where the two chains can no longer be in a competition. The block race competition only exists because the two chains are directly competing for dominance of a single chain, that is why "replay attacks" can exist. It is so, because the two chains are like mirror images. Since BCH has "replay protection", it is actually invisible to your BTC node, and vice versa. For you to store the BCH blockchain, you need a BCH client. That's all true - and also it wouldn't make any difference anyway, since the longest chain is determined by work done, not just which chain has the most blocks. If it was otherwise, anyone could fork any blockchain, force a low diff, and proceed to outrun the main chain. |
|
|
|
You will find the difficulty increase will be nearer 500%
I believe there is a hard limit of +400% for a single difficulty change. |
|
|
|
My hope is that BCC can close the gap and pass BTC in terms of blocks by that time.
Why? What difference do you think that will make? |
|
|
|
Has anyone considered the tax implications of now involuntarily owning BCH?
I'm trying to work that out with my accountant now. Wanted to dump all my BCH to pay off a mortgage and he's trying to wrap his head around the cost-basis and tax implications. I'm thinking they will treat it as if you mined it on the day the chain split. In other words, you will owe capital gains on the value of BCH the day it was created whether you cash it out or not. Pretty sure mined coins are taxed as regular income - not at the capital gains rate. Good point, not like mining then but still capital gains. I would imagine that coins "created" in any way at all would be considered exactly the same as mined coins, and taxed as normal income. IANAL, that's just my best guess. |
|
|
|
|
Show Posts
