feat(rpc): add costUnits to transaction meta

[sduchesneau]

The RPC reports the block cost model charge alongside the compute units consumed, on both the binary and the jsonParsed transaction meta.

[greptile-apps]

Greptile Summary

Adds nullable costUnits fields to binary and JSON-parsed transaction metadata so callers can access the block cost model charge when reported by an RPC node.

• Extends TransactionMeta with CostUnits.
• Extends ParsedTransactionMeta with the matching field.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
rpc/types.go	Adds matching optional costUnits JSON fields to both transaction metadata response representations.

_{Reviews (3): Last reviewed commit: "feat(rpc): add costUnits to transaction ..." | Re-trigger Greptile}

[sonicfromnewyoke]

good catch @sduchesneau

to bypass commitlint, could you run the next commands locally:

git commit --amend -m "feat(rpc): add costUnits to transaction meta"
git push --force-with-lease

[sduchesneau]

good catch @sduchesneau

to bypass commitlint, could you run the next commands locally:

git commit --amend -m "feat(rpc): add costUnits to transaction meta"
git push --force-with-lease

do you need a signed commit on top of that ?

[sonicfromnewyoke]

good catch @sduchesneau
to bypass commitlint, could you run the next commands locally:

git commit --amend -m "feat(rpc): add costUnits to transaction meta"
git push --force-with-lease

do you need a signed commit on top of that ?

yes, sorry forget to mention, signed commit is mandatory

you can check the next links:

• https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification
• https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key
• https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

after creating a signing key, you can add this public key on GH under Settings -> SSH and GPG keys -> "Signing key" - the same key can be registered twice, once for auth, once for signing, for example

and after that:

git config --global gpg.format ssh
git config --global user.signingkey ~/.ssh/id_ed25519.pub
git config --global commit.gpgsign true    # then -S is implicit

and your previous commit message rename should look like follows:

git commit --amend -S -m "feat(rpc): add costUnits to transaction meta"
git push --force-with-lease

[sduchesneau]

@sonicfromnewyoke should be good to go if you can approve the workflows again (same commit, with signature) Thanks!

[sonicfromnewyoke]

@sonicfromnewyoke should be good to go if you can approve the workflows again (same commit, with signature) Thanks!

many thanks for contribution 💪