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

[Timelord2067]

I've got six nodes:

Code:

node2.bullion.one
24.55.154.69:7695
89.210.233.40:7695
82.21.164.47:7695
95.217.77.209:7695
73.121.220.52:7695

and am stuck at block 3762194 as well.


The funny thing is the SexCoin block-chain ground to a halt on Chainz about six weeks ago while the rest of the network was still ticking over, so I'm wondering if this site (Chainz) is the only one to have a block explorer for Bullion?  Hence the wallets have also stopped?

If anyone had a block hight higher than 3762194, then we could move our wallet's block-chains along too.

[1714191915]

1714191915

[1714191915]

1714191915

[1714191915]

1714191915

[1714191915]

1714191915

[Himalayacoin007]

may i know what the issue is? is it a big issue . i hope not as i really like this coin ever since i join up at 60k stas

[dexterw1n]

I'm one of those nodes and I'm stuck at 3762194 too...

[drays]

I see just one page back guys were bragging about this coin "just simply works", and there is no need for a developer..

Uh, it seems this is not the case. It works, until it just doesn't.

Anyone has any idea on why this PoS chain could just stop without visible reason? I have seem similar behavior from few older PoS coins, some were fixed by developer somehow, but nobody eventually wrote anything about the reasons. This is one of the reasons PoW chains (or at least PoW/PoS) are more viable and resilient - anyone can move them again by just directing some hash.

[dexterw1n]

I just wonder if it's something in the 3.0.0 or the 3.0.1 client or both. I suck at crypto, is there something I could put in my conf to block node2.bullion.one? So I can test it and see if it's that? I dunno, I'm currently reindexing right now.

[drays]

I just wonder if it's something in the 3.0.0 or the 3.0.1 client or both. I suck at crypto, is there something I could put in my conf to block node2.bullion.one? So I can test it and see if it's that? I dunno, I'm currently reindexing right now.

As far as I know, there is no explicit way to manually block a node. However you can force the wallet to connect only to some predefined nodes, and reject all others.
For that you need to remove "addnode=" entries from your bullion.conf (in case if there were any), and add "connect=" entries pointing to the hosts you want to exclusively connect to.

So, basically, you need to put this into your bullion.conf:

Code:

connect=95.217.77.209
connect=82.21.164.47
connect=89.210.233.40
connect=24.55.154.69
connect=73.121.220.52

However I doubt this will actually help... Might worth a try, anyway. I already did so, and my wallet is connected to all nodes except node2.bullion.one currently.

[Timelord2067]

I just wonder if it's something in the 3.0.0 or the 3.0.1 client or both. I suck at crypto, is there something I could put in my conf to block node2.bullion.one? So I can test it and see if it's that? I dunno, I'm currently reindexing right now.

As far as I know, there is no explicit way to manually block a node. However you can force the wallet to connect only to some predefined nodes, and reject all others.
For that you need to remove "addnode=" entries from your bullion.conf (in case if there were any), and add "connect=" entries pointing to the hosts you want to exclusively connect to.

So, basically, you need to put this into your bullion.conf:

Code:

connect=95.217.77.209
connect=82.21.164.47
connect=89.210.233.40
connect=24.55.154.69
connect=73.121.220.52

However I doubt this will actually help... Might worth a try, anyway. I already did so, and my wallet is connected to all nodes except node2.bullion.one currently.

Is it bullion.conf or cryptobullion.conf

I have entries in the latter while the former is empty.

In my cryptobullion.conf file I now have:

Code:

connect=95.217.77.209
connect=82.21.164.47
connect=89.210.233.40
connect=24.55.154.69
connect=73.121.220.52

# addnode=174.72.227.20:7695
# addnode=175.156.166.57:7695
# addnode=67.128.36.90:7695
# addnode=76.169.51.184:7695
# addnode=80.3.158.239:7695
# addnode=87.98.243.61:7695
# addnode=94.130.237.52:7695
# addnode=94.15.192.76:7695

[dexterw1n]

I'll try it too but if it was going to work it would have by now.

[Timelord2067]

I'll try it too but if it was going to work it would have by now.

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

Code:

sendrawtransaction 010000002b93ad6001d253fdd196ab612f54839d1926d6b97ee4c1137acb61c6507e763a001bf0b9ff01000000484730440220308b405752b34b90a9231b677373227007575dd5d8e0aac4bf6bf739595c10e702205f94774bd864db14d3d077b9e4d4de8a6bd1a56596067a02f1ac08ce0d151dd801ffffffff0159808e00000000001976a9145d7beb10318f4b9977209241cbd4cf1e278b83f388ac00000000

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)

[dexterw1n]

I'll try it too but if it was going to work it would have by now.

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

Code:

sendrawtransaction 010000002b93ad6001d253fdd196ab612f54839d1926d6b97ee4c1137acb61c6507e763a001bf0b9ff01000000484730440220308b405752b34b90a9231b677373227007575dd5d8e0aac4bf6bf739595c10e702205f94774bd864db14d3d077b9e4d4de8a6bd1a56596067a02f1ac08ce0d151dd801ffffffff0159808e00000000001976a9145d7beb10318f4b9977209241cbd4cf1e278b83f388ac00000000

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)

Just tried it.

[Timelord2067]

Just tried it.

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

Code:

reservebalance false

to the console to ensure my coins are staking and can (hopefully) process the transaction.

(worth a shot)

[dexterw1n]

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.

[Timelord2067]

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.

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.

[drays]

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...

[Timelord2067]

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.

Yes, I tried that and it worked.

Last few days I have installed temporarily 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.

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.

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...

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.

[Killiz]

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 temporarily 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...

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.

[drays]

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.

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

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.

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...

[Noojna]

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

[drays]

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

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

[dexterw1n]

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.