Also does anyone have a Slack invite link?
https://cryptobismuth.herokuapp.com/ 
Topic: 🤖[ANN][BIS]Bismuth 2.0 - Beyond DeFi - page 129. (Read 156111 times)
Also does anyone have a Slack invite link?
Pool information is here:
Dev-pool (may be getting some updates): https://bitcointalksearch.org/topic/m.20081310
Acc-pool: https://bitcointalksearch.org/topic/m.20173585
Using the ACC-Pool method how do i limit the amount of threads the miner uses? Dev-pool (may be getting some updates): https://bitcointalksearch.org/topic/m.20081310
Acc-pool: https://bitcointalksearch.org/topic/m.20173585
Great. Thanks for the info!
Very interested in Bismuth. Is it best to wait for it to be added to exchanged or is it still worth trying to mine? Any guesses on the first exchange it might be added too?
Join slack and search #exchanges. To summarize, both Bittrex and Cryptopia have contacted the dev requesting additional methods to be implemented.
Very interested in Bismuth. Is it best to wait for it to be added to exchanged or is it still worth trying to mine? Any guesses on the first exchange it might be added too?
Any news about listing Bismuth Coin to an exchange?
Pool information is here:
Dev-pool (may be getting some updates): https://bitcointalksearch.org/topic/m.20081310
Acc-pool: https://bitcointalksearch.org/topic/m.20173585
Dev-pool (may be getting some updates): https://bitcointalksearch.org/topic/m.20081310
Acc-pool: https://bitcointalksearch.org/topic/m.20173585
Another interesting project, TOR, Python, CPU minable. I think I'm going to start my old Dual-XEON server.
But at first would like to know where is some pool, because in OP links, the first one is not working, and second one
is link to slack. So anyone can en-light this to me?
But at first would like to know where is some pool, because in OP links, the first one is not working, and second one
is link to slack. So anyone can en-light this to me?
I would jump into the slack and get in touch with the guys in the #pool channel. They will have the info needed to hop on the mining train.
Hi Guys,
I have a question.
What hardware do you recommend to mine CPU coin. For example to mine Bismuth (BIS) OR Zero coin based on Zcash by CPU.
If you have a link where I can grab more info it will be helpful
Thanks
I have a question.
What hardware do you recommend to mine CPU coin. For example to mine Bismuth (BIS) OR Zero coin based on Zcash by CPU.
If you have a link where I can grab more info it will be helpful
Thanks
Another interesting project, TOR, Python, CPU minable. I think I'm going to start my old Dual-XEON server.
But at first would like to know where is some pool, because in OP links, the first one is not working, and second one
is link to slack. So anyone can en-light this to me?
But at first would like to know where is some pool, because in OP links, the first one is not working, and second one
is link to slack. So anyone can en-light this to me?
I just don't understand why difficulty is so high considering it's supposed to be CPU mining only, could it be bots maybe? not sure if it's worth mining.
Thanks for single file ledger.db on github.
I have exactly the same problem. Thanks for the link, but I wonder if this synchronisation issue is being addressed?
Healthy blockchain should be easy to sync without snapshots. Right now, it looks like snapshots of the ledger are the only way to sync this. Without them, the chain keeps going back and forward, gets some blocks, then rewinds back. I though that is just my node, but it seems to be a common issue.
Isn't this a serious issue to address?
P.S. One additional small question: what is the right way to do a backup? Is making a copy of "privkey.der" enough, or other files may be needed too?
Healthy blockchain should be easy to sync without snapshots. Right now, it looks like snapshots of the ledger are the only way to sync this. Without them, the chain keeps going back and forward, gets some blocks, then rewinds back. I though that is just my node, but it seems to be a common issue.
Isn't this a serious issue to address?
P.S. One additional small question: what is the right way to do a backup? Is making a copy of "privkey.der" enough, or other files may be needed too?
I have experienced the same with the last few wallets I tried installing and syncing. The number of blocks climbs and then keeps jumping back down. So I am never in complete sync. Just gets stuck somewhere rewinding over and over.
Hey guys,
Having issues syncing after removing VPN. Network blocks that im behind are actually increasing once i try to sync. How can i start the syncing again from the begining?
Having issues syncing after removing VPN. Network blocks that im behind are actually increasing once i try to sync. How can i start the syncing again from the begining?
Try this up to date, place in bismuth folder/static:
https://mega.nz/#!tdJkER6Q!Z9wBdNVXmQv0LXRft722s2JBXDh20YPsl_RxFwxOivs
I have exactly the same problem. Thanks for the link, but I wonder if this synchronisation issue is being addressed?
Healthy blockchain should be easy to sync without snapshots. Right now, it looks like snapshots of the ledger are the only way to sync this. Without them, the chain keeps going back and forward, gets some blocks, then rewinds back. I though that is just my node, but it seems to be a common issue.
Isn't this a serious issue to address?
P.S. One additional small question: what is the right way to do a backup? Is making a copy of "privkey.der" enough, or other files may be needed too?
To my understanding, this is what the hard fork for 3.9 is trying to accomplish. Remember Bismuth is an *experimental* Python blockchain.
Backing up privkey.der is enough, but might as well back up pubkey.der to save a step of having to regenerate it.
there are 2 types of pools atm.
a closed source, developed by a community member and an open source, developed by hclievess.
search through topic to find the information or join slack.
a closed source, developed by a community member and an open source, developed by hclievess.
search through topic to find the information or join slack.
Let me announce there will be a 3.9 hardfork on August 1 to improve mining difficulty tapering and to introduce full data serialization (mainly on the network level)
The hardfork will be immediate with the new client and old clients will be diverted to a fork, because communication protocol dramatically changes
The hardfork will be immediate with the new client and old clients will be diverted to a fork, because communication protocol dramatically changes
Do we have a steady pool now? Or an exchange?
To make a wallet backup you need pubkey.der and privkey.der (or privkey_encrypted.der)
Hey guys,
Having issues syncing after removing VPN. Network blocks that im behind are actually increasing once i try to sync. How can i start the syncing again from the begining?
Having issues syncing after removing VPN. Network blocks that im behind are actually increasing once i try to sync. How can i start the syncing again from the begining?
Try this up to date, place in bismuth folder/static:
https://mega.nz/#!tdJkER6Q!Z9wBdNVXmQv0LXRft722s2JBXDh20YPsl_RxFwxOivs
I have exactly the same problem. Thanks for the link, but I wonder if this synchronisation issue is being addressed?
Healthy blockchain should be easy to sync without snapshots. Right now, it looks like snapshots of the ledger are the only way to sync this. Without them, the chain keeps going back and forward, gets some blocks, then rewinds back. I though that is just my node, but it seems to be a common issue.
Isn't this a serious issue to address?
P.S. One additional small question: what is the right way to do a backup? Is making a copy of "privkey.der" enough, or other files may be needed too?
Maybe stupid question:
How do we upgrade a wallet? I'm running the windows version with gui.
How do we upgrade a wallet? I'm running the windows version with gui.
Jump to: