You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Claims created by a node are sent to a rollups-claims stream and further processed by the authority-claimer, which works well in a regular rollups-node
A rollups-node running the experimental sunodo validator mode on the sunodo designated provider will point to an external standalone authority-claimer, which expects to handle claims from multiple applications via a single rollups-claims stream.
Such scenario is not currently supported.
However, we could extend the current rollups-node capabilities to allow for that, so that a standalone authority-claimer could be configured to support publishing claims for multiple applications running on the same chain.
Create application-specific rollups-claims streams, identified by the application address and the chain-id, the same way its rollups-inputs and rollups-outputs counterparts
Extend the authority-claimer so it can handle multiple rollups-claims streams simultaneously when running on standalone mode
📈 Subtasks
advance-runner
add support to application-specific rollups-claims streams
improve tests
authority-claimer
add support to application-specific rollups-claims streams
allow configuration of the applications to be managed by the claimer when running on standalone mode
update command line program
improve tests
The text was updated successfully, but these errors were encountered:
📚 Context
Claims created by a node are sent to a
rollups-claims
stream and further processed by the authority-claimer, which works well in a regular rollups-nodeA rollups-node running the experimental sunodo validator mode on the sunodo designated provider will point to an external standalone authority-claimer, which expects to handle claims from multiple applications via a single
rollups-claims
stream.Such scenario is not currently supported.
However, we could extend the current rollups-node capabilities to allow for that, so that a standalone authority-claimer could be configured to support publishing claims for multiple applications running on the same chain.
This would address the case described at #522.
✔️ Solution
rollups-claims
streams, identified by the application address and the chain-id, the same way itsrollups-inputs
androllups-outputs
counterpartsrollups-claims
streams simultaneously when running on standalone mode📈 Subtasks
rollups-claims
streamsrollups-claims
streamsThe text was updated successfully, but these errors were encountered: