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?
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 428. (Read 2171061 times)
February 05, 2015, 10:33:09 PM
This is answer from server... Which pool do you use?
February 05, 2015, 10:31:43 PM
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.
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.
February 05, 2015, 09:43:53 PM
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.
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.
February 05, 2015, 09:05:37 PM
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.
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?
February 05, 2015, 08:00:46 PM
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?
February 05, 2015, 06:35:32 PM
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?
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.
February 05, 2015, 05:45:22 PM
Well done sir, works like a charm 
Would be nice to include the Lottery .html for Average Joe to play without barriers.
Would be nice to include the Lottery .html for Average Joe to play without barriers.
February 05, 2015, 05:19:49 PM
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.
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.
February 05, 2015, 04:32:05 PM
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?
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
February 05, 2015, 04:17:28 PM
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?
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?
February 05, 2015, 03:31:11 PM
-[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!
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!
February 05, 2015, 03:23:38 PM
If you got Twitter or other social media stuff, can you spread this, please?
https://twitter.com/real_BURSTCOIN/status/563000791473340417
We want new users
https://twitter.com/real_BURSTCOIN/status/563000791473340417
We want new users
The giveaway to relatively new users at BurstForum.com will end in about 90 minutes
The giveaway has ended, finally
February 05, 2015, 02:16:06 PM
I'm already using burst miner 1.15, and still having these log.
What could be the problem?
Does it mean that this will slowdown my mining speed?
What could be the problem?
Does it mean that this will slowdown my mining speed?
delete both files
I'm getting this semi-randomly across different plots. The 'null' file problem still exists with your new miner.exe as well. This includes a brand new plot I made tonight with the GPU plotter. Is there a way to verify plot integrity?
February 05, 2015, 01:43:10 PM
I'm already using burst miner 1.15, and still having these log.
What could be the problem?
Does it mean that this will slowdown my mining speed?
What could be the problem?
Does it mean that this will slowdown my mining speed?
delete both files
Trying to re-plot those corrupted files, will keep update.
February 05, 2015, 01:41:21 PM
If you got Twitter or other social media stuff, can you spread this, please?
https://twitter.com/real_BURSTCOIN/status/563000791473340417
We want new users
https://twitter.com/real_BURSTCOIN/status/563000791473340417
We want new users
The giveaway to relatively new users at BurstForum.com will end in about 90 minutes
February 05, 2015, 01:27:52 PM
I'm already using burst miner 1.15, and still having these log.
What could be the problem?
Does it mean that this will slowdown my mining speed?
What could be the problem?
Does it mean that this will slowdown my mining speed?
delete both files
February 05, 2015, 12:11:29 PM
I'm already using burst miner 1.15, and still having these log.
What could be the problem?
Does it mean that this will slowdown my mining speed?
What could be the problem?
Does it mean that this will slowdown my mining speed?
Yeah it will slow your speed.
February 05, 2015, 12:09:43 PM
Thanks for answer. Is the assembler somewhere?
Or do you mind the at.cpp on your web (in that case I have to look more precisely on it, because now I can only enter hexcode there :-) )
Or do you mind the at.cpp on your web (in that case I have to look more precisely on it, because now I can only enter hexcode there :-) )
Here:
https://github.com/BurstProject/ATAssembler/blob/master/src/scala/ATAssembler.scala
(you will like that much better than typing in hex code)
February 05, 2015, 12:07:27 PM
I'm already using burst miner 1.15, and still having these log.
What could be the problem?
Does it mean that this will slowdown my mining speed?
What could be the problem?
Does it mean that this will slowdown my mining speed?
February 05, 2015, 11:58:55 AM
Question: Is there any tool for developing automated transactions? Or are they writen "by hand" right now?
An "assembler tool" has been written but yes currently they need to be hand-written.
The plan is to create simple UI forms for using well known AT "templates" (rather than having to write code at all).
Thanks for answer. Is the assembler somewhere?
Or do you mind the at.cpp on your web (in that case I have to look more precisely on it, because now I can only enter hexcode there :-) )
Jump to: