| README.mdView |
|---|
| 31 | 31 … | - Each receives a [`secret_invite`](./schemas/invite.json) that references the rootId |
| 32 | 32 … | |
| 33 | 33 … | _Therefore_ |
| 34 | 34 … | - Abaddon is not restricted to just sharding his SSB key, he can shard anything he likes. |
| 35 | | -- Abaddon can still send out more invitations if he likes. |
| 35 … | +- Abaddon can send out more invitations. |
| 36 | 36 … | |
| 37 | 37 … | All of Abaddon's different secret sharing `root` events can be summoned using: |
| 38 | 38 … | |
| 39 | 39 … | ```javascript |
| 40 | | -api.secrets.root.get() |
| 41 | | -api.secrets.root.stream(callback) |
| 40 … | +api.secrets.root.get(callback) |
| 41 … | +api.secrets.root.stream() |
| 42 | 42 … | ``` |
| 43 | 43 … | |
| 44 | 44 … | Invites can be viewed through the API and a FlumeView... something along the lines of: |
| 45 | 45 … | |
| 46 | 46 … | ``` |
| 47 | | -api.secrets.invites.get(rootId) |
| 48 | | -api.secrets.invites.stream(rootId, callback) |
| 47 … | +api.secrets.invites.get(rootId, callback) |
| 48 … | +api.secrets.invites.stream(rootId) |
| 49 | 49 … | ``` |
| 50 | 50 … | |
| 51 | 51 … | ### 2. Responses |
| 52 | 52 … | |
| 57 | 57 … | - A response writes a [`secret_response`](./schemas/response.json) that indicates whether they accepted the invite or not |
| 58 | 58 … | - References the rootId so can be easily filtered through the API / a FlumeView |
| 59 | 59 … | |
| 60 | 60 … | ``` |
| 61 | | -api.secrets.responses.get(rootId) |
| 62 | | -api.secrets.responses.stream(rootId, callback) |
| 61 … | +api.secrets.responses.get(rootId, callback) |
| 62 … | +api.secrets.responses.stream(rootId) |
| 63 | 63 … | ``` |
| 64 | 64 … | |
| 65 | 65 … | ### 3. Trustees |
| 66 | 66 … | |
| 88 | 88 … | - If Abaddon enabled it, those within that group of final cosigners can now see who eachother are. |
| 89 | 89 … | - Immediately triggers the [Secrets event](#4-secrets) |
| 90 | 90 … | |
| 91 | 91 … | ``` |
| 92 | | -api.secrets.trustees.get(rootId) |
| 93 | | -api.secrets.trustees.stream(rootId, callback) |
| 92 … | +api.secrets.trustees.get(rootId, callback) |
| 93 … | +api.secrets.trustees.stream(rootId) |
| 94 | 94 … | ``` |
| 95 | 95 … | |
| 96 | 96 … | **Questions** |
| 97 | 97 … | * Does having a secretive or non-secretive sharding require two different types of event? Or is it just a boolean flag? Needs clarification as it depends how the data is scuttled... |
| 102 | 102 … | **What does this do?** |
| 103 | 103 … | - Each trustee receives a shard of Abaddon's soul. |
| 104 | 104 … | |
| 105 | 105 … | ``` |
| 106 | | -api.secrets.pieces.get(rootId) |
| 107 | | -api.secrets.pieces.stream(rootId, callback) |
| 106 … | +api.secrets.pieces.get(rootId, callback) |
| 107 … | +api.secrets.pieces.stream(rootId) |
| 108 | 108 … | ``` |
| 109 | 109 … | |
| 110 | | -// Needs more thought... Should the trustees know the rootId? Do they need to? |
| 110 … | +// Needs more thought... Should the trustees know the root? Do they need to? |
| 111 | 111 … | |
| 112 | 112 … | |
| 113 | 113 … | ## Note: |
| 114 | 114 … | - `secret_invite` and `secret_response` looks a lot like Patchbay's `ssb-chess`: `chess_invite` and `chess_accept`. |