8000 Establish one-to-one binding for capabilities · Issue #94 · econia-labs/econia · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Establish one-to-one binding for capabilities #94

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.

Sign up for GitHub

By clicking &l 8F93 dquo;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

Jump to bottom
Open
alnoki opened this issue Mar 20, 2023 · 0 comments
Open

Establish one-to-one binding for capabilities #94

alnoki opened this issue Mar 20, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@alnoki
Copy link
Member
alnoki commented Mar 20, 2023

Presently, custodian capabilities and underwriter capabilities can become a contended resource if they are used in multiple contexts.

Hence a binding schema is proposed, whereby a capability contains a field(s) describing the context in which it should be used.

Also proposed is a "duplicate_cap()" function, which creates a new unbound capability instance from a bound capability, for example so that multiple accounts can be presided over by the same custodian without transaction collisions.
@alnoki alnoki added the enhancement New feature or request label Mar 20, 2023
@alnoki alnoki changed the title Establish one-to-one binding for capabilities. Establish one-to-one binding for capabilities Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alnoki
0