--print-calldata for later proof submission

[jbrower95]

Summary

• If --print-calldata is specified during the credentials or checkpoint command, we will prepare the transaction(s) without sending, and print the calldata as structured JSON.
• For checkpoint proofs, we will print the calldata to start the checkpoint if one is not active yet. if one is already active, we will print the calldata for the proofs, batched according to --batchSize.

The proofs will be printed with (TO) and (CALLDATA) fields, all hex encoded. Credential proofs include validator_indices, which is an array of validator indices to be attested in that proof. You should submit the sequentially to network, taking care of your nonces as needed. They may be submitted by either the Eigenpod's owner, or an approved proof submitter (see assign-submitter command).

Approach

We use the NoSend option in abigen, and combine it with a burner ETH wallet. I've hardcoded the PK of an eth wallet into the script -- the signed data is never used anyways.

Data Format

You should expect either an array of Transaction, or an array of CredentialProofTransaction

Example Command

./cli checkpoint --podAddress $EIGENPOD_ADDRESS --beaconNode $NODE_BEACON --execNode $NODE_ETH --print-calldata

Submitting to network

You can use the cast tool to submit these proofs to network.

cast send $TO $CALLDATA --rpc-url $NODE_ETH --private-key $EIGENPOD_PK

Testing

checkpoint

## credentials

Test transactions

• startCheckpoint
• verifyCheckpointProofs

[wadealexc]

It may be time to start compiling some of this config into structs. The parameter lists for these methods are getting big :D

[jbrower95]

yeah most of this is going to be structs next week