Well, from the look of things it is obvious that you were being careless with you key phrase. So, don't blame anyone but yourself for this theft. This isn't a case of a wallet being hacked.
So I would suggest that you become more careful with how you handle your key phrase and be mindful of whom you reveal them to.
Anyways, sorry for your loss.
Topic: I was robbed, and the severe setback made me rethink a problem - page 2. (Read 270 times)
Yesterday, my NFT was stolen. The NFT that I spent all my money to buy, the NFT that can give me a bright future, was stolen. This isn't the first time I've been robbed.
So this made me take another look at WEB3. This time the theft was due to the leak of the private key.
Yes, in the blockchain world, private keys are everything. It is the highest authority, and the only thing that can reduce its importance is multisig.
But for ordinary users, multi-signing is a high threshold and difficult to complete. So, is there a tool that can "lock" your wallet?
This "lock" does not review incoming assets, but only reviews assets when they flow out. It can be a secondary password, or a fingerprint verification. This "lock" must follow the address, not a single wallet. As you can imagine, even if the thief logs in to the wallet with the private key from another place, the "lock" existing in the address is still in effect. It may be able to steal your private key, but it cannot steal your secondary password or physical characteristics.
Is this "lock" technically difficult to implement?
Basically only solution that comes into mind is making new kind of protocol, but that is also making the user experience even harder, it would be most likely highly centralized compared to current system, and collecting biometrics or such data would create problems with EU:s privacy rules. Because users would need to have a possibility to opt out afterwards, and with blockchain tech, it would need a whole new structure i guess.So this made me take another look at WEB3. This time the theft was due to the leak of the private key.
Yes, in the blockchain world, private keys are everything. It is the highest authority, and the only thing that can reduce its importance is multisig.
But for ordinary users, multi-signing is a high threshold and difficult to complete. So, is there a tool that can "lock" your wallet?
This "lock" does not review incoming assets, but only reviews assets when they flow out. It can be a secondary password, or a fingerprint verification. This "lock" must follow the address, not a single wallet. As you can imagine, even if the thief logs in to the wallet with the private key from another place, the "lock" existing in the address is still in effect. It may be able to steal your private key, but it cannot steal your secondary password or physical characteristics.
Is this "lock" technically difficult to implement?
Other one would be that the issuer who makes the contract has a possibility to freeze assets and with new kind of tech, even reverse transactions. And that's harder puzzle to solve without going full centralized systems and permissionless transactions and immutability would be thrown out of the window as well. And to be clear, those are the very things that make blockchain tech valuable in the fisrt place.
Private keys can be acquired if your device was infiltrated and you said that this was not your first being robbed it is truly unfortunate but there are not that many technologies to prevent malware from getting into your system yes it could detect some suspicious activities but at the root of it we, ourselves, have to be extra careful and cautious about the links we click, the websites we open or the ads we check out
Though multisig is great, you don't even need to go as far as using multisig.
1. Trezor/Ledger hardware wallet
2. 24-word backup only stored physically(not digitally on your computer/phone)
3. Don't get scammed or phished
That's it. No need for overcomplication.
1. Trezor/Ledger hardware wallet
2. 24-word backup only stored physically(not digitally on your computer/phone)
3. Don't get scammed or phished
That's it. No need for overcomplication.
So this made me take another look at WEB3. This time the theft was due to the leak of the private key.
So possibly that you click some phising links. Theres no way that he can view your private key at all. Most got scammed or hacked exposed to some malicious links. Avoid using social media or click some links underneath legit project cause chances that the second one is fake unless you check the profile first and verify that this is the real one. 
Yesterday, my NFT was stolen. The NFT that I spent all my money to buy, the NFT that can give me a bright future, was stolen. This isn't the first time I've been robbed.
so this is not the first time you have been robbed , I think this is already on you because being robbed for the first time is tolerable but when this happened again then you should understand what is the problem with your security mate.
try not to be confident enough in everything you entered mate and specially in your crypto holdings that you must be securing and
may be taken from you if not making what you must act on.
I want to say that neglect of safety always leads to such cases, unfortunately. It seems to me that everyone stumbled on this, and many, of course, at the beginning of their journey, but even now many experienced ones are losing their money. So you should always take additional protective measures.
So this made me take another look at WEB3. This time the theft was due to the leak of the private key...
The problem is you, I know similar cases and it is also collected a lot in some tech sharing groups, when the market price increases, users join a large number of outright attackers. can take advantage of your ignorance of connection to take over your usage rights. I have seen them share more than 50,000 wallet addresses of the victim daily. However, some services are currently upgrading to protect users more with warnings when participating in the web3 space, be careful not to connect to services with potentially suspicious behavior, as well as the important thing is the "key" that only you know.
Yesterday, my NFT was stolen. The NFT that I spent all my money to buy, the NFT that can give me a bright future, was stolen. This isn't the first time I've been robbed.
So this made me take another look at WEB3. This time the theft was due to the leak of the private key.
Yes, in the blockchain world, private keys are everything. It is the highest authority, and the only thing that can reduce its importance is multisig.
But for ordinary users, multi-signing is a high threshold and difficult to complete. So, is there a tool that can "lock" your wallet?
This "lock" does not review incoming assets, but only reviews assets when they flow out. It can be a secondary password, or a fingerprint verification. This "lock" must follow the address, not a single wallet. As you can imagine, even if the thief logs in to the wallet with the private key from another place, the "lock" existing in the address is still in effect. It may be able to steal your private key, but it cannot steal your secondary password or physical characteristics.
Is this "lock" technically difficult to implement?
So this made me take another look at WEB3. This time the theft was due to the leak of the private key.
Yes, in the blockchain world, private keys are everything. It is the highest authority, and the only thing that can reduce its importance is multisig.
But for ordinary users, multi-signing is a high threshold and difficult to complete. So, is there a tool that can "lock" your wallet?
This "lock" does not review incoming assets, but only reviews assets when they flow out. It can be a secondary password, or a fingerprint verification. This "lock" must follow the address, not a single wallet. As you can imagine, even if the thief logs in to the wallet with the private key from another place, the "lock" existing in the address is still in effect. It may be able to steal your private key, but it cannot steal your secondary password or physical characteristics.
Is this "lock" technically difficult to implement?
Jump to: