upload hangs

[George3d6]

Currently,

It seems that calling .upload just hangs for many dozens of minutes for the first few chunks.

The .upload method borderline works with gasInPct set to 300 - in so far as a 2815.36 KB file was uploaded in ~11 minutes

It's quite unclear to me, a hypothetical user, how to use the gasInPct. A few things that would be reasonable here, from my PoV, are:

1. Have some parameter that controls the speed in a more intuitive way (e.g. gasPerByte or ethPerByte might be a very good abstraction here - whereby that's the maximum I'm willing to spend and the sdk handles how to spend it in order to get as fast an upload as possible)
2. Some estimate of total upload time printed to the console, given the gas I'm spending (right now, unless I modify the undocumented gasInPct it essentially looks like upload hangs - even though I do buy it might finish in some hypothetical future)
3. Estimating upload time with estimateCost, to avoid unreasonably large updates

[iteyelmp]

The .upload method may hang because the SDK relies on the current average gas price and the blob gas price. If either of these changes, a transaction may not get included in a block, causing it to wait indefinitely.

To address this:

Adjust gas for new transactions using gasInPct (gasPrice In Percent). This increases the gas price based on the latest average gas price:

1 = +1%

100 = +100% (effectively doubling the gas price)
Note: This only affects transactions that have not yet been sent.

Replace a stuck transaction using isConfirmedNonce: true. This fetches the nonce of the last confirmed transaction and sends a new transaction with that nonce, replacing the pending one.

Because replacing requires a higher gas price, combine it with gasInPct to ensure the transaction gets included.

[iteyelmp]

There isn’t a precise way to predict upload time yet; however, you can use estimateCost to get an idea of gas requirements and avoid unexpectedly high costs.

We are aware that better abstractions for speed control and more accurate upload time estimates would make the process more intuitive, and improvements in these areas are planned for future versions of the SDK.

export interface EstimateGasRequest {
    key: string,
    content: ContentLike,
    type: UploadType,
    gasIncPct?: number,
    chunkHashes?: string[],
}

async estimateCost(request: EstimateGasRequest): Promise<CostEstimate>