Is there a way to completely burn/discard an object?

[0xbe1]

Discord user ID

No response

Describe your question in detail.

I want to figure out a way to burn/discard an object so that it's not revertable.

What error, if any, are you getting?

No response

What have you tried or looked at? Or how can we reproduce the error?

There's a burn method in the object module however the object can be unburnt by calling the unburn method.

Wonder if there's a way to ensure the object is not redeemable by the original owner.

Which operating system are you using?

macOS

Which SDK or tool are you using? (if any)

TypeScript SDK

Describe your environment or tooling in detail

No response

[0xbe1]

Seems this recent PR addresses it

aptos-labs/aptos-core#13495

[kshitijc1506]

Hey @0xbe1, this PR ensures that the original owner cannot reclaim an object after a soft burn, but only if TransferRef is used before reclaim.

^This was originally possible since we didn't remove the TombStone struct in object::transfer_with_ref.

To address your original question, a user can still call burn and then unburn.

If you want to make sure that the object is discarded, you should use the DeleteRef. This will remove the object from global storage instead of transferring it to the burn address.

[0xbe1]

@kshitjee ty for clarification. tbh it is confusing that burn doesn't really burn an object, wonder if we should make it clear in the document that it is soft deletion and people should use delete for a real deletion?

[kshitijc1506]

That's a fair assessment. Thanks for the feedback, will have a PR in for this soon.

[kshitijc1506]

@0xbe1 note that named objects cannot be deleted. If using named objects is crucial for your use case, a possible workaround is to create a boolean flag and store it in the object.

I will also be adding this information to the documentation later, as I noticed that the only place it is currently mentioned (AFAIK) is in the comments above object::create_named_object.