From 86673c0f275c3276c5177b42e087eb18a4863f38 Mon Sep 17 00:00:00 2001 From: protolambda Date: Mon, 17 Jun 2024 18:27:17 +0000 Subject: [PATCH] deploy: 8efc7a3fe800367bb8f407ab4fe284570a18ebc9 --- experimental/alt-da.html | 4 ++-- print.html | 4 ++-- searchindex.js | 2 +- searchindex.json | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/experimental/alt-da.html b/experimental/alt-da.html index e175581b3..81430e854 100644 --- a/experimental/alt-da.html +++ b/experimental/alt-da.html @@ -259,7 +259,7 @@

DA Server

Content addressed systems like S3 should use the first put/<hex_encoded_commitment> because they can pre-commpute the commitment. Blockchain based DA layers should use put and then submit the returned commitment to L1. -Because commitments can includ the block height or hash, the commitment cannot be computed prior to submitting +Because commitments can include the block height or hash, the commitment cannot be computed prior to submitting it to the DA Layer.

Any DA provider can implement the following endpoints to receive and serve input data: