Topic: Bullion (CBX) 'the Digital Precious Metal' | 2019 Roadmap published - page 3. (Read 359535 times)

I have my issues straightened out, I am going to get another staking node going at work, the laptop there is on 24/7 and hardly ever used and I'm the guy that does any work on it if needed. I have about 2500 CBX, going to send 500 to it to get things going. And I'll make sure and open port 7695.

I'm not able to leave my wallet open to enable staking 24/7 for a variety of reasons.  It may have to a roster system whereby people undertake to commit to leaving their wallets open and staking a couple of days a week and hopefully there will be some sort of overlap of staking wallets to keep the block-chain moving.

The problem seems to be a current insufficient of staking chunks. More CBX would need to stake in order to stabilize the network.

Thanks for the update, if you're out of pocket at all for the VPS (assuming it was online of course) then I for one don't mind helping you out with a few dollars.  Will this be an on going solution, or a one off fix?

Just a follow up in case it could be useful for somebody: it turns out the wallet slow loading/unloading is indeed due to the lack of RAM and using the swap space. I upgraded to 2GB RAM VPS, and the wallet loading/unloading there is 100x (if not 1000x) faster. So the recommended minimum RAM for Bullion wallet should be around 2GB.

Give me a couple of hours... It took too long to load/unload the wallet yesterday (probably my VPS is way too slow/cheap, but the wallet somehow takes up to 2 hours to load on 1GB RAM Ubuntu VPS, and around the same time to unload properly (until bullion-shutoff process disappears), so I gust gave up and went to sleep

Turning it on now. Hope it'll work like it did last time...

EDIT: it did work - the chain moves forward now!

I suppose you had no luck there.

I believe your suggestion is mostly right: after 6 hours, all wallets consider themselves out-of-sync, at least when restarted. I also made a similar hack to try to move things around but unfortunately this time none of my current coin chunks meet the necessary criteria to stake: being still for 1 hour is not enough, although in practice it usually is. There is a flag called "stake-modifier". Your chunks can only stake if there is a block with this flag at least an hour in the future since your chunk was last moved/staked. And this is exactly my problem: most of my chunks are within an hour of that last block, so not eligible at all. I have 2 other chunks that are older than the current last block, just over an hour, but unfortunately the last 2 blocks in the chain (those over an hour for me) do not have the necessary "stake-modifier" flag so I cannot make them stake.
The solution seems to be someone with eligible chunks to try to stake hacking the wallet code and bypassing that 6-hour sync limit..

This chain needs staking nodes, not just regular ones. It is worth to have some coins on those nodes, preferably divides into several inputs.

I'll try to move the chain today.

I wish I was better at programing or had more contacts, I am an admin in the CBX Telegram channel but the only one that was really around then was Elambert and he hasn't been there in a long time, since the failed swap. I really think his last huzzah was the Coinbook listing, and after that fell through he just gave up, he seemed to have a bunch of family issues going on as well. He wasn't one of the programmers, he always talked about being in contact with the person that was doing the work but if he was even telling the truth is up for debate, I don't really know if anything was going on. So I really don't think there's anyone to take the reigns as it currently sits. Such a shame. If we can get the chain going again, I can get at least 2 more nodes up.

See my post above yours... It describes the reason. I'll try to kickstart it again, but frankly speaking, we need that dev...

So this blockchain has hung itself again. How does it happen? Can we restart it?

Your theory is nice, but I can confirm it was not the case, because I had my wallet completely synced, ready to stake, and with mature coins ready to stake. They did not stake however.

Now I can guess what happened (I am at least 95% sure this was the case): about 22 days ago by some reason (might be just a coincidence) all the staking wallets were offline, and there were no block produced for 6 hours. In the source code it is programmed that if there is no block for 6 hours, the wallets consider themselves "not synced" (https://github.com/elambert2014/bullion/blob/81e92ab63a64e85887540ff609d140203ed98b9d/src/masternode-sync.cpp#L22).

So even when the staking nodes returned, they found themselves in "not synced" state, and waited to catch up and get fresh blocks. That never happened as there were just no fresh blocks produced by anybody, because of the same reason - every single wallet waited to be "synced".

So what I did, I modified this line: https://github.com/elambert2014/bullion/blob/81e92ab63a64e85887540ff609d140203ed98b9d/src/masternode-sync.cpp#L24, to "static bool fBlockchainSynced = true;". It is an obviously wrong modification for the general case, but in such deadlock situation it helped, because after I started the modified wallet, it considered itself "synced", and immediately produced a block; all other staking wallets got a fresh block, changed their status to "synced" and started staking (that can be seen in block explorer: first block after the long delay is from my wallet, the following ones are from other mixed ones).

So, bottomline - if by some reason this chain stops again for 6 hours, it will stop forever (or until someone makes a modification similar to the one I did).
Conclusion: try to keep your staking wallets always online


Yep, I really hope some of the original developers feels a kind of nostalgia and returns to keep this good old coin. There just aren't many projects like this, with such rich history going back to the roots...

My wallet is now back in synch and staking again. It did stop along with Chainz block explorer for 22 days. Looks like whatever you did, got it moving again. Good job drays👍🏻

Now to continue performing CPR until someone resuscitates, or until all hope is lost and forgotten.
Such a shame.

Yes, I tried that and it worked.


I'm now at block 3762216 which was received eleven minutes ago.  My transaction has also been confirmed which can only mean that there just simply hasn't been any coins staked in the last two weeks.


My guess is that there were no transactions plus there were no coins being staked and, although every-one's block-chain had downloaded the entire block-chain the program though it hadn't been completely downloaded and was showing "Out of sync" - if that makes sence?

I'll try to keep my wallet open a bit more often from now on to help ensure there are coins staking.

Sorry guys, I did not follow this thread for few days (Bitcointalk didn't send me a notification of new post to the thread update - that's strange).
I assume the correct conf file is "bullion.conf", because after I put the "connect" entries there, they made an effect.

Last few days I have installed temporary nodes on two Linux servers, synced them from scratch, and will try to modify the source code a bit, to stake at least once... I assume the wallet doesn't stake, because it thinks it is not synced. So I want to forcefully set the "synced" status and see what it does... Lets see if this works, if not, I'll try to send the transaction as Timelord2067 suggested.

UPDATE: well, it seems this indeed worked! My wallet staked once, then some other wallets started staking, and the chain is moving ahead now! Now we need just two things: (1) enough stakers to move it further (I have just 12 inputs..); (2) somebody doing anything to revive not only the blockchain, but the coin itself...

Yobit has allowed their various coin's wallets to fork from their relevant block-chains and go off on a tangent - you can send coins to Yobit, but if you withdraw, nothing comes back out and they blame you not themselves for the funds going "missing".  About two years ago this Forum put a block on Yobit advertising and various persons on DT have taken it upon themselves to dish out negative trust feedback should a user display a Yobit signature.

Yobit is probably the cause of this stalling.

Looks like Yobit's wallet is in maintenance as well, but it probably has been for a while now lol surprised they're still in business.

I had to restart my wallet a couple of hours ago but sent the rawtransaction at that time and again just now after seeing your message.  Not sure if it'll work or not - I've also retyped in to the console to ensure my coins are staking and can (hopefully) process the transaction.

(worth a shot)

Just tried it.

I have created a transaction - can everyone go to their debug console and enter this (providing you know what you are doing)


If we're sending the same transaction to the mempool, then it's possible that the network will kick start (or not - I'm open to suggestions)