Silk Road forums

Support => Customer support => Topic started by: DtownsFinest on August 28, 2013, 05:12 am

Title: Archived Address used please help with info to proceed
Post by: DtownsFinest on August 28, 2013, 05:12 am
Got this message from SR

    You have recently used an archived Bitcoin address (1xxxxxxxxxxxxxxvxxxxx) to deposit x amount of BTC to your account. This address could be retired at any time. It is strongly advised that you use a new bitcoin address for future deposits.

Best regards,
Silk Road staff


So does this mean i need to spend up what coin is in there now, or i should i transfer my remaining balance to another addy or i can i just request a new one. I just dont want anything to go wrong and i loose my btc or something crazy like that. Anyone with info that could hold my hand thru this process i would appreciate it thanks
Title: Re: Archived Address used please help with info to proceed
Post by: samesamebutdifferent on August 28, 2013, 05:30 am
Please refer to the sticky thread at the top of this board titled "DELAY WITH BITCOIN DEPOSITS"

The issue you are experiencing is being discussed there:

http://dkn255hz262ypmii.onion/index.php?topic=207692.msg1497313#new
Title: Re: Archived Address used please help with info to proceed
Post by: DtownsFinest on August 28, 2013, 05:52 am
thank you i think i can figure out what i need from here, although i was not experiencing a delay with my coins being funded into my account so i did not know to look at that sticky. Titled delay with bitcoin deposits because that was not a problem for me, i had never changed my deposit addy because i didnt want to change something that was working i always just wanted to fund to my account and proceed without a problem so i didnt try to fix what wasnt broken. Anyway thank you im sure ill get a better understanding by reading thru this thread'
Title: Re: Archived Address used please help with info to proceed
Post by: samesamebutdifferent on August 28, 2013, 06:35 am
Yeah when I stickied that thread last night it was an apparent delay issue, I see logging in today it has morphed into something else with the delay only being part of the problem..

Hope you got what you needed anyway.