You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to differentiate between "native" credits and "non-native" credits. We also need to differentiate between credits issued through the registry program and credits issued independent of the registry program.
This could be solved with the curation module (#890) and/or registries as on-chain entities (#1459).
Problem Definition
The non-blockchain market generally does not accept credits that have been issued through a one-way bridge. A user should be able to differentiate between "native" credits and "non-native" credits in the marketplace.
Not all "native" credits will be issued through the registry program and therefore we also need to differentiate between credits issued through the registry program and credits issued independent of the registry program.
Proposal
[ WIP ]
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Summary
We need to differentiate between "native" credits and "non-native" credits. We also need to differentiate between credits issued through the registry program and credits issued independent of the registry program.
This could be solved with the curation module (#890) and/or registries as on-chain entities (#1459).
Problem Definition
The non-blockchain market generally does not accept credits that have been issued through a one-way bridge. A user should be able to differentiate between "native" credits and "non-native" credits in the marketplace.
Not all "native" credits will be issued through the registry program and therefore we also need to differentiate between credits issued through the registry program and credits issued independent of the registry program.
Proposal
[ WIP ]
For Admin Use
The text was updated successfully, but these errors were encountered: