search

JoinColony / colonyCDapp

An iteration of the Colony Dapp sporting both a fully decentralized operating mode, as well as a mode enhanced by a metadata caching layer
5 stars 13 forks source link

Handling more than one action in transaction (multicall) #2317

Open jakubcolony opened 5 months ago

jakubcolony commented 5 months ago

Specification

Since the current implementation of actions uses transaction hash as ID, it will only create the first action in a transaction and skip any further potential actions.

This issue will capture the details and subtasks to remove this limitation.

The initial idea revolves around appending a log index to transaction hash to create an ID that's unique for an event instead of a transaction.

jakubcolony commented 4 months ago

We need to consider how this will impact clickable transaction in the user hub. The current idea to facilitate multiple actions is to append the log index to action ID but this is something that the Transaction model is unaware of.