Skip to content
Discussion options

You must be logged in to vote

Yes, a resource account can be used to create another resource account.

If you publish a module under a resource account (create_resource_account_and_publish(&signer, SEED)), and in that module's init_module you call create_resource_account(&signer, SEED), there is no logic that verifies that the origin signer reference is another resource account. You can see this here.

Essentially, create_resource_account(&signer, SEED) will create a new resource account, and the original resource account will be the owner. The signer_cap will be stored in the original resource account's Container resource. You can see that logic here.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@jojothomas1515
Comment options

@kshitijc1506
Comment options

Answer selected by kshitijc1506
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resource-account Questions about resource account
2 participants