Skip to content

Commit

Permalink
update readme
Browse files Browse the repository at this point in the history
  • Loading branch information
yusefnapora committed Mar 15, 2021
1 parent 446160f commit f142647
Showing 1 changed file with 2 additions and 11 deletions.
13 changes: 2 additions & 11 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,8 +127,8 @@ minty show 1

### Pin IPFS assets for an NFT

The assets for new tokens are stored in a local IPFS repository, which is only "online" temporarily while
running `minty` commands.
The assets for new tokens are stored in a local IPFS repository, which is only "online" while a local IPFS daemon is running.
The `start-local-environment.sh` script starts a local daemon for you, in case you're not already running IPFS.

To make the data highly available without needing to run a local IPFS daemon 24/7, you can request that a [Remote Pinning Service][pinning-service-api] like [Pinata](https://pinata.cloud) store a copy of your IPFS data on their IPFS nodes.

Expand All @@ -144,15 +144,6 @@ Pinning metadata (ipfs://QmUJibEFFTNEbvof9AroJK8m4HBUz427FTX8ejW2FoZpzn) for tok
Pinned all data for token id 1
```

Instead of or in addition to pinning data remotely, you can make the data available when `minty` is not running by installing `js-ipfs` globally, and running the IPFS daemon:

```shell
npm install -g ipfs
js-ipfs daemon
```

This will use the same local repository as Minty, and will provide your data to the IPFS network as long as your computer is online.

[pinning-service-api]: https://ipfs.github.io/pinning-services-api-spec/

<!-- TODO: add tutorial link -->
Expand Down

0 comments on commit f142647

Please sign in to comment.