Єгор Попович, CTO @Tesseract, (Lviv, Ukraine) "Blockchain user: myth or reality?"

2. BLOCKCHAIN USER
M Y T H O R R E A L I T Y ?

3. BLOCKCHAIN USER
M Y T H O R R E A L I T Y ?
OVERVIEW

4. DOWNLOADING
DESKTOP CLIENT...

5. DOWNLOADING
DESKTOP CLIENT...

6. DOWNLOADING
DESKTOP CLIENT...
!
SUDDENLY…
You’ve just installed the wrong software!

7. AWESOME!
( nope… )"
"

8. OK, CLICKED
“SEE ALL VERSIONS”

9. OK, CLICKED
“SEE ALL VERSIONS”

10. WARNINGS
FROM APPLE

11. WARNINGS
FROM APPLE

12. GOOD, IT WORKS!

13. GOOD, IT WORKS!

14. HMM. I WONDER WHY?..

15. FIRST
TRANSACTION!

16. FIRST
TRANSACTION!" N"PE

17. HELLO, COINBASE

18. HELLO, COINBASE

20. #SUCCESS!
Finally! Got registered in Ethereum Web3 DApp.
$

21. AWESOME!
( yes! )%
%

22. BROKEN DAPPS IN MIST

23. &
Top 3 gaming DApps on StateOfTheDapps
can’t work in the official client.
BROKEN DAPPS IN MIST
•CryptoKitties (some Segment related exception)
•Etheremon (sync calls to APIs)
•My Crypto Heroes (Mist bug with personal_sync)

24. AWESOME!
( nope… )"
"

25. OK, IT WAS PRETTY EASY...

26. OK, IT WAS PRETTY EASY...
•Download problems (hell-hard-to-find
links, unsigned binary).
•Slightly over-using space on the hard
drive (~100 GB).
•Non-native interface (ugly).
•Gas usage for registration /
transactions (how did I know to buy it?).
•ETH purchasing hassle.
•Broken DApps.

27. OK, IT WAS PRETTY EASY...
•Download problems (hell-hard-to-find links, unsigned binary)
•Slightly over-using space on the hard drive (~100 GB)
•Non-native interface (ugly)
•Gas usage for registration/transactions (how did I know to buy it?)
•ETH purchasing hassle
•Broken DApps
ALTERNATIVES ON THE WEB

28. ALTERNATIVES ON THE WEBMETAMASK

29. METAMASK

30. SOLVED PROBLEMS

31. PARTIALLYSOLVED PROBLEMS
•Download problem - simply
install browser plugin.
•Space usage - uses public
nodes.
•Interface - browser plugin
is ok to look non-native.

32. PARTIALLY
•ETH purchase hassle - will
forward you to Coinbase.
•DApps bugs - DApps work
better in browsers.
SOLVED PROBLEMS

33. UNSOLVED PROBLEMS
All write transactions use Ethereum.
You can’t use DApps without it.

34. GOOD NEWS!
THERE IS MORE NOW.

35. GOOD NEWS!
THERE IS MORE NOW.
•Security concerns (private keys stored in JS engine with web access)
•App will need own public nodes, or it will be slow
•Only Web based DApps

36. NATIVE APPS

37. Do you use web version of Skype or Slack on your Desktop?
How often do you use mobile web version of Facebook or Instagram?
NATIVE APPS

38. WHAT PROBLEMS DEVELOPERS
HAVE IN NATIVE APPS?

39. WHAT PROBLEMS DEVELOPERS
HAVE IN NATIVE APPS?
•Dependency on full network node
(Geth, Parity…). This leads to space
usage problem.
•If we don’t want to depend on network
node, we need own Wallet
implementation inside apps (with
secure storage) and own public nodes.
Security problem + implementation time
+ Audit of non-smart-contract code.
•Stable SDKs for native platforms
(for key generation and storage,
blockchain network access).

40. HOW IT AFFECTS OUR USERS?

41. •Applications with official wallets
(Geth, Parity, etc.) will use huge
amounts of hard disk space. But
will allow to reuse private key.
•For each application with own
wallet we need new private key
(for security reasons). It’s a hell to
manage them, and we will loose
funds on transfers between them
•Non-stable SDKs leads to bugs /
crashes.
HOW IT AFFECTS OUR USERS?

42. POTENTIAL SOLUTIONS

43. •“Blockchain-native” platforms
•Hardware Wallets
•Open Wallet Protocol
POTENTIAL SOLUTIONS

44. “BLOCKCHAIN” NATIVE
PLATFORMS.

45. “BLOCKCHAIN” NATIVE
PLATFORMS.
Mobile: Desktop:
•Sirin
•Labs
•Status
•“Blockchain” Linux distros

46. HARDWARE WALLETS

47. HARDWARE WALLETS
• Secure key storage
• Can be used with public or light nodes
Pros
• Don’t have standard
• Costs
• Not common
Cons

48. HARDWARE WALLETS
•Pros
• Secure key storage
• Can be used with public or light nodes
•Cons
• Don’t have standard
• Costs
• Not common
OPEN WALLET PROTOCOL

49. •Wallets can be secure and audited.
•Wallet can be shared between apps. Keys can be stored at one place.
•Can be implemented by Hardware Wallets, or Wallet application can
expose Hardware Wallets via protocol.
•Can work on existing mobile platforms (iOS and Android).
•Can be a standard, which will lead to stable and tested native SDKs.
•Can be used with native or Web DApps.
OPEN WALLET PROTOCOL
•Wallet application, which works like hardware wallet.
BEST ONE

50. WALLETS CAN DO MORE!

51. WALLETS CAN DO MORE!
•Payments for non-blockchain Apps
•Authentication (as a replacement for OAuth, OpenID, BankID, …)
•More to come…

52. WALLETS CAN DO MORE!
•Payments for non-blockchain Apps
•Authentication (as a replacement for OAuth, OpenID, BankID, …)
•More to come…
THANK YOU!

53. This talk was not about problems,
it was about opportunities.
THANK YOU! '