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.

Sign up for GitHub

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

Jump to bottom

CIP-0067 | add ADA Handles Virtual SubHandle #504

Closed
wants to merge 1 commit into from
+5 −0
Closed

CIP-0067 | add ADA Handles Virtual SubHandle #504

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CIP-0067/registry.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,11 @@
"class": "NFT",
"description": "CIP-0068 - Datum Metadata Standard (222 sub standard)"
},
{
"asset_name_label": 314,
"class": "Virtual_SubHandle",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if this should be accepted as a valid class. What does this represent?

Copy link
Author

@papag00se papag00se Apr 13, 2023 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An upcoming feature of ADA Handles is SubHandles. A root Handle owner can choose to sell NFT SubHandles that essentially behave just like Handles today. They are actual NFTs that the root Handle owner loses control over the moment it mints and is sent to the new owner.

Virtual SubHandles are SubHandles that the root Handle owner retains control over and can revoke or reassign. This means this particular class of Handle will need to resolve addresses by UTxO datum in the token.

This is to support more corporate or enterprise use cases where SubHandles may be temporarily issued to employees or representatives of the larger entity. It can also support other smaller business use cases of SubHandle "renting".

Virtual SubHandles will have nearly all the same personalization characteristics of Handles.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I should further clarify that since Virtual SubHandles do not have an "Owner Token" component like our CIP-68 Handles/SubHandles will, DApps will need a way to identify them apart from these tokens.
(222) tokens resolve to the address they reside in.
(314) tokens resolve the the address within the UTxO datum

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the (222) Handles - the personalization data will be housed by the (100) Reference Token.
With the (314) Virtual SubHandles - the personalization data will be housed in the token itself.

"description": "ADA Handles Virtual SubHandle"
},
{
"asset_name_label": 333,
"class": "FT",
Expand Down