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
This provides pretty average UX / DX in that the ownerMUST always be the same as the signer for stamps applied to chunks. This is a large handbrake on some particularly important features that would greatly smooth UX / DX.
Solution
Considering that stamps that have been processed by Swarm clients are in effect immutable, I propose:
The owner field is changed to a signer field. This represents the public address of the signer that must sign the chunks, as inspected by Swarm clients when exchanging data over Swarm. The signer would still effectively have root control over the batch.
An owner field is created, which can be instantiated on createBatch to a custom address. This owner has the additional benefits of being able to call dilute the batch and set a delegate as described below.
A delegate field (or better terminology TBD), which is configurable on createBatch, and configurable by owner. This field can also call the topUp and dilute functions for the respective batch.
Use cases
This allows for atomic dilution of a batch to increase it's capacity. Mandating that dilute can only be called by the owner requires the owner to posses gas, which prohibits smart contracts / smart contract wallets from possessing batches, which is prohibitively exclusive given the moves towards account abstraction.
The text was updated successfully, but these errors were encountered:
Actually, a much tighter solution to this would be to enable an EIP-712 signatures on dilute so that owner could sign a dilute. This would represent significant UX/DX experience, allowing for many dilutes to be batched effectively, and atomically.
Problem
Refer to the postage batch struct:
storage-incentives/src/PostageStamp.sol
Lines 61 to 74 in e97ec10
This provides pretty average UX / DX in that the
owner
MUST always be the same as the signer for stamps applied to chunks. This is a large handbrake on some particularly important features that would greatly smooth UX / DX.Solution
Considering that stamps that have been processed by Swarm clients are in effect immutable, I propose:
owner
field is changed to asigner
field. This represents the public address of the signer that must sign the chunks, as inspected by Swarm clients when exchanging data over Swarm. Thesigner
would still effectively have root control over the batch.owner
field is created, which can be instantiated oncreateBatch
to a custom address. Thisowner
has the additional benefits of being able to call dilute the batch and set adelegate
as described below.delegate
field (or better terminology TBD), which is configurable oncreateBatch
, and configurable byowner
. This field can also call thetopUp
anddilute
functions for the respective batch.Use cases
This allows for atomic dilution of a batch to increase it's capacity. Mandating that
dilute
can only be called by theowner
requires theowner
to posses gas, which prohibits smart contracts / smart contract wallets from possessingbatches
, which is prohibitively exclusive given the moves towards account abstraction.The text was updated successfully, but these errors were encountered: