2.9BTC for number 1

2.6BTC for number 1

2.4BTC for number 1

WARNING!

I just had an email from a fake newb Kialara ` account attempting to get me to deposit my bid amount in a BTC address.

BEWARE SCAMMER

Also 1.8BTC bid on serial number five

2.1BTC bid for #1

I'm at work now but will provide some proof and/or send you the funding amount as you asked. I'll be home before any auctions close

I will be throwing in a bonus to sweeten the deal!

A Coinographic Silver Plated 1 LTC coin. I am at work now but will update later with some pictures of this coin.

Hi all 

I'm looking to sell a rare fully funded 25LTC Coinographic "Bull" coin. It really is beautiful. Originally 500 of these were to be made / sold but in the end very few were ever sold due to bad management by Coinographic forcing the company to go under. Many of the coins that were sold were funded.

I have a very rare fully funded coin still with original seal intact and in as new condition.

Coin's wallet as shown in pictures below
https://block-explorer.com/address/LeXkkJyc7y47ZWZ8Cu3Zq79Zhpyu9nXLXS

PICTURES HERE
http://imgur.com/a/PZbWH

I'd like to sell the coin for 3BTC or best offer if this is not met in a reasonable amount of time (I may also auction the coin if no offer here is acceptable).

The coin will be shipped worldwide from the UK.

Shipping costs will be added to the winning bid after the auction (shipping options negotiable). Buyer agrees to not hold myself liable if the coin is lost/stolen/damaged while in transit. Insured mail is more secure than Standard priority so I would suggest that. Choose your level of risk appetite.

Only Bitcoin accepted.

Any questions feel free to ask

After alot of googling and some trial and error I figured out the problem.

BTC-E provide you an unpadded key basically. Some apps will deal with this others won't.

In my gauth app I had to pad out the key to make it dividable by 8. This was done in my case by adding one extra "=" to the end of the key they provided. Thats the accepted padding for BASE32. You can add any amount of extra "=" to make the total key length dividable by 8.

So there you are, hope this helps someone out! If it did and you are in a generous mood please consider a small donation for my efforts!

1EQMmUirpFwvQdooD7qR6u9sxRhSgR6cVk

After alot of googling and some trial and error I figured out the problem.

BTC-E provide you an unpadded key basically. Some apps will deal with this others won't.

In my gauth app I had to pad out the key to make it dividable by 8. This was done in my case by adding one extra "=" to the end of the key they provided. Thats the accepted padding for BASE32. You can add any amount of extra "=" to make the total key length dividable by 8.

So there you are, hope this helps someone out! If it did and you are in a generous mood please consider a small donation for my efforts!

1EQMmUirpFwvQdooD7qR6u9sxRhSgR6cVk

As per the subject title I can't get 2 factor up and running on my BTC-E account.

For clarity I'm familiar with how 2 factor works and have it setup on my Bitstamp account and several other websites.

My problem is that 1) I don't have the ability to scan QR codes so I always just manually enter the private key (np usually but...), 2) the private key on BTC-E is bizarrely longer than 16 characters / they give a private key and a BASE32 private key. Both the keys they provide are longer than 16 characters and neither produce a 6 digit code when entered into my gauth app.

I've googled and read up a bit on gauth codes but can't find any mention of keys ever being longer than 16 characters. I've tried mailing BTC-E but they replied with a generic "how to setup 2 factor response".

Anyone have this issue with BTC-E? Is there a way to use the long private keys they provide? Thanks for any help!

As per the subject title I can't get 2 factor up and running on my BTC-E account.

For clarity I'm familiar with how 2 factor works and have it setup on my Bitstamp account and several other websites.

My problem is that 1) I don't have the ability to scan QR codes so I always just manually enter the private key (np usually but...), 2) the private key on BTC-E is bizarrely longer than 16 characters / they give a private key and a BASE32 private key. Both the keys they provide are longer than 16 characters and neither produce a 6 digit code when entered into my gauth app.

I've googled and read up a bit on gauth codes but can't find any mention of keys ever being longer than 16 characters. I've tried mailing BTC-E but they replied with a generic "how to setup 2 factor response".

Anyone have this issue with BTC-E? Is there a way to use the long private keys they provide? Thanks for any help!

mojo-mantis-22

Nice site

AnAnarchist

Thanks for the awesome promo!

AnAnarchist

Thanks for the promo

1J13uy2yXcPkXEp2Qwc44Y3Be1quZbRdm9

AnAnarchist

AnAnarchist

Ice-Dice.com is awesome!

AnAnarchist


Daily offer thanks

AnAnarchist


Daily offer thanks