An electrum-style light CBX wallet will be possible after phase 2 of Roadmap; although it is not part of roadmap right now. I think it's a good idea, however, so we can definitely keep this idea in mind as a future project.

The snapshot approach with re-using same private keys was exactly what we intended to do with CBXi. Still seen as a 50 000.$ "swap" by Cryptopia.


A "fork" is pretty much a common occurence in the altcoin world and it's not considered a swap by Cryptopia, this is confirmed by one of their admins.


Did everybody miss this? I think it's a pretty major idea.

Well people here complain about not being listed on bittrex or polo all the time, and now you guys don't mind we lose Cryptopia? We are just changing one thing in our development of Vault 3.0.0 - so that we don't call Vault 3.0.0 a "swap". A swap is an expensive word - to put things in perspective:

With the new sharp rise of the BTC, exchanges did not readjust their listing fees quickly - and, surprisingly they are noticing that, they can still charge the old BTC fees and still coin developers are paying these new inflated prices (!!!). One reason for this is new coins are created by crowdfunding ICO process; now exchanges want their share of the pie and are getting away with it.

Cryptopia charges 5 million DOT for listing a new coin which is 50 000.$
Bittrex charges anywhere from 5000$ to 15 000.$
even a new exchange like Coss.io charges 17 000.$

Now, CBX is a second-gen coin from 2013, so we never had a huge ICO development fund; it would be counter-productive for us to pay those listing fees, even if we could. So being listed on a good exchange is a valuable strategic advantage we should strive to maintain. And yes, we keep asking new exchanges to list CBX as we meet them; but guys, since you are mentioning this, you are more than welcome to join us and roll up your sleaves and send in some requests to exchanges as well.

All this being said, we are negociating with people from another crypto who want to create a new exchange, which would be CBX (and said coin) centered. Stay tuned.

Roadmap 2017 status report!

We have been discussing with Cryptopia for some time now, about the upcoming CBXi swap: long story short, there is good news and there is bad news. Let's start with the good news.

A few people had brought up the risk of CBX getting delisted from Cryptopia because of our development of Vault 3.0, and the good news is we will stay at Cryptopia even after Vault 3.0 is officially introduced.

CBX has always been well served by Cryptopia and thanks to the latest crypto world developments and good management, the exchange Cryptopia is moving up, becoming gradually more important and influential.

Now the bad news is, to stay at Cryptopia, Vault 3.0.0 cannot be a coin swap.


