- OpenEthereum
- Setup OpenEthereum
- Beginner Introduction
- Frequently Asked Questions
- Usage and Config
- Technical Documentation
- Pluggable Consensus
- Aura - Authority Round
- Proof-of-Authority Chains
- Demo PoA-Tutorial
- Private Development Chain
- Transaction Queue
- Warp Sync (par)
- Warp Sync Snapshot Format
- Code flow
- Secret Store
- Permissioning
- WebAssembly (Deprecated)
- JSON RPC API
文章来源于网络收集而来,版权归原创者所有,如有侵权请及时联系!
Secret Store Tutorial Overview
In this tutorial, we will learn step by step how to setup a Secret Store with 3 nodes and use it for a simple use case:
Alice has a confidential document stored locally on her hard-drive. She will encrypt it and store the encryption key in a secure way. Later on, Alice will share this encrypted document with Bob making sure that he is the only one able to decrypt it.
To keep things simple we will work on a Private development chain but the Secret Store nodes are meant to be connected to and synchronize any blockchain (Private or Public).
The overall picture of this tutorial is the following:
- 3 Secret Store nodes (each with an account)
- 3 regular user accounts (Alice, Bob and Charlie)
- Each entity on this picture is running a node on the same blockchain. Interactions with the blockchain are not represented on this diagram.
- The nodes part of the secret store are connected with each other using a secure connection (blue lines).
- The Secret Store node 1 (SS1) exposes an HTTP API that Alice, Bob and Charlie can use to generate, store or retrieve encryption keys (orange lines).
- Alice will send an encrypted document to Bob per email (gray line).
- Charlie should not be able to decrypt the document.
Table of contents:
- Part 1 - Configuring each node
- Part 2 - Document encryption
- Part 3 - Key retrieval
- Part 4 - Introducing permissioning
Part 1 - Configuring each node → |
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论