tx: Update c-kzg to big endian implementation

[g11tech]

c-kzg npm (and other kzg impls/bindings) have been updated to big endian, this PR aims to update the same

Ref

• Update the endianness of the polynomial commitments to be big endian ethereum/consensus-specs#3354

TODO:

- [ ] Update the setup file confirmed setup file remain sames

• Update and fix tests

[codecov]

Codecov Report

Merging #2746 (860b42e) into master (8d105af) will increase coverage by 0.11%.
The diff coverage is n/a.

Additional details and impacted files

Flag	Coverage Δ
block	90.82% <ø> (ø)
blockchain	90.72% <ø> (?)
client	86.82% <ø> (-0.02%)	⬇️
common	97.00% <ø> (?)
ethash	∅ <ø> (∅)
evm	79.98% <ø> (ø)
rlp	∅ <ø> (∅)
statemanager	86.28% <ø> (ø)
trie	89.92% <ø> (ø)
tx	95.76% <ø> (ø)
util	81.13% <ø> (?)
vm	81.07% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

[holgerd77]

Have updated this via UI

[holgerd77]

LGTM

[holgerd77]

Maybe this file gets more readable and we will save some disk space if we do something like '00'.repeat(1000000) or so. 😂

Won't make it a blocker though, but might really be worth to update on the sideline on one of the next updates.

[holgerd77]

(or is this then hindering others from other clients to take the data over? 🤔)

[g11tech]

yea we can do that, but for now the idea was to make sure consensus with other clients
we can def cleanup now

[holgerd77]

Hi @g11tech, just having another look at this PR for release notes. Out of interest: why is the changeset for this PR and this tx tests actually so small? 🤔

Wouldn't e.g. the following from above (just totally abitrary example) also change and therefore a lot of hash and the like comparisons?

t.equal(
  bytesToHex(unsignedTx.getMessageToSign(true)),
  '8ce8c3544ca173c0e8dd0e86319d4ebfe649e15a730137a6659ba3a721a9ff8b',
  'produced the correct transaction hash'
)

Just wondering what "I am not getting" here. 🙂

[g11tech]

@holgerd77 the txMeta (see at L392) changes exactly what you been mentioning

[holgerd77]

👍