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

Linking to capability #2431

Closed
bluesign opened this issue Apr 10, 2023 · 1 comment
Closed

Linking to capability #2431

bluesign opened this issue Apr 10, 2023 · 1 comment

Comments

@bluesign
Copy link
Contributor

Issue to be solved

This idea came out today when discussing hybrid custody (child account) , I wanted to run it with you if it is viable.

Considering I have a capability to &FlowToken.Vault from another account. ( let's say 0x2 ) I am thinking it would be great if I have some kind of option to link to that capability, without writing a proxy contract.

var cap : Capability<&FlowToken.Vault> = ...   [ Capability(account:0x2, borrowType: &FlowToken.Vault, path:/private/flowtokenvault ) ]
acc.save(cap, /storage/cap0x2 )
acc.link<&{FungibleToken.Receiver}>( /public/receiver, /storage/cap0x2)

was this considered before? I can see few edge cases ( bit those are also same for proxy objects )

Suggested Solution

No response

@turbolent
Copy link
Member

That's an interesting idea.

Given the case that the plan is to replace the existing linking API with Capability Controllers, we can maybe discuss this as a follow-up feature once the FLIP got approved (or not).

@bluesign bluesign closed this as completed Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants