Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Number of collections and ownership transfer during the seller update #784

Open
1 task
zajck opened this issue Aug 29, 2023 · 0 comments
Open
1 task

Number of collections and ownership transfer during the seller update #784

zajck opened this issue Aug 29, 2023 · 0 comments

Comments

@zajck
Copy link
Member

zajck commented Aug 29, 2023

If the number of collections gets too high, it might become impossible to update the seller because of

uint256 collectionCount = sellersAdditionalCollections.length;
for (uint256 j = 0; j < collectionCount; ) {
// Additional collections (if they exist)
IBosonVoucher(sellersAdditionalCollections[j].collectionAddress).transferOwnership(sender);
unchecked {
j++;
}

Options

  1. Create a new protocol limit maxCollectionsPerSeller. After the seller reaches it, createNewCollection reverts
  2. Enable removing existing collections
  3. Change the voucher implementation to not store the owner in its storage, but retrieves it from the protocol when needed.

Note

It's not critical now, since the maximum number of collections before running into the problem should be relatively high.

Tracking issue for:

@zajck zajck changed the title Number of collections and ownership transfer during the Number of collections and ownership transfer during the seller update Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant