API(DA interface) may need to update for same with celestia-node

updated codes in celestia-node

💡 Verification agent

-        if currentSize+blobLen > maxBlobSize {
-            api.Logger.Info("Blob size limit reached for batch", ...)
-            break
-        }
-        currentSize += blobLen
+        // Only enforce the per-blob limit; let the DA layer decide on batch limits.
+        currentSize += blobLen   // remove if aggregate limiting is not required

#!/bin/bash
set -e
# Locate the MaxBlobSize method definition and nearby comments
rg -n "func .*MaxBlobSize" -C3 .

#!/bin/bash
set -e
# Display the API struct and its methods to understand the Internal field and surrounding context
sed -n '1,200p' da/jsonrpc/client.go

Clarify MaxBlobSize Semantics
The MaxBlobSize method (e.g. in LocalDA and DummyDA) clearly returns the maximum size per blob, yet here you also treat it as a batch limit by summing currentSize. This will silently drop valid blobs once the aggregate size exceeds the same threshold.

• Location: da/jsonrpc/client.go, SubmitWithOptions loop (around lines 157–162)

• Remove or isolate the cumulative check if you only intend to enforce a per-blob limit:

  // per-blob limit already checked above:
  // if blobLen > maxBlobSize { … }
  
  // ↓ Remove these lines if no aggregate restriction is needed
  if currentSize+blobLen > maxBlobSize {
      api.Logger.Info("Batch size limit reached", …)
      break
  }
  currentSize += blobLen

• If you actually need a batch-size cap, rename MaxBlobSize → MaxBatchSize (and adjust the RPC/DA interface) to avoid confusion.

Please confirm which contract the DA server expects and update the code or naming accordingly.