Topic: ►►►[XBC] BitcoinPlus ►Official Thread◄官方公告◄◄◄ - page 23. (Read 407808 times)

2018-06-22 04:40 UTC

Difficulty
POW: 0.01442156
POS: 0.00024414
Coin Supply (XBC)
111009.53522037
614805 blocks
35 connections

Last Price
0.00440000
24hr Change
-1.72%
24hr High
0.00461279
24hr Low
0.00438456
24hr Volume:
0.29137009 BTC / 65.07450975 XBC

easy! yes thats great want to support! youre the one I have to say thank you! cheers

Hi,I will give you an address once we have the new client testing tx's.Thanks again

ok is there a developer bounty wallet for completed tasks , i will donate to?

Sync is the first part, then we have to go through every single PoS function to make sure the protocol is the same. Then we need to test PoS block generation, We only have 3 coins minus TX fees as coins were split it into lots of inputs. When we test block generation it would be helpful to have more coins to speed up the process. Once sync and block generation is in the bag Peter will rebase everything into Bitcoin 0.13.2. Using the 0.13 testnet test that SegWit will happily activate with PoS blocks and that everything still works after activation. Then we can create the 2.7 client for Windows, Mac and Linux and distribute.

We still need to do some bespoke code to make sure that 2.6 clients display correctly based on PROTOCOL_VERSION number. 2.6 shows as scrambled and 2.7 is blank but we can tell them apart with the PROTOCOL_VERSION, however anything with a higher PROTOCOL_VERSION than 2.7 We will let it display it normally as we can assume that the client will have a full substr message, this will make 2.7 the bridging client.

I'm currently spending close to full time hours on Bitcoin Plus at the moment. If it is possible Peter hopes to have old TX/Block disk position restored this week.

2018-06-20 14:52 UTC

Difficulty
POW: 0.01442156
POS: 0.00024414
Coin Supply (XBC)
110949.33577374
613729 blocks
37 connections

Last Price
0.00429408
24hr Change
-1.60%
24hr High
0.00470000
24hr Low
0.00417768
24hr Volume:
0.57938210 BTC / 132.89891821 XBC

Hi

JJMV is no longer a team member so you have not made a donation towards XBC unfortunately however JJMV did do great work on behalf of XBC in the past so it is not a wasted donation in that sense.

Wallet not found in blockexplorer!! Heya you should Post an existing one? Or is this this some Kind of Tor thing

I will send 2 xbc bitcoinplus! Should bring you at least a rack of cold beer! Keep up the great work! Staking xbc! Next bullrun coming latest arrival November! Cmon guys

2018-06-19 04:44 UTC

Difficulty
POW: 0.01442156
POS: 0.00024414
Coin Supply (XBC)
110881.45632767
612542 blocks
37 connections

Last Price
0.00425000
24hr Change
+0.54%
24hr High
0.00440324
24hr Low
0.00413000
24hr Volume:
0.79977644 BTC / 187.86148758 XBC

2018-06-18 04:47 UTC

Difficulty
POW: 0.01442156
POS: 0.00028817
Coin Supply (XBC)
110853.77852316
611792 blocks
37 connections

Last Price
0.00422728
24hr Change
+3.02%
24hr High
0.00487798
24hr Low
0.00397999
24hr Volume:
5.74912316 BTC / 1320.14600463 XBC

If we don't like fegwit I vote we fork XBC and have big blocks instead 

2018-06-17 09:22 UTC

Difficulty
POW: 0.01442156
POS: 0.00025358
Coin Supply (XBC)
110823.59386878
611137 blocks
35 connections

Last Price
0.00414790
24hr Change
-5.34%
24hr High
0.00438207
24hr Low
0.00405001
24hr Volume:
0.22177166 BTC / 53.33280210 XBC

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.

2018-06-16 10:16 UTC

Difficulty
POW: 0.01442156
POS: 0.00024414
Coin Supply (XBC)
110783.74455747
10379 blocks
33 connections

Last Price
0.00419162
24hr Change
+0.37%
24hr High
0.00438482
24hr Low
0.00403759
24hr Volume:
0.51774353 BTC / 121.19847884 XBC

2018-06-15 07:14 UTC

Difficulty
POW: 0.01442156
POS: 0.00024414
Coin Supply (XBC)
110747.50291768
609555 blocks
31 connections

Last Price
0.00412722
24hr Change
-1.60%
24hr High
0.00438474
24hr Low
0.00395990
24hr Volume:
1.25807540 BTC / 302.63494021 XBC

I can see where Peter has pushed a few commits to the xbcwalletsource repo to deal with compiler warnings during the compilation process.


https://github.com/bitcoinplusorg/xbcwalletsource/commit/d933f8c010fd6034166ac16df3f66c6020461a5a


https://github.com/bitcoinplusorg/xbcwalletsource/commit/49d312bda6f0186308c6e34f26b3830966d50ba7

https://github.com/bitcoinplusorg/xbcwalletsource/commit/d893c88ecbeb9579a9dc016514e2705f4ffaf45b

https://github.com/bitcoinplusorg/xbcwalletsource/commit/f5e66f794ba81834a9aec249316650ffed6098ec

2018-06-14 10:00 UTC

Difficulty
POW: 0.01442156
POS: 0.00024414
Coin Supply (XBC)
110719.98018137
608823 blocks
29 connections

Last Price
0.00411194
24hr Change
-6.15%
24hr High
0.00420532
24hr Low
0.00400578
24hr Volume:
1.69083881 BTC / 409.16919079 XBC

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.