v0.1.0

Highlights

• Added configuration allowing node deployment to the production network.
• Implemented a logging API that allows logs for various sub-systems to be turned on or off at your leisure.
• Fixed many issues uncovered by upload, replication and retrieval testing.
• UX improvements to piri init command.

Upgrading from v0.0.18

This release is NOT a breaking change. You do NOT need to remove your data directory.

1. Stop your Piri process.
2. Upgrade your Piri binary to v0.1.0.
3. Start your Piri process

Note: migrating from any version less than v0.0.18 requires a node reset, per the previous release docs.

Migrating to Production

Piri nodes can now be run on the production network! This is how you move a Piri node running on the Staging network to the Production network.

If you want to setup a new Piri node for the production network then these are not the instructions you want, please read the next section.

1. Satisfy Filecoin Mainnet prerequisites.
   • Setup a Lotus node on the Filecoin Mainnet.
     • Sync Lotus using the latest Mainnet Snapshot.
     • Enable ETH RPC.
   • Create a Funded Delegated Wallet on the Filecoin Mainnet.
     • Run: lotus wallet new delegated
     • Add funds (At least 5 FIL to cover one time network joining fee).
     • Verify funds: lotus wallet balance YOUR_DELEGATED_ADDRESS
   • Read our Filecoin prerequisites guide for full details.
2. Stop your Piri process.
3. Delete your data directory (preserving service.pem):

   rm -rf /path/to/piri/data  # or your custom data directory path

   ⚠️ IMPORTANT: Keep your service.pem key file!

4. Upgrade your Piri binary to v0.1.0.
5. Prepare your wallet for import into Piri:

   # Export wallet from Lotus to hex format
   lotus wallet export YOUR_DELEGATED_ADDRESS > wallet.hex

6. Run piri init with the following parameters, updated as appropriate (note: new --network parameter):

   piri init \
     --network=forge-prod \
     --data-dir=/path/to/data \
     --temp-dir=/path/to/temp \
     --key-file=/path/to/service.pem \
     --wallet-file=/path/to/wallet.hex \
     --lotus-endpoint=wss://YOUR_LOTUS_ENDPOINT/rpc/v1 \
     [email protected] \
     --public-url=https://piri.example.com > config.toml

   ℹ️ All parameters other than --network MUST be updated.

7. Start your Piri node using the config you generated:

   piri serve --config=config.toml

   ℹ️ If the --config option is not provided, Piri will automatically load config from your user config directory e.g. ~/.config/piri/config.toml.

Setting up on Production from scratch

Follow the Piri getting started guide for the Forge Production Network.

What's Changed

• update docs for release by @frrist in #353
• fix: watcher_eth_test by @frrist in #355
• feat: more feedback during registration by @alanshaw in #356
• chore: upgrade go-ucanto dependency by @alanshaw in #359
• feat(ipni): move to double step ipni publish by @hannahhoward in #331
• feat: implement logging api by @frrist in #354
• feat: implement minimal tracing in piri for upload and download by @frrist in #357
• fix: panic when handling unallocated stored blob by @frrist in #361
• fix: transfer promise selector by @alanshaw in #358
• fix: ucan/conclude invocation facts by @alanshaw in #360
• feat: forge production presets and preset overhaul by @volmedo in #334
• feat: mainnet smart contract presets by @volmedo in #362
• fix: network is the right variable name by @volmedo in #364
• feat: add delete method to objectstore interface by @alanshaw in #369
• fix: write the blob outside of the transaction by @frrist in #368
• fix: adjust client config by @volmedo in #367
• fix: do not display usage when init error by @alanshaw in #363

Full Changelog: v0.0.18...v0.1.0