Cafe137

@significance you can provide `--stamp 0000000000000000000000000000000000000000000000000000000000000000` to bypass the debug API usage

Related: https://github.com/ethersphere/swarm-cli/issues/421

No longer the case with the merge

Dependency: https://github.com/ethersphere/bee/issues/3359

Node-Intl is huge: https://github.com/vercel/pkg/issues/999 Going below 40MB does not seem possible to me when packaging the node binary. I am happy to do some research to see if JS code...

@agazso, should we use GitHub's releases tab to distribute `swarm-cli` binaries? Pressing _edit_ on any existing release provides a drag-and-drop area where binaries can be uploaded.

Uploaded binaries manually to the latest release. We have the https://github.com/ethersphere/swarm-cli/actions/workflows/make.yaml CI workflow to build the binaries, the missing piece is making this run for each new release and place...

This can be implemented in stamp/buy.ts: ``` const estimatedCost = Utils.getStampCostInBzz(this.depth, Number(this.amount)) const estimatedCapacity = new Storage(Utils.getStampMaximumCapacityBytes(this.depth)) const estimatedTtl = Utils.getStampTtlSeconds(Number(this.amount)) this.console.log(createKeyValue('Estimated cost', `${estimatedCost.toFixed(3)} BZZ`)) this.console.log(createKeyValue('Estimated capacity', estimatedCapacity.toString())) this.console.log(createKeyValue('Estimated TTL',...

I believe SOCs are no longer supported in `bee dev` mode, please see https://github.com/ethersphere/bee/issues/4652 Do you have this issue on testnet or mainnet?

Please reopen if this issue happens outside of `dev` mode.