Bitcoin Forum
November 10, 2024, 01:28:15 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 [4]  All
  Print  
Author Topic: What can be done to stop loss sending to wrong bitcoin address  (Read 610 times)
Zeke_23
Sr. Member
****
Offline Offline

Activity: 868
Merit: 333



View Profile
December 15, 2019, 10:14:51 AM
 #61

I think you cannot undone or cancel it when you already have sent a bitcoin to the wrong bitcoin address, that is why there are a lot of incidents in the past years that they submitted their bitcoin in a wrong address. It is also the reason why mobile crypto wallets started to create QR codes to avoid submitting a bitcoin and altcoin to the wrong address.

To satisfy the issue, rather than sending bitcoin to address even in QR or copy and pasting the wallet address. If we already sent an amount to that particular address then we should take into consideration that looking on the transaction history and making a transaction will be more secure on it rather than inputting the address again and scanning the QR. In other ways, the developers should also consider making a payment profile to easily send bitcoin to particular address with just one click without risking on some clipboard scams and hacking.
You mean to have a history once we have done with our transaction, and if we ever gonna send another transaction to the same address, there won't be the need for us to copy and paste the same address but to browse the history and create another transaction? You can already do that since we always have a transaction history in our wallet, but the thing is you just have to manually find the same address where you can find it more convenient if you just copy and paste again.

AMEPAY
▄▄█████████▄▄
▄█████████████████▄
▄█████████████████████▄
▄█████████▀▀▄▀▀█████████▄

▄██████▄▄█▀ ▀█▄▄██████▄
███████  ▀▀█▄██▀▀▄███████
███████ █ ▄ █ ▄▀▀▄███████
████████ █ █ █ ▄▀▀▄████████
▀█████████▄█ █ ▄██████████▀
▀████████  ▀▀▀  ████████▀
▀█████████████████████▀
▀██
███████████████▀
▀▀█████████▀▀
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
│▌
AME TRADE HERE
▄██████▄ ▀██████▄
█████████  ▀█████
███████▀     ▀███
██████▀  ▄█▄  ▀██
██████▄  ▀█▀  ▄██
███████▄     ▄███
█████████  ▄█████
▀██████▀ ▄██████▀
AME TRADE HERE
   ▐███▄
   ████▌
▐██████████▄
████████████
 ████▌  █████
▐████  ▄████
██████████▀
 ▀█████▀▀
▐│
▄▄█████████▄▄
▄█████████████████▄
▄█████████████████████▄
▄█████████▀▀▄▀▀█████████▄

▄██████▄▄█▀ ▀█▄▄██████▄
███████  ▀▀█▄██▀▀▄███████
███████ █ ▄ █ ▄▀▀▄███████
████████ █ █ █ ▄▀▀▄████████
▀█████████▄█ █ ▄██████████▀
▀████████  ▀▀▀  ████████▀
▀█████████████████████▀
▀██
███████████████▀
▀▀█████████▀▀
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
AicecreaME
Sr. Member
****
Offline Offline

Activity: 2450
Merit: 455


OrangeFren.com


View Profile
December 15, 2019, 04:41:43 PM
 #62

A 2 way check system can be this way,
I- Mr A about to send Bitcoin to Mr B using protocol safe
II- Mr B opens a allow protocol safe using either senders address or generates an option notifying incoming bitcoin to his wallet and amount
III- Mr A Sends bitcoin to Mr B
III- Mr A protocol checks to see if Mr B's protocol is expecting and if Yes, [Suspicious link removed]ives Mr B, if not bitcoin goes back to Mr A.

Lets say the copy and paste malware attacked and changed address while Mr A paste to the system then btc will be returned and no harm.

I may have missed something however, it's not clear how this could help.
Clearly Mr B will not spend time checking if money is about to come and allow it, it would be a huge overload for shops, for example.
So an automation will have to be done in a way or another. And this makes all that workflow useless.

But, for the sake of discussion, let's say the automation is not done.
What stops the sender be careless twice when sending out the money?

I agree, that is too hassle, and a lot of work just for someone to make sure his bitcoin is safe. We don't need this kind of thing as a precaution to prevent losing our bitcoins, we should discipline ourselves to be responsible for everything and we have to be sure that when we are making a move or having a transaction, we have to be accurate and focus to avoid accidentally sending it to the wrong bitcoin address, double checking as always will help, actually.

████████████████████                                                    OrangeFren.com                                                ████████████████████
instant KYC-free exchange comparison
████████████████████     Clearnet and onion available #kycfree + (prepaid Visa & Mastercard)     ████████████████████
Aikidoka
Sr. Member
****
Offline Offline

Activity: 1078
Merit: 342


Sinbad Mixer: Mix Your BTC Quickly


View Profile
December 15, 2019, 04:55:37 PM
 #63

most of the ways that users could send to a wrong address involve having a malware on their computer, in which case these users are also susceptible to a lot of different attacks and can lose their money in much easier ways than simply sending to a wrong unintended address. your solution is also not going to solve anything, the same malware can intercept the communication between A and B and change the address to its own.

other ways that involve user typing in a wrong address are already protected by the checksum that each address has in place which means they won't be able to pay to a wrong address because of typos.
I fully agree with what you said, I mean, if you get hacked or you got a malware on your PC, you may lose your bitcoin funds. There's a lot of ways, like for example when you would like to send some bitcoin to an address, the address will change automatically without even noticing it, otherwise even if you type your address wrong and was a typo you'll be safe because the system only send bitcoin to only valid addresses.

I've seen once someone sends me few bitcoin but then he was able to cancel it before the first verification, which it's one of the ways you could do if you send your bitcoin to a wrong address, but I don't know how he did that exactly.
Pages: « 1 2 3 [4]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!