ChainID & NetworkID mixup

[H34D]

Describe the bug

The Ethereum Protocol supports two different identifiers for Networks ChainID and NetworkID

They can be retrieved with:

        const networkId = await this.web3.eth.net.getId()
        const chainId = await this.web3.eth.getChainId()

Using NetworkId for ChainId and vice versa can lead to unexpected problems on networks where they are different.

Additional info can be found here: https://besu.hyperledger.org/en/stable/Concepts/NetworkID-And-ChainID/

sdk-js/src/events/ContractEvent.ts

Lines 37 to 52 in 5858c0c

	public async getPastEvents(options: EventOptions): EventResult {
	const chainId = await this.web3.eth.net.getId()
	options.fromBlock = 0
	options.toBlock = 'latest'
	// Temporary workaround to work with mumbai
	// Infura as a 1000 blokcs limit on their api
	if (chainId === 80001 || chainId === 42) {
	const latestBlock = await this.web3.eth.getBlockNumber()
	options.fromBlock = latestBlock - 99
	}
	const data = await this.getEventData(options)
	return data
	}

sdk-js/src/keeper/contracts/ContractBase.ts

Lines 203 to 209 in 5858c0c

	// TODO: https://github.com/nevermined-io/sdk-js/issues/265
	// If the error is because of no support for eip-1559, just continue
	const chainId = await this.web3.eth.net.getId()
	// no eip-1559 support
	if (![42220, 44787, 80001, 8997, 137].includes(chainId)) {
	throw new KeeperError(err)
	}

Peer-to-peer communication between nodes uses the network ID, 
while the transaction signature process uses the chain ID.

sdk-js/src/keeper/contracts/ContractBase.ts

Lines 214 to 223 in 5858c0c

	const chainId = await this.web3.eth.net.getId()
	if (chainId == 44787 || chainId == 42220) {
	console.log('Calling Celo...')
	txparams = {
	from,
	value,
	gas,
	gasPrice
	}
	}

To Reproduce

Steps to reproduce the behavior:
1.
2.

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.