Accidently send BTC to USDT address | Bitcointalksearch.org

TryNinja

legendary

Activity: 2758

Merit: 6830

Quote from: Elemco.in on March 17, 2018, 08:10:53 AM

Even if they have the private key, how can they reverse such a transaction?

They can't reverse a transaction. But if they have the private-key, they can use it to send the USDT back to you (a completely new transaction).

So, two transactions will happen there:

1. You sent the USDT to them.
2. They sent the USDT back to you.

Elemco.in

newbie

Activity: 37

Merit: 0

Even if they have the private key, how can they reverse such a transaction?

AdolfinWolf

legendary

Activity: 1946

Merit: 1427

Quote from: Xynerise on March 13, 2018, 02:59:45 PM

Quote from: balotelli on March 13, 2018, 12:52:36 PM

Me too
i sent usdt to btc wallet in binance exchange
and binance support said
"Your transaction has been confirmed in the block chain already. Which means that Binance has transferred coins in the block chain successfully.

If your still has issue on the transaction. It is suggested to negotiate to the owner of designation address or target wallet kindly. Sorry, Binance has no way to help you at this moment."
I lost all money Sad

. Very sad,

I guess that's the boilerplate response they give everyone.
If the address you sent it to was given to you by Binance then they actually hold the private key to that address and can retrieve the coins IF they wish to.
Whether they choose to help you or not however is up to them.

No, it seems that in this case he sent USDT from binance to a BTC adress he chose. Binance can actually do nothing in that case.

Where did you send the USDT to balotelli?

Quote from: u-partner on March 05, 2018, 11:29:56 PM

Hi!

Unfortunately, There is no chance to get back a transaction! Embarrassed

BTC Wallets no have any admins.

You obviously don't understand how exchanges work. Ofcourse they have access to the private keys of their clients.

Xynerise

sr. member

Activity: 322

Merit: 363

39twH4PSYgDSzU7sLnRoDfthR6gWYrrPoD

Quote from: balotelli on March 13, 2018, 12:52:36 PM

Me too
i sent usdt to btc wallet in binance exchange
and binance support said
"Your transaction has been confirmed in the block chain already. Which means that Binance has transferred coins in the block chain successfully.

If your still has issue on the transaction. It is suggested to negotiate to the owner of designation address or target wallet kindly. Sorry, Binance has no way to help you at this moment."
I lost all money Sad

. Very sad,

I guess that's the boilerplate response they give everyone.
If the address you sent it to was given to you by Binance then they actually hold the private key to that address and can retrieve the coins IF they wish to.
Whether they choose to help you or not however is up to them.

balotelli

full member

Activity: 317

Merit: 104

Why Always Me,.

Me too
i sent usdt to btc wallet in binance exchange
and binance support said
"Your transaction has been confirmed in the block chain already. Which means that Binance has transferred coins in the block chain successfully.

If your still has issue on the transaction. It is suggested to negotiate to the owner of designation address or target wallet kindly. Sorry, Binance has no way to help you at this moment."
I lost all money Sad

. Very sad,

btccrusher

member

Activity: 742

Merit: 12

There is a 50/50 chance to recover it. I'm guessing the amount is fair enough to get support from cryptopia team. As far I know, cryptopia's new rules are much priority to its users and they are promised to resolve such problems under certain conditions. Let's hope the postive thing. Good luck.

drm

legendary

Activity: 1176

Merit: 1005

Quote from: askarisyed on January 16, 2018, 09:53:03 AM

Dear members,

On 15.01.17. In a moment of carelessness, I made a transaction of bitcoins (BTC) from my coinbase account to USDT address in Cryptopia. I realized my mistake but it was too late and the transaction cleared with 6+ confirmations in a couple of hours.

Transaction ID: 27ddeac780978f24d49b493cc9b6b819a6d819e2d9c406fd5f1673246da814f7
Output address: 1DJheE2EGZsyXRG8SfeTtivSgbezL34bGB

the address I sent my bitcoins to is: 1EqkMgZaR8vaPQJ1gHjbNY75Cp9k7i1L6T

I checked with transaction hash and transaction ID and it shows my BTC balance.

I am new here to cryptocurrencies and invested all money from credit.

Is there someone who can help me out here?

I heard one way to do it is to find the private key and export this key to another wallet.

1. How to I find the private key of my Cryptopia USDT wallet (where I transferred BTC)

I have contacted both supports but still no reply....is my hope lost?

Wait for a reply, cryptopia can get you your money back.
They deal with this more often.

u-partner

newbie

Activity: 19

Merit: 0

Hi!

Unfortunately, There is no chance to get back a transaction! Embarrassed

BTC Wallets no have any admins.

BenOnceAgain

member

Activity: 208

Merit: 84

🌐 www.btric.org 🌐

Quote from: Xynerise on March 05, 2018, 03:36:40 PM

Quote from: BenOnceAgain on March 05, 2018, 01:32:20 PM

Hey while I'm thinking of it, I had a question about the prefix on a bech32 address that wasn't apparent when I read the BIP. Does the prefix have to exactly match, i.e. "bc1" or "tb1", for example? Would either of these prefixes pass muster: "bc1xyzabc1" or "xyzabc1bc1"? If so, which one is the proper one if you were to include additional human-readable information in the prefix?

If anyone knows the answer to that, I'd appreciate it. Otherwise, I'll check out the code.

Best regards,
Ben

Yes, it does.
For segwit implementation in Btcoin, the hrp is "bc" for mainnet, and "tb" for testnet.
Then the separator is 1.

However for other implementations of Bech32 not related to bitcoin, you can use any 1 to 83 US-ASCII characters, with each character having a value in the range [33-126]

If you want to play around with Bech32 addresses, check out Nullius' segwit vanity address generator

Thank you very much for your response. Yes, I had reviewed the BIP and I was thrown off by one of the examples of invalid addresses:

Code:

separatoran84characterslonghumanreadablepartthatcontainsthenumber1andtheexcludedcharactersbio1569pvx: overall max length exceeded

I see now in the spec it states that if there's multiple separator "1" characters, the last one is considered the separator. But for Bitcoin the addresses will begin with "bc" pre-separator. If I'm reading the spec correctly, I think in the above example, besides the HRP length being exceeded, the data area must also be missing, as the "569pvx" is the checksum.

I am very impressed with the considerations that went into this address specification. I've worked with DOD projects (IUID/UID) that did not take into account all of the real-world factors that have been addressed in this BIP.

I am going to clone Nullius' code and mess around with it.

Thanks again!

Ben

Xynerise

sr. member

Activity: 322

Merit: 363

39twH4PSYgDSzU7sLnRoDfthR6gWYrrPoD

Quote from: BenOnceAgain on March 05, 2018, 01:32:20 PM

Hey while I'm thinking of it, I had a question about the prefix on a bech32 address that wasn't apparent when I read the BIP. Does the prefix have to exactly match, i.e. "bc1" or "tb1", for example? Would either of these prefixes pass muster: "bc1xyzabc1" or "xyzabc1bc1"? If so, which one is the proper one if you were to include additional human-readable information in the prefix?

If anyone knows the answer to that, I'd appreciate it. Otherwise, I'll check out the code.

Best regards,
Ben

Yes, it does.
For segwit implementation in Btcoin, the hrp is "bc" for mainnet, and "tb" for testnet.
Then the separator is 1.

However for other implementations of Bech32 not related to bitcoin, you can use any 1 to 83 US-ASCII characters, with each character having a value in the range [33-126]

If you want to play around with Bech32 addresses, check out Nullius' segwit vanity address generator

BenOnceAgain

member

Activity: 208

Merit: 84

🌐 www.btric.org 🌐

Quote from: DannyHamilton on January 17, 2018, 07:13:57 AM

Quote from: BenOnceAgain on January 16, 2018, 10:44:02 PM

Bech32 cannot come fast enough. We need addresses that can be easily distinguished from one another and will be rejected if you enter the wrong address for a given currency.

Too many coins all using the same address namespace is just an added layer to the adoption challenge.

Unfortunately, bech32 does not fix the problem of lazy developers. When people create altcoins, they can (and will) just use the same addresses for their altcoins as bitcoin uses. The problem will still exist.

As far as I'm concerned, lazy developers that overlap their address space with Bitcoin are demonstrating a lack of concern about the funds that will eventually be conveyed on their blockchain. But you're right, they'll do the absolute minimum. (sed -i 's/Bitcoin/Shitcoin/g' *)

Hey while I'm thinking of it, I had a question about the prefix on a bech32 address that wasn't apparent when I read the BIP. Does the prefix have to exactly match, i.e. "bc1" or "tb1", for example? Would either of these prefixes pass muster: "bc1xyzabc1" or "xyzabc1bc1"? If so, which one is the proper one if you were to include additional human-readable information in the prefix?

If anyone knows the answer to that, I'd appreciate it. Otherwise, I'll check out the code.

Best regards,
Ben

evgeshti

member

Activity: 161

Merit: 10

If you sent bitcoin to another address, whether it's the address of bitcoin or yusdt, I think the issue of solving this problem is closed and you lost your money. at the time of sending, almost all the services issue a message that if the funds are sent to the wrong address, they will be lost and can not be recovered(((((

loopes

sr. member

Activity: 952

Merit: 323

Quote from: TryNinja on January 16, 2018, 10:17:33 AM

Quote from: askarisyed on January 16, 2018, 09:53:03 AM

Due to an influx of tickets of this nature having a significant impact on our support capacity as we continue to grow and scale to meet demand, Cryptopia is now implementing a 10% recovery fee on support tickets involving recovery of deposits made to Cryptopia where a required PaymentId/Message/etc are not correctly included in the transaction.

Keep in mind that they are literally the only ones that can help you. If they don't answer your support ticket or deny your request, your BTC is gone.

Quick edit: oops... Swapped BTC with USDT. Thx DannyHamilton

Fortunately he sent btc to usdt, if he send to other currency he will loss his money for his carelessness. There is an option to swap from btc to usdt in cryptopia when someone has been wrong to sent btc to usdt address.

HCP

legendary

Activity: 2086

Merit: 4361

Quote from: HighCommander on February 11, 2018, 05:48:43 PM

....Well that's not smart system design, imo.

No, it wasn't... but it was a deliberate move on behalf of the Bitcoin Cash developers. They were trying to become "THE" Bitcoin... so they left everything the same as Bitcoin except for the consensus rules around blocksize... and, thankfully, at the last minute... added in the 2-way replay protection.

Personally, I believe it was more of a political move than anything... but that's just my opinion.

Quote

I mean I am not saying this should work this way or that way, I am seeing there's an issue and there were instances in the past when people had same issue and it seems like there needs to be an improvement to the system.

Personally, I don't think the system needs to be improved... but that users need to be better educated and take more responsibility for their actions. A system like Bitcoin that has no "undo" functionality can be very unforgiving.

Everyone was always quick to hype "Be Your Own Bank" as a mantra for the financial freedom being promoted by Bitcoin... However, they conveniently ignored the fact that this should actually have said "Be Your Own Bank, and your own Security Department, and your own Risk and Analysis Department, and your own IT Department" etc.

People are very quick to blame "The System"™ for their own carelessness and mistakes. Take the time to double (or triple check) what you are doing before you press the "send" or "confirm" button.

thorexs

newbie

Activity: 266

Merit: 0

i think you have to wait technical support reply,its the best thing to do,

HighCommander

member

Activity: 65

Merit: 14

Read and comprehend. Evaluate and take action.

Quote from: HCP on February 10, 2018, 06:03:25 PM

Which would require that different blockchains didn't use the same address formats... like BitcoinCash using identical address format to Bitcoin. In cases like that, it is IMPOSSIBLE for a software wallet to determine if the address is BitcoinCash or Bitcoin.

Also, I'm not sure how you think this idea will help? Huh

