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
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.
The text was updated successfully, but these errors were encountered:
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
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
linked a pull request
Jan 14, 2024
that will
close
this issue
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 putnamesByAddress
in vstorage. It's low-privilege.What's a good path for it? put it near
published.wallet
? Perhapspublished.walletNames
?Probably best not to make up a new name now. Better stick with
published.namesByAddress
.The text was updated successfully, but these errors were encountered: