ardrive-cli
Advanced tools
The ArDrive Command Line Interface (CLI is a Node.js application for terminal-based ArDrive workflows. It also offers utility operations for securely interacting with Arweave wallets and inspecting various Arweave blockchain conditions.
The ArDrive Command Line Interface (CLI) is a Node.js application for terminal-based ArDrive workflows. It also offers utility operations for securely interacting with Arweave wallets and inspecting various Arweave blockchain conditions.
Create your first drive and permanently store your first file on the permaweb with a series of simple CLI commands like so:
ardrive create-drive --wallet-file /path/to/my/wallet.json --drive-name "Teenage Love Poetry"
{
"created": [
{
"type": "drive",
"metadataTxId": "giv2R8Xj0bbe6l5taBTQJk_38zwIrMH_g1-knSCisjU",
"entityId": "898687ea-b678-4f86-b4e7-49560b190356"
},
{
"type": "folder",
"metadataTxId": "VljnttwUxRStnVuPYakF9e2whjhYJVWB0nSxD5dVyJ8",
"entityId": "f0c58c11-430c-4383-8e54-4d864cc7e927"
}
],
"tips": [],
"fees": {
"giv2R8Xj0bbe6l5taBTQJk_38zwIrMH_g1-knSCisjU": 1415103,
"VljnttwUxRStnVuPYakF9e2whjhYJVWB0nSxD5dVyJ8": 1391904
}
}
ardrive upload-file --wallet-file /path/to/my/wallet.json --parent-folder-id "f0c58c11-430c-4383-8e54-4d864cc7e927" --local-file-path ./helloworld.txt --dest-file-name "ode_to_ardrive.txt"
{
"created": [
{
"type": "file",
"metadataTxId": "EvE06MmE9IKeUzFMnxSgY1M5tJX4uHU64-n8Pf_lZfU",
"dataTxId": "tSMcfvAQu_tKLUkdvRRbqdX93oAf3h6c9eJsSj8mXL4",
"entityId": "bd2ce978-6ede-4b0d-8f79-2d7bc235a0e0"
}
],
"tips": [
{
"txId": "FidEhcZtmDtvQxWrnVJlKnj_ZkwxYXvn7wjbUpasRKo",
"recipient": {
"address": "i325n3L2UvgcavEM8UnFfY0OWBiyf2RrbNsLStPI73o"
},
"winston": "10000000"
}
],
"fees": {
"tSMcfvAQu_tKLUkdvRRbqdX93oAf3h6c9eJsSj8mXL4": 1384601,
"EvE06MmE9IKeUzFMnxSgY1M5tJX4uHU64-n8Pf_lZfU": 1447752,
"FidEhcZtmDtvQxWrnVJlKnj_ZkwxYXvn7wjbUpasRKo": 1379016
}
}
This project is in a state of active development. Use at your own risk!
ArDrive is a permanent storage platform whose applications and core libraries offer hierarchical organization, privacy via complete end-to-end encryption, flexibility, extensibility, and access control over your most valuable data, all made possible by its innovative core technology, the Arweave File System (ArFS) Protocol.
ArFS is a data modeling, storage, and retrieval protocol designed to emulate common file system operations and to provide aspects of mutability to your data hierarchy on Arweave's otherwise permanent, immutable data storage blockweave.
Data uploaded via the ArDrive CLI, once indexed by Arweave's Gateways and sufficiently seeded across enough nodes on the network, can be accessed via all other ArDrive applications including the ArDrive Web application at https://app.ardrive.io.
All transactions successfully executed by ArDrive can always be inspected in the Viewblock blockchain explorer.
This tool is intended for use by:
For deeper integrations with the ArDrive platform, consider using the ArDrive Core (Node) library's configurable and intuitive class interfaces directly within your application.
CLI users and developers must both follow these steps to get the application and/or developer environment up and running:
Both the ArDrive CLI and ArDrive Core JS use Yarn 2 to manage dependencies and initiate workflows, so follow the yarn installation instructions in order to get the latest version. In most cases:
# Brew (OSX):
brew install yarn
# Or with NPM (all supported platforms):
npm install -g yarn
We use husky 6.x to manage the git commit hooks that help to improve the quality of our commits. Please run:
yarn husky install
to enable git hooks for your local checkout. Without doing so, you risk committing non-compliant code to the repository.
This repository uses the Node Version Manager (NVM) and an .nvmrc file to lock the Node version to the current version used by ardrive-core-js.
Note for Windows: We recommend using WSL for setting up NVM on Windows using the instructions described here
Follow these steps to get NVM up and running on your system:
nvm installnvm useTo test a with a custom version of the ardrive-core-js library on your local system, change the "ardrive-core-js" line in package.json to the root of your local ardrive-core-js repo:
- "ardrive-core-js": "1.0.0"
+ "ardrive-core-js": "../ardrive-core-js/"
npm install -g ardrive-cli
# then invoke the CLI from anywhere on your system:
ardrive
Now that your runtime and/or development environment is set up, to install the package simply run:
yarn && yarn build
And then start the CLI (always from the root of this repository):
yarn ardrive
For convenience in the non-developer case, you can install the CLI globally on your system by performing the following step:
yarn pack
# then using the path generated by yarn from the step above:
npm install i -g /path/to/package.tgz
# then invoke the CLI from anywhere on your system:
ardrive
To ensure your environment is compatible, we also recommend the following VSCode extensions:
Number of files in a bulk upload: Theoretically unlimited
Max individual file size: 2GB (Node.js limitation)
Max ANS-104 bundled transaction size: Not yet implemented. 2GB per bundle. App will handle creating multiple bundles.
Max ANS-104 data item counts per bundled transaction: Not yet implemented. Also not adequately specified, though a very large number of data items per bundle is associated with increased rates of GQL indexing failure.
Learn to use any command:
ardrive --help
Browsing of ArDrive public data is possible without the need for an Arweave wallet. However, for all write operations, or read operations without encryption/decryption keys, you'll need a wallet.
As you utilize the CLI, you can use either your wallet file or your seed phrase interchangeably. Consider the security implications of each approach for your particular use case carefully. If at any time you'd like to generate a new wallet altogether, start by generating a new seed phase. And if you'd like to use that seed phrase in the form of a wallet file, or if you'd like to recover an existing wallet via its seed phrase, use either or both of the following commands:
# Generate seed-phrase
ardrive generate-seedphrase
"this is an example twelve word seed phrase that you could use"
# Generate/recover wallet file (with example output file path)
ardrive generate-wallet -s "this is an example twelve word seed phrase that you could use" > /path/to/wallet/file.json
Public attributes of Arweave wallets can be retrieved via their 43-character Arweave wallet address. You can retrieve the wallet address associated with your wallet file or 12-word seed phrase (e.g. wallets generated by ArConnect) like so:
# Wallet file
ardrive get-address -w /path/to/wallet/file.json
# Seed Phrase (with sample output)
ardrive get-address -s "this is an example twelve word seed phrase that you could use"
HTTn8F92tR32N8wuo-NIDkjmqPknrbl10JWo5MZ9x2k
You'll need AR in your wallet for any write operations you perform in ArDrive. You can always check your wallet balance (in both AR and Winston units) by performing:
# Getting the balance for your own wallet
ardrive get-balance -w /path/to/wallet/file.json
# Getting the balance for ANY wallet (with sample output)
ardrive get-balance -a "HTTn8F92tR32N8wuo-NIDkjmqPknrbl10JWo5MZ9x2k"
1500000000000 Winston
1.5 AR
If, at any time, you need to send AR out of your wallet to another wallet address, you may perform:
# Using our previously generated wallet as the destination...
ardrive send-ar -w /path/to/wallet/file.json --dest-address "HTTn8F92tR32N8wuo-NIDkjmqPknrbl10JWo5MZ9x2k" --ar-amount 2.12345
ArDrive's ArFS integration provides for hierarchical organization of your file and folder data on Arweave.
The fundamental entity types specified by ArFS are:
Each instance of these entities have a Version 4 UUID entity ID that is commonly referred to by its entity type, i.e. drive ID, folder ID, and file ID.
When you execute write functions with the CLI, the JSON output will contain information about the Arweave Transaction IDs that were registered when writing your entities to the blockweave, any miner rewards or ArDrive Community tips that were disbursed from your wallet, and any new entity IDs and, when applicable, encryption keys that were generated in the process of creating the entities. Typically, you'll want to keep track of those and get proficient with retrieving them in order to build your drive hierarchy to your liking. See Understanding Drive and File Keys for more info.
An important feature of the ArDrive CLI is the --dry-run flag. On each command that would write an ArFS entity, there is the option to run it as a "dry run". This will run all of the steps and print the outputs of a regular ArFS write, but will skip sending the actual transaction:
ardrive <my-command> <other-options> --dry-run
This can be very useful for gathering price estimations or to confirm that you've copy-pasted your entity IDs correctly before committing to an upload.
At the root of every data tree is a "Drive" entity. When a drive is created, a Root Folder is also created for it. The entity IDs for both are generated and returned when you create a new drive:
# Use `tee` to keep a receipt of the full set of transactions info and `jq` to focus on the data of interest
ardrive create-drive --wallet-file /path/to/my/wallet.json --drive-name "Teenage Love Poetry" |
tee created_drive.json |
jq '[.created[] | del(.metadataTxId)]'
[
{
"type": "drive",
"entityId": "6939b9e0-cc98-42cb-bae0-5888eca78885"
}
{
"type": "folder",
"entityId": "d1535126-fded-4990-809f-83a06f2a1118"
}
]
The relationship between the drive and its root folder is clearly visible when retrieving the drive's info:
ardrive drive-info -d "6939b9e0-cc98-42cb-bae0-5888eca78885"
| jq '{driveId, rootFolderId}'
{
"driveId": "6939b9e0-cc98-42cb-bae0-5888eca78885",
"rootFolderId": "d1535126-fded-4990-809f-83a06f2a1118"
}
All file and folder entities in the drive will be anchored to it by a "Drive-ID" GQL Tag. And they'll each be anchored to a parent folder ID, tracked via the "Parent-Folder-ID" GQL tag, forming a tree structure whose base terminates at the Root Folder.
Private Drives achieve privacy via end-to-end encryption facilitated by hash-derived "Keys". Drive Keys encrypt/decrypt Drive and Folder data, and File Keys encrypt/decrypt File Data.
The relationships among your data and their keys is as follows:
When you create private entities, the returned JSON data from the ArDrive CLI will contain the keys needed to decrypt the encrypted representation of your entity that is now securely and permanently stored on the blockweave.
To derive the drive key again for a drive, perform the following:
# Will throw an error if the wallet or password specified can't be used to decrypt the on-chain drive
ardrive get-drive-key -w /path/to/my/wallet.json -d "6939b9e0-cc98-42cb-bae0-5888eca78885" -P
To derive the file key again for a file, perform the following:
# Will throw an error if the drive key or drive-key-derivation data specified can't be used to decrypt the on-chain file
ardrive get-file-key --file-id "bd2ce978-6ede-4b0d-8f79-2d7bc235a0e0" --drive-id "6939b9e0-cc98-42cb-bae0-5888eca78885" --drive-key "yHdCjpCK3EcuhQcKNx2d/NN5ReEjoKfZVqKunlCnPEo"
The ArDrive CLI's private drive and folder functions all require either a drive password OR a drive key. Private file functions require either the drive password or the file key. Keys and passwords are sensitive data, so manage the entry, display, storage, and transmission of them very carefully.
Drive passwords are the most portable, and fundamental, encryption facet, so a few options are available during private drive operations for supplying them:
# Securely type your password into a read prompt, store it to TMP_ARDRIVE_PW, and export it for the shell session
read -rs TMP_ARDRIVE_PW
export ARDRIVE_DRIVE_PW=$(TMP_ARDRIVE_PW)
ardrive <some private command> -w /path/to/wallet.json -P
# Pipe your drive password to the ArDrive CLI
cat /path/to/my/drive/password.txt | ardrive <some private command> -w /path/to/wallet.json -P
# Redirect your drive password to the ArDrive CLI
ardrive <some private command> -w /path/to/wallet.json -P < /path/to/my/drive/password.txt
# When all other options fail, the CLI will prompt for your password (NOT COMPATIBLE WITH PIPES AND REDIRECTS!)
ardrive <some private command> -w /path/to/wallet.json -P
? Enter drive password: › ********
# Public drive
ardrive create-drive --wallet-file /path/to/my/wallet.json --drive-name "My Public Archive"
# Private drive
ardrive create-drive --wallet-file /path/to/my/wallet.json --drive-name "Teenage Love Poetry" -P
You can list all the drives associated with any Arweave wallet address, though the details of private drives will be obfuscated from you unless you provide the necessary decryption data.
# List all your own drives
ardrive list-all-drives -w /path/to/my/wallet.json -P
# List any address's drives
ardrive list-all-drives --address "HTTn8F92tR32N8wuo-NIDkjmqPknrbl10JWo5MZ9x2k"
Useful notes on listing the contents of drives:
# List everything in a private drive
ardrive list-drive -d "c7f87712-b54e-4491-bc96-1c5fa7b1da50" -w /path/to/my/wallet.json -P
# List the contents of a public drive up to and including those in the grandchild folders of the root folder
ardrive list-drive -d "c7f87712-b54e-4491-bc96-1c5fa7b1da50" --max-depth 2
You can utilize jq and the list commands to reshape the commands' output data into useful forms and stats for many use cases. Here are a few examples:
# Get share links for a PUBLIC drive
ardrive list-drive -d a44482fd-592e-45fa-a08a-e526c31b87f1 | jq '.[] | select(.entityType == "file") | "https://app.ardrive.io/#/file/" + .entityId + "/view"'
Example output:
"https://app.ardrive.io/#/file/1337babe-f000-dead-beef-ffffffffffff/view"
"https://app.ardrive.io/#/file/cdbc9ddd-1cab-41d9-acbd-fd4328929de3/view"
"https://app.ardrive.io/#/file/f19bc712-b57a-4e0d-8e5c-b7f1786b34a1/view"
"https://app.ardrive.io/#/file/4f8e081b-42f2-442d-be41-57f6f906e1c8/view"
"https://app.ardrive.io/#/file/0e02d254-c853-4ff0-9b6e-c4d23d2a95f5/view"
"https://app.ardrive.io/#/file/c098b869-29d1-4a86-960f-a9e10433f0b0/view"
"https://app.ardrive.io/#/file/4afc8cdf-4d27-408a-bfb9-0a2ec21eebf8/view"
"https://app.ardrive.io/#/file/85fe488d-fcf7-48ca-9df8-2b39958bbf15/view"
...
# Get total size of all files within drive
ardrive list-drive -d 13c3c232-6687-4d11-8ac1-35284102c7db | jq ' map(select(.entityType == "file") | .size) | add'
# Get total number of files within drive
ardrive list-drive -d 01ea6ba3-9e58-42e7-899d-622fd110211c | jq '[ .[] | select(.entityType == "file") ] | length'
As discussed previously, all folders in a drive are linked by way of parent folder references back to the root folder of a drive. Folders can be moved into any folder in the hierarchy that's not in their own subtree.
Creating folders manually is straightforward:
ardrive create-folder --parent-folder-id "63153bb3-2ca9-4d42-9106-0ce82e793321" --name "My Awesome Folder" -w /path/to/wallet.json
Example output:
{
"created": [
{
"type": "folder",
"metadataTxId": "AYFMBVmwqhbg9y5Fbj3Iasy5oxUqhauOW7PcS1sl4Dk",
"entityId": "d1b7c514-fb12-4603-aad8-002cf63015d3",
"key": "yHdCjpCKD2cuhQcKNx2d/XF5ReEjoKfZVqKunlCnPEk"
}
],
"tips": [],
"fees": {
"AYFMBVmwqhbg9y5Fbj3Iasy5oxUqhauOW7PcS1sl4Dk": 1378052
}
}
Note: Folders can also be created when supplying a folder for the --local-file-path during an upload-file command, however, the folder hierarchy on the local disk will be reconstructed on chain during the course of the recursive bulk upload.
Moving a folder is as simple as supplying a new parent folder ID. Note that naming collisions among entities within a folder are not allowed.
ardrive move-folder --folder-id "9af694f6-4cfc-4eee-88a8-1b02704760c0" --parent-folder-id "29850ab7-56d4-4e1f-a5be-cb86d5513921" -w /path/to/wallet.json
To view the metadata of a folder, users can use the folder-info command:
ardrive folder-info --folder-id "9af694f6-4cfc-4eee-88a8-1b02704760c0"
Similar to drives, the list-folder command can be used to fetch the metadata of each entity within a folder. But by default, the command will fetch only the immediate children of that folder (--maxdepth 0):
# List immediate children of folder "My Public Folder"
ardrive list-folder --parent-folder-id "29850ab7-56d4-4e1f-a5be-cb86d5513940"
Example output:
[
{
"appName": "ArDrive-CLI",
"appVersion": "2.0",
"arFS": "0.11",
"contentType": "application/json",
"driveId": "01ea6ba3-9e58-42e7-899d-622fd110211a",
"entityType": "folder",
"name": "mytestfolder",
"txId": "HYiKyfLwY7PT9NleTQoTiM_-qPVUwf4ClDhx1sjUAEU",
"unixTime": 1635102772,
"parentFolderId": "29850ab7-56d4-4e1f-a5be-cb86d5513940",
"entityId": "03df2929-1440-4ab4-bbf0-9dc776e1ed96",
"path": "/My Public Folder/mytestfolder",
"txIdPath": "/09_x0X2eZ3flXXLS72WdTDq6uaa5g2LjsT-QH1m0zhU/HYiKyfLwY7PT9NleTQoTiM_-qPVUwf4ClDhx1sjUAEU",
"entityIdPath": "/29850ab7-56d4-4e1f-a5be-cb86d5513940/03df2929-1440-4ab4-bbf0-9dc776e1ed96"
},
{
"appName": "ArDrive-CLI",
"appVersion": "2.0",
"arFS": "0.11",
"contentType": "application/json",
"driveId": "01ea6ba3-9e58-42e7-899d-622fd110211a",
"entityType": "folder",
"name": "Super sonic public folder",
"txId": "VUk1B_vo1va2-EHLtqjsotzy0Rdn6lU4hQo3RD2xoTI",
"unixTime": 1631283259,
"parentFolderId": "29850ab7-56d4-4e1f-a5be-cb86d5513940",
"entityId": "452c6aec-43dc-4015-9abd-20083068d432",
"path": "/My Public Folder/Super sonic sub folder",
"txIdPath": "/09_x0X2eZ3flXXLS72WdTDq6uaa5g2LjsT-QH1m0zhU/VUk1B_vo1va2-EHLtqjsotzy0Rdn6lU4hQo3RD2xoTI",
"entityIdPath": "/29850ab7-56d4-4e1f-a5be-cb86d5513940/452c6aec-43dc-4015-9abd-20083068d432"
},
{
"appName": "ArDrive-CLI",
"appVersion": "2.0",
"arFS": "0.11",
"contentType": "application/json",
"driveId": "01ea6ba3-9e58-42e7-899d-622fd110211a",
"entityType": "file",
"name": "test-number-twelve.txt",
"txId": "429zBqnd7ZBNzgukaix26RYz3g5SeXCCo_oIY6CPZLg",
"unixTime": 1631722234,
"size": 47,
"lastModifiedDate": 1631722217028,
"dataTxId": "vA-BxAS7I6n90cH4Fzsk4cWS3EOPb1KOhj8yeI88dj0",
"dataContentType": "text/plain",
"parentFolderId": "29850ab7-56d4-4e1f-a5be-cb86d5513940",
"entityId": "e5948327-d6de-4acf-a6fe-e091ecf78d71",
"path": "/My Public Folder/test-number-twelve.txt",
"txIdPath": "/09_x0X2eZ3flXXLS72WdTDq6uaa5g2LjsT-QH1m0zhU/429zBqnd7ZBNzgukaix26RYz3g5SeXCCo_oIY6CPZLg",
"entityIdPath": "/29850ab7-56d4-4e1f-a5be-cb86d5513940/e5948327-d6de-4acf-a6fe-e091ecf78d71"
},
{
"appName": "ArDrive-CLI",
"appVersion": "2.0",
"arFS": "0.11",
"contentType": "application/json",
"driveId": "01ea6ba3-9e58-42e7-899d-622fd110211a",
"entityType": "file",
"name": "wonderful-test-file.txt",
"txId": "6CokwlzB81Fx7dq-lB654VM0XQykdU6eYohDmEJ2gk4",
"unixTime": 1631671275,
"size": 23,
"lastModifiedDate": 1631283389232,
"dataTxId": "UP8THwA_1gvyRqNRqYmTpWvU4-UzNWBN7SiX_AIihg4",
"dataContentType": "text/plain",
"parentFolderId": "29850ab7-56d4-4e1f-a5be-cb86d5513940",
"entityId": "3274dae9-3487-41eb-94d5-8d5d3d8bc343",
"path": "/My Public Folder/wonderful-test-file.txt",
"txIdPath": "/09_x0X2eZ3flXXLS72WdTDq6uaa5g2LjsT-QH1m0zhU/6CokwlzB81Fx7dq-lB654VM0XQykdU6eYohDmEJ2gk4",
"entityIdPath": "/29850ab7-56d4-4e1f-a5be-cb86d5513940/3274dae9-3487-41eb-94d5-8d5d3d8bc343"
}
]
# List all contents of a folder
ardrive list-folder --parent-folder-id "9af694f6-4cfc-4eee-88a8-1b02704760c0" --all
Similar to folders, files are linked to a parent folder which ultimately chains the file back to the root folder of its parent drive. As such, a parent folder ID is required in order to upload files. Files can be freely moved to other folders within their original drive.
The important difference for file entities is that they also hold a reference to their data transaction ID, which is the dataTxId as returned by the file-info command. This is where your uploaded data lives on the permaweb.
NOTE: The CLI currently (v1.0.0) has progress logging on uploads DISABLED for producing clean JSON outputs that can be piped in the terminal. On larger uploads, remember to be patient. You can check your system's node process to confirm the process is still uploading.
To upload a file, you'll need a parent folder id, the file to upload's file path, and the path to your wallet:
# Supply the parent folder ID to upload-file
ardrive upload-file --local-file-path /path/to/file.txt --parent-folder-id "9af694f6-4cfc-4eee-88a8-1b02704760c0" -w /path/to/wallet.json
Example output:
{
"created": [
{
"type": "file",
"metadataTxId": "YfdDXUyerPCpBbGTm_gv_x5hR3tu5fnz8bM-jPL__JE",
"dataTxId": "l4iNWyBapfAIj7OU-nB8z9XrBhawyqzs5O9qhk-3EnI",
"entityId": "6613395a-cf19-4420-846a-f88b7b765c05"
}
],
"tips": [
{
"txId": "1zwdfZAIV8E26YjBs2ZQ4xjjP_1ewalvRgD_GyYw7f8",
"recipient": {
"address": "3mxGJ4xLcQQNv6_TiKx0F0d5XVE0mNvONQI5GZXJXkt"
},
"winston": "10000000"
}
],
"fees": {
"l4iNWyBapfAIj7OU-nB8z9XrBhawyqzs5O9qhk-3EnI": 1369131,
"YfdDXUyerPCpBbGTm_gv_x5hR3tu5fnz8bM-jPL__JE": 1432001,
"1zwdfZAIV8E26YjBs2ZQ4xjjP_1ewalvRgD_GyYw7f8": 1363608
}
}
NOTE: To upload to the root of a drive, specify its root folder ID as the parent folder ID for the upload destination. You can retrieve it like so:
ardrive drive-info -d "c7f87712-b54e-4491-bc96-1c5fa7b1da50" | jq -r '.rootFolderId'
Users can perform a bulk upload by using the upload-file command on a target folder. The command will reconstruct the folder hierarchy on local disk as ArFS folders on the permaweb and upload each file into their corresponding folders:
ardrive upload-file --local-file-path /path/to/folder --parent-folder-id "9af694f6-4cfc-4eee-88a8-1b02704760c0" -w /path/to/wallet.json
By default, the upload-file command will use the upsert behavior if existing entities are encountered in the destination folder tree that would cause naming conflicts.
Expect the behaviors from the following table for each resolution setting:
| Source Type | Conflict at Dest | skip | replace | upsert (default) |
|---|---|---|---|---|
| File | None | Insert | Insert | Insert |
| File | Matching File | Skip | Update | Skip |
| File | Different File | Skip | Update | Update |
| File | Folder | Skip | Fail | Fail |
| Folder | None | Insert | Insert | Insert |
| Folder | File | Skip | Fail | Fail |
| Folder | Folder | Re-use | Re-use | Re-use |
The default upsert behavior will check the destination folder for a file with a conflicting name. If no conflicts are found, it will insert (upload) the file.
In the case that there is a FILE to FILE name conflict found, it will only update it if necessary. To determine if an update is necessary, upsert will compare the last modified dates of conflicting file and the file being uploaded. When they are matching, the upload will be skipped. Otherwise the file will be updated as a new revision.
To override the upsert behavior, use the --replace option to always make new revisions of a file or the --skip option to always skip the upload on name conflicts:
ardrive upload-file --replace --local-file-path /path/to/file.txt --parent-folder-id "9af694f6-4cfc-4eee-88a8-1b02704760c0" -w /path/to/wallet.json
ardrive upload-file --skip --local-file-path /path/to/file.txt --parent-folder-id "9af694f6-4cfc-4eee-88a8-1b02704760c0" -w /path/to/wallet.json
Simply perform the file-info command to retrieve the metadata of a file:
ardrive file-info --file-id "e5ebc14c-5b2d-4462-8f59-7f4a62e7770f"
Example output:
{
"appName": "ArDrive-Web",
"appVersion": "0.1.0",
"arFS": "0.11",
"contentType": "application/json",
"driveId": "51062487-2e8b-4af7-bd81-4345dc28ea5d",
"entityType": "file",
"name": "2_depth.png",
"txId": "CZKdjqwnmxbWchGA1hjSO5ZH--4OYodIGWzI-FmX28U",
"unixTime": 1633625081,
"size": 41946,
"lastModifiedDate": 1605157729000,
"parentFolderId": "a2c8a0cb-0ca7-4dbb-8bf8-93f75f308e63",
"entityId": "e5ebc14c-5b2d-4462-8f59-7f4a62e7770f",
"fileId": "e5ebc14c-5b2d-4462-8f59-7f4a62e7770f",
"dataTxId": "Jz0WsWyAGVc0aE3UzACo-YJqG8OPrN3UucmDdt8Fbjc",
"dataContentType": "image/png"
}
# Use `tee` to store command json outputs for later review/backup/automation/etc.
# Use `jq` to parse json output and retrieve the root folder ID for use in downstream command
ardrive create-drive -w /path/to/wallet.json -n "My Public Archive" |
tee create_drive_output.json |
jq -r '.created[] | select(.type == "folder") | .entityId' |
while read -r parentFolderId; do
ardrive upload-file -w /path/to/wallet.json --local-file-path ./myarchives -F "$parentFolderId";
done |
tee upload_folder_output.json
Block time on Arweave is typically between 2-3 minutes in duration, so transactions can be mined within that time frame when network congestion is low. Transactions, in the general case, proceed through the following set of states:
Monitor any Arweave transaction's status via its transaction ID by performing:
# Peek at the status:
yarn ardrive tx-status -t "ekSMckikdRJ8RGIkFa-X3xq3427tvM7J9adv8HP3Bzs"
Example output:
ekSMckikdRJ8RGIkFa-X3xq3427tvM7J9adv8HP3Bzs: Mined at block height 775810 with 22439 confirmations
# Reprint the status every 10 seconds:
watch -n 10 yarn ardrive tx-status -t "ekSMckikdRJ8RGIkFa-X3xq3427tvM7J9adv8HP3Bzs"
Currently, Arweave blocks hold up to 1000 transactions per block. The "mempool", where pending transactions reside until they've been included into a block, will only hold a transaction for 50 blocks (~100-150 minutes) before it's discarded by the network resulting in no fees or data being transacted. During periods of network congestion (i.e. those where the mempool contains 1000 or more pending transactions), it may make sense to either:
a) wait for congestion to dissipate before attempting your transactions.
b) apply the fee boost multiplier to your transactions rewards with the --boost parameter during write operations in order to front-run some of the congestion.
# See all the transactions in the mempool
ardrive get-mempool
# Return the count of the transactions in the mempool
ardrive get-mempool | jq 'length'
# Increase the miner reward on your transactions by 50%
ardrive upload-file --wallet-file /path/to/my/wallet.json --parent-folder-id "f0c58c11-430c-4383-8e54-4d864cc7e927" --local-file-path ./helloworld.txt --boost 1.5
█████╗ ██████╗ ██████╗ ██████╗ ██╗██╗ ██╗███████╗
██╔══██╗██╔══██╗██╔══██╗██╔══██╗██║██║ ██║██╔════╝
███████║██████╔╝██║ ██║██████╔╝██║██║ ██║█████╗
██╔══██║██╔══██╗██║ ██║██╔══██╗██║╚██╗ ██╔╝██╔══╝
██║ ██║██║ ██║██████╔╝██║ ██║██║ ╚████╔╝ ███████╗
╚═╝ ╚═╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝╚═╝ ╚═══╝ ╚══════╝
██████╗██╗ ██╗
██╔════╝██║ ██║
██║ ██║ ██║
██║ ██║ ██║
╚██████╗███████╗██║
╚═════╝╚══════╝╚═╝
Write ArFS
===========
create-drive
create-folder
upload-file
move-file
move-folder
Read ArFS
===========
file-info
folder-info
drive-info
list-folder
list-drive
list-all-drives
Wallet Ops
===========
generate-seedphrase
generate-wallet
get-address
get-balance
send-ar
get-drive-key
get-file-key
Arweave Ops
===========
tx-status
get-mempool
# Learn more about a command:
ardrive <command> --help
FAQs
The ArDrive Command Line Interface (CLI is a Node.js application for terminal-based ArDrive workflows. It also offers utility operations for securely interacting with Arweave wallets and inspecting various Arweave blockchain conditions.
We found that ardrive-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 6 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team uncovered a malicious Python package typosquatting the popular 'fabric' SSH library, silently exfiltrating AWS credentials from unsuspecting developers.
Security News
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.