You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/documentation/act.md
+43-9Lines changed: 43 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -277,17 +277,51 @@ You can choose which `History Reference` to share depending on which set of publ
277
277
278
278
## Download With ACT
279
279
280
-
:::
281
-
🚧 Under Construction 🚧
282
-
ACT download with bee-js is not currently functioning, however you can still download directly using a curl command for the Bee API and the corresponding headers.
283
-
:::
284
280
285
-
Below are curl commands for downloading the file we uploaded with ACT. Each command is for the same file, but uploaded using a different grantees list. Therefore if we try downloading the file from the node with the public key of `03636056d1e08f100c5acaf14d10070102de9444c97b2e8215305ab3e97254ede6`, it will only work with the second command, since that one was uploaded using the grantees list which contained the public key, while the first one was uploaded using a list that does not contain it:
281
+
In order to download using ACT, we must pass in the public key from the grantee list creator along with the file reference and history reference returned from the file upload operation:
Content: This is a sample string that will be uploaded securely using ACT. 01.
325
+
```
326
+
327
+
In the example above, we used the history reference from the file uploaded using the grantees list with only one public key included (`027d0c4759f689ea3dd3eb79222870671c492cb99f3fade275bcbf0ea39cd0ef6e`), and so it will only be able to be retrieved and decrypted by the node with that public key.
0 commit comments