Feature/l1bridge2infoindexsync

[arnaubennassar]

Review guide

aggoracle

Reviewers: @rachit77
Notes:

• Encapsulated the code to setup the env into functions in a new package test/helpers, actual code is unchanged

bridgesync

Reviewers: @goran-ethernal @Stefan-Ethernal
Notes:

• Addeed config and minor changes to run from cmd
• Added E2E test using simulator covering the bridge event (claim event still missing)
• Added missing db tx closing on the processor + debugger has prefix to know if it's the syncer of L1 or L2

claimsponsor

Reviewers: @begmaroman @ToniRamirezM
Notes:

• new component in charge of sending claims on behalf of the user to the L2

cmd & config

Reviewers: @vcastellm @rachit77
Notes:

• Added new component RPC
• Restructured the logic following the pattern of isNeeded?: have all the sub-components declared before the component switch / case so they can be re-used
• Lots of work to clean the config file, and everything in general. Didn't wanted to go all the way through, but done some cleaning
• @rachit77 please check that the configs for the "block finality" match with your work on another PR (on the underlaying packages)

l1bridge2infoindexsync

Reviewers: @goran-ethernal @Stefan-Ethernal
Notes:

• new syncer to track the relation of L1 bridge -> includded on L1 info tree index
• a bit different to previous syncers that depend strictly on EVM, this one depends on other syncers as well

l1infotreesync

Reviewers: @goran-ethernal @Stefan-Ethernal
Notes:

• Exposed some methods
• Update interface for proofs []common.Hash -> [32]common.Hash (this is gonna be a recurring topic, just mentioning here)
• Added missing rollbacks on processor

lastgersync

Reviewers: @ToniRamirezM @begmaroman
Notes:

• new syncer to track the injected GERs on L2
• a bit different to previous syncers as it doesn't relay on events but on eth_calls

reorgdetector

@begmaroman @goran-ethernal FYI I've comented a bunch of code as it was giving problems, and this is being re-worked on another branch

rpc

Reviewers: @vcastellm @rachit77
Notes:

• RPC server with the endpoints for the bridge_ namespace
• Have tested it here

sync

Reviewers: @goran-ethernal @Stefan-Ethernal
Notes:

• Made some stuff public to be reused on other syncers
• Added log with prefix so we can know from which syncer the logs come from

test/helpers

reviewers: @rachit77
notes: linked to the aggoracle

tree

Reviewers: @goran-ethernal @Stefan-Ethernal
Notes:

• []common.Hash -> [32]common.Hash
• Other minor changes and fixes

[joanestebanr]

maybe make more sense to do singleton lazy initialization? then you avoid double knownledge, if you have an error on list of components that require a object could be difficult to find it... it's more simple to create objects when are required:

aggOracle := createAggoracle(*c, l1Client(), l2Client(), l1InfoTreeSync() )

To create the constructor function can use sync.OnceValue. Example:

l1Client:= sync.OnceValue[*ethclient.Client]( func() *ethclient.Client]{
    l1CLient, err := ethclient.Dial(urlRPCL1)
	if err != nil {
		log.Fatal(err)
	}
	return l1CLient
})

[arnaubennassar]

this sounds like a great idea. Would u mind moving this into another PR tho? This PR is already gigantic, and there is a lot of work to do in terms of config + cmd, I think that your suggestion would be great on that scope?

(if you agree I'd make sure that we have the right ticket for it, and link ur suggestion in there)

[rachit77]

LGTM

[joanestebanr]

The PR does'nt pass the checks

[sonarcloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud