[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[bensam1231]

Wallet shouldn't even connect to outdated wallets after hard forks to prevent people from abusing version differences.

Just was going to ask about 1.2.2, but I'll update right now.

[1714852899]

1714852899

[1714852899]

1714852899

[go6ooo1212]

Just installed the new wallet 1.2.3. Its working fine , and I have to say I had nice mining rewards at Crowetic's pool last several weeks. Cheers...

[ltcnim]

After the update I have to download the complete blockchain again Oo
I never had that problem when updating, I always just copied the burst_db folder and my config file over to the new installation.

ok, I'm kinda dumb, everything works as expected.

[go6ooo1212]

After the update I have to download the complete blockchain again Oo
I never had that problem when updating, I always just copied the burst_db folder and my config file over to the new installation.

ok, I'm kinda dumb, everything works as expected.

I had no problem at all , just moved the burst_db folder from 1.2.2 to 1.2.3 folder. Deleted the 1.2.2 folder and started the 1.2.3 - its fully synced...

[jamoes]

Burst 1.2.3

https://mega.co.nz/#!PwwCyBAL!R89Dkzc6cn-tI-5CeNLeceEV7irgU1X4Brs8Lu-JGD8
sha256: b0008bc63aab921ef427b6a9c817d8747cd34252560996343c4183ddfb6fad98

Hard fork at block 92000, so all users must update within the next 5 days, but are recommended to update as soon as possible.

This release fixes bugs with ATs and the asset exchange and changes the windows run.bat to a universal one that doesn't depend on java 7.

Thanks for all your hard work, @burstcoin!

Could you please start signing your releases with a GPG signing key? The sha256sum is nice, but it's not enough. I'd prefer not to trust the bitcointalk servers and the root cert authorities when verifying new releases.

[mmmaybe]

[---]
\conf\nxt-default.properties

# Known bad peers to be blacklisted
nxt.knownBlacklistedPeers=69.30.248.190; 142.4.211.170; 83.141.0.226; 213.64.226.230; 71.245.115.177; 70.168.116.190; 109.121.255.96; 192.162.248.15; 73.9.183.86; 178.19.240.227:8123; 192.198.95.51; 95.42.91.214

Thanks for this important list!! Just one question: how have you found them, and how can we find more?

[mmmaybe]

Edited the thread about donations on BurstForum and added a post:

Today 50,000 BURST have been donated to kurairaito for translating our official site into French: http://burstcoin.info -> http://burstcoin.fr

Details here: http://bit.ly/1K0q57K

[Mark77]

butstcoin, I mine solo, and today I faced an unpleasant thing in BURST wallet. After I had mined more than 100 blocks, there was “100+” instead of the exact amount of blocks in the wallet. It is very inconvenient for monitoring the statistics. Is it possible to fix it someways?
http://prntscr.com/6vi2s2

[727miner]

New wallet works well for me. Also sent another small donation to the project tonight 

[Razerglass]

Burst 1.2.3

https://mega.co.nz/#!PwwCyBAL!R89Dkzc6cn-tI-5CeNLeceEV7irgU1X4Brs8Lu-JGD8
sha256: b0008bc63aab921ef427b6a9c817d8747cd34252560996343c4183ddfb6fad98

Hard fork at block 92000, so all users must update within the next 5 days, but are recommended to update as soon as possible.

This release fixes bugs with ATs and the asset exchange and changes the windows run.bat to a universal one that doesn't depend on java 7.

Thanks for all your hard work, @burstcoin!

Could you please start signing your releases with a GPG signing key? The sha256sum is nice, but it's not enough. I'd prefer not to trust the bitcointalk servers and the root cert authorities when verifying new releases.

thanks for the update good work burst dev

[bensam1231]

[miner]

new version Burst-miner v1.150401
https://github.com/Blagodarenko/miner-burst/releases/download/v1.150401/miner-burst-1.150401.zip

- MaxThreads (Paths) = 48 Unlimited
- MaxAccounts =100 Unlimited
- MaxFiles per directory =1000 Unlimited (limited by OS)
- parameter "SkipBadPlots" did not used
https://github.com/Blagodarenko/miner-burst

Im getting the same error

Faulting application name: miner_blago.exe, version: 0.0.0.0, time stamp: 0x551ceedf
Faulting module name: MSVCR120D.dll, version: 12.0.21005.1, time stamp: 0x524f8403
Exception code: 0xc0000005
Fault offset: 0x000000000004b2b2
Faulting process id: 0xd84
Faulting application start time: 0x01d070f5727d5042
Faulting application path: d:\miner\miner-burst-blago\miner_blago.exe
Faulting module path: d:\miner\miner-burst-blago\MSVCR120D.dll
Report Id: 81692c3d-dd25-11e4-80d6-1c6f656bb765
Faulting package full name:
Faulting package-relative application ID:

Still getting this problem. I reverted to 319 for the time being.

Weird enough, even though I wasn't hashing faster on 401, I was finding a LOT more blocks. Maybe just coincidence, but it seems as though there is a bug in the current version (319) that severely hampers my ability to find blocks. I've been mining on a pool for some time now, so it doesn't really affect me, but I'm sure doesn't help the pool I'm supposed to be 'contributing' to.

12 days w/o crashes for me... using 401

Try setup "ShowWinner" : false

Still happening with winner being false.

set "UseCleanMem" : false
it worked for me, so far 3 days w/o crashes

I was using memclean false on all my machines to begin with. I am running them as admin though.

Just a bump, it appears as though running as a normal user instead of admin fixes this. Which means it has something to do with the memclean feature, which doesn't work unless you run as admin. Setting memclean false doesn't fix this nor does it properly stop memclean from working.

This doesn't fix it. I'm not certain what does. I have some machines running fine with 401 and others that still crash even though they have identical setups. Memclean doesn't seem to be the issue. The crashing also seems sporadic. I have one that has been running fine for the last week. I thought it may have been the visual c++ redistributables, but they're all running the same versions now.

[mmmaybe]

In preparation for the launch of our Chinese site, the PR team has recruited two BTT-members,
zhu_lianbing and lihuajkl, to help us get listed on an Asian exchange and learn more of the crypto culture over there. See the BF thread http://bit.ly/1K0q57K for spending of donated money.

Likewise has daWallet been recruited for this major event. Don't forget that China is the second biggest BTC market it the world; if we can get good press there, great things are likely to happen.


As with work of this kind of PR work, it requires funding. Please consider supporting our Chinese endeavor and other promotional efforts by donation (see sig).

Thanks to 727miner for your generosity once again; your dedication will be given credit on http://burstcoin.info/about/#Angels which now has a little introduction to way your support is vital for the coin.

[Blago]

[---]
\conf\nxt-default.properties

# Known bad peers to be blacklisted
nxt.knownBlacklistedPeers=69.30.248.190; 142.4.211.170; 83.141.0.226; 213.64.226.230; 71.245.115.177; 70.168.116.190; 109.121.255.96; 192.162.248.15; 73.9.183.86; 178.19.240.227:8123; 192.198.95.51; 95.42.91.214

Thanks for this important list!! Just one question: how have you found them, and how can we find more?

manualy added to wallet properties from wallet's list of connected peers (if version < 1.2.2)

[Blago]

...
This doesn't fix it. I'm not certain what does. I have some machines running fine with 401 and others that still crash even though they have identical setups. Memclean doesn't seem to be the issue. The crashing also seems sporadic. I have one that has been running fine for the last week. I thought it may have been the visual c++ redistributables, but they're all running the same versions now.

It is not yet fixed. Error spontaneous, so until I found the cause of its origin...

[FakeAccount]

...
This doesn't fix it. I'm not certain what does. I have some machines running fine with 401 and others that still crash even though they have identical setups. Memclean doesn't seem to be the issue. The crashing also seems sporadic. I have one that has been running fine for the last week. I thought it may have been the visual c++ redistributables, but they're all running the same versions now.

It is not yet fixed. Error spontaneous, so until I found the cause of its origin...

I noticed this error when the system loses a drive and you get a 0 or -1 size... maybe if USB drive gets disconnected but miner attempts to read it anyway you could try reproducing this error.

[bobafett]

i got this error also on my miner with sata drives only. energy option on high power and no hdd sleep timer.

[muhrohmat]

ah ok wallet 1.2.3 got out i better see this and wait a bit in mining till burst come to 150 satoshis again and the btc goes to 250 euros soo nice of you guys to post this

[bensam1231]

...
This doesn't fix it. I'm not certain what does. I have some machines running fine with 401 and others that still crash even though they have identical setups. Memclean doesn't seem to be the issue. The crashing also seems sporadic. I have one that has been running fine for the last week. I thought it may have been the visual c++ redistributables, but they're all running the same versions now.

It is not yet fixed. Error spontaneous, so until I found the cause of its origin...

I noticed this error when the system loses a drive and you get a 0 or -1 size... maybe if USB drive gets disconnected but miner attempts to read it anyway you could try reproducing this error.

Yeah it's on a all SATA system. I've tried looking for the cause, but I can't find it. 319 doesn't have this issue. It seems as though the more drives the system has, the faster it crashes. But now I have some systems that were crashing with it that aren't (?!!?).

[catbref]

ninja pool updated to v1.2.3
historic pie rendering fixed (data was okay, just stats page was wrong)

BONUS PAYMENT CODE coming very soon (yum yum)

[FakeAccount]

...
This doesn't fix it. I'm not certain what does. I have some machines running fine with 401 and others that still crash even though they have identical setups. Memclean doesn't seem to be the issue. The crashing also seems sporadic. I have one that has been running fine for the last week. I thought it may have been the visual c++ redistributables, but they're all running the same versions now.

It is not yet fixed. Error spontaneous, so until I found the cause of its origin...

I noticed this error when the system loses a drive and you get a 0 or -1 size... maybe if USB drive gets disconnected but miner attempts to read it anyway you could try reproducing this error.

Yeah it's on a all SATA system. I've tried looking for the cause, but I can't find it. 319 doesn't have this issue. It seems as though the more drives the system has, the faster it crashes. But now I have some systems that were crashing with it that aren't (?!!?).

i got this error also on my miner with sata drives only. energy option on high power and no hdd sleep timer.

then it's it's all random.