Skip to content

Commit a96e37d

Browse files
committed
feat: more readme cleanup
1 parent a416255 commit a96e37d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -98,9 +98,9 @@ const deleteRelationOp: DeleteRelationOp = Relation.remove('id of relation');
9898

9999
Once you have a set of ops ready to publish, you'll need to binary encode them into an Edit and upload the Edit to IPFS.
100100

101-
Currently the indexer only supports reading from the [Lighthouse gateway](https://lighthouse.storage/). You should use the Lighthouse gateway to guarantee data availability for your published data while in early access. To write to Lighthouse you'll need an [API key](https://docs.lighthouse.storage/lighthouse-1/quick-start#create-an-api-key).
101+
Currently the indexer only supports reading a specific gateway. You should use our IPFS API to guarantee data availability for your published data while in early access.
102102

103-
Additionally, the indexer expects that IPFS CIDs be prefixed with `ipfs://` so it knows how to process it correctly.
103+
Additionally, the indexer expects that IPFS CIDs be prefixed with `ipfs://` so it knows how to process it correctly. The API already returns the CID prefixed with `ipfs://`.
104104

105105
```ts
106106
import { EditProposal } from '@graphprotocol/grc-20/proto';
@@ -116,7 +116,7 @@ const blob = new Blob([binaryEncodedEdit], { type: 'application/octet-stream' })
116116
const formData = new FormData();
117117
formData.append('file', blob);
118118

119-
const result = await fetch('https://geobrowser.io/api/ipfs/upload-binary, {
119+
const result = await fetch('https://geobrowser.io/api/ipfs/upload-binary', {
120120
method: 'POST',
121121
body: formData,
122122
});

0 commit comments

Comments
 (0)