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

helpers around management of non-fungible tokens and their token mappings #65

Closed
Tracked by #56
hathbanger opened this issue Apr 3, 2024 · 1 comment
Closed
Tracked by #56

Comments

@hathbanger
Copy link
Contributor

hathbanger commented Apr 3, 2024

basically, we need to start building guardrails helpers around the data field in a non-fungible program. The data field is arbitrary data but if we provide them w tooks that can make it easy for them to manage structured data in the data field, it will help developers out immensely with working with data that is specific to tokenIds.

have some good stuff in this commit here: dca7fc3

@hathbanger hathbanger mentioned this issue Apr 3, 2024
13 tasks
@hathbanger
Copy link
Contributor Author

closing this as i may have been overthinking how we approach data mgmt. THIS ISSUE helps clarify my new direction here..

TLDR: avoid needing to deal with too much nesting in the data field. i've started to using more verbose keys i.e. tweet-<iso_date> or pokemon-<token_id>

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