Let's celebrate; I just turned Legendary!
Congrats!!!
Topic: Bullion (CBX) 'the Digital Precious Metal' | 2019 Roadmap published - page 26. (Read 359514 times)
March 13, 2018, 11:37:09 AM
Congrats!!!
March 13, 2018, 11:31:37 AM
Let's celebrate; I just turned Legendary!
Congrats!!!
March 13, 2018, 11:17:07 AM
Let's celebrate; I just turned Legendary!
March 13, 2018, 09:11:30 AM
Anyone having problems with Vault 3.0 Alpha 2 ? Been running mine for two weeks but it has since stopped synchronizing
and is stuck on block 2,316,077 (roughly 3 days behind).
and is stuck on block 2,316,077 (roughly 3 days behind).
Do you have any peers connected? Does restarting Vault fix the problem?
If you would care to share your debug.log file (in the same dir as your wallet.dat) that would be awesome help.
Yes, connected to 9 peers. Tried restarting numerous times.
debug says "ERROR: mempool transaction missing input" Also, lower left of vault notes "No block source available..."
Powering down laptop before CBX closes the issue perhaps?
BTW, I am running Vault 2.4.4 on a separate laptop with no problems.
There has been an issue resulting in a fork for some wallets over the weekend.
This message "ERROR: mempool transaction missing input" means there is something not right between your wallet and the chain.
First, upgrade to the latest Alpha 3 (same download link as before; check previous messages): this includes the recently added checkpoints that should prevent you from entering the same fork.
Then, try to recover the situation by acessing Tools >> Repair Wallet >> Recover Transactions 2 .
If that still does not work, please follow the bootstrap copy guide (elambert just posted the needed steps a few minutes ago).
Yes, I scrubbed the vault and and re-installed it and it's working perfectly again.
One frustrating issue was that I didn't realize that windows firewall was blocking the app's access to the network.
So add that item to Ben's excellent checklist.
Thanks for all your help.
March 13, 2018, 07:32:40 AM
So, if I'm still running 2.4.3 am I completely wasting my time?
You're not wasting your time if your 2.4.3 is on the right chain.
We compiled 2.4.4 to help with the fork issue we experienced last weekend; it's not a mandatory update.
March 13, 2018, 06:57:23 AM
Anyone having problems with Vault 3.0 Alpha 2 ? Been running mine for two weeks but it has since stopped synchronizing
and is stuck on block 2,316,077 (roughly 3 days behind).
and is stuck on block 2,316,077 (roughly 3 days behind).
Do you have any peers connected? Does restarting Vault fix the problem?
If you would care to share your debug.log file (in the same dir as your wallet.dat) that would be awesome help.
Yes, connected to 9 peers. Tried restarting numerous times.
debug says "ERROR: mempool transaction missing input" Also, lower left of vault notes "No block source available..."
Powering down laptop before CBX closes the issue perhaps?
BTW, I am running Vault 2.4.4 on a separate laptop with no problems.
There has been an issue resulting in a fork for some wallets over the weekend.
This message "ERROR: mempool transaction missing input" means there is something not right between your wallet and the chain.
First, upgrade to the latest Alpha 3 (same download link as before; check previous messages): this includes the recently added checkpoints that should prevent you from entering the same fork.
Then, try to recover the situation by acessing Tools >> Repair Wallet >> Recover Transactions 2 .
If that still does not work, please follow the bootstrap copy guide (elambert just posted the needed steps a few minutes ago).
March 13, 2018, 06:28:12 AM
New Vault 2.4.4 Vault released!
In the past few days, the CBX network has experienced a strong and unwanted fork, which ended up being also propagated by a few nodes. For this reason, here is new version 2.4.4 of the old codebase Vault; this new version deals with this ongoing fork, with a few added checkpoints.
To make sure you are on the right fork, please check your Vault's block height vs. CryptoIDs: https://chainz.cryptoid.info/cbx/#; any lasting block height difference with your live Vault could point to your Vault being on the wrong fork.
Here is the download link to the 2.4.4 Vault: https://github.com/cryptogenicbonds/CryptoBullion-CBX/releases/tag/2.4.4
Here is the link to the V2 bootstrap file; if you have been stuck on the fork, it may be necessary to reload it: http://node.alex4j.cryptobullion.io/bootstrap.zip
New codebase Vault 3 is better equipped to deal with these situations, so these fork issues should be very very rare occurence, of not completely non-existant, in the near future.
We have updated the new codebase Vault 3 alpha 2 as well, to "alpha 3". This updated Vault has a few tweaks that bring us closer to final version, with updated PoW signature verification and staking; I recommend those who have installed alpha 2, to now install this one. This alpha 3 also has the same new checkpoints of Vault 2.4.4 that avoid the fork we have experienced a few days ago.
http://node.alex4j.cryptobullion.io/v30/bullion-qt64
http://node.alex4j.cryptobullion.io/v30/bullion-qt.exe
V3 bootstrap (does not work with Vault 2.4.4):
http://node.alex4j.cryptobullion.io/v30/bootstrap.zip
In the past few days, the CBX network has experienced a strong and unwanted fork, which ended up being also propagated by a few nodes. For this reason, here is new version 2.4.4 of the old codebase Vault; this new version deals with this ongoing fork, with a few added checkpoints.
To make sure you are on the right fork, please check your Vault's block height vs. CryptoIDs: https://chainz.cryptoid.info/cbx/#; any lasting block height difference with your live Vault could point to your Vault being on the wrong fork.
Here is the download link to the 2.4.4 Vault: https://github.com/cryptogenicbonds/CryptoBullion-CBX/releases/tag/2.4.4
Here is the link to the V2 bootstrap file; if you have been stuck on the fork, it may be necessary to reload it: http://node.alex4j.cryptobullion.io/bootstrap.zip
New codebase Vault 3 is better equipped to deal with these situations, so these fork issues should be very very rare occurence, of not completely non-existant, in the near future.
We have updated the new codebase Vault 3 alpha 2 as well, to "alpha 3". This updated Vault has a few tweaks that bring us closer to final version, with updated PoW signature verification and staking; I recommend those who have installed alpha 2, to now install this one. This alpha 3 also has the same new checkpoints of Vault 2.4.4 that avoid the fork we have experienced a few days ago.
http://node.alex4j.cryptobullion.io/v30/bullion-qt64
http://node.alex4j.cryptobullion.io/v30/bullion-qt.exe
V3 bootstrap (does not work with Vault 2.4.4):
http://node.alex4j.cryptobullion.io/v30/bootstrap.zip
Here is a quick guide to updating your Vault to new 2.4.4 or new Alpha V3. Please note that V3 is still alpha for testing so our official recommendation remains to use V2.4.4. (LINKS ARE ABOVE)
1. Access your cryptobullion or bullion roaming folder and backup your wallet.dat (copy to desktop, usb, etc)
2. Delete all other contents of the roaming folder
3. Delete your qt executable
4. Download new version (links above)
5. Download new bootstrap (links above)
6. Extract bootstrap file and folder
7. Copy/paste bootstrap extract into roaming folder
8. Paste copy of wallet.dat into roaming folder
9. Start up Vault
10. Allow to sync
11. Check blockchain information in Vault for current number of blocks, verify this data versus CryptoID to verify you are on the correct chain (https://chainz.cryptoid.info/cbx/)
12. If yes, unlock and begin staking; If no, ask for assistance
March 13, 2018, 05:20:27 AM
Roadmap 2018 status report!
We have updated the new codebase Vault 3 alpha 2 as well, to "alpha 3". This updated Vault has a few tweaks that bring us closer to final version, with updated PoW signature verification and staking; I recommend those who have installed alpha 2, to now install this one. This alpha 3 also has the same new checkpoints of Vault 2.4.4 that avoid the fork we have experienced a few days ago.
http://node.alex4j.cryptobullion.io/v30/bullion-qt64
http://node.alex4j.cryptobullion.io/v30/bullion-qt.exe
V3 bootstrap (does not work with Vault 2.4.4):
http://node.alex4j.cryptobullion.io/v30/bootstrap.zip
We have updated the new codebase Vault 3 alpha 2 as well, to "alpha 3". This updated Vault has a few tweaks that bring us closer to final version, with updated PoW signature verification and staking; I recommend those who have installed alpha 2, to now install this one. This alpha 3 also has the same new checkpoints of Vault 2.4.4 that avoid the fork we have experienced a few days ago.
http://node.alex4j.cryptobullion.io/v30/bullion-qt64
http://node.alex4j.cryptobullion.io/v30/bullion-qt.exe
V3 bootstrap (does not work with Vault 2.4.4):
http://node.alex4j.cryptobullion.io/v30/bootstrap.zip
Thanks Ben!
I've shared the news with the other communities!
March 12, 2018, 11:20:04 PM
So, if I'm still running 2.4.3 am I completely wasting my time?
You're not wasting your time if your 2.4.3 is on the right chain.
We compiled 2.4.4 to help with the fork issue we experienced last weekend; it's not a mandatory update.
I like many aspects of this coin, in particular the very low supply. But the daily volume is like $10...
What are the projections? Is this going to change?
What are the projections? Is this going to change?
Of course we want this tiny daily volume to change; in fact, we think that our current BPN approach, along with listing at Coinbook.com put CBX on path for explosive price growth! Essentially the choice people have today is, either buy an already expensive coin/token with tons of volume hoping that it will double in value this year, or, buy a coin like CBX which is still cheap and looks promising.
March 12, 2018, 11:12:49 PM
$10 at least.
March 12, 2018, 11:07:20 PM
I like many aspects of this coin, in particular the very low supply. But the daily volume is like $10...
What are the projections? Is this going to change?
What are the projections? Is this going to change?
March 12, 2018, 08:27:25 PM
So, if I'm still running 2.4.3 am I completely wasting my time?
March 12, 2018, 04:49:36 PM
Anyone having problems with Vault 3.0 Alpha 2 ? Been running mine for two weeks but it has since stopped synchronizing
and is stuck on block 2,316,077 (roughly 3 days behind).
and is stuck on block 2,316,077 (roughly 3 days behind).
Do you have any peers connected? Does restarting Vault fix the problem?
If you would care to share your debug.log file (in the same dir as your wallet.dat) that would be awesome help.
Yes, connected to 9 peers. Tried restarting numerous times.
debug says "ERROR: mempool transaction missing input" Also, lower left of vault notes "No block source available..."
Powering down laptop before CBX closes the issue perhaps?
BTW, I am running Vault 2.4.4 on a separate laptop with no problems.
March 12, 2018, 02:04:41 PM
Anyone having problems with Vault 3.0 Alpha 2 ? Been running mine for two weeks but it has since stopped synchronizing
and is stuck on block 2,316,077 (roughly 3 days behind).
and is stuck on block 2,316,077 (roughly 3 days behind).
Do you have any peers connected? Does restarting Vault fix the problem?
If you would care to share your debug.log file (in the same dir as your wallet.dat) that would be awesome help.
March 12, 2018, 01:27:47 PM
Roadmap 2018 status report!
We have updated the new codebase Vault 3 alpha 2 as well, to "alpha 3". This updated Vault has a few tweaks that bring us closer to final version, with updated PoW signature verification and staking; I recommend those who have installed alpha 2, to now install this one. This alpha 3 also has the same new checkpoints of Vault 2.4.4 that avoid the fork we have experienced a few days ago.
http://node.alex4j.cryptobullion.io/v30/bullion-qt64
http://node.alex4j.cryptobullion.io/v30/bullion-qt.exe
V3 bootstrap (does not work with Vault 2.4.4):
http://node.alex4j.cryptobullion.io/v30/bootstrap.zip
We have updated the new codebase Vault 3 alpha 2 as well, to "alpha 3". This updated Vault has a few tweaks that bring us closer to final version, with updated PoW signature verification and staking; I recommend those who have installed alpha 2, to now install this one. This alpha 3 also has the same new checkpoints of Vault 2.4.4 that avoid the fork we have experienced a few days ago.
http://node.alex4j.cryptobullion.io/v30/bullion-qt64
http://node.alex4j.cryptobullion.io/v30/bullion-qt.exe
V3 bootstrap (does not work with Vault 2.4.4):
http://node.alex4j.cryptobullion.io/v30/bootstrap.zip
March 12, 2018, 01:00:18 PM
Anyone having problems with Vault 3.0 Alpha 2 ? Been running mine for two weeks but it has since stopped synchronizing
and is stuck on block 2,316,077 (roughly 3 days behind).
and is stuck on block 2,316,077 (roughly 3 days behind).
March 11, 2018, 08:28:54 PM
New Vault 2.4.4 Vault released!
In the past few days, the CBX network has experienced a strong and unwanted fork, which ended up being also propagated by a few nodes. For this reason, here is new version 2.4.4 of the old codebase Vault; this new version deals with this ongoing fork, with a few added checkpoints.
To make sure you are on the right fork, please check your Vault's block height vs. CryptoIDs: https://chainz.cryptoid.info/cbx/#; any lasting block height difference with your live Vault could point to your Vault being on the wrong fork.
Here is the download link to the 2.4.4 Vault: https://github.com/cryptogenicbonds/CryptoBullion-CBX/releases/tag/2.4.4
Here is the link to the V2 bootstrap file; if you have been stuck on the fork, it may be necessary to reload it: http://node.alex4j.cryptobullion.io/bootstrap.zip
New codebase Vault 3 is better equipped to deal with these situations, so these fork issues should be very very rare occurence, of not completely non-existant, in the near future.
In the past few days, the CBX network has experienced a strong and unwanted fork, which ended up being also propagated by a few nodes. For this reason, here is new version 2.4.4 of the old codebase Vault; this new version deals with this ongoing fork, with a few added checkpoints.
To make sure you are on the right fork, please check your Vault's block height vs. CryptoIDs: https://chainz.cryptoid.info/cbx/#; any lasting block height difference with your live Vault could point to your Vault being on the wrong fork.
Here is the download link to the 2.4.4 Vault: https://github.com/cryptogenicbonds/CryptoBullion-CBX/releases/tag/2.4.4
Here is the link to the V2 bootstrap file; if you have been stuck on the fork, it may be necessary to reload it: http://node.alex4j.cryptobullion.io/bootstrap.zip
New codebase Vault 3 is better equipped to deal with these situations, so these fork issues should be very very rare occurence, of not completely non-existant, in the near future.
March 11, 2018, 08:19:57 PM
Roadmap 2018 Development Update!
As you can see with the mysterious "Protocol 70010" in the current live nodes below, we are focused now on adding BPN masternodes to the new codebase CBX Vault!
I still cannot provide a delivery date for BPN and subsequent hardfork that will finalize the addition of masternodes to Bullion, unfortunately, but be assured this date will be provided as soon as I have a probable date. Also, we are in the process of adding the promised convenient CBX staking/network metrics, directly in the GUI.
In the meantime, the other part of the Bullion team is contacting and notifying all web agents about the new "Bullion" name and logo: last two were the coin explorer and coinmarketcap.com (we are still waiting for CMC to update CBX however).
As you can see with the mysterious "Protocol 70010" in the current live nodes below, we are focused now on adding BPN masternodes to the new codebase CBX Vault!
I still cannot provide a delivery date for BPN and subsequent hardfork that will finalize the addition of masternodes to Bullion, unfortunately, but be assured this date will be provided as soon as I have a probable date. Also, we are in the process of adding the promised convenient CBX staking/network metrics, directly in the GUI.
In the meantime, the other part of the Bullion team is contacting and notifying all web agents about the new "Bullion" name and logo: last two were the coin explorer and coinmarketcap.com (we are still waiting for CMC to update CBX however).
Hi , vonpass are the wallet version 3.0 still in testing . Or it’s live now. Thanks , and 70010 are testing masternode ?
Yes, Protocol 70010 nodes are actual nodes testing the BPN Vault build.
March 10, 2018, 12:56:43 AM
Roadmap 2018 Development Update!
As you can see with the mysterious "Protocol 70010" in the current live nodes below, we are focused now on adding BPN masternodes to the new codebase CBX Vault!
I still cannot provide a delivery date for BPN and subsequent hardfork that will finalize the addition of masternodes to Bullion, unfortunately, but be assured this date will be provided as soon as I have a probable date. Also, we are in the process of adding the promised convenient CBX staking/network metrics, directly in the GUI.
In the meantime, the other part of the Bullion team is contacting and notifying all web agents about the new "Bullion" name and logo: last two were the coin explorer and coinmarketcap.com (we are still waiting for CMC to update CBX however).
As you can see with the mysterious "Protocol 70010" in the current live nodes below, we are focused now on adding BPN masternodes to the new codebase CBX Vault!
I still cannot provide a delivery date for BPN and subsequent hardfork that will finalize the addition of masternodes to Bullion, unfortunately, but be assured this date will be provided as soon as I have a probable date. Also, we are in the process of adding the promised convenient CBX staking/network metrics, directly in the GUI.
In the meantime, the other part of the Bullion team is contacting and notifying all web agents about the new "Bullion" name and logo: last two were the coin explorer and coinmarketcap.com (we are still waiting for CMC to update CBX however).
Hi , vonpass are the wallet version 3.0 still in testing . Or it’s live now. Thanks , and 70010 are testing masternode ?
March 09, 2018, 11:33:09 AM
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.
Perfect
ready and waiting to test it FR
Still with same codebase as previously posted Windows alpha 2, here is the 64 bit Linux Vault: http://node.alex4j.cryptobullion.io/v30/bullion-qt64
Looks like there a number of dependency issues running on a clean/patched install of Ubuntu, detailed below (along with the "quick" fixes) - would be good to publish an official breakdown of what you need to install to get up and running...
Code:
error while loading shared libraries: libboost_program_options.so.1.58.0: cannot open shared object file: No such file or directory
-> sudo apt-get install libboost-all-dev(overkill I feel)
Code:
error while loading shared libraries: libqrencode.so.3: cannot open shared object file: No such file or directory
-> sudo apt-get install libqrencode3Code:
error while loading shared libraries: libdb_cxx-4.8.so: cannot open shared object file: No such file or directory
-> sudo add-apt-repository -y ppa:bitcoin/bitcoin-> sudo apt-get update
-> sudo apt-get install -y libdb4.8-dev libdb4.8++-dev
(this is a gross fix!)
FR
Thanks for the info.
It's true we still haven't looked into the shared dependencies issue in Linux, but it will surely be looked into.
Jump to: