Search content
Sort by
Showing 20 of 35 results by ExploitAgency
Re: [ANN][GRS] Groestlcoin | Upgrade to NEW Groestlcoin Core ASAP | Segwit activated
GRS price 22 March: 620 sat
BTC price 22 March: 1011 USD
Congrats ExploitAgency and hterw !!
BTC price 22 March: 1011 USD
Congrats ExploitAgency and hterw !!
Woo hoo! My Net is wonky but I will distribute the rewards shortly.
Hmmm . . . let's see:
hterw get 1,000 GRS from me
and ExploitAgency gets 1,000 GRS from jwinterm.
EDIT: Happy birthday, GRS!!
YA! Happy Birthday Groestlcoin!
Re: excavator - multi-algorithm advanced NVIDIA CUDA miner [1.1.3a]
https://github.com/wine-compholio/wine-staging/wiki/Installation
Closest to running on linux is using wine-staging but it throws constant errors.
Maybe someone with more time can figure it out if a Linux binary/source doesn't come out soon. I am not a Wine expert by any means. In a similar bit with GPU's I've only ran scallion through mono.
Startup
Closest to running on linux is using wine-staging but it throws constant errors.
Maybe someone with more time can figure it out if a Linux binary/source doesn't come out soon. I am not a Wine expert by any means. In a similar bit with GPU's I've only ran scallion through mono.
Code:
fixme:msvcrt:_CurrentScheduler_Id stub
fixme:msvcrt:_CurrentScheduler_Id stub
fixme:msvcrt:_CurrentScheduler_Id stub
fixme:msvcrt:_CurrentScheduler_Id stub
fixme:msvcrt:_CurrentScheduler_Id stub
fixme:msvcrt:_CurrentScheduler_Id stub
fixme:msvcrt:_CurrentScheduler_Id stub
fixme:msvcrt:_CurrentScheduler_Id stub
fixme:msvcrt:_CurrentScheduler_Id stub
Startup
Code:
wine excavator.exe -a pascal -s pascal.eu.nicehash.com:3358 -u 1LHVh4ZraCMRfKQvtvJx7u3TT7gYvE462F.1070 -cd 0
fixme:winediag:start_process Wine Staging 2.3 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
fixme:heap:RtlSetHeapInformation 0x330000 0 0x23fd30 4 stub
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x23f840 1 C) semi-stub
==================== www.nicehash.com ====================
Excavator v1.1.3a GPU Miner for NiceHash.
Copyright (C) 2017 NiceHash. All rights reserved.
Developed by djeZo with help and contributors of code:
pallas, Vorksholk, bitbandi, ocminer
==================== www.nicehash.com ====================
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x0000002f][info] Log started
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x0000002f][info] Miner starting up, press [CTRL + C] to quit
^Cfixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x0000002f][info] net | Connecting to pascal.eu.nicehash.com:3358
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x0000002f][info] Shutting down
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0xe0de00 1 C) semi-stub
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0xe0d8d0 1 C) semi-stub
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x00000033][info] device#0 | Initializing thread #0 GPU#0 GeForce GTX 1070
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x00000030][info] net | Connected!
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x00000033][info] device#0 | Algorithm: CUDA-pascal parameters: B=122835,TPB=512
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x00000033][info] device#0 | Thread #0 ended (GPU#0 GeForce GTX 1070)
fixme:winediag:start_process Wine Staging 2.3 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
fixme:heap:RtlSetHeapInformation 0x330000 0 0x23fd30 4 stub
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x23f840 1 C) semi-stub
==================== www.nicehash.com ====================
Excavator v1.1.3a GPU Miner for NiceHash.
Copyright (C) 2017 NiceHash. All rights reserved.
Developed by djeZo with help and contributors of code:
pallas, Vorksholk, bitbandi, ocminer
==================== www.nicehash.com ====================
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x0000002f][info] Log started
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x0000002f][info] Miner starting up, press [CTRL + C] to quit
^Cfixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x0000002f][info] net | Connecting to pascal.eu.nicehash.com:3358
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x0000002f][info] Shutting down
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0xe0de00 1 C) semi-stub
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0xe0d8d0 1 C) semi-stub
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x00000033][info] device#0 | Initializing thread #0 GPU#0 GeForce GTX 1070
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x00000030][info] net | Connected!
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x00000033][info] device#0 | Algorithm: CUDA-pascal parameters: B=122835,TPB=512
fixme:msvcrt:_getptd returns undocumented/not fully filled data
fixme:msvcrt:_getptd returns undocumented/not fully filled data
[12:02:44][0x00000033][info] device#0 | Thread #0 ended (GPU#0 GeForce GTX 1070)
Re: [RAFFLE] Extreme NastyFans Set Pack raffle 4 WINNERS
Pm me for my new btc address before sending refund. I was hoping this would pan out. Do not send to old addresss. Thank you
We can do a suicide raffle, i think thats what you called it. You get all other slots and choose a block and maybe i win
but cant modify the posted prizes still draw 1,2,3,4, haha, up to you...
I really want a nastyfans seat below retail or the excitebike coin.
We can do a suicide raffle, i think thats what you called it. You get all other slots and choose a block and maybe i win
but cant modify the posted prizes still draw 1,2,3,4, haha, up to you...I really want a nastyfans seat below retail or the excitebike coin.
Re: [RAFFLE] Extreme NastyFans Set Pack raffle- NastyPennies,Custom,1oz glit
Does the seat have the raised center(Light Deflector) like the original 150?
Only the first 150 all silver 1oz coins had the light diffusers in them. None of the gold highlighted coins had this feature.
Good to know, thanks!
Re: [RAFFLE] Extreme NastyFans Set Pack raffle- NastyPennies,Custom,1oz glit
Sorry, I waited 3-4 hours for 1 confirmation while moving stuff around...
Anyways pretty excited about this one! Hope I get that SEAT & Excitebike.
Does the seat have the raised center(Light Deflector) like the original 150?
Anyways pretty excited about this one! Hope I get that SEAT & Excitebike.
Does the seat have the raised center(Light Deflector) like the original 150?
Re: [ANN] HAM - HamRadioCoin - SHA 256 - Crypto on the radio! Official Thread
... --- ...
Oh well... I'm sorry, I am a ham too. Download scallion... make a novelty gpg key, just make sure to use a higher bit encryption than the default.
Or find a coin on the supported list at my repo that has an address that starts with first letter of your call sign.
I'm in the 4 region.
oclvanitygen should make an address with a callsign prefix when case insensitive in less than 30 minutes on most modern hardware.
Oh well... I'm sorry, I am a ham too. Download scallion... make a novelty gpg key, just make sure to use a higher bit encryption than the default.
Or find a coin on the supported list at my repo that has an address that starts with first letter of your call sign.
I'm in the 4 region.
oclvanitygen should make an address with a callsign prefix when case insensitive in less than 30 minutes on most modern hardware.
Oh ok I thought it chose the one with the best reward for the difficulty not necessarily the easiest. But I've never looked into it just assumed.
How often does your pool sync with vanitypool?
How often does your pool sync with vanitypool?
Consider being solely your own pool once you gain popularity as vanitypool takes 20% fee already subtracted from reward shown(reward shown is actual payout on vanitypool, add 20% for total fee end user paid for address)
Take 2% from reward shown for payout on bitcoin-apps pool.
vanitypool seems to hold funds in a separate wallet for each address submitted
Is there anyway you can choose the easiest addresses first from vanitypool to make sure hashing power is going to good use vs going for the highest reward and we just clear out the backlog since you are in beta?
Also if you ever decide to shut down the pool I'd love it if you sent me your source and I'd gladly keep it going :-D
Take 2% from reward shown for payout on bitcoin-apps pool.
vanitypool seems to hold funds in a separate wallet for each address submitted
Is there anyway you can choose the easiest addresses first from vanitypool to make sure hashing power is going to good use vs going for the highest reward and we just clear out the backlog since you are in beta?
Also if you ever decide to shut down the pool I'd love it if you sent me your source and I'd gladly keep it going :-D
Just a thought, although a new client is a great idea too, just lots of end users don't trust something new, don't know how to read code, and can't compile it themselves even if they could verify changes to code to be secure.. but if you get big and gain some trust and people see payouts maybe that will change. Or maybe I am totally wrong. Just my opinion.
But great project, and I'm looking forward to seeing it grow. I'm throwing 1Mkey/s right now at it to just keep an eye on stats, then I'll send a little hashing power its way later on. Seems to work great though so far!
But great project, and I'm looking forward to seeing it grow. I'm throwing 1Mkey/s right now at it to just keep an eye on stats, then I'll send a little hashing power its way later on. Seems to work great though so far!
I forgot about the minimum payout, Haha, plans foiled! Oh well you thought of everything...
I don't see any problems then, its actually working quite well now, minus a slow miner being rewarded the same as a fast miner.
Possible to generate a getWork specific to a workername? like:
oclvanityminer -u https://bitcoin-apps.appspot.com/mining/worker1 -a BTCADD
maybe use btc payout address twice vs worker name so it will be unique
it avoids using ip addresses, and theres no reason for the getWork files to pile up, if you delete them every few hours they should regenerate as users come back to mine vanity
Quote
Yes, that specific "share already solved" logic is pretty trivial to adjust as a quickfix. The caveat that makes it a little more than a quickfix is that it would have to only accept solutions with a different private key than any already submitted by the miner for the share, as otherwise you can solve one share and then abuse the fact that you know the solution to that share already to basically "print" shares Smiley. Still, should be possible to do while the longer-term solution gets built.
I don't see any problems then, its actually working quite well now, minus a slow miner being rewarded the same as a fast miner.
Possible to generate a getWork specific to a workername? like:
oclvanityminer -u https://bitcoin-apps.appspot.com/mining/worker1 -a BTCADD
maybe use btc payout address twice vs worker name so it will be unique
it avoids using ip addresses, and theres no reason for the getWork files to pile up, if you delete them every few hours they should regenerate as users come back to mine vanity
Scratch 100x 1Mkey/s miners.
Use one big gpu farm then,
One could likely write a script that generates a thousand or however many Bitcoin addresses saving private keys of course.
Then point the farm to miner on your pool with each address until each one finds a share.
Then the reward keeps going down and down per share, but really that one gpu farm has all the shares...
Boom! even if it was just 10% of the pools hash rate it could take all the profits. Because that other big hash rate gpu farm doesn't get but 1 share per 30 minutes because they are playing fair.
Then its pointless to mine if profit was really ever there...
I'm sure sweeping the coins from generated share stealing address would be a breeze too, easier than stopping miners after one share.
But I'm not being critical in a negative sense, its an awesome idea and I wish I did it first. :-D
Good job so far!
PS: A server side only solution would be the best option of perhaps resetting the variable for "share already solved" to zero after adding a share to stats. Don't know the server side code, is this possible? Sounds too easy... Anyways, pretty exciting stuff. Only problem with a custom oclvanitygen is windows users struggle compiling it from source and the trust factor for new precompiled forks is low. I would certainly add your mods to my fork though, but would need an additional flag for setting options for your pool as not to mess up compatibility with any other pools that may exist.
Use one big gpu farm then,
One could likely write a script that generates a thousand or however many Bitcoin addresses saving private keys of course.
Then point the farm to miner on your pool with each address until each one finds a share.
Then the reward keeps going down and down per share, but really that one gpu farm has all the shares...
Boom! even if it was just 10% of the pools hash rate it could take all the profits. Because that other big hash rate gpu farm doesn't get but 1 share per 30 minutes because they are playing fair.
Then its pointless to mine if profit was really ever there...
I'm sure sweeping the coins from generated share stealing address would be a breeze too, easier than stopping miners after one share.
But I'm not being critical in a negative sense, its an awesome idea and I wish I did it first. :-D
Good job so far!
PS: A server side only solution would be the best option of perhaps resetting the variable for "share already solved" to zero after adding a share to stats. Don't know the server side code, is this possible? Sounds too easy... Anyways, pretty exciting stuff. Only problem with a custom oclvanitygen is windows users struggle compiling it from source and the trust factor for new precompiled forks is low. I would certainly add your mods to my fork though, but would need an additional flag for setting options for your pool as not to mess up compatibility with any other pools that may exist.
So if I have a miner doing 1Mkey/s it will pay the same as one doing 100Mkey/s? Because you can only have one share per 30 minutes no matter how many times you solve that share?
No matter how many times you solve the share it only reports it as one share?
Thats how it is looking for me.
I didn't even see your response and thought stats just started working so I edited my post above, then I saw you had replied. Thats a fast response, good work!
But anyways so am I correct on my assumption with shares that its more profitable to have a bunch of 1Mkey/s miners than one giant?
No matter how many times you solve the share it only reports it as one share?
Thats how it is looking for me.
I didn't even see your response and thought stats just started working so I edited my post above, then I saw you had replied. Thats a fast response, good work!
But anyways so am I correct on my assumption with shares that its more profitable to have a bunch of 1Mkey/s miners than one giant?
Take this in a positive light but your pool has all the problems of a new pool, see below, perhaps the issue is its not updated in real time?:
There is a pretty massive typo...?
Problem:
Has this pool not yet launched?
Also theres a minor typo here(source html is wrong)
Also when looking up address statistics...
And more things, I keep getting these addresses... are they there for testing or is it a bug.(Edit: I now see its shares, but they aren't counted as shares)
https://bitcoin-apps.appspot.com/getWork
Its on the getWork list but says already solved as did these when I started.
Total value for current work: 0.000001 BTC/Gkey
Pattern: 19Z8Cx
Address: 19Z8CxRWQWFRwVQBiZwo6eZ6tHqQyE5nJt
PrivkeyPart: 5JajFv34Hnup1GrkMM36jADChJcJZSaWGSGxJdUCPtzmREiCUuR
[52.04 Mkey/s][total 8886681600][Prob 21.5%][50% in 2.2s][Found 1] share rejected, already solved
Total value for current work: 0.000001 BTC/Gkey
Pattern: 19TVqs
Address: 19TVqsYhEfjG9TvAd8uYnsZiA77hPQB2kf
PrivkeyPart: 5K9DRvcoG2iHLynDPnqXj8PL4GMPTrioXMXEKbw1qpUzMqt5Bx3
share rejected, already solved
Total value for current work: 0.000001 BTC/Gkey
Pattern: 12C6sz
Address: 12C6szsTwFmk9SYMFGjPHLDCvqLjFTP6bD
PrivkeyPart: 5KW9gu2v51kmPxzvuwoPZSXnCyqRxrHhJZ1prGaXwYmYGFpVukD
[54.84 Mkey/s][total 16326328320][Prob 21.2%][50% in 2.2s][Found 1] share rejected, already solved
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Difficulty: 50656515217834
I'm also not seeing the shares increase. With your calculations of 1Mkeys getting 2 shares and hour, I should be getting a few shares every minute. Although I can not view my specific stats because of an error 500, I don't see the shares for the pools stats increasing either.
Really cool project though, I am going to check out the other non piachu pool linked as well.
EDIT:
AHA I was wondering how you calculated shares! But the shares still don't increase as I solve them and stats don't work.
How does the PPS scheme work?
Miners point their vanity mining software at the pool, which generates a "share prefix" every 30 minutes. This share prefix is set at a complexity that takes approximately 30 minutes at 1 million keys/second. When the miner retrieves work to complete, the prefix to mine and the share prefix are both provided, and have the same public key. This allows the software to mine both at the same time.
The software will submit a solution to the share prefix when found. Only one solution to each prefix will be accepted, and this constitutes a "share". As miners continue mining, they will keep mining these shares and receive approximately one share every 30 minutes, assuming their hardware is able to mine the share prefix in that time.
When a miner finds a solution to the customer's vanity address prefix, the solution is checked with the upstream pool. If confirmation succeeds, that miner is rewarded a bonus of 10% of their contributed shares, or one share if they have not yet contributed any shares. The primary reason for this reward is to ensure miners that find the target prefix shortly after starting to mine the prefix (there is always a chance this happens, albeit a low chance) do not miss out on a reward.
The amount miners are paid is determined by dividing the reward by the number of shares to determine a reward per share, and then multiplying each miner's share count to determine their specific reward. Rewards less than one satoshi are discarded.
EDIT Now stats show up but shares still aren't right.
It seems only the first solve of the share is counted as a share? Which in that case how can you calculate hashing power, might as well mine with 1mhkey/s and get paid the same as someone whos mining with 100mhkey/s
There is a pretty massive typo...?
Problem:
Code:
oclvanityminer -u https://vanitymining.appspot.com -a [your Bitcoin address]
Fix: Code:
./oclvanityminer -u https://bitcoin-apps.appspot.com -a [your Bitcoin address]
Has this pool not yet launched?
Also theres a minor typo here(source html is wrong)
Quote
tl;dr the Vanity
Also when looking up address statistics...
Quote
500 Internal Server Error
The server has either erred or is incapable of performing the requested operation.
The server has either erred or is incapable of performing the requested operation.
And more things, I keep getting these addresses... are they there for testing or is it a bug.(Edit: I now see its shares, but they aren't counted as shares)
https://bitcoin-apps.appspot.com/getWork
Quote
1EvanAhrn:0499AEC60DCB61ACCD62A6E8C4668FD5F3671844DA91D072A75E1422BD4897ABAB1A14F2D8A2E35 62C0F5384BE0FA9A358DDA8AE43297DA482B41D8CB44353DB9B:0:0.03499700; 19Z8Cx:0499AEC60DCB61ACCD62A6E8C4668FD5F3671844DA91D072A75E1422BD4897ABAB1A14F2D8A2E35 62C0F5384BE0FA9A358DDA8AE43297DA482B41D8CB44353DB9B:0:0.000000;
Its on the getWork list but says already solved as did these when I started.
Total value for current work: 0.000001 BTC/Gkey
Pattern: 19Z8Cx
Address: 19Z8CxRWQWFRwVQBiZwo6eZ6tHqQyE5nJt
PrivkeyPart: 5JajFv34Hnup1GrkMM36jADChJcJZSaWGSGxJdUCPtzmREiCUuR
[52.04 Mkey/s][total 8886681600][Prob 21.5%][50% in 2.2s][Found 1] share rejected, already solved
Total value for current work: 0.000001 BTC/Gkey
Pattern: 19TVqs
Address: 19TVqsYhEfjG9TvAd8uYnsZiA77hPQB2kf
PrivkeyPart: 5K9DRvcoG2iHLynDPnqXj8PL4GMPTrioXMXEKbw1qpUzMqt5Bx3
share rejected, already solved
Total value for current work: 0.000001 BTC/Gkey
Pattern: 12C6sz
Address: 12C6szsTwFmk9SYMFGjPHLDCvqLjFTP6bD
PrivkeyPart: 5KW9gu2v51kmPxzvuwoPZSXnCyqRxrHhJZ1prGaXwYmYGFpVukD
[54.84 Mkey/s][total 16326328320][Prob 21.2%][50% in 2.2s][Found 1] share rejected, already solved
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Difficulty: 50656515217834
I'm also not seeing the shares increase. With your calculations of 1Mkeys getting 2 shares and hour, I should be getting a few shares every minute. Although I can not view my specific stats because of an error 500, I don't see the shares for the pools stats increasing either.
Really cool project though, I am going to check out the other non piachu pool linked as well.
EDIT:
AHA I was wondering how you calculated shares! But the shares still don't increase as I solve them and stats don't work.
Quote
How does the PPS scheme work?
Miners point their vanity mining software at the pool, which generates a "share prefix" every 30 minutes. This share prefix is set at a complexity that takes approximately 30 minutes at 1 million keys/second. When the miner retrieves work to complete, the prefix to mine and the share prefix are both provided, and have the same public key. This allows the software to mine both at the same time.
The software will submit a solution to the share prefix when found. Only one solution to each prefix will be accepted, and this constitutes a "share". As miners continue mining, they will keep mining these shares and receive approximately one share every 30 minutes, assuming their hardware is able to mine the share prefix in that time.
When a miner finds a solution to the customer's vanity address prefix, the solution is checked with the upstream pool. If confirmation succeeds, that miner is rewarded a bonus of 10% of their contributed shares, or one share if they have not yet contributed any shares. The primary reason for this reward is to ensure miners that find the target prefix shortly after starting to mine the prefix (there is always a chance this happens, albeit a low chance) do not miss out on a reward.
The amount miners are paid is determined by dividing the reward by the number of shares to determine a reward per share, and then multiplying each miner's share count to determine their specific reward. Rewards less than one satoshi are discarded.
EDIT Now stats show up but shares still aren't right.
It seems only the first solve of the share is counted as a share? Which in that case how can you calculate hashing power, might as well mine with 1mhkey/s and get paid the same as someone whos mining with 100mhkey/s
Quote
./oclvanityminer -u https://bitcoin-apps.appspot.com/ -a MYADD
Searching for pattern: "18pSyF" Reward: 0.000000 Value: 0.000000 BTC/Gkey
Difficulty: 259627881
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Next match difficulty: 259626550 (2 prefixes)
Total value for current work: 0.000001 BTC/Gkey
Pattern: 18pSyF
Address: 18pSyFF5Q6iJ4qQna22TVz4NceDmiv7TpN
PrivkeyPart: 5JGx1siC6vPM6MNSLY2gVPypF2qbGSs3B8Yx8cwTdpHYvhFa9jy
OK!
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Difficulty: 50656515217834
Total value for current work: 0.000001 BTC/Gkey
[30.58 Mkey/s][total 2941255680][Prob 0.0%][50% in 13.3d] Searching for pattern: "18pSyF" Reward: 0.000000 Value: 0.000000 BTC/Gkey
Difficulty: 259627881
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Next match difficulty: 259626550 (2 prefixes)
Total value for current work: 0.000001 BTC/Gkey
Pattern: 18pSyF
Address: 18pSyFbDQcDLCAGuqSepYejxREYJ9J3Mpq
PrivkeyPart: 5JeEQjRohB4bFKB7DYgf2zRKJ2AVnzqzUJK1sDBCrBvbqDfGVee
share rejected, already solved
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Difficulty: 50656515217834
Total value for current work: 0.000001 BTC/Gkey
[29.98 Mkey/s][total 6212812800][Prob 0.0%][50% in 13.6d] Searching for pattern: "18pSyF" Reward: 0.000000 Value: 0.000000 BTC/Gkey
Difficulty: 259627881
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Next match difficulty: 259626550 (2 prefixes)
Total value for current work: 0.000001 BTC/Gkey
Pattern: 18pSyF
Address: 18pSyF6SHUmPnq3TihL4dgLvM9hCfXGSvL
PrivkeyPart: 5KJmXsCALh4BmJbvtZHt9DJMfKrxs54KzzPSo8HqwZycTHKMKJE
[27.39 Mkey/s][total 6354370560][Prob 11.4%][50% in 5.4s][Found 1] share rejected, already solved
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Difficulty: 50656515217834
Searching for pattern: "18pSyF" Reward: 0.000000 Value: 0.000000 BTC/Gkey
Difficulty: 259627881
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Next match difficulty: 259626550 (2 prefixes)
Total value for current work: 0.000001 BTC/Gkey
Pattern: 18pSyF
Address: 18pSyFF5Q6iJ4qQna22TVz4NceDmiv7TpN
PrivkeyPart: 5JGx1siC6vPM6MNSLY2gVPypF2qbGSs3B8Yx8cwTdpHYvhFa9jy
OK!
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Difficulty: 50656515217834
Total value for current work: 0.000001 BTC/Gkey
[30.58 Mkey/s][total 2941255680][Prob 0.0%][50% in 13.3d] Searching for pattern: "18pSyF" Reward: 0.000000 Value: 0.000000 BTC/Gkey
Difficulty: 259627881
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Next match difficulty: 259626550 (2 prefixes)
Total value for current work: 0.000001 BTC/Gkey
Pattern: 18pSyF
Address: 18pSyFbDQcDLCAGuqSepYejxREYJ9J3Mpq
PrivkeyPart: 5JeEQjRohB4bFKB7DYgf2zRKJ2AVnzqzUJK1sDBCrBvbqDfGVee
share rejected, already solved
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Difficulty: 50656515217834
Total value for current work: 0.000001 BTC/Gkey
[29.98 Mkey/s][total 6212812800][Prob 0.0%][50% in 13.6d] Searching for pattern: "18pSyF" Reward: 0.000000 Value: 0.000000 BTC/Gkey
Difficulty: 259627881
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Next match difficulty: 259626550 (2 prefixes)
Total value for current work: 0.000001 BTC/Gkey
Pattern: 18pSyF
Address: 18pSyF6SHUmPnq3TihL4dgLvM9hCfXGSvL
PrivkeyPart: 5KJmXsCALh4BmJbvtZHt9DJMfKrxs54KzzPSo8HqwZycTHKMKJE
[27.39 Mkey/s][total 6354370560][Prob 11.4%][50% in 5.4s][Found 1] share rejected, already solved
Searching for pattern: "1EvanAhrn" Reward: 0.034997 Value: 0.000001 BTC/Gkey
Difficulty: 50656515217834