|
|
|
|
|
by michaelmrose
2214 days ago
|
|
1. How do you stop a person who can legally read a book, and thus has the key needed to decrypt it in memory, from obtaining that key and using it to create an unencumbered copy on their hard drive without totally depriving them of ownership of their computer to provide a controlled environment where such copying is impossible? 2. I remember a substantial issue with Etherium wherein someone was able to steal a large amount of currency from other users in 2016. What are the risks of an attacker say stealing a large number of tokens intended to be sold to users from distributor or even the ability to create them? In a decentralized world how do you invalidate them? If you can invalidate them doesn't that mean any seller can take back anything? This can happen now of course they can steal a copy of your pre production movie but potential to monetize is garbage and effect on your legitimate value proposition may be largely unchanged. In this brave new world their stolen tokens may actually have a legitimate market. Steal 1 million tokens sell all 5 days after release as already read for 10% less than going rate before owner bans tokens from legitimate market. 3. What about the case in which someone breaks into your computer or infects it with malware and effectively loots all your books and music and sells it on craigslist/amazon/facebook. How do you invalidate those purchases without a secondary authority. If you can haven't you recreated central distribution with more steps? |
|
2. True, there is always smart contract risk. The DAO hack happened right after Ethereum was founded as nobody really knew what they were doing and tooling was extremely basic. Things are still in the early dial up days for crypto but even now tooling is vastly better, there are dedicated firms for contract/code auditing and the systems being created today are much more robustly designed. With that said, nothing can be certified 100% safe and the only concrete proof of security we have is the passing of time itself. These systems will be new for a while and adoption of this tech will happen slowly over time in the same way the internet grew over two decades into what we know today. There will likely be a system that withstands the test of time and becomes old enough to be trusted by even conservative developers, but until then there will likely be mechanisms built-in where the content creator can destroy and re-create tokens in case of failure. Not every token will be this way and the decision is up to the content creator themselves.
3. This is a problem for wallets in general and lots of people are working on it. The leading solution seems to be social recovery which is where you designate trusted addresses (family members, hardware wallets, friends etc) and configure it to allow your wallet to be recovered if say 3 of the 5 agree that you legitimately lost it. If you ever lose your wallet because you forgot the password or your computer/phone died then you can recover it easily and safely, no complicated and technically hard key backup systems needed which is key for normal non-HN people. You can also set outgoing filters so your ERC-721 tokens couldn't be sent unless it's to a whitelisted address or you verify it with another of your trusted addresses, so even if a hacker got into your wallet they couldn't transfer the tokens and you would just recover your wallet using the system above. It's still early days but Argent is the best example of this.