[EVM] Bridged account creation event consolidation

[sideninja]

Currently, the event emitted for COA account creation doesn't have a type that is consistent with other EVM events. The event type ID right now is: A.f8d6e0586b0a20c7.EVM.BridgedAccountCreated.

This is wrong for two reasons:

• we renamed bridged accounts to COA
• other EVM service events have the ID schema of: EVM.{name}

The event should probably be renamed to: EVM.COACreated or EVM.CreatedCOA.

[ramtinms]

I think we ideally should do the reverse, emitting all the events with type A.f8d6e0586b0a20c7.X then we don't need any special handling on access nodes or flow go. thoughts?

[ramtinms]

then if we shard multiple EVMs the events won't cause any issue.

[sideninja]

Consensus is to move back to generic event type ID A.{address}.EVM.{name}

cc @ramtinms @m-Peter

[m-Peter]

Sounds good 👍 This will only require a small change in the EVM Gateway, for the indexer component.

[m-Peter]

We should also include the event definitions in the EVM contract itself, for example:

access(all)
event BlockExecuted(
    height: UInt64,
    hash: String,
    totalSupply: Int,
    parentHash: String,
    receiptRoot: String,
    transactionHashes: [String]
)

access(all)
event TransactionExecuted(
    blockHeight: UInt64,
    blockHash: String,
    transactionHash: String,
    encodedTransaction: String,
    failed: Bool,
    vmError: String,
    transactionType: UInt8,
    gasConsumed: UInt64,
    deployedContractAddress: String,
    returnedValue: String,
    logs: String
)

This will be helpful for other tools (such as the Cadence testing framework), to make use of these types.

[sideninja]

The consensus was to just rollback special even type IDs for EVM, and use the generic type ID signature.