feat!: use content claims (#26)

Converts hoverboard to use content claims and request blocks via byte ranges from blob serving locaitons. BREAKING CHANGE: hoverboard no longer uses R2 binding, and does not talk to DynamoDB or S3. Instead it uses content claims to determine block locations.
storacha-network · May 28, 2024 · c25860c · c25860c
1 parent df2a6e7
commit c25860c
Show file tree

Hide file tree

Showing 27 changed files with 10,911 additions and 14,865 deletions.
diff --git a/.example.dev.vars b/.example.dev.vars
@@ -2,7 +2,4 @@
 
 # stringified dev peerid json
 PEER_ID_JSON='{"id":"12D3KooWJA2ETdy5wYTbCHVqKdgrqtmuNEwjMVMwEtMrNugrsGkZ","privKey":"CAESQAyByThzp930nIDnJgz/jeuI/nr9njEaE25v9AhWgjBJe+aR6KPr8lT60H2MA3ItZF8t37H8PVa8yB4Cp61/pLo=","pubKey":"CAESIHvmkeij6/JU+tB9jANyLWRfLd+x/D1WvMgeAqetf6S6"}'
-
-# api keys for dynamo and s3
-AWS_SECRET_ACCESS_KEY=
-AWS_ACCESS_KEY_ID=
+CONTENT_CLAIMS_URL=
diff --git a/.gitignore b/.gitignore
@@ -2,3 +2,4 @@ node_modules
 .wrangler
 .dev.vars
 .env
+dist
diff --git a/README.md b/README.md
@@ -46,8 +46,6 @@ Fetching bafybeicm3skx7ps2bwkh56l3mirh3hu4hmkfttfwjkmk4cr25sxtf2jmby
 
 Set the following with `wrangler secret put <key>`
 
-- AWS_ACCESS_KEY_ID - aws creds
-- AWS_SECRET_ACCESS_KEY - aws creds
-- PEER_ID_JSON - stringified json peerId spec for this node
+- `PEER_ID_JSON` - stringified json peerId spec for this node
 
 [IPFS Bitswap]: https://specs.ipfs.tech/bitswap-protocol/
diff --git a/docs/hoverboard.svg b/docs/hoverboard.svg