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

how does a user get powers for use with contractStarter? #14

Open
dckc opened this issue Jan 13, 2024 · 1 comment · May be fixed by #17
Open

how does a user get powers for use with contractStarter? #14

dckc opened this issue Jan 13, 2024 · 1 comment · May be fixed by #17
Labels
question Further information is requested

Comments

@dckc
Copy link
Collaborator

dckc commented Jan 13, 2024

The test where starterSam starts the postalSvc starts by giving him namesByAddress. How would that happen? It seems like postalSvc is privileged... or is it? We could just put namesByAddress in vstorage. It's low-privilege.

What's a good path for it? put it near published.wallet? Perhaps published.walletNames?
Probably best not to make up a new name now. Better stick with published.namesByAddress.

@dckc
Copy link
Collaborator Author

dckc commented Jan 13, 2024

permit named powers in contractStarter?

The namesByAddress case is easy because it's OK to publish.

But in general, supplying privateArgs in a contractStarter offer is infeasible: clients can only marshal objects that are on the board, which conflicts with them being private.

So perhaps use a permit system a la core-eval.

  • subsume vstoreShop with a structured permit for vstorage nodes?
  • avoid naming hazards using boardIDs again?

@dckc dckc changed the title how does a user get namesByAddress to start postalSvc? how does a user get powers for use with contractStarter? Jan 14, 2024
@dckc dckc added the question Further information is requested label Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant