Topic: Bullion (CBX) 'the Digital Precious Metal' | 2019 Roadmap published - page 57. (Read 359514 times)
September 19, 2017, 08:54:07 PM
Can you tell me the specific time? I want to invest in this coin
September 19, 2017, 08:38:24 PM
Roadmap 2017 status report!
As we know already, the opcode interpreter rewriting is complete; all internal calls to this new opcode interpreter have been rechecked and modified when necessary.
We are moving forward, because now I am happy to report that we are at the stage where we are running the Vault 3.0 live and attempting to make it synchronise organically from scratch from the online 2.4.3 Vaults (syncing right from the start, CBX genesis block) - naturally the first attempt to sync did not work, so we made adjustments and, so far so good with second attempt, as this is ongoing as I write these lines. Remember that Vault 2.4.3 could never sync alone without bootstrap - so this will be an important improvement.
What is left to do after this is to finalize the GUI interface; but alpha testing can begin even with an incomplete GUI. Thank you for all volunteers who offered to run the testnet of Vault 3.0 with us, we will contact you shortly, should be next week or the week after for the final live testnet. This test will be the perfect opportunity for constructive criticism, and the perfect time to customize the Vault to how we want it - so we are still open for more testers, if more want to join.
Thank you all for your faith in our project, going through and rewriting thousands of lines of code is a tremendous task, as one can imagine.
As we know already, the opcode interpreter rewriting is complete; all internal calls to this new opcode interpreter have been rechecked and modified when necessary.
We are moving forward, because now I am happy to report that we are at the stage where we are running the Vault 3.0 live and attempting to make it synchronise organically from scratch from the online 2.4.3 Vaults (syncing right from the start, CBX genesis block) - naturally the first attempt to sync did not work, so we made adjustments and, so far so good with second attempt, as this is ongoing as I write these lines. Remember that Vault 2.4.3 could never sync alone without bootstrap - so this will be an important improvement.
What is left to do after this is to finalize the GUI interface; but alpha testing can begin even with an incomplete GUI. Thank you for all volunteers who offered to run the testnet of Vault 3.0 with us, we will contact you shortly, should be next week or the week after for the final live testnet. This test will be the perfect opportunity for constructive criticism, and the perfect time to customize the Vault to how we want it - so we are still open for more testers, if more want to join.
Thank you all for your faith in our project, going through and rewriting thousands of lines of code is a tremendous task, as one can imagine.
best update so far, i need more CBX, this is it i can feel it in my bones
September 19, 2017, 11:57:18 AM
Roadmap 2017 status report!
As we know already, the opcode interpreter rewriting is complete; all internal calls to this new opcode interpreter have been rechecked and modified when necessary.
We are moving forward, because now I am happy to report that we are at the stage where we are running the Vault 3.0 live and attempting to make it synchronise organically from scratch from the online 2.4.3 Vaults (syncing right from the start, CBX genesis block) - naturally the first attempt to sync did not work, so we made adjustments and, so far so good with second attempt, as this is ongoing as I write these lines. Remember that Vault 2.4.3 could never sync alone without bootstrap - so this will be an important improvement.
What is left to do after this is to finalize the GUI interface; but alpha testing can begin even with an incomplete GUI. Thank you for all volunteers who offered to run the testnet of Vault 3.0 with us, we will contact you shortly, should be next week or the week after for the final live testnet. This test will be the perfect opportunity for constructive criticism, and the perfect time to customize the Vault to how we want it - so we are still open for more testers, if more want to join.
Thank you all for your faith in our project, going through and rewriting thousands of lines of code is a tremendous task, as one can imagine.
As we know already, the opcode interpreter rewriting is complete; all internal calls to this new opcode interpreter have been rechecked and modified when necessary.
We are moving forward, because now I am happy to report that we are at the stage where we are running the Vault 3.0 live and attempting to make it synchronise organically from scratch from the online 2.4.3 Vaults (syncing right from the start, CBX genesis block) - naturally the first attempt to sync did not work, so we made adjustments and, so far so good with second attempt, as this is ongoing as I write these lines. Remember that Vault 2.4.3 could never sync alone without bootstrap - so this will be an important improvement.
What is left to do after this is to finalize the GUI interface; but alpha testing can begin even with an incomplete GUI. Thank you for all volunteers who offered to run the testnet of Vault 3.0 with us, we will contact you shortly, should be next week or the week after for the final live testnet. This test will be the perfect opportunity for constructive criticism, and the perfect time to customize the Vault to how we want it - so we are still open for more testers, if more want to join.
Thank you all for your faith in our project, going through and rewriting thousands of lines of code is a tremendous task, as one can imagine.
September 19, 2017, 02:52:18 AM
Now this is something i can work with. On it right now. will tell you the reason.
this can be a good troubleshoot for others as well.
thanx. i will get back as soon as its working again.
this can be a good troubleshoot for others as well.
thanx. i will get back as soon as its working again.
Bootstrap was updated to current block height; syncing should be much easier now with this.
September 18, 2017, 11:09:33 PM
I found linux version 2.4.3 to be rather stable. However there is no 32 bit version of the latest wallet. I have run the 64 bit version on another machine and I was fully impressed with it.
Well i am running it on 32bit. my netbook is slow af.
maybe i need to buy a 2nd hand but better lappy for staking purposes
it should not be a problem, i believe they are backward compatible.i run mine on an old asus n53s, with no problems at all
September 18, 2017, 04:00:37 PM
I found linux version 2.4.3 to be rather stable. However there is no 32 bit version of the latest wallet. I have run the 64 bit version on another machine and I was fully impressed with it.
Well i am running it on 32bit. my netbook is slow af.
maybe i need to buy a 2nd hand but better lappy for staking purposes
September 18, 2017, 02:37:48 PM
I found linux version 2.4.3 to be rather stable. However there is no 32 bit version of the latest wallet. I have run the 64 bit version on another machine and I was fully impressed with it.
September 18, 2017, 01:29:21 PM
Now this is something i can work with. On it right now. will tell you the reason.
this can be a good troubleshoot for others as well.
thanx. i will get back as soon as its working again.
this can be a good troubleshoot for others as well.
thanx. i will get back as soon as its working again.
September 18, 2017, 11:30:50 AM
what do you guys think CPU, RAM and HDD have the effect on staking and or rather chain syncing.
Because i know for sure my internet connection is decent. but blocks are being generated faster than my sync.. i am always stuck somewhere from 53000 remaining to 55000 remaining. and right now it seems its going the other way.
Because i know for sure my internet connection is decent. but blocks are being generated faster than my sync.. i am always stuck somewhere from 53000 remaining to 55000 remaining. and right now it seems its going the other way.
I run my Vault in an 8 year old netbook, Intel Atom CPU, 2 GB RAM, damn slow HDD. It's sluggish to sync (high CPU usage), but it still manages to catch up.
well right now im trying it in my acer aspire one netbook. not even 8 years old but nope. but its not the case with few others coins i am staking.. they are always on time.
ETA for Vault 3.0 is in the Roadmap on the OP - but I honestly don't think that 2.4.3 is the issue in this case.
I think something has gone wrong with your blockchain in your computer (perhaps it's gone on a fork), since it's stuck your Vault appears to be looking for someone on the same fork as you but not finding it, so you get connections but your Vault is rejecting all blocks coming from the other Vaults.
The strenght of the hardware used is pretty much irrelevant to stake CBX, as long as you are using Windows 7 and up.
I suggest you try resyncing again from scratch (close your Vault, backup wallet.dat, remove all files from the CryptoBullion folder in Roaming except wallet.dat, reload the bootstrap). I have requested that an updated Bootstrap be posted, this will make syncing much easier (the URL to go get the Bootstrap is in the OP).
Also, very, very important, do not enable staking while your Vault is syncing or you will get many orphans and perhaps this is how your Vault has gone on a fork.
September 18, 2017, 10:57:59 AM
what do you guys think CPU, RAM and HDD have the effect on staking and or rather chain syncing.
Because i know for sure my internet connection is decent. but blocks are being generated faster than my sync.. i am always stuck somewhere from 53000 remaining to 55000 remaining. and right now it seems its going the other way.
Because i know for sure my internet connection is decent. but blocks are being generated faster than my sync.. i am always stuck somewhere from 53000 remaining to 55000 remaining. and right now it seems its going the other way.
I run my Vault in an 8 year old netbook, Intel Atom CPU, 2 GB RAM, damn slow HDD. It's sluggish to sync (high CPU usage), but it still manages to catch up.
well right now im trying it in my acer aspire one netbook. not even 8 years old but nope. but its not the case with few others coins i am staking.. they are always on time.
September 18, 2017, 10:07:12 AM
what do you guys think CPU, RAM and HDD have the effect on staking and or rather chain syncing.
Because i know for sure my internet connection is decent. but blocks are being generated faster than my sync.. i am always stuck somewhere from 53000 remaining to 55000 remaining. and right now it seems its going the other way.
Because i know for sure my internet connection is decent. but blocks are being generated faster than my sync.. i am always stuck somewhere from 53000 remaining to 55000 remaining. and right now it seems its going the other way.
I run my Vault in an 8 year old netbook, Intel Atom CPU, 2 GB RAM, damn slow HDD. It's sluggish to sync (high CPU usage), but it still manages to catch up.
September 18, 2017, 09:39:07 AM
what do you guys think CPU, RAM and HDD have the effect on staking and or rather chain syncing.
Because i know for sure my internet connection is decent. but blocks are being generated faster than my sync.. i am always stuck somewhere from 53000 remaining to 55000 remaining. and right now it seems its going the other way.
Because i know for sure my internet connection is decent. but blocks are being generated faster than my sync.. i am always stuck somewhere from 53000 remaining to 55000 remaining. and right now it seems its going the other way.
Are you using the bootstrap for syncing? Vault 2.4.3 won't sync without using the bootstrap (this is one of the issues that Vault 3.0 solves).
Also, there is a tool posted in the OP of this thread for this type of problem - have you tried it?
Yup i tried bootstrap manually and with the tool. i have like 6 connections but it doesnt sync fast enough for me to stake anything. my lappy has been 24/7 ON from past few days now. no loss in connection as well.
what is the ETA of vault 3.0? and will it be 32bit compi also right?
September 18, 2017, 02:47:17 AM
what do you guys think CPU, RAM and HDD have the effect on staking and or rather chain syncing.
Because i know for sure my internet connection is decent. but blocks are being generated faster than my sync.. i am always stuck somewhere from 53000 remaining to 55000 remaining. and right now it seems its going the other way.
Because i know for sure my internet connection is decent. but blocks are being generated faster than my sync.. i am always stuck somewhere from 53000 remaining to 55000 remaining. and right now it seems its going the other way.
Are you using the bootstrap for syncing? Vault 2.4.3 won't sync without using the bootstrap (this is one of the issues that Vault 3.0 solves).
Also, there is a tool posted in the OP of this thread for this type of problem - have you tried it?
September 18, 2017, 01:23:41 AM
what do you guys think CPU, RAM and HDD have the effect on staking and or rather chain syncing.
Because i know for sure my internet connection is decent. but blocks are being generated faster than my sync.. i am always stuck somewhere from 53000 remaining to 55000 remaining. and right now it seems its going the other way.
Because i know for sure my internet connection is decent. but blocks are being generated faster than my sync.. i am always stuck somewhere from 53000 remaining to 55000 remaining. and right now it seems its going the other way.
September 17, 2017, 05:40:07 PM
I wrote a book about the first year of Crypto Bullion. Please take a look:
https://www.amazon.com/Crypto-Bullion-History-First-Year/dp/1537636022/ref=asap_bc?ie=UTF8
If anyone has questions, please private message me.
https://www.amazon.com/Crypto-Bullion-History-First-Year/dp/1537636022/ref=asap_bc?ie=UTF8
If anyone has questions, please private message me.
September 17, 2017, 05:32:28 AM
looking at the BTC loan service of poloniex
the rates are extremely low 0.013% for 2 days on average.
From time to time loan offers from 1% to 2% for 2 days appear.
your robot can take advantage of its offers?
the rates are extremely low 0.013% for 2 days on average.
From time to time loan offers from 1% to 2% for 2 days appear.
your robot can take advantage of its offers?
yes it can, the A.I. collects the data, which is use to get the correct rates, it can also be program to loan out a part of the sum park there, till there is a spike in the rates, which will activate the bot
September 16, 2017, 04:38:14 PM
CRYPTO BULLION (CBX) cannot be lost or stolen, nor can it be carried away. Purchased with common sense, paid for in full, and managed with reasonable care, it is about the safest investment in the world.
September 16, 2017, 02:39:20 PM
Hey.
for some reason my chain sync is too slow. like the last 10% is taking forever. which is a new because before it used to sync at a reasonable time.
Currently using the 2.4 vault.
Any suggestions?
for some reason my chain sync is too slow. like the last 10% is taking forever. which is a new because before it used to sync at a reasonable time.
Currently using the 2.4 vault.
Any suggestions?
Maybe you're connected to just one peer? I don't really see a reason for that, all other things being equal (PC, CPU, RAM...).
Yeah, that's why it seems weird to me. I am connected to 5 actually. And its not the internet speed for sure, currently in holland with like 150mbps.
well i am just going to stake forever 24/7. have a dedicated laptop for staking coins haha. just waiting for the new vault.
September 16, 2017, 11:58:45 AM
Hey.
for some reason my chain sync is too slow. like the last 10% is taking forever. which is a new because before it used to sync at a reasonable time.
Currently using the 2.4 vault.
Any suggestions?
for some reason my chain sync is too slow. like the last 10% is taking forever. which is a new because before it used to sync at a reasonable time.
Currently using the 2.4 vault.
Any suggestions?
Maybe you're connected to just one peer? I don't really see a reason for that, all other things being equal (PC, CPU, RAM...).
September 16, 2017, 06:53:13 AM
Hey.
for some reason my chain sync is too slow. like the last 10% is taking forever. which is a new because before it used to sync at a reasonable time.
Currently using the 2.4 vault.
Any suggestions?
for some reason my chain sync is too slow. like the last 10% is taking forever. which is a new because before it used to sync at a reasonable time.
Currently using the 2.4 vault.
Any suggestions?
Jump to: