feat: blob mode for loadtest

[jhkimqd]

Description

This PR includes blob mode for polycli loadtest. The new mode sends an EIP-4844 blob transaction. Usage is identical to other loadtest modes e.g.- loadtest --requests 10 --rpc-url <rpc_url> --to-random --verbosity 700 --rate-limit 1 --concurrency 1 --mode \"blob\" --private-key <private_key> will send 10 blob transactions with randomly generated blob and its sidecars:

	blobTx := ethtypes.BlobTx{
		ChainID:    uint256.NewInt(chainID.Uint64()),
		Nonce:      nonce,
		GasTipCap:  uint256.NewInt(gasTipCap.Uint64()),
		GasFeeCap:  uint256.NewInt(gasPrice.Uint64()),
		BlobFeeCap: uint256.NewInt(blobFeeCap),
		Gas:        gasLimit,
		To:         *to,
		Value:      uint256.NewInt(amount.Uint64()),
		Data:       nil,
		AccessList: nil,
		BlobHashes: make([]common.Hash, 0),
		Sidecar: &types.BlobTxSidecar{
			Blobs:       make([]kzg4844.Blob, 0),
			Commitments: make([]kzg4844.Commitment, 0),
			Proofs:      make([]kzg4844.Proof, 0),
		},
	}

The blob fee cap is adjustable using the --blob-fee-cap flag, and the default value is at 100,000 Gwei.

Jira / Linear Tickets

• DVT-1517

Testing

Tested on a Kurtosis-CDK Geth node.

Blob transaction using cast shows a successful transaction of type 0x03

Blob transaction using polycli loadtest --mode "blob" similarly shows the same transaction type when queried using cast receipt <blob_txn_hash>

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-		Generic High Entropy Secret	8d9038c	cmd/loadtest/loadtest.go	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[leovct]

lgtm

nit: I find that the function names are not very clear, especially parseBlobRefs and e/EncodeBlobData (two methods with the same name).

[leovct]

lgtm

nit: I find that the function names are not very clear, especially parseBlobRefs.

I was thinking more along the lines of:

• encodeBlobData(data []byte) kzg4844.Blob could be renamed createBlob(data []byte) kzg4844.Blob.
• encodeBlob(data []byte) (*BlobCommitment, error) => generateBlobCommitment(data []byte) (*BlobCommitment, error).
• parseBlobCommitment(tx *types.BlobTx) error => appendBlobCommitment(tx *types.BlobTx) error.
• randomBlobData(size int) ([]byte, error) => generateRandomBlobData(size int) ([]byte, error).

What do you think?

[leovct]

lgtm