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
Our users want to optimise their cluster operations, thus creating a scenario when 2-4 execution environments (like 4 OPStack chains) are using 1 celestia light node. However, each of the exec env is submitting blobs TXs from their own celestia account. Which brings us to a bad UX, where we have 4 accounts that needs to be funded and tracked.
With fee grant module and signer implementation done on node side, we can eliminate this situation. Meaning that each of the new celestia account for the exec env can be created and granted permissions from a single account to pass fee payments
Implementation ideas
ATM, we need something like a --fee-account $account_address for node's part. This is needed for blob submission
So we can have the following scenario:
Light node is initialised/started with an A account with 0 balances
Background
Our users want to optimise their cluster operations, thus creating a scenario when 2-4 execution environments (like 4 OPStack chains) are using 1 celestia light node. However, each of the exec env is submitting blobs TXs from their own celestia account. Which brings us to a bad UX, where we have 4 accounts that needs to be funded and tracked.
With fee grant module and signer implementation done on node side, we can eliminate this situation. Meaning that each of the new celestia account for the exec env can be created and granted permissions from a single account to pass fee payments
Implementation ideas
ATM, we need something like a
--fee-account $account_address
for node's part. This is needed for blob submissionSo we can have the following scenario:
A
account with 0 balancesA
account perms to pass the fee payments to itThe text was updated successfully, but these errors were encountered: