How to ensure a smart contract doesnt resend a capability?

Question

Im working on a smart contract and I want to ensure that it doesnt send a capability if the user already owns one. This is to avoid unwanted transactions. I am thinking about using an SDK to check all objects a user holds and perhaps using a sui::table::Table to keep a list of minted capabilities. Is this the right approach, or is there a better way to confirm if an address holds a certain object on-chain?

dudley_smith · Accepted Answer

A suggestion for your use case is to keep a list of addresses that have had a capability minted in a shared object. You can manage object size restrictions by using a sui::table::Table, which allows you to maintain a list/map efficiently.

cod · Answer

You can try using the SDK to check for all objects a user holds off-chain. This might help you validate ownership without impacting the on-chain contract flow.

Grizzly · Answer

You might not need an on-chain check for this use case. If you want users to prove they own an object, require them to input proof of ownership.

Post

Share your knowledge.

How to ensure a smart contract doesn't resend a capability?

Answers

Do you know the answer?

Earn Your Share of 1000 Sui