Bitcoin Forum
July 16, 2019, 07:24:23 AM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: « 1 ... 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 [71] 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 ... 203 »
  Print  
Author Topic: [ANN][BLC] Blakecoin Blake-256 for GPU/FPGA With Merged Mined Pools Stable Net  (Read 400351 times)
bzyzny
Sr. Member
****
Offline Offline

Activity: 274
Merit: 254


View Profile
February 02, 2014, 04:42:08 PM
 #1401

BlueDragon747, you mentioned that Blake2 is faster, so why didn't you use that?
1563261863
Hero Member
*
Offline Offline

Posts: 1563261863

View Profile Personal Message (Offline)

Ignore
1563261863
Reply with quote  #2

1563261863
Report to moderator
1563261863
Hero Member
*
Offline Offline

Posts: 1563261863

View Profile Personal Message (Offline)

Ignore
1563261863
Reply with quote  #2

1563261863
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1563261863
Hero Member
*
Offline Offline

Posts: 1563261863

View Profile Personal Message (Offline)

Ignore
1563261863
Reply with quote  #2

1563261863
Report to moderator
1563261863
Hero Member
*
Offline Offline

Posts: 1563261863

View Profile Personal Message (Offline)

Ignore
1563261863
Reply with quote  #2

1563261863
Report to moderator
1563261863
Hero Member
*
Offline Offline

Posts: 1563261863

View Profile Personal Message (Offline)

Ignore
1563261863
Reply with quote  #2

1563261863
Report to moderator
BlueDragon747
Legendary
*
Offline Offline

Activity: 1503
Merit: 1017


Solutions Architect


View Profile WWW
February 02, 2014, 04:56:19 PM
Last edit: February 02, 2014, 07:07:55 PM by BlueDragon747
 #1402

BlueDragon747, you mentioned that Blake2 is faster, so why didn't you use that?

it was a compromise you can't currently get Blake2 in OpenCL and Verilog and only a few examples in VHDL which as kramble has pointed out can make things more difficult for an implementation.

to get best speed from Blake2 it would also be best to remove the endian conversion from the wallet and other software, Blake-256 was compatible as it was designed to replace SHA-256 which is big endian

I did the reduced round to minimize the difference between them in terms of speed/power efficiency while maintaining the security buffer, designed for a best attack of min 2128 ideal was 2192 but real world 2200 so quite happy with design decisions  Grin

that buffer basically means no better way than brute force as a boomerang attack would not make any difference to the wallet/mining anyways

for bruteforce its Blake-256 = 2256 and SHA-256D = 2255 (extra collision due to double hash)  

Info: GithubBlakecoin.org - BCT Blakecoin thread - Twitter - BCS - BlakeZone  Trade Blakecoin: Cryptopia - C-patex Merged Mining Pools: EU3 - NY2/AT1 - LA1
Donation Addresses: BLC: Bd3jJftFbwxWSKNSNz35vkDd57kG6jHAjt PHO: BZXPMc8eF9YZcJStskkP2bVia38fv9VmuT BBTC: 2h8c4NbzXJXk6QQ89r7YYMGhe13gQUC2ajD ELT: e7cm6cAgpfhvk3Myh2Jkmi1nqaHtDHnxXb 
UMO: uQH9H17t7kz3eVQ3vKDzMsWCK4hn5nh2gC LIT: 8p8Z4h5fkZ8SCoyEtihKcjzZLA7gFjTdmL BTC: 1Q6kgcNqhKh8u67m6Gj73T2LMgGseETwR6
BlueDragon747
Legendary
*
Offline Offline

Activity: 1503
Merit: 1017


Solutions Architect


View Profile WWW
February 02, 2014, 05:03:34 PM
 #1403


Do the current pools support getwork?


yes getwork is working  Cheesy

Info: GithubBlakecoin.org - BCT Blakecoin thread - Twitter - BCS - BlakeZone  Trade Blakecoin: Cryptopia - C-patex Merged Mining Pools: EU3 - NY2/AT1 - LA1
Donation Addresses: BLC: Bd3jJftFbwxWSKNSNz35vkDd57kG6jHAjt PHO: BZXPMc8eF9YZcJStskkP2bVia38fv9VmuT BBTC: 2h8c4NbzXJXk6QQ89r7YYMGhe13gQUC2ajD ELT: e7cm6cAgpfhvk3Myh2Jkmi1nqaHtDHnxXb 
UMO: uQH9H17t7kz3eVQ3vKDzMsWCK4hn5nh2gC LIT: 8p8Z4h5fkZ8SCoyEtihKcjzZLA7gFjTdmL BTC: 1Q6kgcNqhKh8u67m6Gj73T2LMgGseETwR6
rupy
Hero Member
*****
Offline Offline

Activity: 692
Merit: 500



View Profile
February 02, 2014, 05:43:52 PM
 #1404

@bzyzny I agree, just have to understand the theoretical collision attack for SHA1 and how SHA2 solves that. How is a hash algo developed, by trial and weakness detection or do they "calculate" the theoretical strength somehow?

BANKBOOK GWT Wallet & no-FIAT Billing API
BlueDragon747
Legendary
*
Offline Offline

Activity: 1503
Merit: 1017


Solutions Architect


View Profile WWW
February 02, 2014, 05:59:51 PM
Last edit: February 02, 2014, 07:24:16 PM by BlueDragon747
 #1405

@bzyzny I agree, just have to understand the theoretical collision attack for SHA1 and how SHA2 solves that. How is a hash algo developed, by trial and weakness detection or do they "calculate" the theoretical strength somehow?

read some academic papers they do it in math first before writing an algo then get it independently verified, but most of the algo's are built from previous algo's its not easy to write a secure hashing algo especially from scratch Roll Eyes

e.g blake was from lake and chacha

Daniel J. Bernstein is one of the best:
http://cr.yp.to/djb.html

JP Aumasson is also very good (blake/blake2):
https://131002.net/

SHA-256 uses the Merkle–Damgård construction method
Blake-256 uses the HAIFA construction method which an improved Merkle–Damgård
Keccak uses the sponge construction method

SHA-256 is weak against length extension that's why they use a double hash as it is suposed to give resistance to that attack, Blake-256 is resistant to length extension due to the HAIFA construction method and Keccak is immune to length extension that's why they picked it for SHA-3 not for its speed

This is cool ref and will give you the background on different construction methods:
http://theglobaljournals.com/paripex/file.php?val=MTExNA==

This is how I know 8 round Blake-256 has a best attack of 2200, independent academic paper by one of the worlds leading groups of cryptographers  
https://eprint.iacr.org/2013/852.pdf <-- bottom of table on p4, before this I used an educated guess based on other attacks (I was a little pessimistic at 2192)

Info: GithubBlakecoin.org - BCT Blakecoin thread - Twitter - BCS - BlakeZone  Trade Blakecoin: Cryptopia - C-patex Merged Mining Pools: EU3 - NY2/AT1 - LA1
Donation Addresses: BLC: Bd3jJftFbwxWSKNSNz35vkDd57kG6jHAjt PHO: BZXPMc8eF9YZcJStskkP2bVia38fv9VmuT BBTC: 2h8c4NbzXJXk6QQ89r7YYMGhe13gQUC2ajD ELT: e7cm6cAgpfhvk3Myh2Jkmi1nqaHtDHnxXb 
UMO: uQH9H17t7kz3eVQ3vKDzMsWCK4hn5nh2gC LIT: 8p8Z4h5fkZ8SCoyEtihKcjzZLA7gFjTdmL BTC: 1Q6kgcNqhKh8u67m6Gj73T2LMgGseETwR6
bzyzny
Sr. Member
****
Offline Offline

Activity: 274
Merit: 254


View Profile
February 02, 2014, 07:23:54 PM
 #1406

@bzyzny I agree, just have to understand the theoretical collision attack for SHA1 and how SHA2 solves that. How is a hash algo developed, by trial and weakness detection or do they "calculate" the theoretical strength somehow?

I believe most cryptographic algorithms are made by either academic research groups at universities or by private corporations. Regardless, as BlueDragon pointed out, they usually start with the theoretical math and use existing techniques as a basis. Quite often new algorithms are made because theoretical flaws or weaknesses are found in existing algorithms, and so they apply that knowledge to find ways to remove/reduce those flaws. Once the improved algorithm is made, there is extensive peer review and analysis done before finalizing its implementation. In order for an algorithm to become a standard (like SHA2 and SHA3) it must go through several rounds of examination and comparison to other algorithms. And an important point to remember is that just because a particular algorithm is chosen as the standard (i.e. keccak for sha3) does not necessarily mean it is "better" than the other candidates, but only that it met the required criteria better. They try to pick whichever algo is most well rounded, or that best addresses a specific issue in the previous standard. Point is that keccak and blake not necessarily better or worse than each other, but each has advantages/disadvantages depending on what you are using it for. I think BlueDragon747 made the right choice with using blake since it seems better suited for use in cryptocurrencies than keccak. As for how they detect weaknesses and calculate theoretical strength, I dont know the specifics but it involves a lot of advanced math and statistical analysis regarding probabilities, and also i'd imagine they utilize supercomputers to try to crack it.

if you are interested in the history of cryptography, this is a good read:
https://archive.org/download/NSA-WasntAllMagic_2002/NSA-WasntAllMagic_2002.pdf
bzyzny
Sr. Member
****
Offline Offline

Activity: 274
Merit: 254


View Profile
February 02, 2014, 07:34:24 PM
 #1407

BlueDragon747, thanks for the explanation about blake2 vs blake1, makes sense you would choose the one that has more documentation and resources available and is easier to implement. Also I'm glad you pointed out the reason keccak was chosen for SHA3, I was having trouble finding an explanation of their decision.
BlueDragon747
Legendary
*
Offline Offline

Activity: 1503
Merit: 1017


Solutions Architect


View Profile WWW
February 02, 2014, 07:46:06 PM
 #1408

no problem bzyzny you have quite a good understanding about crypto stuff  Grin


Info: GithubBlakecoin.org - BCT Blakecoin thread - Twitter - BCS - BlakeZone  Trade Blakecoin: Cryptopia - C-patex Merged Mining Pools: EU3 - NY2/AT1 - LA1
Donation Addresses: BLC: Bd3jJftFbwxWSKNSNz35vkDd57kG6jHAjt PHO: BZXPMc8eF9YZcJStskkP2bVia38fv9VmuT BBTC: 2h8c4NbzXJXk6QQ89r7YYMGhe13gQUC2ajD ELT: e7cm6cAgpfhvk3Myh2Jkmi1nqaHtDHnxXb 
UMO: uQH9H17t7kz3eVQ3vKDzMsWCK4hn5nh2gC LIT: 8p8Z4h5fkZ8SCoyEtihKcjzZLA7gFjTdmL BTC: 1Q6kgcNqhKh8u67m6Gj73T2LMgGseETwR6
MikuCoin
Newbie
*
Offline Offline

Activity: 34
Merit: 0


View Profile WWW
February 02, 2014, 07:49:01 PM
 #1409

Network hash rate slowly getting higher.
bzyzny
Sr. Member
****
Offline Offline

Activity: 274
Merit: 254


View Profile
February 02, 2014, 09:15:03 PM
 #1410

no problem bzyzny you have quite a good understanding about crypto stuff  Grin

perhaps more than most, but i feel like im still only scratching the surface. i studied network communications at university and loved protocols and encoding schemes, but cryptography wasn't something i started learning about until i discovered bitcoin Smiley
rupy
Hero Member
*****
Offline Offline

Activity: 692
Merit: 500



View Profile
February 02, 2014, 09:52:53 PM
 #1411

Since 7 this morning there are no credit transactions for my account on eu1... So I see the confirmed coins but no unconfirmed ones...

BANKBOOK GWT Wallet & no-FIAT Billing API
rupy
Hero Member
*****
Offline Offline

Activity: 692
Merit: 500



View Profile
February 02, 2014, 09:59:02 PM
 #1412

pool eu1 my account... wallets don't have workers...

BANKBOOK GWT Wallet & no-FIAT Billing API
BlueDragon747
Legendary
*
Offline Offline

Activity: 1503
Merit: 1017


Solutions Architect


View Profile WWW
February 02, 2014, 10:05:59 PM
Last edit: February 02, 2014, 10:38:02 PM by BlueDragon747
 #1413

pool eu1 my account... wallets don't have workers...

ahh ok I see an error: Potential Double Payout detected

checking DB now

Edit:
should be fixed now

did you get a payout and can you see unconfirmed?

Info: GithubBlakecoin.org - BCT Blakecoin thread - Twitter - BCS - BlakeZone  Trade Blakecoin: Cryptopia - C-patex Merged Mining Pools: EU3 - NY2/AT1 - LA1
Donation Addresses: BLC: Bd3jJftFbwxWSKNSNz35vkDd57kG6jHAjt PHO: BZXPMc8eF9YZcJStskkP2bVia38fv9VmuT BBTC: 2h8c4NbzXJXk6QQ89r7YYMGhe13gQUC2ajD ELT: e7cm6cAgpfhvk3Myh2Jkmi1nqaHtDHnxXb 
UMO: uQH9H17t7kz3eVQ3vKDzMsWCK4hn5nh2gC LIT: 8p8Z4h5fkZ8SCoyEtihKcjzZLA7gFjTdmL BTC: 1Q6kgcNqhKh8u67m6Gj73T2LMgGseETwR6
rupy
Hero Member
*****
Offline Offline

Activity: 692
Merit: 500



View Profile
February 03, 2014, 12:03:57 AM
 #1414

Yeps, all back to normal.

BANKBOOK GWT Wallet & no-FIAT Billing API
BlueDragon747
Legendary
*
Offline Offline

Activity: 1503
Merit: 1017


Solutions Architect


View Profile WWW
February 03, 2014, 12:33:22 AM
 #1415

Yeps, all back to normal.

cool  Cool

if you see any other issues just let me know  Grin

Info: GithubBlakecoin.org - BCT Blakecoin thread - Twitter - BCS - BlakeZone  Trade Blakecoin: Cryptopia - C-patex Merged Mining Pools: EU3 - NY2/AT1 - LA1
Donation Addresses: BLC: Bd3jJftFbwxWSKNSNz35vkDd57kG6jHAjt PHO: BZXPMc8eF9YZcJStskkP2bVia38fv9VmuT BBTC: 2h8c4NbzXJXk6QQ89r7YYMGhe13gQUC2ajD ELT: e7cm6cAgpfhvk3Myh2Jkmi1nqaHtDHnxXb 
UMO: uQH9H17t7kz3eVQ3vKDzMsWCK4hn5nh2gC LIT: 8p8Z4h5fkZ8SCoyEtihKcjzZLA7gFjTdmL BTC: 1Q6kgcNqhKh8u67m6Gj73T2LMgGseETwR6
kramble
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250



View Profile WWW
February 03, 2014, 10:50:46 AM
 #1416


I did solo-mine, would have found two blocks.

But the base difficulty and golden nonce are off in mine.py for the coin so it counted the solved blocks as rejected.

There is an easy work-around, just uncomment line 104 of mine.py. This will submit all shares regardless of the difficulty target, which is harmless when solo mining, and since (AFAIK, Blue may want to chip in here) the blakecoin pools are currently fixed diff=1 (even though the dashboard may report higher), it should be OK there too.

A slightly more sophisticated fix would retain the subsequent CheckTarget() and logger calls, but always return True.

Github https://github.com/kramble BLC BkRaMaRkw3NeyzsZ2zUgXsNLogVVkQ1iPV
BlueDragon747
Legendary
*
Offline Offline

Activity: 1503
Merit: 1017


Solutions Architect


View Profile WWW
February 03, 2014, 12:28:20 PM
 #1417


I did solo-mine, would have found two blocks.

But the base difficulty and golden nonce are off in mine.py for the coin so it counted the solved blocks as rejected.

There is an easy work-around, just uncomment line 104 of mine.py. This will submit all shares regardless of the difficulty target, which is harmless when solo mining, and since (AFAIK, Blue may want to chip in here) the blakecoin pools are currently fixed diff=1 (even though the dashboard may report higher), it should be OK there too.

A slightly more sophisticated fix would retain the subsequent CheckTarget() and logger calls, but always return True.

my pools are fixed diff 1 so work should get accepted if the share is diff 1 and the miner can submit it, kr105's pool blakecoinpool.org is diff 2  

getwork is on port 8337
http://eu1.blakecoin.com
http://ny1.blakecoin.com

give it a try  Grin

Info: GithubBlakecoin.org - BCT Blakecoin thread - Twitter - BCS - BlakeZone  Trade Blakecoin: Cryptopia - C-patex Merged Mining Pools: EU3 - NY2/AT1 - LA1
Donation Addresses: BLC: Bd3jJftFbwxWSKNSNz35vkDd57kG6jHAjt PHO: BZXPMc8eF9YZcJStskkP2bVia38fv9VmuT BBTC: 2h8c4NbzXJXk6QQ89r7YYMGhe13gQUC2ajD ELT: e7cm6cAgpfhvk3Myh2Jkmi1nqaHtDHnxXb 
UMO: uQH9H17t7kz3eVQ3vKDzMsWCK4hn5nh2gC LIT: 8p8Z4h5fkZ8SCoyEtihKcjzZLA7gFjTdmL BTC: 1Q6kgcNqhKh8u67m6Gj73T2LMgGseETwR6
kramble
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250



View Profile WWW
February 03, 2014, 12:59:15 PM
 #1418

my pools are fixed diff 1 so work should get accepted if the share is diff 1 and the miner can submit it, kr105's pool blakecoinpool.org is diff 2  

getwork is on port 8337
http://eu1.blakecoin.com
http://ny1.blakecoin.com

give it a try  Grin

OK, thanks, I was a little confused about the diff, but I did recall kr105's as sometimes reporting diff 2 and sometimes diff 4 on the dashboard. Anyway the worst that can happen is an increased reject rate, which is not ideal from the pool's point of view, but fairly harmless if it's just for testing. The FPGA always returns diff 1 shares, so unless there is an issue with hardware errors there will be no problem on your pools.

Once we've actually got some shares accepted on pool, the mining script can be tweaked to fix any target issues (see my previous post on the workaround).

Github https://github.com/kramble BLC BkRaMaRkw3NeyzsZ2zUgXsNLogVVkQ1iPV
BlueDragon747
Legendary
*
Offline Offline

Activity: 1503
Merit: 1017


Solutions Architect


View Profile WWW
February 03, 2014, 01:28:57 PM
 #1419

my pools are fixed diff 1 so work should get accepted if the share is diff 1 and the miner can submit it, kr105's pool blakecoinpool.org is diff 2  

getwork is on port 8337
http://eu1.blakecoin.com
http://ny1.blakecoin.com

give it a try  Grin

OK, thanks, I was a little confused about the diff, but I did recall kr105's as sometimes reporting diff 2 and sometimes diff 4 on the dashboard. Anyway the worst that can happen is an increased reject rate, which is not ideal from the pool's point of view, but fairly harmless if it's just for testing. The FPGA always returns diff 1 shares, so unless there is an issue with hardware errors there will be no problem on your pools.

Once we've actually got some shares accepted on pool, the mining script can be tweaked to fix any target issues (see my previous post on the workaround).

I am still using your python Blakecoin miner for the Lancelot boards and set that to diff 1 works a treat on the pools Grin

Info: GithubBlakecoin.org - BCT Blakecoin thread - Twitter - BCS - BlakeZone  Trade Blakecoin: Cryptopia - C-patex Merged Mining Pools: EU3 - NY2/AT1 - LA1
Donation Addresses: BLC: Bd3jJftFbwxWSKNSNz35vkDd57kG6jHAjt PHO: BZXPMc8eF9YZcJStskkP2bVia38fv9VmuT BBTC: 2h8c4NbzXJXk6QQ89r7YYMGhe13gQUC2ajD ELT: e7cm6cAgpfhvk3Myh2Jkmi1nqaHtDHnxXb 
UMO: uQH9H17t7kz3eVQ3vKDzMsWCK4hn5nh2gC LIT: 8p8Z4h5fkZ8SCoyEtihKcjzZLA7gFjTdmL BTC: 1Q6kgcNqhKh8u67m6Gj73T2LMgGseETwR6
Jude Austin
Legendary
*
Offline Offline

Activity: 1139
Merit: 1000


The Real Jude Austin


View Profile WWW
February 03, 2014, 03:58:26 PM
 #1420


I did solo-mine, would have found two blocks.

But the base difficulty and golden nonce are off in mine.py for the coin so it counted the solved blocks as rejected.

There is an easy work-around, just uncomment line 104 of mine.py. This will submit all shares regardless of the difficulty target, which is harmless when solo mining, and since (AFAIK, Blue may want to chip in here) the blakecoin pools are currently fixed diff=1 (even though the dashboard may report higher), it should be OK there too.

A slightly more sophisticated fix would retain the subsequent CheckTarget() and logger calls, but always return True.

Thanks for the response Kramble!

I will give this a shot.

Get paid BTC to sign up for free tokens: http://earn.com/judeaustin/referral/?a=d3euriwoffdrlv4b
Pages: « 1 ... 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 [71] 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 ... 203 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!