https://gyazo.com/b2a825aa04208fe287cc67e487d61298
https://gyazo.com/87abdb3d35fa32d48fee57c98b03e079

please look title...

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 read instructions at https://bitcoincore.org/en/contact/.

Describe the issue

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

Expected behaviour

Tell us what should happen

Actual behaviour

Tell us what happens instead

Screenshots.

If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.

What version of bitcoin-core are you using?

List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.

Machine specs:

• OS:
• CPU:
• RAM:
• Disk size:
• Disk Type (HD/SDD):

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

This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.

wallet rescans, shows no balance.

(1) a dynamic explorer with a rich list or coin holder distribution table that we can use to verify the supply information and

(2) a list of addresses that contain any team/developer controlled tokens, privately allocated tokens (locked and unlocked), or tokens allocated for future use/distribution (e.g. marketing, development purposes, bounty programs etc)?

Please supply this information to CMC and they will update the market cap. This would mean a lot for your coin :)

ubuntu server

2018-01-16 12:59:18 mapBlockIndex.size() = 502544
2018-01-16 12:59:18 nBestHeight = 477890

24654 blocks left

receive version message: /BitcoinXCore:0.15.1/: version 70015, blocks=502590, us=52.166.181.96:54218, peer=4
2018-01-16 12:59:56 ERROR: AcceptBlockHeader: block 000000000000000000a27a7ae25106d14f125d129486d870e9b35b2adee00e46 is marked invalid
2018-01-16 12:59:56 ERROR: invalid header received
2018-01-16 12:59:56 ProcessMessages(headers, 162003 bytes) FAILED peer=0
2018-01-16 12:59:58 receive version message: /BitcoinXCore:0.15.1/: version 70015, blocks=502590, us=52.166.181.96:53596, peer=5
2018-01-16 13:01:41 ERROR: AcceptBlockHeader: block 000000000000000000a27a7ae25106d14f125d129486d870e9b35b2adee00e46 is marked invalid
2018-01-16 13:01:41 ERROR: invalid header received
2018-01-16 13:01:41 ProcessMessages(headers, 162003 bytes) FAILED peer=3

sync fail @ 95%
tried 3 times

I run a full node with version 0.16.3。When I use sendrawtransaction methed send transaction，i get a error--“min relay fee not met”。
This is my raw data：
0100000001269b87f70c8bc09e56d78895a21eb9b3a9add85203f4f817a16d4975fc4bbcdf000000006b48304502210095c2fd31c431a692f63b33d1a4e3bf3732bd19117522d0fe1554de9f675123890220441d0d94fbcdf05adb394154c0c23e3fca9f6293219f98c2639f10f99f1b5455c12102699f6c123253ace707345b7c11ea67b8f432f1c05550d0339e786b0992437a6fffffffff0200ca9a3b000000001976a914c13aacee24de4a7ca2d7f732d6a94e57a886043888ac0050d6dc010000001976a914f864b6f3dc70c46845efacf4acb281a839b625af88ac00000000

My node's relayfee is 0.1BCX.This Transaction's fee is 10BCX。
Can any one tell me why? Thank you!!

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 read instructions at https://bitcoincore.org/en/contact/.

Describe the issue

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

Expected behaviour

Tell us what should happen

Actual behaviour

Tell us what happens instead

Screenshots.

If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.

What version of bitcoin-core are you using?

List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.

Machine specs:

• OS:
• CPU:
• RAM:
• Disk size:
• Disk Type (HD/SDD):

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

This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.

Still Stuck on block 501450 with Wallet of B2x "Bitcoin2x Core version v0.15.1.0-92a0756-dirty (64-bit)"
solution #15 don't work for me

Use config file "bitcoin2x.conf" with
addnode=46.4.116.70
addnode=136.243.111.195
addnode=138.201.122.203
addnode=46.28.207.57
addnode=89.163.216.76

Still hangs on this info

And error in debug.log are:

2018-03-02 15:30:05 Opened LevelDB successfully
2018-03-02 15:30:05 Using obfuscation key for R:\Bitcoin2X\chainstate: 2b62ab56f39e613a
2018-03-02 15:30:05 Loaded best chain: hashBestChain=00000000000000000015c5471244cd732db51b772891efe775887c053c25d2b3 height=501450 date=2017-12-28 18:00:28 progress=0.943684
2018-03-02 15:30:05 init message: Rewinding blocks...
2018-03-02 15:30:07 init message: Verifying blocks...
2018-03-02 15:30:07 Verifying last 6 blocks at level 3
2018-03-02 15:30:07 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2018-03-02 15:32:32 No coin database inconsistencies in last 7 blocks (15962 transactions)
2018-03-02 15:32:32 block index 175602ms
2018-03-02 15:32:32 init message: Loading wallet...
2018-03-02 15:32:33 nFileVersion = 150100
2018-03-02 15:32:33 Keys: 2004 plaintext, 0 encrypted, 2004 w/ metadata, 2004 total
2018-03-02 15:32:33 wallet 112ms
2018-03-02 15:32:33 setKeyPool.size() = 2000
2018-03-02 15:32:33 mapWallet.size() = 201
2018-03-02 15:32:33 mapAddressBook.size() = 3
2018-03-02 15:32:33 mapBlockIndex.size() = 531993
2018-03-02 15:32:33 nBestHeight = 501450
2018-03-02 15:32:33 torcontrol thread start
2018-03-02 15:32:33 Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired
2018-03-02 15:32:33 Bound to [::]:8333
2018-03-02 15:32:33 Bound to 0.0.0.0:8333
2018-03-02 15:32:33 init message: Loading P2P addresses...
2018-03-02 15:32:33 Loaded 6733 addresses from peers.dat 41ms
2018-03-02 15:32:33 init message: Loading banlist...
2018-03-02 15:32:33 init message: Starting network threads...
2018-03-02 15:32:33 net thread start
2018-03-02 15:32:33 dnsseed thread start
2018-03-02 15:32:33 init message: Done loading
2018-03-02 15:32:33 addcon thread start
2018-03-02 15:32:33 opencon thread start
2018-03-02 15:32:33 msghand thread start
2018-03-02 15:32:33 GUI: Platform customization: "windows"
2018-03-02 15:32:33 GUI: PaymentServer::LoadRootCAs: Loaded 57 root certificates
2018-03-02 15:32:33 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537583, us=84.29.235.177:50096, peer=1
2018-03-02 15:32:33 receive version message: /Satoshi:0.15.1/: version 70015, blocks=511653, us=84.29.235.177:50095, peer=2
2018-03-02 15:32:33 ProcessMessages(headers, 173938 bytes): Exception 'ReadCompactSize(): size too large: iostream error' caught
2018-03-02 15:32:33 ProcessMessages(headers, 173938 bytes) FAILED peer=1
2018-03-02 15:32:35 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000000000004b269ece007638e0992a83ac12210565a45d101544dae2, not-hardfork, incorrect block version (code 16)
2018-03-02 15:32:35 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000000000004b269ece007638e0992a83ac12210565a45d101544dae2, not-hardfork, incorrect block version (code 16)
2018-03-02 15:32:35 ERROR: invalid header received
2018-03-02 15:32:35 ProcessMessages(headers, 162003 bytes) FAILED peer=2
2018-03-02 15:32:44 Loading addresses from DNS seeds (could take a while)
2018-03-02 15:32:44 141 addresses found from DNS seeds
2018-03-02 15:32:44 dnsseed thread exit

2018-03-02 15:32:46 receive version message: /Satoshi:0.15.1/: version 70015, blocks=511653, us=84.29.235.177:50272, peer=3
2018-03-02 15:32:52 receive version message: /Satoshi:0.15.1/: version 70015, blocks=511653, us=84.29.235.177:50361, peer=4
2018-03-02 15:32:58 receive version message: /Satoshi:0.15.99/: version 70015, blocks=511653, us=84.29.235.177:50365, peer=5
2018-03-02 15:32:59 receive version message: /Satoshi:0.15.1/: version 70015, blocks=511653, us=84.29.235.177:50447, peer=6
2018-03-02 15:32:59 receive version message: /Satoshi:0.15.1/: version 70015, blocks=511653, us=84.29.235.177:50448, peer=7
2018-03-02 15:33:03 receive version message: /Satoshi:0.15.1/: version 70015, blocks=511653, us=84.29.235.177:50452, peer=9
2018-03-02 15:33:14 receive version message: /Satoshi:0.16.0/: version 70015, blocks=511653, us=84.29.235.177:50543, peer=10
2018-03-02 15:33:20 receive version message: /Satoshi:0.14.2/: version 70015, blocks=511653, us=84.29.235.177:50631, peer=11
2018-03-02 15:33:51 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537584, us=84.29.235.177:50974, peer=13
2018-03-02 15:35:08 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537584, us=84.29.235.177:51831, peer=15
2018-03-02 15:36:26 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537585, us=84.29.235.177:52737, peer=17
2018-03-02 15:37:44 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537585, us=84.29.235.177:53606, peer=19
2018-03-02 15:39:01 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537585, us=84.29.235.177:54469, peer=21
2018-03-02 15:40:19 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537585, us=84.29.235.177:55335, peer=23
2018-03-02 15:41:36 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537585, us=84.29.235.177:56208, peer=25
2018-03-02 15:41:51 receive version message: /Satoshi:0.13.1/: version 70014, blocks=511653, us=84.29.235.177:56383, peer=26
2018-03-02 15:42:54 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537586, us=84.29.235.177:57176, peer=28
2018-03-02 15:43:38 socket recv error De externe host heeft een verbinding verbroken. (10054)
2018-03-02 15:44:11 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537586, us=84.29.235.177:58066, peer=31
2018-03-02 15:45:29 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537586, us=84.29.235.177:58842, peer=33
2018-03-02 15:46:47 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537587, us=84.29.235.177:59804, peer=35
2018-03-02 15:47:39 Timeout downloading headers from peer=2, disconnecting
2018-03-02 15:47:39 receive version message: /Satoshi:0.14.2/: version 70015, blocks=511653, us=84.29.235.177:60417, peer=36
2018-03-02 15:47:55 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000000000004b269ece007638e0992a83ac12210565a45d101544dae2, not-hardfork, incorrect block version (code 16)
2018-03-02 15:48:04 ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 0000000000000000004b269ece007638e0992a83ac12210565a45d101544dae2, not-hardfork, incorrect block version (code 16)
2018-03-02 15:48:04 ERROR: invalid header received
2018-03-02 15:48:04 ProcessMessages(headers, 162003 bytes) FAILED peer=3
2018-03-02 15:48:04 receive version message: /Satoshi:0.15.1/: version 70015, blocks=537588, us=84.29.235.177:60697, peer=38
2018-03-02 15:48:09 receive version message: /Satoshi:0.15.99/: version 70015, blocks=511653, us=84.29.235.177:60701, peer=39

