Resources and Transactions
Transaction samples to get you started
What you probably need
We anticipate that most applications will fall under one of two categories.
Share all NFT Collections with a parent, and nothing else
Share some NFT Collections with a parent, and nothing else
Importantly, both of these setup options give no access to Fungible Token capabilities that are not on public paths. Below are some sample transactions depending on the kind of steps you want to follow. You can deploy your own version of the CapabilityFactory and CapabilityFilter resources should you want to customize their behavior
Pre-made resources
Flow has created a few common resources for you to use. If you would like to set your own up, you can find a link to set transactions for each resource to run on your own account to get the same effect.
What Capability types can be obtained?
The CapabilityFactory used in a ChildAccount resource is used to express what types T
can be obtained from a child account from a parent. For example, a CapabilityFactory with an entry that can return Capability<&{NonFungibleToken.Provider}>
would be giving the ability for a parent to obtain NFT Provider capabilities.
A Capability can only be obtained if a child account's CapabilityFilter permits it, there is a CapabilityFactory for the type of the Capability requested, and the path being requested exists.
The order of types specified by a CapabilityFactory matter! There is an open ticket to handle this. Until it is settled, please take note of the types you are linking or expecting to be accessible.
Capability Factory pre-made resources
Capability Filter pre-made resources
Common Transactions
Last updated