Have you sent your crypto to the wrong address, in error? We often get asked for help to reverse erroneous transactions back to the original wallet.
This is a common misconception that, like traditional banks, we can control the network and authorise reverse charges.
By design the Ethereum network is immutable, meaning transactions cannot be reversed by the sender or the platform itself. This feature is one of the core components for both Bitcoin & Ethereum and all other decentralized networks. This means that no wallet provider can reverse confirmed transactions for you (unless you have sent it to their own company wallet), because they don't control the network.
The only option for you to recover your funds is to find and convince the owner of the address itself to return the funds.
Here are a couple of things that might help you find this person/company:
1. Start with the origins of the address. How did you get this address you have send it to? Start by backtracking your actions on that day, and try to remember which apps / projects / people you interacted with to get this wallet address. It is recommended to copy/paste or QR scan the addresses where you want to send crypto and double check before sending.
2. If the address looks like its owned by a person, and you know them, ask politely by explaining the error. If the address is owned by a company, for example an exchange or an ICO, contact their official support.
Only the ETH address is public information, so it would be impossible to track someone only based on that. This is another one of the core features of blockchain - anonymity. Even we as the wallet provider cannot approach the counterparty on your behalf.
For the transaction to be initiated from your wallet, you would have to had inserted the recipients ETH wallet address in the send request. Otherwise no transaction would have occurred at all. It is statistically unlikely for you to hit an actual wallet address with random numbers, so please think where you have copied the address from.
Comments
0 comments
Please sign in to leave a comment.