Please Info how to get it working?

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 read instructions at https://bitcoincore.org/en/contact/.

Describe the issue

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

Expected behaviour

Tell us what should happen

Actual behaviour

Tell us what happens instead

Screenshots.

If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.

What version of bitcoin-core are you using?

List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA.

Machine specs:

• OS:
• CPU:
• RAM:
• Disk size:
• Disk Type (HD/SDD):

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

This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.

I have all the files on my external disk, but I've installed the new wallet. Now it's telling me that's it's starting up for the first time and that I need to download all the blocks again. Is there a way to get the wallet working with the files on my external disk?

Hey all,

Long story short, I forced close via the task manger the BCX Qt wallet while it was scanning the private key, it was at 1%.

Now when I wanted to import the key again, it didn't re-scan, it just gave me null.

What makes me sure that there are funds in the address I'm importing it's private key is that I had funds before the fork and moved the funds after the fork.

Now I don't know what to do, need help please.

Thanks in advance.

who provide bcx version Support insight-api ?

like : https://bcx.info/

THK !

The website isn't working for a while now.

Does anybody have a list of known working BitcoinX Peers that I can manually add? My client is only connected to 1-2 peers.

see the title

There is a chance to generate dust txout when use sendtoaddress rpc interface.

is there any mining software?
or any mining pool?

SHA256 , Equihash, or other? What's it ?

I already have a copy of the blockchain from running a Bitcoin Core node. I have copied the blocks & chainstate folders into the BitcoinX directory and am reindexing using the Core data, but obviously they will diverge at the fork. How do I sync up to BitcoinX without having to re-download the whole blockchain? Can I use invalidateblock at the time of the fork?

Why it downloads binaries (boost) instead of source? Does it check signatures of the binaries?

It would be safer if only source code is downloaded.

Hello
I don't want to sync all the blocks
Can I use another wallet?
If you can, please tell me
Thanks.

HI,
1,I have two wallet softwares. one is for testintenet, other is normal. they are both have years behind. why like this? which one should be will work?
2. I let software working all morning. It doesn't have any change. how to sychronizate wallet soon? Do they have data package download?

What is this "valid-fork"? Bug or a feature?

$ ./bitcoinx-cli getchaintips
[
  {
    "height": 512402,
    "hash": "000000000006b44c23948f0785ae40b03ad521ae6d8ec09997955cd7a9d0027e",
    "branchlen": 0,
    "status": "active"
  }, 
  {
    "height": 512342,
    "hash": "0000000000041e4c8fab5b616142f21f3936cf58c950c0ccb0988837ceb1ec6f",
    "branchlen": 1,
    "status": "valid-fork"
  }
]

Version (built from source):

./bitcoinxd --version
BitcoinX Core Daemon version v0.16.1

When to ore mine?

any static node please?
and what algorithm for mining?

Using windows client debug mode -> console

dumpwallet "a"

not possible error code -8

Has anyone got a synced node that can share their peer ip addresses/list?

Many thanks

To whom it may concern. Could you please provide with me some information on how to import private keys into the BCX wallet. I like the idea of this project and would like to claim the tokens. I held BTC in a paper wallet at the time of this fork. Any help would be greatly appreciated.

keep up the good work

(From my understanding I need to enter a command into the command console followed by the private key that held the BCX? If so could someone be kind enough to explain in simple terms how to perform such a process xx)