UPDATE
We have contacted all exchanges and provided them with the information on how to update their exchange wallets so they can open up withdrawals, deposits, and trading.
We will provide updates as exchanges come back online.
|
|
|
So when can we expect the market to unfreeze?
Likely going to be one more day until we contact them. Then hopefully less than a day for them to get up and running again. If everything goes well and exchanges don't lag, should be good to go by tomorrow afternoon barring any issues.
|
|
|
UPDATEImportant! 03/20/2018 Mandatory Wallet Update (Version 1.2.3) Please update all of your local wallets and masternodes to the latest version 1.2.3 as soon as possible. You will need likely need to remove everything except for wallet.dat and masternode.conf(if applicable) from your Bulwark Data directory before launching 1.2.3 to initiate a full new sync. https://github.com/bulwark-crypto/Bulwark/releaseshttps://github.com/bulwark-crypto/Bulwark-MN-InstallAdditionally, please insert the following addnodes in your bulwark.conf: addnode=bwk1.masterhash.us:52543 addnode=bwk2.masterhash.us:52543 addnode=bwk3.masterhash.us:52543 addnode=bwk4.masterhash.us:52543 addnode=bwk5.masterhash.us:52543 addnode=bwk6.masterhash.us:52543 addnode=bwk7.masterhash.us:52543 addnode=bwk8.masterhash.us:52543 addnode=bwk9.masterhash.us:52543 addnode=bwk10.masterhash.us:52543
|
|
|
UPDATE
Just wanted to keep everybody up to date. Due to the number of wallets needing to be updated to 1.2.2 and with the numbers we've seen, Option #1 is going to take much longer than we'd prefer.
As such, we'll be going with Option #2. We are currently testing a new mandatory wallet version tonight and will be releasing tomorrow. Please keep an eye on our Discord, Telegram, Twitter, Wechat, and Bitcointalk threads as we will announce and provide a link to download the new wallet on these platforms once it is ready for public release.
|
|
|
Hey dev, I see that you are angrily reporting posts that call you out on your BS now. Are you still trying to save face by dodging legitimate questions and tell people to "update" their wallet to a version released weeks ago before the second hardfork?!!
What happened with that app you said you will run for 10+ hours and that it may sort everything out? It seems it's past the 10-hour mark and still nothing has happened.
.....
I haven't reported any of your posts. You're more than welcome to ignore our announcements, discussions, and information we're providing to the community and make up conspiracy theories all you like based on things you seem to know very little about.
|
|
|
UPDATE
For the sake of transparency, we want to keep everyone up to date with what we're doing. This is where we're currently at:
Option 1 Step 1: Get all wallets, masternodes, and pools on 1.2.2 Step 2: Run Spork again to get everything pulled together correctly. Step 3: Provide addnodes if necessary
BLA BLA BLA
please provide a list of actives nodes if possible in order to anyone can make an update with all information we can get from this post, thanks for the info btw. If enough people update and we run the spork so it can do it's job appropriately, addnodes won't be necessary. We will provide them IF needed.
|
|
|
UPDATEFor the sake of transparency, we want to keep everyone up to date with what we're doing. This is where we're currently at: Option 1 Step 1: Get all wallets, masternodes, and pools on 1.2.2 Step 2: Run Spork again to get everything pulled together correctly. Step 3: Provide addnodes if necessary Option 2: Step 1: Release a new wallet update to force everybody onto the same chain Step 2: Get every wallet, pool, and masternode updated. Step 3: Provide addnodes if necessary To Update Your Wallet: 1. Download 1.2.2 from github at https://github.com/bulwark-crypto/Bulwark/releases/tag/1.2.2To Update Your Masternode: 1. Download 1.2.2 from github at https://github.com/bulwark-crypto/Bulwark-MN-Install onto VPS 2. Run update_node.sh If you're having issues opening the wallet after updating to 1.2.2: 1. Delete everything but wallet.dat in your Bulwark data directory (you may also keep masternode.conf if applicable) 2. Restart the wallet using version 1.2.2 executable If you're already updated to 1.2.2: 1. Leave the wallet open. 2. Be patient 3. There is no specific chain or block you should be on currently. If you're updated, just leave it alone and be patient. Following these two will immensely help speed up the time frame in which we are able to push this fix through. With all of these issues, be sure to save a local copy of your .dat and .conf files in case you run into any trouble just to be on the safe side. We are currently attempting to handle this via Option #1 considering a mandatory update isn't something anybody really wants to deal with unless absolutely necessary. If we cannot perform this fix in a timely manner, we will move on to Option #2.
|
|
|
UPDATE
We are going to be utilizing a Spork to attempt to fix the chain issues we're having at this time and get everybody on the same chain.
The Spork will essentially be forcing a reindex on the network of the last portion of blocks in which these splits have caused issues. The goal in doing this is to coerce the network majority to come to consensus on a single chain sooner rather than later by waiting and hoping it does so in a timely manner and without causing any additional issues that may arise.
While this is active, it is imperative that NOBODY reindex, rebuild, or otherwise try to "fix" their wallet. Doing so may result in unwanted issues or potentially lost coins. Please do not under any circumstance do anything other than leave your wallet open while the Spork is doing what it is designed to do.
We will be leaving the Spork activated to do what it needs to for 10+ hours. As soon as we are comfortable and can verify that it has done what it needs to, we will be sure to instantly inform the community of what the next step, if any, users will need to take.
Thank you for your support and patience.
|
|
|
Great project, I'm optimistic with my masternode in this coin.
Very nice. I liked a lot this project and after all issue with the wallet I thinks they are in the right path. I’m gathering some money to buy the coins to have my masternode. Just a question, where did you put your MN? In a VPs? The coins get locked in your local wallet where you have access to them at any time. The actual masternode itself is hosted on a VPS.
|
|
|
please write a list of masternode for config, and the wallet is not synchronized
Could you reword this? I'm not entirely sure what information you're looking for. If you're having issues synchronizing your wallet, make sure you're updated to version 1.2.2 of the wallet. Then, delete everything in your appdata/roaming/bulwark folder except wallet.dat and masternode.conf(if you have one) then open up the wallet with the new 1.2.2 executable and let the wallet sync.
|
|
|
BWK wallet seems disabled at Stocks.Exchange at the moment (along with about 13 other wallets).
We contacted them 4 days ago and had them update their exchange wallet accordingly. If we're down for some other reason there, they haven't reached out to us to let us know why.
|
|
|
Why the wallet is not staking?
Staking isn't active yet. It's only PoW/MN right now. PoS will activate around December 2018.
|
|
|
I notice that Cryptopia's wallet is stuck at block 86399. https://www.cryptopia.co.nz/CoinInfo/?coin=BWKI wonder how long it will take Cryptopia to get their wallet to sync, this time. Hope it doen't take them weeks like last time. To get my wallet to sync, I had to end up deleting everything but the wallet.dat in my appdata folder. It took less than 30 minutes to sync from scratch. Hope the crackerjack team at Cryptopia can figure it out. I just spoke to them and they're working on it now. It's a pretty simple fix so I'm assuming they'll be back up soon. Edit: Cryptopia and Cryptobridge are both synced up and working. I've personally tested a deposit and withdrawal on each with no issues.
|
|
|
If your local wallet is not syncing past block 86399, please delete your peers.dat and remove any addnodes from your Bulwark.conf. Then restart your wallet, and you should sync up with no issues.
If your masternode is stuck on block 86399, please run these commands in your SSH program of choice.
sed -i -e '/^addnode=/d' ~/.bulwark/bulwark.conf
this will delete old nodes in your conf
rm -rf ~/.bulwark/peers.dat
then restart with
bulwark-cli stop bulwarkd -daemon
wait approximately 10 minutes for it to sync, to check your block status you can use this command
bulwark-cli getinfo
While masternode payments should be unaffected, It is advisable to not transfer coins around until futher notice. We are contacting exchanges currently, they will be restarting their wallets which hopefully won't take long.
Apologies for the for the uncertainty in the last few hours, we have been reviewing the situation. Expect a further update once we deem the network stable. Edit: Would like to thank the pool operators and community members who were helping out, cool doods
We've informed all exchanges and they should be doing this very quick fix at their earliest opportunity.
|
|
|
One of Bulwark's main goals is decentralization and it's important that we expand our network globally. Therefore, we have started an official WeChat (微信) group! Scan the QR code below with the WeChat App and join us!
|
|
|
I'm really disappointed with the Bulwark price at the moment (19000 sat it is real dump). Was it problems of Cryptopia only? Or it was problems on Bulwark side? Most imortant question - How to avoid the same problems in the future?
The problem is miners like you or me dump the coin before anyone else does and because most of them think same they do it so quickly the price goes down even quicker. That causes miners to decide to move to another coin. Difficulty and hashrate drop so mininers who continue mining BWK mine it easier. So easier to get profit and dump the price further. Nevereding story so I do not believe in recovery. Check Tun, GOA, DSR, DIN, DNR and many more masternode coins. Also masternode owners dmp for the same reason - to ensure they dump before someone else does. HODL does not exist anymore and those who shout it usually dump first. I'd have to disagree with you there considering we're all still holding our dev shares of the premine. Any news for pump? When a next update? We released v1.2.2 of the wallet not too long ago. We're also working on a brand new custom built explorer as well as an official mobile wallet.
|
|
|
There was a few cases with another coins that could not be resolved for weeks! Great job by devs to sort out issue with cryptopia so smooth and fast.
Are you for real? Fast? It took a few weeks. Ask your doctor to change your meds or change the doctor... We had the issue fixed within 2 days, tested for another few just to make absolutely sure everything was good to go again before we re-opened, and then had all exchanges, pools, and wallets up and running just fine again after that. Cryptopia continued having issues for another 2-3 weeks after the fact with issues that were out of our control.
|
|
|
I'm really disappointed with the Bulwark price at the moment (19000 sat it is real dump). Was it problems of Cryptopia only? Or it was problems on Bulwark side? Most imortant question - How to avoid the same problems in the future?
The problem is miners like you or me dump the coin before anyone else does and because most of them think same they do it so quickly the price goes down even quicker. That causes miners to decide to move to another coin. Difficulty and hashrate drop so mininers who continue mining BWK mine it easier. So easier to get profit and dump the price further. Nevereding story so I do not believe in recovery. Check Tun, GOA, DSR, DIN, DNR and many more masternode coins. Also masternode owners dmp for the same reason - to ensure they dump before someone else does. HODL does not exist anymore and those who shout it usually dump first. I'd have to disagree with you there considering we're all still holding our dev shares of the premine.
|
|
|
Nope, it's not resolved. Their last updated was the following, LUX, BWK, DIME & XVG Deposit Issues We are aware that there is a number of LUX, BWK, DIME and XVG deposits that are not being processed successfully. Due to this, we have put these wallets in maintenance until this issue is resolved. We currently have a fix being deployed and estimate it will be resolved by COB tomorrow. When the wallets are removed from maintenance, all pending deposits will go through normally and these funds will appear in your accounts. Please note, this is not an issue with the wallets themselves, and is currently beyond the control of the coin developers.
Published by: froufrou @ 2/27/2018 4:10:20 AM Anyone know what they meant by COB? They say COB tomorrow, which would have been the 28th..which has now passed so again the problems continue....atleast they are giving updates ya know? At this point its almost like it doesnt even matter, seems like most have moved to crypto bridge, and honestly i think crypto bridge is the place to be, their staking is pretty juicy right now and their volume is growing fast. As for cryptopia keeping coins to run masternodes...I highly doubt it, although there has been accusations in the past of other exchanges staking coins in their wallet I have never seen any proof of an exchange doing something like this. My guess is it's just people upset that it's taking so long for them to update and get all the broken coins working again so they're looking for reasons outside of simply "they have too much on their plate" to justify why it's taking so long. People frequently land on "it's a scam!" because it's easy to say.
|
|
|
|