VanitySearch (Yet another address prefix finder)

[Jean_Luc]

Hello
By default it is the dedicated memory of the graphics processor that is used but would it be possible also to force the use of the shared ram? Could this increase the speed of execution or am I wrong?

Hello
VanitySearch uses the GPU global memory to store hash160 that partially match (16bit lookup table) the desired prefixes, the transfer to the RAM of the motherboard is done by the DMA, then the CPU checks all returned hash160 against the complete prefix.
There is no really shared memory that can be accessed directly by the CPU and the GPU (may be it exists on embedded GPU). Transfers are mainly done by the DMA trough the PCIe.
What we usually called "shared memory" in CUDA is a GPU memory shared inside a WARP. A WARP is a block of 32 threads (or more on powerfull GPU) executed on a stream processor.

[Lolo54]

ok thank you jean luc you answered my question! as for the error for -b or -u with 3 characters (ex 1TesT) did you manage to reproduce the error message and understand where it could come from? This remains very marginal and only involves a small percentage the result even if it was not resolved 

[Jean_Luc]

No I didn't manage to reproduce the issue. If you use a prefix with 4 char and also starting with a T you can expect that the bug will occurs 58 times less. It could be interesting to test with 'BTC' prefix , for instance, more probable that 'TeS'.

[Lolo54]

Ok jean luc i’m trying  tomorrow

[Jean_Luc]

I manged to reproduce the bug.
It happens only for uncompressed addresses.
It is not link to CUDA 8 or 10.
It happens also if CPU is used alone or if GPU is used alone.
But with a probability of ~1/2000
I don't know if it is also linked to the prefix length (I don't think) it is difficult to reproduce with longer prefix due to the small probability.

I'll try to debug this...

[Jean_Luc]

Hello,

I fixed the issue. New release 1.12 is ready. I upload the CUDA8 ASAP.
The bug was due to 'negative zero' when a match was found for a symmetric point at index 0 of the group.
In that case the symmetric point noted -0 was interpreted as 0.
It did not affect compressed address because, for that case, the y value of the point does not matter (the parity is handled using an other way).
So I simply applied the same logic for compressed and uncompressed, it should work fine.
It happened with a probability of 1/(GPR_SIZE*2) = 1/2048.

Many thanks to Lolo54 for all the tests.

[Lolo54]

Perfect it works very well no more error message with -b nor with -u with this version 1.12
It's amazing the speed difference according to the prefix to calculate  
1BTC is calculated on average according to the mode 10 to 15 times slower than 1Tes

Code:

VanitySearchCUDA10.112.exe -gpu -b -o vanity.txt 1teS
VanitySearch v1.12
Difficulty: 4553521
Search: 1teS [Compressed or Uncompressed]
Start Tue Apr  9 13:30:55 2019
Base Key:CA0095835D96BB099F1EDF9837E0E41A233C9516D98CDA6989A4D9483DDAE8BE
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
335.488 MK/s (GPU 324.686 MK/s) (2^34.16) [P 100.00%][99.00% in 00:00:00][8525]

Code:

VanitySearchCUDA10.112.exe -gpu -u -o vanity.txt 1BTC
VanitySearch v1.12
Difficulty: 78509
Search: 1BTC [Uncompressed]
Start Tue Apr  9 13:34:17 2019
Base Key:AB1137C6F8BF8074E57D27F2F4882FE84FA334A56CDD2BC8E9F2570F306E9493
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
43.005 MK/s (GPU 28.219 MK/s) (2^31.70) [P 100.00%][99.00% in 00:00:00][41788]

Code:

VanitySearchCUDA10.112.exe -gpu -o vanity.txt 1BTC
VanitySearch v1.12
Difficulty: 78509
Search: 1BTC [Compressed]
Start Tue Apr  9 13:41:11 2019
Base Key:4BED85DFFA3A1B529E95EA2CF90F9BFE80EFDE547B419F8EA5DE9EABBBDF47B0
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
50.841 MK/s (GPU 22.619 MK/s) (2^28.92) [P 100.00%][99.00% in 00:00:00][6105]

Code:

VanitySearchCUDA10.112.exe -gpu -b -o vanity.txt 1BTC
VanitySearch v1.12
Difficulty: 78509
Search: 1BTC [Compressed or Uncompressed]
Start Tue Apr  9 13:53:18 2019
Base Key:FD10E87508883CE873902008A49CA5DC300A83628B3081A3673B25691B70E28C
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
22.865 MK/s (GPU 14.056 MK/s) (2^28.83) [P 100.00%][99.00% in 00:00:00][13889]

[Jean_Luc]

1BTC is calculated on average according to the mode 10 to 15 times slower faster than 1Tes

Yes this is due to the pivot at 1QLbz7... (The switch from 0x[00]FFFFFFFF.... to 0x[00]0XXXXXXX...).

Thanks for the tests.

[Jean_Luc]

Is it possible to generate a split-key address so I can create an address for someone else and they don't have to worry that I know their private-key?
>> https://en.bitcoin.it/wiki/Split-key_vanity_address

Yes this can be done.
I'll add this feature ASAP.

[Jean_Luc]

In fact i already added the feature. It is committed on GutHub but not yet released (there is still a bug, from time to time the address cannot be reconstructed)
Few word for those who want to test from the source:

Case: Alice want a nice prefix but does not have CPU power available, Bob has the power but cannot know the private key of Alice.

Alice generate a key pair then she sends the public key and the wanted prefix to Bob:

Code:

C:\C++\VanitySearch\x64\Release>VanitySearch.exe -s "AliceSeed" -kp
Priv : L4U2Ca2wyo721n7j9nXM9oUWLzCj19nKtLeJuTXZP3AohW9wVgrH
Pub  : 03FC71AE1E88F143E8B05326FC9A83F4DAB93EA88FFEACD37465ED843FCC75AA81

Bob runs VanitySeacrh using the Alice's public key and send back the keyinfo.txt file to Alice:

Code:

C:\C++\VanitySearch\x64\Release>VanitySearchCUDA8.exe -sp 03FC71AE1E88F143E8B05326FC9A83F4DAB93EA88FFEACD37465ED843FCC75AA81 -gpu -o keyinfo.txt -stop 1ALice
VanitySearch v1.12
Difficulty: 264104224
Search: 1ALice [Compressed With Public Key]
Start Wed Apr 17 20:03:19 2019
Base Key: 8B456380CE20C7CA2ACA52A6B17EB53B98C789AD8215F09D1D478260492E7DD3
Number of CPU thread: 3
GPU: GPU #0 GeForce GTX 645 (3x192 cores) Grid(24x128)
49.429 MK/s (GPU 45.930 MK/s) (2^26.60) [P 31.92%][50.00% in 00:00:01][0]

File keyinfo.txt:

Code:

Pub Addr: 1ALiceQeUJwFKwGYLvZDMfKC1h9XCshLJ7
PartialPriv: L54zKpetuL8rVVvyWRFJG8PdQs4PaPuvP3Rb7G8SXLBVSjLsMx4m

Alice runs VanitySearch using her first generated private key and the Bob's file to get safely the final private key:

Code:

C:\C++\VanitySearch\x64\Release>VanitySearchCUDA8.exe -rp L4U2Ca2wyo721n7j9nXM9oUWLzCj19nKtLeJuTXZP3AohW9wVgrH keyinfo.txt

Pub Addr: 1ALiceQeUJwFKwGYLvZDMfKC1h9XCshLJ7
Priv (WIF): p2pkh:L1kjZP36qVCcp1eXXJE7CfyuWojc1rCTw8Xs8rNrCxM5imLgm4ro
Priv (HEX): 0xD874F31B0B73ED255865FEB210C181589A860ACDB4C374FB4F685DFE2077797F2

[Jean_Luc]

Hello,

The new release 1.13 is available for download. It supports split-key.

More info in the readme:
https://github.com/JeanLucPons/VanitySearch/blob/master/README.md#generate-a-vanity-address-for-a-third-party-using-split-key-vanity-address

Thanks to test it

[Lolo54]

Hello Jean_Luc

always a good speed for the basic command (identical)
I tried to be as complete as possible for the test

Code:

VanitySearchCUDA10.113.exe -gpu 1Testbtc
VanitySearch v1.13
Difficulty: 51529903411245
Search: 1Testbtc [Compressed]
Start Thu Apr 18 13:11:49 2019
Base Key: DFDABB80A765A04F86AF2D673B7CCDD59DED63D8DECBC52CA9907B2EDA16FE4B
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1321.297 MK/s (GPU 1294.818 MK/s) (2^35.81) [P 0.12%][50.00% in 07:29:15][0]

for new functions

Code:

VanitySearchCUDA10.113.exe -gpu -s "laurent123456" -kp
Priv : KxFuiDGdGLoMKGnVfZ4x4sXLs6GPkp2a7teATCyLV65XKxt65s35
Pub  : 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8

Code:

VanitySearchCUDA10.113.exe -gpu -stop -sp 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8 -o keyinfo.txt 1Laure
VanitySearch v1.13
Difficulty: 264104224
Search: 1Laure [Compressed With Public Key]
Start Thu Apr 18 14:19:08 2019
Base Key: BEBF153068FCE331CCE0CAD96E7A28C257FCFDA27106E406615425D394FD3A5A
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)

go to the keyinfo.txt file the key pair is generated

Code:

Pub Addr: 1LaureDAydQYaq9MCAmdtSMTdVEqwCYGNu
PartialPriv: L3CUQDbWbAAN1nrpC7VtkWUcmGHvfrwqbQXyzX7R4Y85Kt1yM9yw

we can also remove the command -stop so several key pair will be generated just as well and choose the desired one

Code:

VanitySearchCUDA10.113.exe -gpu -sp 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8 -o keyinfo.txt 1Laure
VanitySearch v1.13
Difficulty: 264104224
Search: 1Laure [Compressed With Public Key]
Start Thu Apr 18 14:23:32 2019
Base Key: 69CB978C32F80D552D1974EF9C602DB3AC0429CF69FA6E7449AF467E4A673D2E
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1389.539 MK/s (GPU 1356.604 MK/s) (2^32.96) [P 100.00%][99.00% in 00:00:00][32]

generated keyinfo.txt file

Code:

Pub Addr: 1Laure8jVGTY9PwSmHirbMLiWwTCnfyUTA
PartialPriv: L2Fgvp4tSRbnef3q1xN3tdUKtXL7xV3FLsUhkUaK6rSbvgZeJfJo

Pub Addr: 1LaurecbFFeL1U4WWZ5975ygCimkU5LtDw
PartialPriv: KwrrMpy91Sgxf5bRSapMMDdM28e6xZk3DJD2eWSnG9t8DRagK5cQ

Pub Addr: 1Laureaz3vp1QjQHPgC6gfqYEJC2do5DeU
PartialPriv: L2Fgvp4tSRbnef3q1xN3tdUKtXL7y2C51CjCQEB2CnkmVGPdN6JS

Pub Addr: 1LaurebqudrAdzGoCcdTehayF6YBPecfTy
PartialPriv: L2P4pvzHr1YyGE5y2yZ5BmH8pe4vVtQaGhGUfNcnVt6eaQqtW3ek

Pub Addr: 1LauresDqY9bMsYXYPAjg8or8ZnBkcbbhy
PartialPriv: L2dvi9DnFyRSsgaMPxGfx3KaaR3EkWgXiwGZYtG3RExGDkrWr65J

Pub Addr: 1LaureGCSLrGBp7z3QmZnxxuWUKxUyd87K
PartialPriv: Kz1LpDaW169L9W53UCajYexviSLgCL7vKj5eRvPNrixxeuwWN7LB

Pub Addr: 1Laurecjn2vCiVQJK9hvRdDQactAaSEUT7
PartialPriv: KxHvnxoAer6GZSN4Jd78jEomCCE6rVVTdS8cTVynNjAXL3GSgRqN

Pub Addr: 1LaureZeYBTtN8BN9Kh56dQUyVHV9uthSs
PartialPriv: KyBrP3Acsp6sBiLfyQd7sCbdkHh2LusLF36xE1c4ZXTbJWNxpoHW

Pub Addr: 1LauresFskwLLuJcao1cutuu8F9WjPe1jY
PartialPriv: Kxq44WvEBmSxdX8EH5x4uJZ55Ym47zPtXSuGMgCoRTFdQsk7Upfe

Pub Addr: 1LaureSMMPCUTUcmdMEwqSq5j9NeoGjGdp
PartialPriv: KzQXt3mjoMybfoJbbcUsPaZyLV4jY3kwcAPdViFNHEDZns21YpcD

Pub Addr: 1Laurezhs8jKTkyLLGMBQhawDwbF9MyE2V
PartialPriv: L1Qcgc7EHidrCNTC6jAJvwaFSBgBFc4kzQJqZhr1SoggkFqjCCQD

Pub Addr: 1Laure1ogSdn7BwN2jcoyRDUEhofWTLSCE
PartialPriv: KzmN1fYJZ5rYnLMb7X5Ti6qW4u2FigYhDqp3AXMBDsskwdWjyjnL

Pub Addr: 1LaurecRE9STrJLeuJ6274HJP5LWBMnXLg
PartialPriv: L2Fgvp4tSRbnef3q1xN3tdUKtXL7xUBrWSrM3zgXjvJ3UMZZqriW

Pub Addr: 1LaureJM3Lq3UPUDygkpRSNMX7JFz2mBYC
PartialPriv: L2Fgvp4tSRbnef3q1xN3tdUKtXL7xPLS7RjtBjbwKdMUU2MXbULe

Pub Addr: 1Laure28fPTiqh1hX5V3o4TTTYtRog7aHA
PartialPriv: KzmN1fYJZ5rYnLMb7X5Ti6qW4u2FiSULfRbGctumFBNxwjemVq4D

Pub Addr: 1LaureTvZgrj8WJTEjjLdiVGpRWeEjoVRc
PartialPriv: KzMgFNNrxeSGiPMuEbBfFQNLXysvXzsAdFKKBbVxWoPTDRobNPZd

Pub Addr: 1Laure6kksCGnCksLeKYiLUGnBrKj3gEVS
PartialPriv: L2Fgvp4tSRbnef3q1xN3tdUKtXL7xmkyDQZigZJNyVrhJNG9mVUT

Pub Addr: 1LaureK5uaDeKPBwU3pnLPhwmCzWah8FLm
PartialPriv: L1FGpjDXuontforrEo9nK9L2KCn5bctbPPZpLBG58WpHYsBxEspD

we can also add the -r 10000 or 5000000 command to generate

Code:

C:\Users\Laurent\Documents\Bitcoin\VanitySearchCUDA10.113.exe -gpu -r 1000000 -sp 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8 -o keyinfo.txt 1Laure
VanitySearch v1.13
Difficulty: 264104224
Search: 1Laure [Compressed With Public Key]
Start Thu Apr 18 13:40:54 2019
Base Key: Randomly changed every 1000000 Mkeys
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)
1341.496 MK/s (GPU 1311.409 MK/s) (2^33.65) [P 100.00%][99.00% in 00:00:00][52]

The manipulation works perfectly with the 3 types of addresses in 1Laure in 3AbV1 and with bc1q

Code:

VanitySearchCUDA10.113.exe -gpu -stop -sp 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8 -o keyinfo.txt bc1qlaure
VanitySearch v1.13
Difficulty: 33554432
Search: bc1qlaure [Compressed With Public Key]
Start Thu Apr 18 14:30:55 2019
Base Key: 2D94FBC6143DC091781AE96773F1089260EE575ABE467906BA01AA01EE1931A9
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)

fiLE keyinfo.txt

Code:

Pub Addr: bc1qlaure4pu9nl3rnnec8qmxqc42kcndwhc6gne3q
PartialPriv: L4GjeJDYKNEZzRZw4qEgK1LUG5sHigygFLbcFU3ViwxNJd9Q9dq9

I have this error message at the end to rebuild the final private key using the partial private key

Code:

VanitySearchCUDA10.113.exe -rp KzpaHTHmod39eYQZ7jMwQUNSSZrQeZfEMpPoVXNRETnWg5tejVnR keyinfo.txt
Unable to reconstruct final key from partialkey line 0
 Addr: 1Laure3pgFU6v1EdqT15B9SQ612tTBS4WE
 PartKey: KzpaHTHmod39eYQZ7jMwQUNSSZrQeZfEMpPoVXNRETnWg5tejVnR

otherwise the program is still easy to use, all commands run perfectly except for this moment this little bug in the end or so I did a wrong handling

Code:

VanitySearchCUDA10.113.exe -gpu -s "laurent123456" -kp
Priv : KxFuiDGdGLoMKGnVfZ4x4sXLs6GPkp2a7teATCyLV65XKxt65s35
Pub  : 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8

VanitySearchCUDA10.113.exe -gpu -stop -sp 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8 -o keyinfo.txt 1Laure
VanitySearch v1.13
Difficulty: 264104224
Search: 1Laure [Compressed With Public Key]
Start Thu Apr 18 14:50:31 2019
Base Key: 41C8D10E5CBCB278109D8CFDFD4508AF2D6787F34AF7EE5FD9F5AA243586F5DF
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)

Pub Addr: 1Laure3pgFU6v1EdqT15B9SQ612tTBS4WE
PartialPriv: KzpaHTHmod39eYQZ7jMwQUNSSZrQeZfEMpPoVXNRETnWg5tejVnR

VanitySearchCUDA10.113.exe -rp KzpaHTHmod39eYQZ7jMwQUNSSZrQeZfEMpPoVXNRETnWg5tejVnR keyinfo.txt
Unable to reconstruct final key from partialkey line 0
 Addr: 1Laure3pgFU6v1EdqT15B9SQ612tTBS4WE
 PartKey: KzpaHTHmod39eYQZ7jMwQUNSSZrQeZfEMpPoVXNRETnWg5tejVnR

Why this message " Unable to reconstruct final key from partialkey line 0 "

[Jean_Luc]

Thanks for the test

You didn't reconstruct the final private key with the good key, you have to use the first generated private key (for -rp) which is the one which should be kept secret by the requester of the prefix.

Code:

C:\C++\VanitySearch\x64\Release>VanitySearch.exe -rp KxFuiDGdGLoMKGnVfZ4x4sXLs6GPkp2a7teATCyLV65XKxt65s35 keyinfo.txt

Pub Addr: 1Laure3pgFU6v1EdqT15B9SQ612tTBS4WE
Priv (WIF): p2pkh:L1PqadvjgQJ7XXQZ8c8hf7j8RRu7F7J8Fws1t3Zasd7qiXjwyLwT
Priv (HEX): 0x7C8F3FC0B693F368219BD4F7DCE82C10FEBFA2F9CBB1FD55EF5B68DE24411C6C

[Lolo54]

Effectively

everything works perfectly   

Code:

VanitySearchCUDA10.113.exe -gpu -s "laurent123456" -kp
Priv : KxFuiDGdGLoMKGnVfZ4x4sXLs6GPkp2a7teATCyLV65XKxt65s35
Pub  : 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8

VanitySearchCUDA10.113.exe -gpu -stop -sp 026F6F0A6D845EA109C837976BC06040F4C1DA98881B7E165C9431FE1A7198AAD8 -o keyinfo.txt 1Laure
VanitySearch v1.13
Difficulty: 264104224
Search: 1Laure [Compressed With Public Key]
Start Thu Apr 18 17:31:42 2019
Base Key: 4C4F9EA9EC872852E88364D461C68A8B17B4A49A3556C0B1FD97B341CA64E495
Number of CPU thread: 5
GPU: GPU #0 GeForce RTX 2070 (36x64 cores) Grid(288x128)

VanitySearchCUDA10.113.exe -rp KxFuiDGdGLoMKGnVfZ4x4sXLs6GPkp2a7teATCyLV65XKxt65s35 keyinfo.txt

Pub Addr: 1LaureFDXZ7qs9cWU8PgiZ5fhWHgQJ5eNY
Priv (WIF): p2pkh:KzpFMQA6UcDJCDWDYFpz9LdV4VAFSm8EiQbonHx48s9MEAcB3B7p
Priv (HEX): 0x6B478EFA094CFDD0A1030610C25F223DB4D95C0639634C042A1711B8A6B2C2F2

[gaz1]

why the result is not saved in txt?

[Jean_Luc]

why the result is not saved in txt?

You can use the -o option to save within a file.

[DaveF]

I know a few pages back you said that you needed some help with OpenCL, did you find anyone able to help?
I am sitting on a bunch of older RX470 cards and figure this would be a good way for them to spend their retirement years :-)

If not, no big deal but I can always hope.

Thanks,
Dave

[Jean_Luc]

No, for the moment, nobody has proposed an OpenCL kernel for VanitySearch and I didn't find a good bigint library for OpenCL.
If somebody has some infos, it would be appreciated

[FistBump]

Salut Jean-Luc Smiley

Do you plan to add support for P2SH (segwit starting with 3) adresses anytime soon to your tool? That would be a nice to have.

For instance this project by nullios implemented both P2SH and bech32 addies.

Is this included in your roadmap?

Nice work anyway!

[asche]

Do you plan to add support for P2SH (segwit starting with 3) adresses anytime soon to your tool? That would be a nice to have.

This is already supported in the current version afaik.

It is a first attempt, this is just to allow to run VanitySearch like this (for those who want a private address starting with 3).

Code:

C:\C++\VanitySearch\x64\ReleaseSM30>VanitySearch.exe -stop 3Priv
VanitySearch v1.11
Difficulty: 4553521
Search: 3Priv [Compressed]
Start Tue Apr  2 07:43:52 2019
Base Key:B0A317C56CF0CF3C63E118687C153CD1336F2D5DCE33A3ADB3CE5E4EEA401436
Number of CPU thread: 8

Pub Addr: 3PrivG5uq7hwXLyAHbYkFTnFkzx1FEWQdf
Priv (WIF): p2wpkh-p2sh:L2wAVD273GwAxGuEDHvrCqPfuWg5wWLZWy6H3hjsmhCvNVuCERAQ
Priv (HEX): 0xAA83217B3A11FCCFF8142EF0681AD774D7AB6822F574C4BB99CBF9B9DD01E7F2

Bech32/native segwit supported as well

Hello,

I just published the release 1.11 of VanitySearch:
https://github.com/JeanLucPons/VanitySearch/releases/tag/1.11
- Added support for segwit address P2SH and BECH32
I upload the windows release for CUDA8 asap.

Code:

C:\C++\VanitySearch\x64\Release>VanitySearch.exe -stop bc1queen
VanitySearch v1.11
Difficulty: 1048576
Search: bc1queen [Compressed]
Start Wed Apr  3 08:56:32 2019
Base Key:6F907FDE30067DCDE802739E47C6463FE49C32791242458C2D141212DB107A55
Number of CPU thread: 8

Pub Addr: bc1queenu8kq0vjrl509w88mwefdu4pztkdvlst4at
Priv (WIF): p2wpkh:L24UVC7ZYgYjy4cStQvBHD3quJkeYN3xHYBqFjTYjJjwmht84jsg
Priv (HEX): 0x906F8021CFF9823217FD8C61B839B9BED612AA6D9D065AAF92BE4C79F5251BBA

Thanks for testing

Edit: Now I see you are just another multi account spammer. => https://bitcointalk.org/index.php?topic=5134513
Edit2: You are banned, goodbye.