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

How to get 20% per year, If I plan to hold this coin?

2018-04-24 06:12 UTC

Difficulty
POW: 0.01442156
POS: 0.00028931
Coin Supply (XBC)
108797.22585934
568559 blocks
30 connections

Last Price
0.00677386
24hr Change
+10.25%
24hr High
0.00677386
24hr Low
0.00608148
24hr Volume:
6.89320977 BTC / 1073.68394059 XBC

Awesome thanks for the info. I'll leave Tor off for the time being then since it seems to be working fine without it

It should still work with Tor.I ran it there and it had almost 30 connections but took ages to get the initial connection.It makes no difference to performance re:staking etc on standard I2P and you should always have at least 4 connections and much quicker to sync.

Tor is only for extra privacy layer but its going to be an external client after the upgrade anyway because we can't get the native client to work on 0.13 version.We will try to resolve that later of course because some community members prefer the client to have native Tor.

So whilst I did get it synced without Tor, I can't get it to work with Tor anymore.

Is it better to have it running with Tor or will it not affect the usage really?

Great got it thanks. Turning Tor off for now has got it syncing up.

Nice one!

2018-04-23 06:16 UTC

Difficulty
POW: 0.01442156
POS: 0.00029347
Coin Supply (XBC)
108769.03408251
567755 blocks
28 connections

Last Price
0.00614411
24hr Change
+18.88%
24hr High
0.00636055
24hr Low
0.00516818
24hr Volume:
12.03406501 BTC / 2130.85050662 XBC

If you are running it on Tor you could try switching over to standard I2P connection to get it synced.Sometimes the Tor wallet can find it hard to connect to relays due to it using an older Tor bundle.

If that doesn't work maybe backup wallet.dat and keys for any addresses with balances on them.Then slide out your wallet.dat from the data files in (search for  %appdata% ) and let it load with a new wallet.dat and see if it syncs.If it works just slide back in the original one.

Hi - I'm having a bit of trouble in that I've been away for a few days so turned my computer off. Before then my wallet was all up to date and in sync, now I can't get any connections at all though, despite having left the wallet open for hours with a continuous internet connection.

Not sure why it's decided it doesn't want to connect but any help would be great.

Thanks

2018-04-22 11:06 UTC

Difficulty
POW: 0.01442156
POS: 0.00024414
Coin Supply (XBC)
108747.37381132
567165 blocks
25 connections

Last Price
0.00531999
24hr Change
+5.50%
24hr High
0.00532000
24hr Low
0.00485604
24hr Volume:
1.37853117 BTC / 272.02247897 XBC

The work will be completed one way or the other.Its just a matter of time.

We arent a gambling site,lottery,online mall?Are you on the right thread?

Alright... thanks for the tech update. It was thorough.

Nice to have the additional developer.

Not sure about a gambling site but the lottery and an online mall sounds interesting and it would help with funding server costs etc if viable.

2018-04-21 08:49 UTC


Difficulty
POW: 0.01442156
POS: 0.00029501
Coin Supply (XBC)
108690.01491157
566293 blocks
29 connections

Last Price
0.00513806
24hr Change
-4.23%
24hr High
0.00540274
24hr Low
0.00498967
24hr Volume:
1.81541207 BTC / 351.44027224 XBC

The code change for 2.6 is as follows in main.cpp in the ProcessMessage function.
-        if (!vRecv.empty())
-            vRecv >> pfrom->strSubVer;
+        if (!vRecv.empty()) {
+            try {
+                vRecv >> pfrom->strSubVer;
+            } catch (std::ios_base::failure& e) {
+                pfrom->strSubVer = "/bitcoinplus:2.7.0/";
+            }
+        }
All it does is it tries to get the version from the remote client and if it fails set it to bitcoinplus:2.7.0. That gets the two versions talking to one another.

We did not find a reason why the two would not talk as the handshake and sending versions seems to be identical between the two, 2.6 sends and receives version to itself and 2.7 can also talk to itself but they will not exchange version between them. Once they are connected then messaging between versions seems to be fine.
The 0.13 client synced all the way up to block 472,460 before it hit an issue, will investigate now.
Actually the client also fails to share its block height properly as part of the handshake.


We have to got to get this working without touching the original client. We think that the issue is going to be serialisation of the messages. That's the next thing to look at as both version and height do not send correctly as part of the version message.

We cannot see why the subversion string in the version message is not readable by other clients, serialisation appears almost identical in XBC as BTC 0.7.
On the 0.13 client, you can run it and sync the majority of blocks.
Checking the peers tab in the debug window is showing no peer versions.
Other clients get a CDataStream error when 0.13 connects.
This problem has been reported rarely for other altcoins. It does not understand smessage messages.

0.13 can talk to 0.13 without the subver issue.
There's an issue syncing the chain on 0.13 but I stopped working on the sync to go back to the subver issue.
I think that other messages may be affected by this issue as well.



The 2.6 client gets the version message, parses it fine until it gets to the subver string then throws an errors. As a result it cannot read the block height that comes after. The substr issue is the issue to look into, could be due to sending serialised string as the numbers before worked.

We now have another developer using his free time going through what has been done in order to diagnose the problem and suggest some workarounds.Its a slow tedious process mainly due to the time constraints of each developer involved.

Hi team

So... closing Q1 it was reported that the developers ran into some obstacles that got them baffled. Can it be shared what they are working on now?

Thanks

2018-04-20 05:53 UTC

Difficulty
POW: 0.01442156
POS: 0.00024414
Coin Supply (XBC)
108564.72505321
565352 blocks
26 connections

Last Price
0.00540166
24hr Change
+2.32%
24hr High
0.00542395
24hr Low
0.00520600
24hr Volume:
1.96634160 BTC / 369.32862938 XBC

2018-04-19 08:06 UTC

Difficulty
POW: 0.01442156
POS: 0.00024414
Coin Supply (XBC)
108540.95902914
564669 blocks
29 connections

Last Price
0.00523025
24hr Change
-1.41%
24hr High
0.00537432
24hr Low
0.00492422
24hr Volume:
4.56950165 BTC / 877.68567136 XBC

Buy support still poor on poloniex but volume has improved at least.