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

[crowetic]

-[ANNOUNCEMENT]- ByteEnterprises Team - Asset payouts/changes!


Hello, this will be the first of 2 announcements. This is the small announcement, the other will be VERY big.


We have decided to initiate payouts and changeovers for the assets related to the ByteEnterprises team. The following is what will occur today...



1. The asset named HardInvest will be paid out, the account will be emptied to the current holders.

2. The HardInvest asset will be rolled into our new overall asset which is called ByteEnt (more detail on this coming in tomorrow's announcement.)

3. Current holders of HardInvest will get a slight bonus in payouts due to money changing hands into new asset. We're just emptying the account so we can get rid of HardInvest.

4. Once payouts and transfer to new asset complete, HardInvest will be destroyed.

5. Each HardInvest will equal 10 ByteEnt (like I said, more info on ByteEnt tomorrow.)

6. There was an accidental release early, of the ByteEnt asset, and any holders currently, will be getting a payout as well, before the official release of the asset. They will also be getting a bonus by getting the asset cheaper than the release price due to our error.



Thank you! We look forward to continuing to provide services and opportunity to the BURST community. Stay tuned for the BIG announcement tomorrow about ByteEnt asset!

[1714251943]

1714251943

[1714251943]

1714251943

[FakeAccount]

experimenting with win 10, i get this error with blago's miner:
The application was unable to start correctly (0xc000007b). Click OK to close the application.

googling, leads me to believe miner.exe needs to be compiled for 64 bit?

anyone got Blago's miner working on win 10?

[swannsonite]

experimenting with win 10, i get this error with blago's miner:
The application was unable to start correctly (0xc000007b). Click OK to close the application.

googling, leads me to believe miner.exe needs to be compiled for 64 bit?

anyone got Blago's miner working on win 10?

I had the same issue. I was able to use this miner on Windows 10 and the Latest version of OSX.

https://github.com/uraymeiviar/burst-miner/releases

[burstcoin]

Burst 1.2.2

https://mega.co.nz/#!z8BT0BCZ!Z1MXYcVJrObMcx2M_zjHPbsMKQLxGKVqQYqh1u1etWY
sha256: 2e1a7f2d74c584e46b16b40ac8889101e44039ebcaa95a0c1b71abc9eb83a37b

All users must update by block 67000 (about 9 days from now)

This is a bugfix release mainly for ATs, and also loosens restrictions on ecblock info.

[daWallet]

Well done sir, works like a charm  

Would be nice to include the Lottery .html for Average Joe to play without barriers.

[haitch]

experimenting with win 10, i get this error with blago's miner:
The application was unable to start correctly (0xc000007b). Click OK to close the application.

googling, leads me to believe miner.exe needs to be compiled for 64 bit?

anyone got Blago's miner working on win 10?

You need the Visual C++ Runtime Libraries - I think it's this one: http://www.microsoft.com/en-us/download/details.aspx?id=26999

H.

[seasonw]

I have been using Blago miner mining at pool for some days... But it keeps showing "Missing Passphrase" error recently, any clue? Or it is the server issue?

[jamoes]

Burst 1.2.2

https://mega.co.nz/#!z8BT0BCZ!Z1MXYcVJrObMcx2M_zjHPbsMKQLxGKVqQYqh1u1etWY
sha256: 2e1a7f2d74c584e46b16b40ac8889101e44039ebcaa95a0c1b71abc9eb83a37b

All users must update by block 67000 (about 9 days from now)

This is a bugfix release mainly for ATs, and also loosens restrictions on ecblock info.

Glad to see progress marching onwards!

This looks like another hard-forking change, and it would be nice if we didn't experience a major issue like we did earlier this week with the 1.2.0 > 1.2.1 upgrade. What's the best way to maximize the chances that all the exchanges and the major mining pools upgrade within the next 9 days?

Can anyone pro-actively reach out to the exchanges and pools and make sure they upgrade before the fork occurs?

[yellowduck2]

Burst 1.2.2

https://mega.co.nz/#!z8BT0BCZ!Z1MXYcVJrObMcx2M_zjHPbsMKQLxGKVqQYqh1u1etWY
sha256: 2e1a7f2d74c584e46b16b40ac8889101e44039ebcaa95a0c1b71abc9eb83a37b

All users must update by block 67000 (about 9 days from now)

This is a bugfix release mainly for ATs, and also loosens restrictions on ecblock info.

Glad to see progress marching onwards!

This looks like another hard-forking change, and it would be nice if we didn't experience a major issue like we did earlier this week with the 1.2.0 > 1.2.1 upgrade. What's the best way to maximize the chances that all the exchanges and the major mining pools upgrade within the next 9 days?

Can anyone pro-actively reach out to the exchanges and pools and make sure they upgrade before the fork occurs?

Perhaps there should be a SOP (Standard Operating Procedure) for deploying new version and should be executed every single time there is a new version. E.g Who should be the one informing and making sure all exchange and major pool are notified to update their version.

[Merick]

Has anyone tried running Blago's miner under Wine64 in Linux?
My Linux skills are not the sharpest and I am having trouble getting Wine64 installed. 
I tried running it under the standard 32-bit Wine, and obviously it chokes before it even gets started.  Fails on some library call to determine system ram.

Just wondering if Blago's miner will work inside Wine64. If the answer is maybe then I can keep trying and learn how to get Wine64 to install.  If the answer is definitely not, then I will use my time for other things.

Nothing against the Linux native miner programs, just that Blago's development seems very active and steady so I wanted to give it a try inside Linux.

Thank you.

[Blago]

I have been using Blago miner mining at pool for some days... But it keeps showing "Missing Passphrase" error recently, any clue? Or it is the server issue?

This is answer from server... Which pool do you use?

[FakeAccount]

experimenting with win 10, i get this error with blago's miner:
The application was unable to start correctly (0xc000007b). Click OK to close the application.

googling, leads me to believe miner.exe needs to be compiled for 64 bit?

anyone got Blago's miner working on win 10?

You need the Visual C++ Runtime Libraries - I think it's this one: http://www.microsoft.com/en-us/download/details.aspx?id=26999

H.

that was it. thank you!!!

[FakeAccount]

Has anyone tried running Blago's miner under Wine64 in Linux?
My Linux skills are not the sharpest and I am having trouble getting Wine64 installed. 
I tried running it under the standard 32-bit Wine, and obviously it chokes before it even gets started.  Fails on some library call to determine system ram.

Just wondering if Blago's miner will work inside Wine64. If the answer is maybe then I can keep trying and learn how to get Wine64 to install.  If the answer is definitely not, then I will use my time for other things.

Nothing against the Linux native miner programs, just that Blago's development seems very active and steady so I wanted to give it a try inside Linux.

Thank you.

see my post above this

[Youghoor]

Burst 1.2.2

https://mega.co.nz/#!z8BT0BCZ!Z1MXYcVJrObMcx2M_zjHPbsMKQLxGKVqQYqh1u1etWY
sha256: 2e1a7f2d74c584e46b16b40ac8889101e44039ebcaa95a0c1b71abc9eb83a37b

All users must update by block 67000 (about 9 days from now)

This is a bugfix release mainly for ATs, and also loosens restrictions on ecblock info.

Glad to see progress marching onwards!

This looks like another hard-forking change, and it would be nice if we didn't experience a major issue like we did earlier this week with the 1.2.0 > 1.2.1 upgrade. What's the best way to maximize the chances that all the exchanges and the major mining pools upgrade within the next 9 days?

Can anyone pro-actively reach out to the exchanges and pools and make sure they upgrade before the fork occurs?

It is the job the pool and exchanges to be on the correct wallet.

[yellowduck2]

Burst 1.2.2

https://mega.co.nz/#!z8BT0BCZ!Z1MXYcVJrObMcx2M_zjHPbsMKQLxGKVqQYqh1u1etWY
sha256: 2e1a7f2d74c584e46b16b40ac8889101e44039ebcaa95a0c1b71abc9eb83a37b

All users must update by block 67000 (about 9 days from now)

This is a bugfix release mainly for ATs, and also loosens restrictions on ecblock info.

Glad to see progress marching onwards!

This looks like another hard-forking change, and it would be nice if we didn't experience a major issue like we did earlier this week with the 1.2.0 > 1.2.1 upgrade. What's the best way to maximize the chances that all the exchanges and the major mining pools upgrade within the next 9 days?

Can anyone pro-actively reach out to the exchanges and pools and make sure they upgrade before the fork occurs?

It is the job the pool and exchanges to be on the correct wallet.

Someone need to monitor if they are "doing their job". Otherwise we will encounter multiple fork every single time when there is new version.

[timk225]

I can't decide which is a bigger waste of someones time...  voting for Obama or mining BURST coin.  Neither will work out well.

[TwinWinNerD]

I don't think you can vote for obama anymore.

[haitch]

Wow - don't think I've seen a -28 Trust level before. Awesome effort!

[FakeAccount]

I can't decide which is a bigger waste of someones time...  voting for Obama or mining BURST coin.  Neither will work out well.

[bensam123]

So I just updated to 1.2.2 and I've noticed a problem since 1.2.1 where my wallets are not all on the same block and they update sporadically. One wallet is currently five blocks behind and of course mining isn't happening because I'm five blocks behind. Sometimes it's just 1-2 blocks of difference, even weirder the wallet that is 'behind' still tries to mine the block it's on, even though there is a newer block being currently mined. Sometimes they're on exactly the same block.

Is this just me having this happen? It's definitely a big deal. I don't think you'd even notice if you're running one wallet.


I've also finished optimizing all five of the drives for my G3220 with 5x5TB. The system now completes the mining phase 10 seconds slower overall then with the non-optimized plots?!?!