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

Add USER data model architecture #166

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

Conversation

ctindogaru
Copy link
Collaborator

This PR is a 1:1 copy of https://github.com/near-daos/sputnik-dao-contract/wiki/%5BDRAFT%5D-USER-Data-Model-Architectures to allow easy feedback (via PR comments) on the original proposal.

@ctindogaru
Copy link
Collaborator Author

@TrevorJTClarke

To be honest, I am not sure what's the use case for all of this. Do you have some context on why we created this wiki in the first place? Why do we need a structure for the user etc?

Everything seems overwhelming and it introduces a high complexity to the smart contracts...

// Default could be set with preferences, to either always allow new or always require approval
pub notaries: LookupSet<AccountId>,
// Allows user to control who & types of data allowed to be stored
pub preferences: UnorderedMap<Hash, Vec<u8>>,
Copy link
Collaborator Author

@ctindogaru ctindogaru Apr 27, 2022

Choose a reason for hiding this comment

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

this might be just me, but these names are not very intuitive. What attestations should represent? What attributions should represent? Why do we need notaries etc?

Maybe I'm not understanding the purpose entirely, but everything seems over-engineered.

@TrevorJTClarke TrevorJTClarke self-requested a review April 29, 2022 17:46
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.

1 participant