vojfox

It's a similar situation on iOS, where new developers sometimes use (in Objective-C) `[[NSDate date] timeIntervalSince1970]` which is natural, but wrong. NSDate draws from the network synchronized clock and will occasionally hiccup when re-synching it against the network, among other reasons.

If you're looking at measuring relative timing (for example for games or animation), you should instead use `double currentTime = CACurrentMediaTime();` That's the correct way.

How can this/these be exploited?

math score: 243 In just 10 seconds http://mental-math-trainer.com

i know the guy who made this game for iOS

https://itunes.apple.com/us/app/brain-tuner-free/id391266485...

https://itunes.apple.com/us/app/brain-tuner-x/id287360582?mt...

Kraken (https://www.kraken.com) - San Francisco - Full Time

We're looking for software engineers and developers! Help build the most professional Bitcoin exchange.

• iOS, backend, frontend and full-stack engineers

Join Kraken and enjoy the first truly professional trading platform for Bitcoin and other math-based currencies (cryptocurrencies). We have robust technology, rock-solid security, and a proactive approach to regulatory compliance.

Here's an interview with our CEO Jesse Powell and General Counsel Constance Choi: https://www.youtube.com/watch?v=qQmOTtMVav4

Please get in touch! To apply, email [email protected]

This is related to how Bitcoin gambling sites can be made to be provably fair.

I wonder how practical it would be to take Bitcoin Core and gradually reduce its # of (non-blank) lines.

its, not it's.

I would agree with you, except for tree chains. Tree chains could eliminate scalability issues: http://letstalkbitcoin.com/ltb104-tree-chains-with-peter-tod...

Hold your own keys yourself, possibly with the addition of multi-sig service(s) to make this safer and more convenient. That is undoubtedly the long-term vision of bitcoin, and it's quite different from banks/USD.