a16z-contracts
a16z-contracts copied to clipboard
a16z
upgradable
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
The license text could provide that rights cannot be withdrawn from the owner - i.e., the owner's rights are cumulative across versions.
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. For example, I would like to integrate an ability to offer one hand-signed print to the wallet holder, but haven't yet found a solution.
Is there a problem with placing a custom license in a "Hidden" property of an ERC721?
On Oct 24, 2022, at 2:26 PM, Mason Hall @.***> wrote:
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 https://github.com/Akira-Taniguchi — Reply to this email directly, view it on GitHub https://github.com/a16z/a16z-contracts/pull/5#issuecomment-1289422603, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQTEXLISR4XYM3E2D3RQXTWE3IGVANCNFSM6AAAAAAQDAYLBE. You are receiving this because you are subscribed to this thread.
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.