Pages:
Author

Topic: Electronic devices that can detect wrong wallet - page 2. (Read 357 times)

legendary
Activity: 2268
Merit: 18509
I don't know how this happened, but it did happen.
You can read how it happened in this post on that thread: https://bitcointalksearch.org/topic/m.54860249

It was a bug in Atomic wallet where it extracted the pubkeyhash from the doge address which was pasted in and then generated a corresponding bitcoin address using that pubkeyhash. The user in question ended up sending bitcoin to this mistakenly generated bitcoin address, and not to the original dogecoin address he pasted in, which as I said would not be possible as the network would reject such a transaction.
legendary
Activity: 1680
Merit: 1853
#SWGT CERTIK Audited
I remember that there was a software bug in the Atomic wallet, where a member of the forum wanted to send Bitcoin using Atomic Wallet, but he put a Dogecoin address instead of a Bitcoin address, An error message was supposed to appear showing that this is an invalid address, but that did not happen and the member did not notice the error, and the amount BTC was actually sent to the Dogecoin address.
This is not possible. You cannot send bitcoin to a dogecoin address. The network will not accept such an invalid transaction. Perhaps he had accidentally generated a bitcoin address from a private key in his dogecoin wallet?
I don't know how this happened, but it did happen. You can read the original thread on the forum here:
[RESOLVED] Atomic wallet. Bitcoin sent to a Dogecoin address...

The member did lose his bitcoin and the wallet compensated 50% of his loss as I remember, because it was a mistake with the wallet and his fault because he put an invalid address.
legendary
Activity: 2268
Merit: 18509
during sending someone Bitcoin with wrong and address it happens to bounce without confirmation.
If you try to send bitcoin to an invalid address, either your wallet software will return an error or the transaction will be rejected by the first node you try to broadcast it to and will never reach the network. You can only send bitcoin to valid addresses, which will receive a confirmation at some point (barring rare cases when the mempool is too full). Your proposed software has no way of knowing whether the bitcoin address you have entered is valid and correct or valid but incorrect. You just have to manually double check.

I remember that there was a software bug in the Atomic wallet, where a member of the forum wanted to send Bitcoin using Atomic Wallet, but he put a Dogecoin address instead of a Bitcoin address, An error message was supposed to appear showing that this is an invalid address, but that did not happen and the member did not notice the error, and the amount BTC was actually sent to the Dogecoin address.
This is not possible. You cannot send bitcoin to a dogecoin address. The network will not accept such an invalid transaction. Perhaps he had accidentally generated a bitcoin address from a private key in his dogecoin wallet?

funds won't be bounced if you send to the wrong address format eg bitcoin to ethereum address
Again, not possible. This transaction would be invalid.
hero member
Activity: 2002
Merit: 633
Your keys, your responsibility
I have seen from the suggestions above that it's possible to build such application that will detect when transactions of Bitcoin occur by using a wrong wallet address. But if someone work on such technology won't it actualize it and mostly building an application when you apply during sending someone Bitcoin with wrong and address it happens to bounce without confirmation. Can't such application won't be build if apply wisdom and time.

As a rule, transactions can't be reversed after you actually click "send", funds won't be bounced if you send to the wrong address format eg bitcoin to ethereum address even if you use the most advanced software. I also don't know if for example this kind of missent prevention app can intervene in other apps like disabling the send button if your input address isn't valid.
legendary
Activity: 1680
Merit: 1853
#SWGT CERTIK Audited
Most wallets have the ability to detect an invalid bitcoin address and give you a warning that there is an error in the address, but the other case is if you enter a valid but wrong address this case can only be detected by manual checking.

I remember that there was a software bug in the Atomic wallet, where a member of the forum wanted to send Bitcoin using Atomic Wallet, but he put a Dogecoin address instead of a Bitcoin address, An error message was supposed to appear showing that this is an invalid address, but that did not happen and the member did not notice the error, and the amount BTC was actually sent to the Dogecoin address.
the Bitcoin was lost as a result of this sending to an invalid address, it was The bug was reported and the wallet team fixed the bug and compensated the member for the lost bitcoins.

The application you want to create can be useful in preventing such cases.
full member
Activity: 490
Merit: 151
I have seen from the suggestions above that it's possible to build such application that will detect when transactions of Bitcoin occur by using a wrong wallet address. But if someone work on such technology won't it actualize it and mostly building an application when you apply during sending someone Bitcoin with wrong and address it happens to bounce without confirmation. Can't such application won't be build if apply wisdom and time.
legendary
Activity: 2828
Merit: 6108
Jambler.io
Yeah, the TXID should show that it's there, or that it's not if there really was some issue. If both sides are being honest here, it's possible the transaction is just stuck because it was sent with too low of a transaction fee.

Impossible, OP started the topic on February the 9th, claiming the transaction deal was around one week old
On February 5th we had a bunch of blocks from 775142 to 775160 that were not full and confirmed even the lowest transactions at 1sat/kb so if it was sent a week go (February 2nd)  it's impossible for it to not have been already confirmed for four days prior to OP opening the topic.
Also:
Quote
not seeing the coin and not even showing a sign of coin is on process
So probably his friend checked the mempool and saw there are unconfirmed deposits to his address at all.


legendary
Activity: 2268
Merit: 18509
If both sides are being honest here, it's possible the transaction is just stuck because it was sent with too low of a transaction fee. Sending another transaction with a higher-than-normal fee should fix that right up.
That's not great advice.

If the original sender simply uses their wallet software to make another transaction with a higher fee, then chances are that software will create an entirely separate transaction which has nothing to do with the first. And so when the mempool empties out, there will be two separate confirmed transactions both sending the same amount of bitcoin to the recipient, and the original sender will be out of pocket.

If you want to bump the fee of an existing transaction, then you either need to use a wallet which supports RBF to specifically replace the existing transaction, or you need to specifically spend one of the unconfirmed child outputs in a new CPFP transaction.
full member
Activity: 130
Merit: 150
Yeah, the TXID should show that it's there, or that it's not if there really was some issue. If both sides are being honest here, it's possible the transaction is just stuck because it was sent with too low of a transaction fee. Sending another transaction with a higher-than-normal fee should fix that right up. Just in case this is the issue, here's a guide on that: https://coingate.com/blog/post/btc-mempool-stuck.
legendary
Activity: 2828
Merit: 6108
Jambler.io
somebody sent Bitcoin to Bitcoin address given and since a week the person insist of not seeing the coin and not even showing a sign of coin is on process and he complained to me.

It's easy, have him give you the tx id!
I have a feeling this might be either a case of scamming or somebody had his computer infected with some clipboard malware.
Every transaction that is valid will appear in the blockchain, if he sent coins to somebody it will show where those coins went!

That aside, there is not possible to build a program that will automatically detect if the address you want to send coins to is the address your friend sent you via telegram or email, or any kind of new address generated by your exchange, in order to make sure you only send coins to selected addresses you will first have to insert them in that program's database so it will know them, which brings us to the address book NotATether mentioned.
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
When you say wrong wallet device, do you mean wrong address, but one that is still a valid BTC address or?

I think OP is referring to "an address where was bitcoin was sent to accidentally instead of the correct address" so not necessarily a device. Hardware is not necessary for this at all.

Well, you could add the address to your address book and give it a label if you use it frequently. Now if only wallet software had a feature to block sending transactions to addresses which are not in your address book, then if you combined it with some double-checking of the address, should prevent you from sending coins to any wrong address.
hero member
Activity: 1764
Merit: 694
[Nope]No hype delivers more than hope
Could you please be more specific on what "wrong wallet device" means? Do you mean detect a device that is possibly infected with a virus(es), thereby giving addresses that doesn't actually belong to you? Just install an antivirus.

Regarding your issue, the tx explorers such as mempool.space should be transparent enough to track bitcoin tx, unless you are sending bitcoins internally on a centralized service to your clients.
member
Activity: 124
Merit: 11
I want to ask if it's possible to create a device that detect wrong wallet device, i dont know such device or bot app is already existing, somebody sent Bitcoin to Bitcoin address given and since a week the person insist of not seeing the coin and not even showing a sign of coin is on process and he complained to me. Having such device that  notice Bitcoin addresses will help bitcoiners.

When you say wrong wallet device, do you mean wrong address, but one that is still a valid BTC address or?
legendary
Activity: 3500
Merit: 6205
Looking for campaign manager? Contact icopress!
I want to ask if it's possible to create a device that detect wrong wallet device, i dont know such device or bot app is already existing, somebody sent Bitcoin to Bitcoin address given and since a week the person insist of not seeing the coin and not even showing a sign of coin is on process and he complained to me. Having such device that  notice Bitcoin addresses will help bitcoiners.

Bitcoin addresses do contain a checksum and the proper wallets do check it before allowing you send coins to an address.
This being said I'm not sure what would achieve such a device as you propose.

You can have a clipboard virus and send to a different (but valid!) address than his.
He can have a clipboard virus and tell you a different (but valid!) address than where he expects the coins.
You may have been sending from a scam platform that doesn't process withdrawals/payments.
He may have the wallet on a scam platform or one with bugs that ignored the incoming money and didn't fund the account.
(there may be many more cases that didn't come to my mind right now)

Would the device you propose fix this? No.
Would the device you propose do more than what a proper wallet already does? No.

And then..?
full member
Activity: 490
Merit: 151
I want to ask if it's possible to create a device that detect wrong wallet address, i dont know such device or bot app is already existing, somebody sent Bitcoin to Bitcoin address given and since a week the person insist of not seeing the coin and not even showing a sign of coin is on process and he complained to me. Having such device that  notice Bitcoin addresses will help bitcoiners.

It's a mistake and it has being corrected to wrong Bitcoin address.
Pages:
Jump to: