Contact Bushstar about it.What is that link?

I don't see it on coinmarketcap "markets" website yet.I was going to post on their thread here but it seems to be locked now.Maybe Peter will give them a heads up though when he is around.

Try a wallet repair if the function exists with the client.

If you put a valid wallet.dat into the executables folder %appdata%>roaming>Devcoin there is no reason for it not to show your balance once it is on the correct and fully synced chain.Make sure your wallet.dat does not have any additional tags/names after the file name such as wallet.dat.devcoin or devcoin.wallet.dat

Name of wallet file can ONLY be wallet.dat

Not sure if devcoin allows importpriv key comand in the console but if you have your private key you could import it into your new wallet.To get private key for any address simply open the console and enter the dumpprivkey input.Just type:     dumpprivkey[your wallet address]      .

Another option is rescan/reindex or even zapwallettxes but ensure you back up your wallet.dat file before it because it will delete everything from your wallet, then rescan the blockchain from block 0 for every transaction that matches your wallet addresses.This is mainly used for tx's that haven't confirmed.

Will you be helping out any coins affected by the cryptopia closure with a free listing like Nova excahange are apparently doing?

Peter maybe we can get XBC news and updates losted through this service.It works through api too so news feeds would be realtime as they are posted ? https://www.coingecko.com/en/why_beam

Yep decentralized exchanges where developers can load up their own client are the way to go alright.Any suggestions?

On another note I heard Novaexchange are accepting listings from coins affected by cryptopia closure and developers are asked being to contact them.Not sure how good the exchange is but maybe something worth looking into?

Cryptopia is gone bust now.Some developers from other coins are petitioning them to release their community's coins so maybe its worth sending them or the liquidators an email from your official email address or something?

All current markets are listed here https://coinmarketcap.com/currencies/bitcoin-plus/#markets

I'd say even a few regular tweets in the right direction or the odd pm to any services people would like to see us on such as shapeshift,changelly etc would be agreat help.The larger the voice we have the more chances of being heard by these people.

We are near the final stages now unless something else goes wrong.We were almost there before this until bugs started cropping up.

No.The 1:1 swap back in 2015 was for coins off an old dead chain that was abandoned.

Have you installed the libevent-dev dependency?

Some other trivial features were proposed such as direct links to exchanges,blockexplorer etc but the whole issue around security may prevent this.No point in spending endless time and effort ensuring a secure functional client and then add in some unnescessary cosmetic stuff that adds no real value with the potential to undermine the important stuff.I would personally have no links whatsoever coming off the wallet.

Some progress, we have found the issue for the blockchain sticking at block 472,474 but it now gets stuck at block 590,436 with the same error as before though the cause will be different as the previous issue is now resolved.


Also client version now displays correctly locally in the GUI.Peter spotted the issue where it got stuck previously, thought we were going to get a full sync but it stopped three weeks short. Adding additional logging to both 2.6 and 2.7 now.

Old clients were notoriously problematic like that but the 2.7 client will sync much better. The issue here is to do with the client rejecting a valid block for an invalid stake target.The block header sync completes fine with the whole chain, just whole block validation that fails.

We need to compare the values being used to compute the target and see where they differ between 2.6 and 2.7.We now have added the same level of debugging to CheckStakeKernelHash in 2.6 and are waiting for it to sync to the same point that 2.7 fails to see the output.

Also adding additional logging directly into the CheckStakeKernelHash function to see the state of every variable used to computer the PoS target.Will use git to compare diffs and presume that there will be a noticeable difference between variables in 2.6 and 2.7 as the CheckStakeKernelHash function is not the same as they cannot be the same due to the large differences between the codebases.

We have found the exact line of code where 0.13 stops syncing, basically PoS hash does not meet the target. The block is Decemeber 2017. Not sure if it is a bit of a rogue block or of the issue is with the new client.Peter Will get all values for CheckStakeKernelHash from 2.6 and compare tomorrow.

Old version sends 112 bytes non-standard, Bitcoin sends 88 bytes.

Two options, the first is applied currently that allows the clients to sync. 0.2.7 has no subver set at all, so 0.2.6 shows it as blank and other 0.2.7 clients also show as blank in 0.2.7. 0.2.6 show incorrectly in 0.2.7 as well, we'd want to hide that and possibly just show the PROTOCOL_VERSION instead. 0.2.7 would be the bridge and newer clients can behave as normal. This is a bit hacky but functional.
Option two is to set 0.2.7 to use 112 bytes the same as 0.2.6. It is non-standard and you'd have to break every subsequent versions in the same way. The plus here is that versions should show correctly between new and old.

If we go for the hacky solution now then we do not need to make changes to compensate for this in version 0.2.8 sort of thing, like when porting 0.14 to Bitcoin Plus it can then just connect to the 0.2.7. So 0.2.7 will bridge new and old versions.
I'd prefer it to show the subver but then you always have to support bespoke code.
I'll send some screens of what the hacky route looks like. We can pretty much remove the info from display in the GUI as it was never shown in the 0.2.7 release.
Basically hide the subver in the GUI and getpeerinfo.
There's going to be some complaining about broken subver, basically we'd need to explain that it was non-standard in the past and moving to standard will mean that 0.2.7 has no subver at all so that 0.2.6 will not reject it but that 0.2.8 will return to normal and have standard handshake. That's probably the way to do it but it is up to you. The other way will keep subver intact and displaying correctly.

First option we get to go standard Bitcoin in the future.We do not compromise anything by dropping subver, we can identify versions using protocol version and it might be straight forward to use that to lookup subver and replace broken strings in the GUI and console.The more vanilla you are the easier it is to follow Bitcoin developments.

Bitcoinplus [XBC] now added to OctaexOctaex & Tradebytrade  https://coinmarketcap.com/currencies/bitcoin-plus/#markets


Bitcoin Plus Markets

#   Source   Pair   Volume (24h)   Price   Volume (%)                   Updated
1    Octaex    XBC/BTC    $46,720    $49.21    47.48%            Recently
2    Trade By Trade    XBC/USDT    $21,534    $50.25    21.88%    Recently
3    Trade By Trade    XBC/BTC    $16,784    $51.69    17.06%    Recently
4    Poloniex    XBC/BTC    $12,304    $51.72    12.50%            Recently
5    Cryptopia    XBC/BTC    $946    $53.80    0.96%                    Recently
6    CoinExchange    XBC/BTC    $117    $54.95    0.12%            Recently
7    Trade Satoshi    XBC/BTC    $0    $47.60    0.00%            Recently
8    Trade Satoshi    XBC/DOGE    $0    $114.40    0.00%            Recently
9    Trade Satoshi    XBC/LTC    $0    $140.18    0.00%            Recently