[ANN][BWK] BULWARK | NO ICO | Masternodes | Accelerated PoW | Seesaw PoS/MN

[GEFE5T]

When will the chain be restored?

[1715086983]

1715086983

[1715086983]

1715086983

[muzuca]

To ensure the health of the network and to get it back in sync, it is extremely important that everyone has the latest wallet (Version 1.2.2) both locally and on masternodes.


Wallet:
https://github.com/bulwark-crypto/Bulwark/releases

Masternode script:
https://github.com/bulwark-crypto/Bulwark-MN-Install/blob/master/update_node.sh

Extremely important announcement. Please upgrade your wallet to latest version, everyone. Please do it in order to avoid chainsplit on Bullwark network.

I updated my wallet to the last version, but it’s stucked on block 94302.

What I need to do?

Are you completely synced to that block? Or does the wallet say syncing in process at the bottom?

It’s saying: synchronizing with network ... and the block 94302.

I need to delete any files to start from the begin?

[bitChipper]

To ensure the health of the network and to get it back in sync, it is extremely important that everyone has the latest wallet (Version 1.2.2) both locally and on masternodes.


Wallet:
https://github.com/bulwark-crypto/Bulwark/releases

Masternode script:
https://github.com/bulwark-crypto/Bulwark-MN-Install/blob/master/update_node.sh

Extremely important announcement. Please upgrade your wallet to latest version, everyone. Please do it in order to avoid chainsplit on Bullwark network.

I updated my wallet to the last version, but it’s stucked on block 94302.

What I need to do?

Are you completely synced to that block? Or does the wallet say syncing in process at the bottom?

It’s saying: synchronizing with network ... and the block 94302.

I need to delete any files to start from the begin?

I dont think you need to delete any files just make sure you are on v 1.2.2 and let wallet sync, we don't have a set block to be at cause technically there isnt a correct chain yet, they are still waiting for everyone to update from 1.2.1 to 1.2.2

[Eatbatterys]

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

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

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

[thecil]

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.

[Eatbatterys]

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.

[tomassamot]

update to 1.2.2  delete all data but wallet.dat
resync
bulwark core error
error:A fatal internal error occured ,see debug.log for detials




2018-03-17 04:54:40 UpdateTip: new best=000000000013a24d7cdef42f41e41f373b3d2c2113494c8210c239edd52d542e  height=94246  log2_work=63.710515  tx=175243  date=2018-03-16 17:22:58 progress=0.988435  cache=38441
2018-03-17 04:54:40 ProcessNewBlock : ACCEPTED
2018-03-17 04:54:40 ProcessNewBlock : ACCEPTED
2018-03-17 04:54:41 *** System error while flushing: CDB : Error -30974, can't open database
2018-03-17 05:09:54 ERROR: ProcessNewBlock : ActivateBestChain failed
2018-03-17 05:09:54 Loaded 39077 blocks from external file in 1066299ms
2018-03-17 05:09:54 Reindexing finished
2018-03-17 05:09:54 dumpaddr thread stop
2018-03-17 05:09:54 opencon thread interrupt
2018-03-17 05:09:54 addcon thread interrupt
2018-03-17 05:09:54 ThreadStakeMinter() error
2018-03-17 05:09:54 ThreadStakeMinter exiting,
2018-03-17 05:09:54 stakemint thread exit
2018-03-17 05:09:55 net thread interrupt
2018-03-17 05:09:55 msghand thread interrupt
2018-03-17 05:09:55 PrepareShutdown: In progress...
2018-03-17 05:09:55 StopNode()
2018-03-17 05:09:55 Verifying mncache.dat format...
2018-03-17 05:09:55 Loaded info from mncache.dat  0ms
2018-03-17 05:09:55   Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, nDsqCount: 7
2018-03-17 05:09:55 Writting info to mncache.dat...
2018-03-17 05:09:55 Written info to mncache.dat  0ms
2018-03-17 05:09:55   Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, nDsqCount: 7
2018-03-17 05:09:55 Masternode dump finished  0ms
2018-03-17 05:09:55 Verifying budget.dat format...
2018-03-17 05:09:55 Loaded info from budget.dat  0ms
2018-03-17 05:09:55   Proposals: 0, Budgets: 0, Seen Budgets: 0, Seen Budget Votes: 0, Seen Final Budgets: 0, Seen Final Budget Votes: 0
2018-03-17 05:09:55 Writting info to budget.dat...
2018-03-17 05:09:55 Written info to budget.dat  0ms
2018-03-17 05:09:55 Budget dump finished  0ms
2018-03-17 05:09:55 Verifying mnpayments.dat format...
2018-03-17 05:09:55 Loaded info from mnpayments.dat  16ms
2018-03-17 05:09:55   Votes: 1783, Blocks: 683
2018-03-17 05:09:55 Writting info to mnpayments.dat...
2018-03-17 05:09:55 Written info to mnpayments.dat  15ms
2018-03-17 05:09:55 Budget dump finished  31ms
2018-03-17 05:09:55 *** System error while flushing: CDB : Error -30974, can't open database
2018-03-17 05:09:57 CDBEnv::EnvShutdown : Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
2018-03-17 05:09:57 Shutdown: done