For instance, for any given Bitcoin address, there is a "matching" BitcoinCash address. If I accidentally sent some Bitcoin to a BCH address, the transaction will be successful, regardless of whether or not anyone can actually access the private key for that address.

Huh. Didn't know that. Well that's not smart system design, imo. Okay, detecting right away based on the address isn't an option. I have a book about bitcoin internals but haven't read it yet, hence I don't know such details.

Quote from: HCP on February 10, 2018, 06:03:25 PM

The small transaction confirms... the 99.99% transaction then gets sent anyway. All this idea would do is A. create more transactions (which we really don't need)... and B. cost users more in fees.

However, if BitcoinCash used an unique address format, then if one were to attempt to send BTC to BCH, it would fail as the address would be rejected.

I agree, small transaction confirms isn't ideal at all. A bunch of extra transactions, fees(I hate fees, here comes again - bad design, imo). But hey, we are dealing with money here. If protocol is designed the way that one sends X amount and accidentally messes up the recipients address in the process and sends it, then what? Oh well, too bad it's your fault or your system's fault your money is gone, sorry you're stupid, come again. Let's face it, how do most people usually input addresses to which they send coins to, they copy and paste them, and just to "be safe" they check first 3-4 chars and last 3-4 chars so they match and then click send. Am I right? I mean I am not saying this should work this way or that way, I am seeing there's an issue and there were instances in the past when people had same issue and it seems like there needs to be an improvement to the system.

HCP

legendary

Activity: 2086

Merit: 4361

Quote from: HighCommander on February 10, 2018, 03:57:26 PM

Personally, I think it would be smart to program wallets so that software would auto detect if you are sending it to proper address, to catch such a mistake before it becomes fatal.

Which would require that different blockchains didn't use the same address formats... like BitcoinCash using identical address format to Bitcoin. In cases like that, it is IMPOSSIBLE for a software wallet to determine if the address is BitcoinCash or Bitcoin.

It would also require that other currencies stop "piggybacking" on other networks... like the way that USDT does (via Omni).

Quote

To take it a step further, a system would send smallest amount possible to that address and if transaction is successful, send the rest 99.99%.

Also, I'm not sure how you think this idea will help? Huh

For instance, for any given Bitcoin address, there is a "matching" BitcoinCash address. If I accidentally sent some Bitcoin to a BCH address, the transaction will be successful, regardless of whether or not anyone can actually access the private key for that address.

The small transaction confirms... the 99.99% transaction then gets sent anyway. All this idea would do is A. create more transactions (which we really don't need)... and B. cost users more in fees.

However, if BitcoinCash used an unique address format, then if one were to attempt to send BTC to BCH, it would fail as the address would be rejected.

HighCommander

member

Activity: 65

Merit: 14

Read and comprehend. Evaluate and take action.

Seems like there was already a response on Cryptopia forums with a link for a recovery process - https://www.cryptopia.co.nz/Forum/Thread/6507

Hopefully their support will be able to resolve this.

Personally, I think it would be smart to program wallets so that software would auto detect if you are sending it to proper address, to catch such a mistake before it becomes fatal. To take it a step further, a system would send smallest amount possible to that address and if transaction is successful, send the rest 99.99%.

Quote from: Madeon on February 10, 2018, 03:39:22 PM

How many BTC did you send? Sad

OP included transaction ID:

Quote from: askarisyed

Transaction ID: 27ddeac780978f24d49b493cc9b6b819a6d819e2d9c406fd5f1673246da814f7
Output address: 1DJheE2EGZsyXRG8SfeTtivSgbezL34bGB

the address I sent my bitcoins to is: 1EqkMgZaR8vaPQJ1gHjbNY75Cp9k7i1L6T

https://blockchain.info/address/1DJheE2EGZsyXRG8SfeTtivSgbezL34bGB

Amount is showing 0.7543611

Madeon

newbie

Activity: 48

Merit: 0

How many BTC did you send? Sad

TheBasta24

newbie

Activity: 47

Merit: 0

You’re lucky if they give ur money back, most of exchanges just keep them

Topic: Accidently send BTC to USDT address (Read 619 times)