357 karma · joined December 28, 2017
None of the current implementations can scale, so even their utility is questionable. There is a way to make a scalable trust-less digital currency by using a mutable leder, but none of the current coins that I know of are heading that way. The main difficulty will be how to distribute ledger space in a way that cannot be monopolized by the richest. That is a simple technical problem to solve though, because storage capacity will eventually surpass the ratio of richest to average wealth. Then you can allocate ledger space in exchange for an affordable deposit, redeemable when the balance is emptied.
Really?
https://play.google.com/intl/en_us/about/developer-distribut...
> (4.5) Alternative Stores. You may not use Google Play to distribute or make available any Product which has a purpose that facilitates the distribution of software applications and games for use on Android devices outside of Google Play.
You have no chance of bootstrapping an alternative store outside of Google Play. Sideloading APKs is not how users get software on Android. Amazon failed hard with their attempt, and they pumped tons of money into it by paying developers to give away their apps for free; that, and they shipped hardware that has their store preloaded. Still didn't even make a dent.
No. As long as at least one person is brute forcing hashes, transactions will be processed at the same rate of about 10 tx/s.
What? Why would you want to do that beyond covering expenses for scam prevention?
To see why that toy example is insufficient, consider that you could simply execute the load directly without putting an exception in front of it and you would be able to read the value.
CryTek was on the verge of bankruptcy a year ago when they were unable to pay their employees. The one-time payment from Amazon in exchange for the engine distribution rights is probably running out.
https://www.reddit.com/r/gamedev/comments/7l640w/crytek_has_...
https://www.reddit.com/r/gamedev/comments/5wzlf2/crytek_empl...
http://www.eurogamer.net/articles/2016-12-20-crytek-breaks-s...
Differentiable functions
> Sounds like servers handling lots of small UDP packets would be hit pretty hard.
That's sadly not enough.
There are also potential speculation-based side-channels that are unrelated to cache: timing the idiv operation whose latency "depends on number of significant bits in absolute value of dividend." Furthermore there are many ways to measure contention on the execution ports which can leak information about the speculative execution.
Even if speculative loads do not modify the cache, you could still have a side channel by analyzing the memory bus contention.
IMO there is no way to get rid of these timing attacks entirely without getting rid of SMT and speculation.
From the abstract:
> Information leakage through covert channels and side channels is becoming a serious problem, especially when these are enhanced by modern processor architecture features. We show how processor architecture features such as simultaneous multithreading, control speculation and shared caches can inadvertently accelerate such covert channels or enable new covert channels and side channels.