[theonlyone]

Did you upgrade your daemon wallet?

[kaneo]

Worried about getting your wallet updated?

Just watch the video here to find out how to backup and update your wallet correctly, as well as some basic troubleshooting if you do have any issues.

https://www.bitchute.com/video/OBW8jBoEHj3l/

[feboru2]

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.

What about your "great relationship with Cryptopia"? Still trying to fool crypto profit calculators to lure in more unsuspecting miners?

What about your alt accounts created in a hurry trolling and insulting anyone who asks questions or tries to warn others of your scammy ways?


The people that you, along with your amateur and incompetent team, have tried to scam have the right to know that THEY SHOULD STOP MINING YOUR COIN, PERIOD. Because even if they have everything sorted out on their end, as did I, THEY WILL LOSE ANY AND ALL THE PROFITS GAINED FROM MINING THIS SH*TCOIN AS YOU WILL HARDFORK THE CHAIN FOR A THIRD TIME IN 2 MONTHS.


My suggestion to you in the post that you reported is still the same, and I will say it nicely this time as I am more calm today and have accepted that my profits from mining this coin will never see the light of day:


Dear Bulwark Developers,

Please give up trying to fool more unsuspecting miners and save face on this scam project. This is clearly not for you. Leave this to professionals and people who know what they are doing. Just sell your premined coins at the lowest price, pocket the profits, and fade into the sun. And then laugh at us for falling for your scam.

And for your next project, if you decide to still be part of the crypto world, please study the matter a lot more than watching a few videos on how to make a coin and scam people, if you want to be a recognized and respected name in this space.

Signed,

A Cryptocurrency Enthusiast


And I suggest any miner still mining this coin and hoping for the best, to reconsider what they are doing and stop mining this coin if they want to gain ANY profit from their rig.

[thecil]

To ensure the health of the network and to get it back in sync, it is extremely important that everyone has the latest wallet (Version 1.2.2) both locally and on masternodes.


Wallet:
https://github.com/bulwark-crypto/Bulwark/releases

Masternode script:
https://github.com/bulwark-crypto/Bulwark-MN-Install/blob/master/update_node.sh

Extremely important announcement. Please upgrade your wallet to latest version, everyone. Please do it in order to avoid chainsplit on Bullwark network.

I updated my wallet to the last version, but it’s stucked on block 94302.

What I need to do?

Are you completely synced to that block? Or does the wallet say syncing in process at the bottom?

It’s saying: synchronizing with network ... and the block 94302.

I need to delete any files to start from the begin?

check the network monitor, if ur getting data in response, wait some time to see if sync (some hours maybe).

othewise try to delete everything from the appdata/.../bwk folder (backup your wallet.dat first) in order to resync all the blockchain files.

[Eatbatterys]

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.

[feboru2]

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

Yes I will try to ignore your "announcements" and "information" you are providing to the community once I get my profits back. I sure as hell will sell all my Bulwark coins and will never look back. Thank you for your "helpful" reply.

Meanwhile I still suggest that you think about my suggestion to you, as this project seems to be stuck in an infinite loop of miners being lured in, the chain getting hardforked, miners getting scammed out of their profit, devs do not know what they are doing, devs dodging questions, and we are back to square one.

Remember you don't have to take this personally as this is business, and a good experience for you and your team to learn from, and also it saves you a lot of future headaches as well if you listen to my advice.

... make up conspiracy theories all you like based on things you seem to know very little about.

I have answered this to one of your team's alt accounts yesterday. And for your convenience, I will quote my previous post here again:

And to answer your last point, I have enough idea about the crypto world that when I see a situation like this happening (and I have seen quite a few of them in recent months), I know that there is something wrong and I try to warn other people who might be tempted to try the coin to make some profit based on common indicators (results of crypto profit calculators being one).

[feboru2]

And you still have not provided any answers to my other questions that I have asked you repeatedly. Professionalism indeed!

It seems that all of your team's defense strategy is based on name calling me for referring to Spork as "some app." Yes I know what Spork is and what it does, and a straightforward and well thought out crypto project does not need to have Spork executed on it AT ALL.

Do you think that it is necessary to run Spork in the first place if you and your team have the experience and knowledge to run a crypto project, and/or when you do not have malicious intentions in mind when starting your project?

[bspus]

My vps masternode is updated to latest core and is working fine, but my controller wallet on windows is giving me grief
Even after a full sync from scratch it crashes with a db error when trying to add the latest MN payment. Something about not being able to get a cursor.

I have also another instance running on a different machine/ISP. It has the same wallet but not configured to control the MN.
That one works fine.

[LukSus]

I resynched my wallet but I not see coins who mining from yesrtrday.

This Coin is lost forever?

If you any idea what can I do to get back?
My wallet must by open all time?
I mining with pooloDf32th, I must write to them something?

[kaneo]

My vps masternode is updated to latest core and is working fine, but my controller wallet on windows is giving me grief
Even after a full sync from scratch it crashes with a db error when trying to add the latest MN payment. Something about not being able to get a cursor.

I have also another instance running on a different machine/ISP. It has the same wallet but not configured to control the MN.
That one works fine.

Please try the following and then get back to us if you have further issues.

Windows key + R

Type "%appdata%" (without quotations)

Press enter

Navigate to the Bulwark folder

Delete everything but wallet.dat and masternode.conf

Start your wallet again

There is a full video on updating the wallet, with a video guide for these steps at the end here:

https://www.bitchute.com/video/qiR19zw5M7M/

I resynched my wallet but I not see coins who mining from yesrtrday.

This Coin is lost forever?

If you any idea what can I do to get back?
My wallet must by open all time?
I mining with pooloDf32th, I must write to them something?

It's entirely possible your wallet is on a different chain to your pool, please read all our recent announcements for more information on this.

Once the situation is resolved, we can look in to where your coins are and if they are recoverable.

[bspus]

Please try the following and then get back to us if you have further issues.

Windows key + R

Type "%appdata%" (without quotations)

Press enter

Navigate to the Bulwark folder

Delete everything but wallet.dat and masternode.conf

Start your wallet again

I've already done that. That's what I meant by sync from scratch. I also kept bulwark.conf but it only has the username/password info which I need for the masternode

here is the debug log last lines . I only removed the IP info.
It still crashes with a  fatal error everytime I close it

Code:

2018-03-17 12:48:22 getblocks 86400 to 0000000000e8ee8173e212c22277c67ab05de6747d58b4eb560e233839643924 limit 500 from peer=1
2018-03-17 12:48:26 P2P peers available. Skipped DNS seeding.
2018-03-17 12:48:26 dnsseed thread exit
2018-03-17 12:48:28 receive version message: /Bulwark Core:1.2.1/: version 70811, blocks=86399, us=xx.xx.xx.xx:49810, peer=3
2018-03-17 12:48:28 Added time data, samples 4, offset +0 (+0 minutes)
2018-03-17 12:48:50 receive version message: /Bulwark Core:1.2.2/: version 70811, blocks=95621, us=xx.xx.xx.xx:49825, peer=4
2018-03-17 12:48:50 Added time data, samples 5, offset +1 (+0 minutes)
2018-03-17 12:48:50 nTimeOffset = +0  (+0 minutes)
2018-03-17 12:49:02 receive version message: /Bulwark Core:1.2.2/: version 70811, blocks=94482, us=xx.xx.xx.xx:49833, peer=5
2018-03-17 12:49:02 Added time data, samples 6, offset +0 (+0 minutes)
2018-03-17 12:49:03 receive version message: /Bulwark Core:1.2.2/: version 70811, blocks=94862, us=xx.xx.xx.xx:49834, peer=6
2018-03-17 12:49:03 Added time data, samples 7, offset +0 (+0 minutes)
2018-03-17 12:49:03 nTimeOffset = +0  (+0 minutes)
2018-03-17 12:49:08 msghand thread interrupt
2018-03-17 12:49:08 dumpaddr thread stop
2018-03-17 12:49:08 addcon thread interrupt
2018-03-17 12:49:08 ThreadStakeMinter() error 
2018-03-17 12:49:08 ThreadStakeMinter exiting,
2018-03-17 12:49:08 stakemint thread exit
2018-03-17 12:49:08 net thread interrupt
2018-03-17 12:49:08 opencon thread interrupt
2018-03-17 12:49:08 PrepareShutdown: In progress...
2018-03-17 12:49:08 StopNode()
2018-03-17 12:49:08 Verifying mncache.dat format...
2018-03-17 12:49:08 Loaded info from mncache.dat  0ms
2018-03-17 12:49:08   Masternodes: 70, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 86, nDsqCount: 0
2018-03-17 12:49:08 Writting info to mncache.dat...
2018-03-17 12:49:08 Written info to mncache.dat  0ms
2018-03-17 12:49:08   Masternodes: 30, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, nDsqCount: 0
2018-03-17 12:49:08 Masternode dump finished  0ms
2018-03-17 12:49:08 Verifying budget.dat format...
2018-03-17 12:49:08 Loaded info from budget.dat  0ms
2018-03-17 12:49:08   Proposals: 0, Budgets: 0, Seen Budgets: 0, Seen Budget Votes: 0, Seen Final Budgets: 0, Seen Final Budget Votes: 0
2018-03-17 12:49:08 Writting info to budget.dat...
2018-03-17 12:49:08 Written info to budget.dat  0ms
2018-03-17 12:49:08 Budget dump finished  0ms
2018-03-17 12:49:08 Verifying mnpayments.dat format...
2018-03-17 12:49:08 Loaded info from mnpayments.dat  0ms
2018-03-17 12:49:08   Votes: 0, Blocks: 0
2018-03-17 12:49:08 Writting info to mnpayments.dat...
2018-03-17 12:49:08 Written info to mnpayments.dat  16ms
2018-03-17 12:49:08 Budget dump finished  16ms
2018-03-17 12:49:08 *** System error while flushing: CDB : Error -30974, can't open database 
2018-03-17 12:49:10 CDBEnv::EnvShutdown : Error -30974 shutting down database environment: DB_RUNRECOVERY: Fatal error, run database recovery
2018-03-17 12:49:10 Shutdown: done

[muzuca]

I resynched my wallet but I not see coins who mining from yesrtrday.

This Coin is lost forever?

If you any idea what can I do to get back?
My wallet must by open all time?
I mining with pooloDf32th, I must write to them something?

I’m in the same situation. I synchronized the wallet, and there are two transactions in conflict, see the detail of one:

Status: conflicted
Date: 15/03/2018 06:16
From: unknown
To: bXpjnVAgYA3QBBmEv16KHXzEstytdJQbUo (own address, label)
Credit: 8.70968181 BWK
Net amount: +8.70968181 BWK
Transaction ID: 014a3e0a5b7c87f1656f07b7fdce2cd73b04ae32ff2789fc6584f217cef4ee7f
Output index: 0

In my old wallet, this coins were in my balance.

[DNADavid]

Which pool is good now ?

http://bsod.pw/ and http://yiimp.poolofd32th.club/ are both decent.  Though the latter appears to be down at the moment.

I use yiimp and I not get my money from yestrday

I would advise that you read the announcement from EatBatterys. It's not that Yiimp, which i assume is poolofd32th because yiimp is the software its built on, hasn't paid you, is that the blocks you mined very well may have been orphans, or the transaction is conflicted. In both cases you just need to wait until the Spork is over and wait for further instructions.

Yes I mean http://yiimp.poolofd32th.club/

And I am waiting

http://yiimp.poolofd32th.club/site/block?id=2880 ... mined block 94968 now but actual block on explorer is 95629 (http://explorer.bulwarkcrypto.com/#/)

Realy actual block is mined on bsod !!