Topic: [ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net - page 136. (Read 409641 times)
February 01, 2014, 07:38:19 PM
February 01, 2014, 07:19:17 PM
What are you trying to say?
lol
lol
nvm I found it at 181
seems to open the port and get device number in program.py though
February 01, 2014, 06:58:16 PM
But when I run mine.py I get:
Hmm.
Code:
Run Summary:
-------------
Traceback (most recent call last):
File "mine.py", line 271, in
logger.printSummary(settings)
File "C:\Users\block_000\Desktop\x6500-miner-master\x6500-miner-master\Console
Logger.py", line 210, in printSummary
self.say('Device: %d' % self.devicenum, True, True)
AttributeError: 'ConsoleLogger' object has no attribute 'devicenum'
-------------
Traceback (most recent call last):
File "mine.py", line 271, in
logger.printSummary(settings)
File "C:\Users\block_000\Desktop\x6500-miner-master\x6500-miner-master\Console
Logger.py", line 210, in printSummary
self.say('Device: %d' % self.devicenum, True, True)
AttributeError: 'ConsoleLogger' object has no attribute 'devicenum'
Hmm.
I have not used this one yet
did you try to pass in a device number?
-d DEVICENUM, --devicenum=DEVICENUM
Device number, optional. If left out, the first available
device will be opened.
did you try to comment out that line as it is just a loger? does it repeat in other functions/lines?
Yeah, I did.
I think I have something wrong.
When the programming part stops it just hangs, I can't even end the task, tells me permission denied.
I think that might have something to do with it.
I need to setup a linux box to do this on, this shit is no fun on Windows.
I noticed this and is missing from mine.py:
https://github.com/kramble/x6500-miner/blob/master/program.py#L44
What are you trying to say?
lol
February 01, 2014, 06:54:10 PM
But when I run mine.py I get:
Hmm.
Code:
Run Summary:
-------------
Traceback (most recent call last):
File "mine.py", line 271, in
logger.printSummary(settings)
File "C:\Users\block_000\Desktop\x6500-miner-master\x6500-miner-master\Console
Logger.py", line 210, in printSummary
self.say('Device: %d' % self.devicenum, True, True)
AttributeError: 'ConsoleLogger' object has no attribute 'devicenum'
-------------
Traceback (most recent call last):
File "mine.py", line 271, in
logger.printSummary(settings)
File "C:\Users\block_000\Desktop\x6500-miner-master\x6500-miner-master\Console
Logger.py", line 210, in printSummary
self.say('Device: %d' % self.devicenum, True, True)
AttributeError: 'ConsoleLogger' object has no attribute 'devicenum'
Hmm.
I have not used this one yet
did you try to pass in a device number?
-d DEVICENUM, --devicenum=DEVICENUM
Device number, optional. If left out, the first available
device will be opened.
did you try to comment out that line as it is just a loger? does it repeat in other functions/lines?
Yeah, I did.
I think I have something wrong.
When the programming part stops it just hangs, I can't even end the task, tells me permission denied.
I think that might have something to do with it.
I need to setup a linux box to do this on, this shit is no fun on Windows.
https://github.com/kramble/x6500-miner/blob/master/program.py#L44
February 01, 2014, 06:48:03 PM
But when I run mine.py I get:
Hmm.
Code:
Run Summary:
-------------
Traceback (most recent call last):
File "mine.py", line 271, in
logger.printSummary(settings)
File "C:\Users\block_000\Desktop\x6500-miner-master\x6500-miner-master\Console
Logger.py", line 210, in printSummary
self.say('Device: %d' % self.devicenum, True, True)
AttributeError: 'ConsoleLogger' object has no attribute 'devicenum'
-------------
Traceback (most recent call last):
File "mine.py", line 271, in
logger.printSummary(settings)
File "C:\Users\block_000\Desktop\x6500-miner-master\x6500-miner-master\Console
Logger.py", line 210, in printSummary
self.say('Device: %d' % self.devicenum, True, True)
AttributeError: 'ConsoleLogger' object has no attribute 'devicenum'
Hmm.
I have not used this one yet
did you try to pass in a device number?
-d DEVICENUM, --devicenum=DEVICENUM
Device number, optional. If left out, the first available
device will be opened.
did you try to comment out that line as it is just a loger? does it repeat in other functions/lines?
Yeah, I did.
I think I have something wrong.
When the programming part stops it just hangs, I can't even end the task, tells me permission denied.
I think that might have something to do with it.
I need to setup a linux box to do this on, this shit is no fun on Windows.
February 01, 2014, 06:44:25 PM
But when I run mine.py I get:
Hmm.
Code:
Run Summary:
-------------
Traceback (most recent call last):
File "mine.py", line 271, in
logger.printSummary(settings)
File "C:\Users\block_000\Desktop\x6500-miner-master\x6500-miner-master\Console
Logger.py", line 210, in printSummary
self.say('Device: %d' % self.devicenum, True, True)
AttributeError: 'ConsoleLogger' object has no attribute 'devicenum'
-------------
Traceback (most recent call last):
File "mine.py", line 271, in
logger.printSummary(settings)
File "C:\Users\block_000\Desktop\x6500-miner-master\x6500-miner-master\Console
Logger.py", line 210, in printSummary
self.say('Device: %d' % self.devicenum, True, True)
AttributeError: 'ConsoleLogger' object has no attribute 'devicenum'
Hmm.
I have not used this one yet
did you try to pass in a device number?
-d DEVICENUM, --devicenum=DEVICENUM
Device number, optional. If left out, the first available
device will be opened.
did you try to comment out that line as it is just a loger? does it repeat in other functions/lines?
February 01, 2014, 06:13:29 PM
Ok, getting it programmed just fine:
But when I run mine.py I get:
Hmm.
Code:
2014-02-01 17:02:46 | Opening bitstream file: X6500-Robust-v04-2core-fmax-100MHz
.bit
2014-02-01 17:02:46 | Bitstream file opened:
2014-02-01 17:02:46 | Design Name: blakeminer_top_routed.ncd;UserID=0x42240402
2014-02-01 17:02:46 | Firmware: rev 4, build: 2
2014-02-01 17:02:46 | Part Name: 6slx150fgg484
2014-02-01 17:02:46 | Date: 2013/10/29
2014-02-01 17:02:46 | Time: 17:31:23
2014-02-01 17:02:46 | Bitstream Length: 4220212
2014-02-01 17:02:46 | Device 0 opened (A5VOPER6)
2014-02-01 17:02:46 | Connected to 2 FPGAs
2014-02-01 17:02:46 | Pre-processing bitstream for chain = 2...
2014-02-01 17:06:16 | Pre-processed bitstream in 210.252000 seconds
2014-02-01 17:06:16 | Saving pre-processed bitstream...
2014-02-01 17:06:17 | Saved pre-processed bitstream in 0.165000 seconds
2014-02-01 17:06:17 | Beginning programming...
2014-02-01 17:06:17 | Programming both FPGAs...
Completed: 100.0% [67 kB/s] [0s remaining]
.bit
2014-02-01 17:02:46 | Bitstream file opened:
2014-02-01 17:02:46 | Design Name: blakeminer_top_routed.ncd;UserID=0x42240402
2014-02-01 17:02:46 | Firmware: rev 4, build: 2
2014-02-01 17:02:46 | Part Name: 6slx150fgg484
2014-02-01 17:02:46 | Date: 2013/10/29
2014-02-01 17:02:46 | Time: 17:31:23
2014-02-01 17:02:46 | Bitstream Length: 4220212
2014-02-01 17:02:46 | Device 0 opened (A5VOPER6)
2014-02-01 17:02:46 | Connected to 2 FPGAs
2014-02-01 17:02:46 | Pre-processing bitstream for chain = 2...
2014-02-01 17:06:16 | Pre-processed bitstream in 210.252000 seconds
2014-02-01 17:06:16 | Saving pre-processed bitstream...
2014-02-01 17:06:17 | Saved pre-processed bitstream in 0.165000 seconds
2014-02-01 17:06:17 | Beginning programming...
2014-02-01 17:06:17 | Programming both FPGAs...
Completed: 100.0% [67 kB/s] [0s remaining]
But when I run mine.py I get:
Code:
Run Summary:
-------------
Traceback (most recent call last):
File "mine.py", line 271, in
logger.printSummary(settings)
File "C:\Users\block_000\Desktop\x6500-miner-master\x6500-miner-master\Console
Logger.py", line 210, in printSummary
self.say('Device: %d' % self.devicenum, True, True)
AttributeError: 'ConsoleLogger' object has no attribute 'devicenum'
-------------
Traceback (most recent call last):
File "mine.py", line 271, in
logger.printSummary(settings)
File "C:\Users\block_000\Desktop\x6500-miner-master\x6500-miner-master\Console
Logger.py", line 210, in printSummary
self.say('Device: %d' % self.devicenum, True, True)
AttributeError: 'ConsoleLogger' object has no attribute 'devicenum'
Hmm.
February 01, 2014, 06:10:55 PM
FPGA = awesome.
Will it work with the X6500s?
I have 3 of them laying around.
Will it work with the X6500s?
I have 3 of them laying around.
https://github.com/kramble/x6500-miner
Ahh, thank you!
Off to mine some Blakecoin!
not sure which is the best bitstream though
https://github.com/kramble/FPGA-Blakecoin-Miner/tree/master/experimental
February 01, 2014, 06:07:48 PM
Or he can better join Blakecoin!
February 01, 2014, 06:03:22 PM
February 01, 2014, 05:45:14 PM
FPGA = awesome.
Will it work with the X6500s?
I have 3 of them laying around.
Will it work with the X6500s?
I have 3 of them laying around.
https://github.com/kramble/x6500-miner
Ahh, thank you!
Off to mine some Blakecoin!
February 01, 2014, 05:30:14 PM
FPGA = awesome.
Will it work with the X6500s?
I have 3 of them laying around.
Will it work with the X6500s?
I have 3 of them laying around.
miner:
https://github.com/kramble/x6500-miner
the different fpga bitstreams/source for the supported boards:
https://github.com/kramble/FPGA-Blakecoin-Miner/tree/master/experimental
Thanks to kramble for his awesome work
February 01, 2014, 04:01:57 PM
FPGA = awesome.
Will it work with the X6500s?
I have 3 of them laying around.
Will it work with the X6500s?
I have 3 of them laying around.
February 01, 2014, 03:56:52 PM
I wanted to extend the olive branch and apologize to BlueDragon747 for the friction over merged mining and Blakecoin.
As I look back with a somewhat clearer head(as clear as it can be now
), I realize that it would have never been possible using an unaltered MM proxy because of conflicting goals.
When I set out to relaunch Federation Credits, one of the main goals was an automatic redistribution of the coins on the original chain. I wanted coin holders to be able to simply place their old wallet files in the new UFC directory, salvage the wallet, and have their coins and addresses back on the new chain. This is also the reason for the 8 Million coin super block, it was redistributed in block 121 to all the same addresses and amounts the coins were on in the original chain.
Part of Blakecoin design was a change in the way keys are encoded. While in itself this is perfectly fine and adds more “Blakeness” to the coin, I could not use that system and have an easy coin redistribution .I had to change the key encoding back to sha256. Note: key encoding and block encoding are not the same thing, every coin I have seen up until now, uses sha256 key encoding regardless of the block encryption scheme.
When I first talked to Bluedragon747, I was not aware that the key encode had been changed or the repercussions it would have on the redistribution.
The second issues with versions. Just my policy. After repairing coin clients and seeing it happen to others, I do everything I can to prevent crosstalk between different chains and incompatible client versions. In theory, all one needs to do is change the network identifier (prefix) and P2P port, but I have seen many strange things happen when nodes that should not be talking to each other start to. I use version numbers to further block out old clients/other chains, which was especially necessary in this case to make sure UFC 1.5.5 and lower were completely blocked from this chain. I was also using wallet version to facilitate an auto-detection and wallet salvage routine that did not turn out as planned.
I just want to end by stating the friction that occurred in previous posts was my fault. The amount of pressure I was under to fix a third coin of which I was not the original developer , but now am the developer, was taking its toll. The blockchain was completely POS locked and the new client had to be made and the new blockchain in place with redemption very quickly to avoid the coin dying out.
If we can see past this, I would be happy to work with Bluedragon747 on a merged mine solution, if he still wants to. If not, it is perfectly understandable.
As I look back with a somewhat clearer head(as clear as it can be now
), I realize that it would have never been possible using an unaltered MM proxy because of conflicting goals.When I set out to relaunch Federation Credits, one of the main goals was an automatic redistribution of the coins on the original chain. I wanted coin holders to be able to simply place their old wallet files in the new UFC directory, salvage the wallet, and have their coins and addresses back on the new chain. This is also the reason for the 8 Million coin super block, it was redistributed in block 121 to all the same addresses and amounts the coins were on in the original chain.
Part of Blakecoin design was a change in the way keys are encoded. While in itself this is perfectly fine and adds more “Blakeness” to the coin, I could not use that system and have an easy coin redistribution .I had to change the key encoding back to sha256. Note: key encoding and block encoding are not the same thing, every coin I have seen up until now, uses sha256 key encoding regardless of the block encryption scheme.
When I first talked to Bluedragon747, I was not aware that the key encode had been changed or the repercussions it would have on the redistribution.
The second issues with versions. Just my policy. After repairing coin clients and seeing it happen to others, I do everything I can to prevent crosstalk between different chains and incompatible client versions. In theory, all one needs to do is change the network identifier (prefix) and P2P port, but I have seen many strange things happen when nodes that should not be talking to each other start to. I use version numbers to further block out old clients/other chains, which was especially necessary in this case to make sure UFC 1.5.5 and lower were completely blocked from this chain. I was also using wallet version to facilitate an auto-detection and wallet salvage routine that did not turn out as planned.
I just want to end by stating the friction that occurred in previous posts was my fault. The amount of pressure I was under to fix a third coin of which I was not the original developer , but now am the developer, was taking its toll. The blockchain was completely POS locked and the new client had to be made and the new blockchain in place with redemption very quickly to avoid the coin dying out.
If we can see past this, I would be happy to work with Bluedragon747 on a merged mine solution, if he still wants to. If not, it is perfectly understandable.
February 01, 2014, 03:13:39 PM
My service provider is having some issues in one of the datacenters 
Edit:
ok should be back to normal but will keep a close eye on it
Edit:
ok should be back to normal but will keep a close eye on it
January 31, 2014, 07:07:39 PM
Good news everybody
Blakecoin has just been listed on Crypto-Currency Exchange https://c-cex.com
https://bitcointalksearch.org/topic/c-cexcom-trusted-secure-friendly-exchange-since-2013-200-altsusdlow-fees-418700
Edit
BLC-USD
https://c-cex.com/index.html?p=blc-usd
BLC-BTC
https://c-cex.com/index.html?p=blc-btc
Blakecoin has just been listed on Crypto-Currency Exchange https://c-cex.com
https://bitcointalksearch.org/topic/c-cexcom-trusted-secure-friendly-exchange-since-2013-200-altsusdlow-fees-418700
Edit
BLC-USD
https://c-cex.com/index.html?p=blc-usd
BLC-BTC
https://c-cex.com/index.html?p=blc-btc
Congrats! A great start for the lunar new year!
January 31, 2014, 01:08:19 PM
Good news everybody
Blakecoin has just been listed on Crypto-Currency Exchange https://c-cex.com
https://bitcointalksearch.org/topic/c-cexcom-trusted-secure-friendly-exchange-since-2013-200-altsusdlow-fees-418700
Edit
BLC-USD
https://c-cex.com/index.html?p=blc-usd
BLC-BTC
https://c-cex.com/index.html?p=blc-btc
Blakecoin has just been listed on Crypto-Currency Exchange https://c-cex.com
https://bitcointalksearch.org/topic/c-cexcom-trusted-secure-friendly-exchange-since-2013-200-altsusdlow-fees-418700
Edit
BLC-USD
https://c-cex.com/index.html?p=blc-usd
BLC-BTC
https://c-cex.com/index.html?p=blc-btc
January 31, 2014, 06:33:02 AM
Happy lunar new year to those who are celebrating !! 
Happy Lunar New Year, I wish you good health and lasting prosperity
Let's wish everyone here good health and lasting prosperity from Blakecoins!!! May Blakecoin blast to the moon as exchange trollbox always say ;-p
January 31, 2014, 06:15:31 AM
What are the exchanges where this coin is currently listed on?
Atomic-Trade allows trading of Blakecoin
www.atomic-trade.com
OpenEx is in Maintenance for 2-3 weeks according to r3wt
https://bitcointalksearch.org/topic/openex-closing-for-improvementspostponed-437532
January 31, 2014, 05:15:44 AM
Happy lunar new year to those who are celebrating !!
Happy Lunar New Year, I wish everyone good health and lasting prosperity
Jump to: