Private Modules

[maximousblk]

Private modules

Because of the nature of arweave, we cannot "hide" the data. The option left is encrypting the data. furthermore we can push the data to arweave in multiple pieces making it harder to put together the encrypted data.

Publishing

• User sets private: true in config while creation
• User runs nest publish <version>
• Nest CLI uploads the tarball
• Backend encrypts the tarball contents
• Backend uploads the encrypted tarball contents to arweave

Using

• Set DENO_AUTH_TOKENS to <api_key>@nest.land (nest switch would handle this env var)
• User runs deno cache/deno run
• Deno sends a GET request with the active account's access token using Authorization: bearer <api_key> header
• Backend fetches the requested file from arweave and decrypts it
• Backend returns the unencrypted file to Deno
• Deno caches the fetched file.

Notes

• private modules probably will also be accessible using an ?auth=<token> query to access from the browser.
• ?auth=<token> takes precedence over the Authorization header.

[maximousblk]

relevant deno issue: denoland/deno#5239

[maximousblk]

Updated to comply with denoland/deno#9508