What this means is, we need to go back to our initial and time-consuming approach of keeping the old CBX blockchain into Vault 3.0, and not be creating a new ticker or a new coin (it's not going to be CBXi).

Essentially, the 2017-2018 roadmap stays the same: new look, new Vault 3.0, masternodes, PoSP, anonymity with zerocoin algo, etc...  Just we can't make Vault 3.0 be a swap. Therefore, although we are not losing the work previously done, we need to find the way to make the new Vault 3.0 be able to understand and continue the historic CBX blockchain. It's going to take more time to do this, hopefully not too much time; and we feel the additional time required is worth the strategic advantage of staying on a good and valuable exchange like Cryptopia.

I'm not sure how I can help you here; this is the Crypto Bullion's forum thread and we have no control over Pesobit's (PSB) servers, we're not the same team...

In the meantime, we benefit from the very good staking algo that currently pays me 8-15% per annum!

Roadmap 2017 status report!

I have to report that things are looking pretty good right now; the implementation of mutex, which was one of the very innovative approaches to Vault 3 and masternodes is a success so far. Also, the patch from Zerocoin which was reported the last time as a fix to a wekness will be implemented using the github merge procedure, so it is no longer an issue.

We also had an issue with block timing, which has been corrected just today; we are currently testing internally the latest daemon to make sure it is running smoothly - last time it was with this testing that we isolated certain problems that we are correcting now.

Another team is working on the GUI interface (the "qt"), and putting together the new visuals for CBXi: no longer gold, we are turning to a "platinum" look - but shhhhh. I will let you discover the rest when the Vault 3.0.0 rolls out.

Still no final date for the alpha testing phase, but it's coming...

In your case you have 300 CBX in one Vault, but I assume they came in as 2 separate inputs (one 200 CBX and one 100 CBX), so in effect all 300 CBX are staking but as 2 separate inputs within the same Vault/address.

We are still ironing out the details, and trying to make this the simplest procedure possible: in order to receive your CBXi, all you will need to do is run Vault 3.0.0 (and enter your password if you had encrypted your CBX previously). Vault 3.0 will appropriate itself your old CBX addresses and your new CBXi coin will appear in your new Vault 3.0.0. (I am using CBXi here, as clearly this ticker is winning the poll)

We will let you know when Vault 3.0 is ready and from what date will this swap procedure be open.

End of sparktokens ICO CBX refund period

I have been notified that there are still some Quintessence ICO investors who have not claimed yet their CBX contribution back from that ICO which did not gather enough CBX for development. While what is left is only a small percentage of the total ICO contribution, we don't want to make people who want their CBX to lose it.  There was ample time for SPK contributors to answer back to the email which was sent to all and claim their CBX but this claim period will now close in 30 days, starting today. After this 30 day period is over, it will not be possible to claim ICO CBX and the leftover CBX from the ICO shall be transfered to Foundation and used for development and bounties. To make a claim now, the best way is to reply to the official email which was sent to you (none bounced back) using that same address which was entered in the ICO program; otherwise please write to me by PM, here in Bitcointalk, and please provide your email address that you had given at ICO time and we will proceed to verify your credentials.

Roadmap 2017 status report!

An important part of the anonymity provided by the upcoming BPNs, will be derived from existing code from the Zerocoin protocol  http://zerocoin.org/.

It has come to our attention, however, that the Zerocoin code we were using is vulnerable to a certain specific type of exploit, so a patch needs to be added and verified.


https://www.reddit.com/r/zcoin/comments/7bjw8f/zcoin_hardfork_and_security_update_version_01331/
https://forum.pivx.org/t/update-on-recent-zerocoin-protocol-exploit-patch-information/2753

While this thing is slowing us down, the bright side of it is that now is the perfect time to come across problems of that nature, when Vault 3.0 is not yet deployed. We will keep you informed on how this goes, still with a short term goal of initiating the alpha-testing phase.

Roadmap 2017 status report!

Thanks to our new coding approach that we have outlined at the last post, we are seeing positive results in developing Vault 3.0.

We will be conducting Vault core tests this week-end and into next week, and unless we encounter a problem, public alpha testing may start as soon as the end of next week.

Happy Friday everyone!

Seems your Dell Windows Home Server 2011 is not accepting even a brand new blank wallet.dat file, am I right?

You said you had tried to run Vault 2.4.3 with CryptoBullion folder completely erased, new bootstrap loaded, (wallet.dat backed up elsewhere, naturally) and this failed too, am I correct?

If you cannot even run the Vault with a brand new wallet.dat, then a corruption with your current wallet.dat isnt the issue; I would look at perhaps an overzealous security/virus protection on your computer.

Also, you had said:


This could also point to your C++ library not being up to date; have all your Windows update patches been successful?

a mutex is a software construction that allows, in a multithread environment, to allow one node to 'speak' while the others are muted.

Roadmap 2017 status report!

It's been too long since we published a development update and the reason for this has been that we stumbled upon an unforeseeable problem and realized we needed a new approach to allow this project to go forward in a timely fashion while not impacting on value.

What changes now is that we have decided not to let the new code be burdened by the existing old blockchain by attempting to make the new code accomodate it; this means that a CBX swap will be necessary, from old CBX to the new CBX currency instead of the simple seamless install of Vault 3.0 we had in mind. We still envision an elegant migration process: a snapshot of all existing CBX address balances will be taken, and then applied to the new CBX blockchain.

To regular users, the new Vault 3.0 will be able, upon first launch, to fetch the user's private keys which are in the old wallet.dat, and then from these old keys fetch his new CBX coin into the new blockchain. May I remind people that the CBX address' values will not be affected in any way by this swap, all balances stay the same.

The last hurdle we will find prior to alpha testing lies in the mandatory global money supply limitation of 250 000 CBX that can be associated to BPNs (masternodes) at any time. To address this, an innovative solution was proposed, applying a mutex; this solution is unheard of in the Crypto world and we think it will give good results.

Thank you for your patience and continued support

I understand the frustration! So, reloading and syncing a brand new Crypto Bullion empty wallet with bootstrap is a job of a few hours: how did it go?

While it's true that Vault 2.4.3 cannot sync alone, even if I'm not much of a techie I was always able to sync using bootstrap.

Have you tried the steps I outlined above?

When you say "used the bootstrap", you mean you reloaded the whole blockchain? Because according to my experience with Vault 2.4.3, this happens sometimes when your PC blockchain goes corrupt.

To make sure you delete the whole blockchain, remove all files from your CryptoBullion folder, except wallet.dat - then load the bootstrap. If you leave some old files there, then maybe the corruption stays.

Also, have you tried to run Vault 2.4.3 with an old wallet.dat file, or are you starting a new one from scratch? If your Vault works with a blank wallet.dat file but doesnt work with your old file, then it's bad news.

More detail please...

We have made hardforks in collaboration with Cryptopia a few times before, there were no issues. Cryptopia de-lists coins who meddle with their blockchain, which is something we will never do.

If nothing changes, then everything stays the same; including value and price. We are committed to bringing the modern cryptocurrency features that are inline with Crypto Bullion's "Precious Metal" ideology that will increase usefulness and add value.

XBX sounds a lot like X-box, no?


Allow me to disagree on that one. Surprisingly enough, Yobit is still not dead, and as long as it can scam its users to buy coins which people can't withdraw, fellows are going to buy CBX there, we see this happen more often than you think. It's our responsability to make it as obvious as possible that buyers there are not getting the real deal.