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
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Changed
Breaking:create-snapshot publishes an ArFS Drive State entity (Entity-Type: drive-state): the drive's whole state as one SQLite database, which ArDrive clients read in one download. It no longer publishes JSON snapshots (Entity-Type: snapshot), which stay readable. Its JSON output names the result txId and adds driveStateId, stateVersion, blockEnd, entityCount, plaintextBytes, sealedBytes, encrypted and transport
create-snapshot supports private drives, with --private or --drive-key, and refuses a drive the wallet does not own. It says when a drive's privacy does not match the flags given, before reading the drive
create-snapshot --dry-run no longer requires the wallet to hold the estimated cost
list-drive, list-folder, download-drive and download-folder read a drive's snapshot first, through ardrive-core-js. ARDRIVE_DISABLE_DRIVE_STATE=1 turns this off
Added
hide-file, unhide-file, hide-folder and unhide-folder: hide an item from ArDrive's listings, or show it again, without deleting anything
pin-file: add an existing Arweave transaction to a public drive as a file, without uploading its data again
snapshot-info: whether a drive has a usable snapshot, and why not. With --drive-key it needs no wallet
Updated
Updated to ardrive-core-js@4.5.0: snapshot reading is stricter and faster, and create-snapshot refuses to publish a snapshot every reader would refuse, or one with fewer entities than the drive's newest published snapshot (a gateway that has not indexed the whole drive)