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

upgradable #5

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

Akira-Taniguchi
Copy link

Tests will be added after this pull request passes.

@Akira-Taniguchi
Copy link
Author

@fmhall
@Blauyourmind

please jeck it

@fmhall
Copy link
Collaborator

fmhall commented Oct 24, 2022

Part of the challenge here is that NFT owners expect the License they have to be immutable, or at the very least, at least as beneficial to them as it was when they purchased. Enabling upgradeability would give creators the ability to restrict the permissions given to NFT holders at any point, which kind-of defeats the purpose. Would be curious to get your perspective @Akira-Taniguchi

@HazardJ
Copy link

HazardJ commented Oct 24, 2022

The license text could provide that rights cannot be withdrawn from the owner - i.e., the owner's rights are cumulative across versions.

@flatout
Copy link

flatout commented Oct 24, 2022 via email

@fmhall
Copy link
Collaborator

fmhall commented Oct 24, 2022

The license text could provide that rights cannot be withdrawn from the owner - i.e., the owner's rights are cumulative across versions.

The licenses will contradict each other if combined, but I see your general point - I think the same is being made below:

While I understand your argument, the converse holds as well. I would like to UPGRADE a customer's license as more opportunities become available for the user. Not to take away opportunities.

And I agree this would be a valuable feature. I think the best way to do it would be to allow owners to upgrade their licenses, but only if they are moving from a restrictive license to a more permissible one. For example, they could go from "No hate speech" to cc0, but not the other way around. If you agree with this solution, feel free to modify the PR to support it, or start a new one. Alternatively we can work on this internally.

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

Successfully merging this pull request may close these issues.

None yet

4 participants