Bullion (CBX) 'the Digital Precious Metal' | 2019 Roadmap published

[aizzaku]

Roadmap 2018 status report!

Good morning fellow Bullionaires; here is a significant step towards the new CBX network, as we had imagined it a while back.

The link to the new codebase Vault 3.0.0 alpha2 is the following: http://node.alex4j.cryptobullion.io/v30/bullion-qt.exe

Important notice: we have been testing internally this new software for two weeks and have not encountered any major issues that would have led us to lose CBX coin, but before you go ahead and use it with your own CBX address it would be important that you backup your wallet.dat file; if you are unsure how to backup that file, please ask.  Wallet.dat files should be backed up periodically with all coins, in any case.

This public alpha test is the occasion to try out the new codebase and give us feedback, if you see anything that could be improved. You may occasionally find references to non-implemented features in the software, we will correct this as we go.

One major thing we have to warn people about this new codebase is that the new Vault is now able to sync organically, which it has not been able to do for some time now; syncing organically takes a long time however, and this new Vault has an auto-bootstrap feature to speed up this process. The auto-bootstrap feature still has issues with Windows: we are aware of this problem and will be fixed shortly.

This new codebase Vault software is a major step towards our planned roadmap as outlined in the OP of this thread, it does not yet however have the BPN (or masternode) capability. We are still working on our unique approach for CBX masternodes and will have a better idea regarding timing of this development next week.

We are also using this new Vault opportunity to gradually modernize/rebrand our image; you will already be able to see the new name and logo for CBX in this new Vault. Has anyone noticed that Cryptopia has changed "Crypto Bullion" to the new "Bullion" name already?

Sweet news. Downloaded. took the backup and now trying to sync.

Will stake and test the wallet and get back to you.
The new branding look nice but the dark background on the logo is making it hard to see the bull.

Also the wallet mentioned do not stake...or do transactions.. so right now we cannot stake?

[1714958344]

1714958344

[1714958344]

1714958344

[VonSpass]

Roadmap 2018 status report!

Good morning fellow Bullionaires; here is a significant step towards the new CBX network, as we had imagined it a while back.

The link to the new codebase Vault 3.0.0 alpha2 is the following: http://node.alex4j.cryptobullion.io/v30/bullion-qt.exe

Important notice: we have been testing internally this new software for two weeks and have not encountered any major issues that would have led us to lose CBX coin, but before you go ahead and use it with your own CBX address it would be important that you backup your wallet.dat file; if you are unsure how to backup that file, please ask.  Wallet.dat files should be backed up periodically with all coins, in any case.

This public alpha test is the occasion to try out the new codebase and give us feedback, if you see anything that could be improved. You may occasionally find references to non-implemented features in the software, we will correct this as we go.

One major thing we have to warn people about this new codebase is that the new Vault is now able to sync organically, which it has not been able to do for some time now; syncing organically takes a long time however, and this new Vault has an auto-bootstrap feature to speed up this process. The auto-bootstrap feature still has issues with Windows: we are aware of this problem and will be fixed shortly.

This new codebase Vault software is a major step towards our planned roadmap as outlined in the OP of this thread, it does not yet however have the BPN (or masternode) capability. We are still working on our unique approach for CBX masternodes and will have a better idea regarding timing of this development next week.

We are also using this new Vault opportunity to gradually modernize/rebrand our image; you will already be able to see the new name and logo for CBX in this new Vault. Has anyone noticed that Cryptopia has changed "Crypto Bullion" to the new "Bullion" name already?

Sweet news. Downloaded. took the backup and now trying to sync.

Will stake and test the wallet and get back to you.
The new branding look nice but the dark background on the logo is making it hard to see the bull.

Also the wallet mentioned do not stake...or do transactions.. so right now we cannot stake?

Malafaya has staked with 500 CBX; I think it's safe to stake with it. Personally, I dont stake my whole stash of CBX just yet; but with smaller amounts I think it's safe.

If anyone has a computer at home feeling lonely and looking for something to do, it would be nice for people to test syncing from scratch. For me it was reliable and much faster than before.

Also, this being an entirely new codebase, the RAM leak issue Vault 2.4.3 had should be fixed and new codebase should be able to maintain its usage of memory around a stable 1.2 to 1.3 gigs while staking; we would like to hear your experience with this too.

[avariahb]

I restart from 0.
I have two years and 45 weeks left.
I test the staking and keep you informed

New features in the tools tab

[aizzaku]

Malafaya has staked with it 500 times; I think it's safe to stake with it. Personally, I dont stake my whole stash of CBX just yet; but with smaller amounts I think it's safe.

If anyone has a computer at home feeling lonely and looking for something to do, it would be nice for people to test syncing from scratch. For me it was reliable and much faster than before.

Also, this being an entirely new codebase, the RAM leak issue Vault 2.4.3 had should be fixed and new codebase should be able to maintain its usage of memory around a stable 1.2 to 1.3 gigs while staking; we would like to hear your experience with this too.

Yes. i started the sync. it shows 4 years 19 weeks behind. now i dont think it was bootstrapped. The first launch asked me for the dir for the blockchain.. i just said default.
should have i selected the old roaming dir?

anyhow it is downloading the chain but quite slow. i wudn't think the chain is bigger than 3gb right?

[ohmdoctor]

I'm trying out 3.0 Alpha 2 right now. I got an error message saying Snapshot Extraction failed when I first started it but the wallet still launched. Trying to get it to download the blockchain now.

[VonSpass]

Malafaya has staked with it 500 times; I think it's safe to stake with it. Personally, I dont stake my whole stash of CBX just yet; but with smaller amounts I think it's safe.

If anyone has a computer at home feeling lonely and looking for something to do, it would be nice for people to test syncing from scratch. For me it was reliable and much faster than before.

Also, this being an entirely new codebase, the RAM leak issue Vault 2.4.3 had should be fixed and new codebase should be able to maintain its usage of memory around a stable 1.2 to 1.3 gigs while staking; we would like to hear your experience with this too.

Yes. i started the sync. it shows 4 years 19 weeks behind. now i dont think it was bootstrapped. The first launch asked me for the dir for the blockchain.. i just said default.
should have i selected the old roaming dir?

anyhow it is downloading the chain but quite slow. i wudn't think the chain is bigger than 3gb right?

Thank you for your feedback aiz; if you select "Default", the new Vault will create a new directory on your computer: /bullion which will also create a brand new "wallet.dat" file, and because of this your old wallet.dat file addresses will not be imported.

[VonSpass]

I'm trying out 3.0 Alpha 2 right now. I got an error message saying Snapshot Extraction failed when I first started it but the wallet still launched. Trying to get it to download the blockchain now.

Yes this is what I was saying about the auto-bootstrap feature, it won't work correctly for now. Either bootstrap by hand, or sync organically.

[ohmdoctor]

I'm trying out 3.0 Alpha 2 right now. I got an error message saying Snapshot Extraction failed when I first started it but the wallet still launched. Trying to get it to download the blockchain now.

Yes this is what I was saying about the auto-bootstrap feature, it won't work correctly now. Either bootstrap by hand, or sync organically.

Oh I see, well my plan was to let it sync organically so I guess that's a good thing.

[Alec40Gr]

synchronizing from scratch without bootstrap stuck at block #2256008 Sat Jan 20 03:06:01 2018 (win 7 x64 - tried 2 times)

debug.log

2018-02-26 06:36:01 ERROR: GetTransaction : Deserialize or I/O error - non-canonical ReadCompactSize()
2018-02-26 06:36:01 ERROR: CheckProofOfStake() : INFO: read txPrev failed, aa2f8c400739d2cc6576bda8b19088f099bda90a05789a393dd428dbafaa2286
2018-02-26 06:36:01 WARNING: ProcessBlock(): check proof-of-stake failed for block 4bf4fd27021a7130e6397f34b04d051c60cf6b39694f52dfc891b2ffa5c1dec7
2018-02-26 06:36:01 ERROR: ProcessNewBlock : AcceptBlock FAILED

[FiniteRed]

Is there Linux build of the alpha?

[aizzaku]

so i synced from scratch. Took some time but its working.

next thing i did was replaced my wallet.dat thinking it will work. but apparently it said wallet.bat corrupt, salvage failed. so how do you think we should restore them coins.

luckily i have dumped all the priv keys and i'll just access with it, but not everyone will do that.

[avariahb]

I started from 0.
I sent cbx on the new wallet in the morning.
they're stuck all day on "pending."
I had to reboot the cbx to be available.
Likewise I had to restart the wallet for the staking to become active.

[alexvilis]

New CBX Exchange Listing

Listing on Coinbook
We are delighted to announce that in the coming months CBX will be listed on coinbook.com. Coinbook is a USA based exchange which will soon offer all trading pairs against USD, transparency, no hidden fees and top of the line security. Currently, Coinbook are preparing and finalising the trading platform before it can go live. You are still able to signup on coinbook.com now and you will receive an email once it goes live.

Listing Information
CBX is in constant communication with the Coinbook team to ensure everything proceeds smoothly and according to plan. We have high hopes for this exchange to become an important trading platform within the crypto community and we are extremely excited to be involved. Below is a recent message we received from the Coinbook team regarding their progress and when listing CBX can become a reality.

"Things are moving forward. We have a few hurdles to get over before we can go live which has pushed us back for much longer than anticipated. The biggest one is an audit that we need which is scheduled before the end of March. That was the earliest we could get it and that has to happen before we can cross the final legal hurdle to go live. In the mean time, we are still working on a diversified banking relationship, a few more anti-fraud partners, and payment processors. This can easily be accomplished before then so we are really just waiting on the audit. They have been really busy with tax season and everyone's year end hitting all at the same time. But we are still on track to go live as soon as we can."

As you can see Coinbook are racing ahead and awaiting an important audit before being able to launch their exchange, the audit is scheduled to happen before the end of March. As you might of noticed, Coinbook have many other exciting features in the works, and it is a fantastic opportunity to have CBX listed on another high quality exchange! As soon as more information becomes available we will be sure to keep the community updated.

https://steemit.com/cbx/@cbx/new-cbx-exchange-listing

[alexvilis]

CBX Vault 3.0 Alpha Testing is Live!

Alpha Release
We have been pushing to get the alpha release out as fast as possible, whilst maintaining a high quality level of coding. I am happy to announce that Vault 3.0 is now available for alpha testing! This new codebase Vault 3.0 software is a major step in our roadmap, but it does not yet have the BPN (masternode) capability. We are still working hard on our unique mutex approach for CBX masternodes and will have a better idea regarding timing of this development next week.

This public alpha release gives users an opportunity to experiment with the new software and receive feedback from the Bullion community. So if you do find any issues, bugs or have other concerns please do get in contact with us. We highly value and appreciate every single piece of constructive feedback from the community and strive to take every opinion into consideration. You may occasionally find references to non-implemented features in the software, we will correct this as we go.

Backup wallet.dat
It is extremely important to be aware that the Bullion devs have been internally testing this new software for the past two weeks and have not encountered any major issues that could lead to loss of any CBX coins. One dev tested with 500 CBX and had no issues, but we still caution against doing so with your entire stash of CBX just yet! However, before you update to the new installation please make sure to backup your wallet.dat! If you are unsure how to backup your wallet.dat file correctly, please join our Telegram group (link at bottom of post) and ask an admin for further information.

Download Info & Notes
Alpha Release:

http://node.alex4j.cryptobullion.io/v30/bullion-qt.exe

One major thing we have to warn people about this new codebase is that the new Vault is now able to sync organically, which no Vault has been able to do for some time now; syncing organically takes some time however, so this new Vault has an auto-bootstrap feature to speed up this process. The auto-bootstrap feature still has issues with Windows: we are aware of this problem and will be fixed shortly. Since we still have to apply a bootstrap manually if you don't want to sync organically, here is the link to current updated bootstrap:

Bootstrap download:

http://node.alex4j.cryptobullion.io/v30/bootstrap.zip.

Also, this being an entirely new codebase, the RAM leak issue Vault 2.4.3 had should be fixed and new codebase should be able to maintain its usage of memory around a stable 1.2 to 1.3 gigs while staking; we would love to hear your experience with this too.

https://steemit.com/cbx/@cbx/cbx-vault-3-0-alpha-testing-is-live

[misospider]

Hi! I read a bit website and white paper and i couldn't find what is the amount of CBX coins requested for a MN ?

Hi fellow bullionaire, the amount required to run a masternode is 2000 cbx coins. Returns are at 9-18% per annum

This was what I was looking for. Thanks!

[FiniteByDesign]

Roadmap 2018 status report!

Good morning fellow Bullionaires; here is a significant step towards the new CBX network, as we had imagined it a while back.

The link to the new codebase Vault 3.0.0 alpha2 is the following: http://node.alex4j.cryptobullion.io/v30/bullion-qt.exe

Important notice: we have been testing internally this new software for two weeks and have not encountered any major issues that would have led us to lose CBX coin, but before you go ahead and use it with your own CBX address it would be important that you backup your wallet.dat file; if you are unsure how to backup that file, please ask.  Wallet.dat files should be backed up periodically with all coins, in any case.

This public alpha test is the occasion to try out the new codebase and give us feedback, if you see anything that could be improved. You may occasionally find references to non-implemented features in the software, we will correct this as we go.

One major thing we have to warn people about this new codebase is that the new Vault is now able to sync organically, which no Vault has been able to do for some time now; syncing organically takes some time however, so this new Vault has an auto-bootstrap feature to speed up this process. The auto-bootstrap feature still has issues with Windows: we are aware of this problem and will be fixed shortly. Since we still have to apply a bootstrap manually if you don't want to sync organically, here is the link to current updated bootstrap: http://node.alex4j.cryptobullion.io/v30/bootstrap.zip.

This new codebase Vault software is a major step towards our planned roadmap as outlined in the OP of this thread, it does not yet however have the BPN (or masternode) capability. We are still working on our unique approach for CBX masternodes and will have a better idea regarding timing of this development next week.

We are also using this new Vault opportunity to gradually modernize/rebrand our image; you will already be able to see the new name and logo for CBX in this new Vault. Has anyone noticed that Cryptopia has changed "Crypto Bullion" to the new "Bullion" name already?

My orphan rate is down with new version from 5% to 3% - nice!

[malafaya]

synchronizing from scratch without bootstrap stuck at block #2256008 Sat Jan 20 03:06:01 2018 (win 7 x64 - tried 2 times)

debug.log

2018-02-26 06:36:01 ERROR: GetTransaction : Deserialize or I/O error - non-canonical ReadCompactSize()
2018-02-26 06:36:01 ERROR: CheckProofOfStake() : INFO: read txPrev failed, aa2f8c400739d2cc6576bda8b19088f099bda90a05789a393dd428dbafaa2286
2018-02-26 06:36:01 WARNING: ProcessBlock(): check proof-of-stake failed for block 4bf4fd27021a7130e6397f34b04d051c60cf6b39694f52dfc891b2ffa5c1dec7
2018-02-26 06:36:01 ERROR: ProcessNewBlock : AcceptBlock FAILED

Hi, Alec40Gr.

This means there's data corruption in the blockchain in the disk.
When you say you tried twice, do you mean you tried to sync the chain from zero twice? And did it stop at the same block height in both runs?
There's no way to be sure at this time but my guess would be a corrupted/broken disk as that code (tx disk serialization/deserialization) is pretty solid in other wallets as well. Let's see how it goes for other users too and keep this issue in mind if it pops up again.

[malafaya]

Is there Linux build of the alpha?

Hi, FiniteRed.

Yes, there surely can be one (you probably want a 64-bit build). We'll publish a note here when it's available.

[malafaya]

so i synced from scratch. Took some time but its working.

next thing i did was replaced my wallet.dat thinking it will work. but apparently it said wallet.bat corrupt, salvage failed. so how do you think we should restore them coins.

luckily i have dumped all the priv keys and i'll just access with it, but not everyone will do that.

Hi, aizzaku.

This is still an alpha build so things like this can happen.
The old wallet is supposed to work with the new version. I personally tried it a couple of times and it worked.
My questions are: how old is your wallet file, meaning what kind of transactions does it hold? Old PoW mining? Just PoSP? Also old PoS?
Was it encrypted at the time you copied?

This is one thing we want working, exactly to prevent the user having to use those advanced features you mentioned.

P.S. you message was not clear enough to figure out but KEEP A SEPARATE BACKUP OF YOUR WALLET.DAT when trying it out with this alpha build.

[malafaya]

I started from 0.
I sent cbx on the new wallet in the morning.
they're stuck all day on "pending."
I had to reboot the cbx to be available.
Likewise I had to restart the wallet for the staking to become active.

Hi, avariahb.

I have come across this not-staking issue myself.
It seems to happen when the wallet gets a transaction it did not make (this instance): this happens for example when you sync the whole blockchain from zero and it detects all the transactions associated with your addresses. But still it doesn't happen most of the time.
A restart fixes it and it probably won't happen again unless you restart it having the same issue mentioned before. Anyway this should be fixed.
You can check the staking status by looking at the arrow icon in the bottom right corner: it should be green to indicate you're staking.
As for the sent CBX being pending for a whole day, I never observed such behavior. Can you now tell if the transaction apparently wasn't even broadcast or if it was just a wallet refresh issue (check the transaction date, if it approximately matches the time you sent it or the time you restarted the wallet)?