How to use resize_legacy_inscription_as_uauth / what is uauth?

[zpalmtree]

Hey, sorry for another ticket. Looking into resize after our discussion before.

From what I can tell we're meant to use the libreplex legacy library to interact with the libreplex inscriptions contract.

I think I figured out the correct way to form a resize_legacy_inscription_as_uauth transaction, my accounts seem to match up to a working resize, but is failing with > Program log: AnchorError occurred. Error Code: BadAuthority. Error Number: 6002. Error Message: Bad authority.

My guess is this instruction is meant to be used while the user is creating the inscription, and once its created, I should instead use resize_legacy_inscription_as_holder - but that instruction is commented out.

Here's an example of one of my attempts: https://solscan.io/tx/558XRXN72sDB4fkw4AYbGoSxi1bMGnx5r2HPu2HVTfALmq1aQ55U3aZTApXSurFxz7fUgeo6zZmERHhmcnr7PoV2

My accounts:

Working instruction i found on solscan during a Inscribe transaction:

Only real difference in accounts is the signer, so I think I'm not understanding how the authorization process works

[nilpferdschaefer]

hey there! Your best best would be to look at ResizeLegacyInscriptionAsUAuthTransactionButton in the sample-ui repo. In the legacy case, the inscription update authority is a PDA. It's not a wallet address. If we didn't do this and the legacy metadata UAUTH changed, then the inscription would be stuck with the original UAUTH. So check the PDA calculations and you will be fine! Hope that helps!

…

On Sat, 25 Nov 2023 at 01:29, zpalmtree ***@***.***> wrote: Hey, sorry for another ticket. Looking into resize after our discussion before. From what I can tell we're meant to use the libreplex legacy library to interact with the libreplex inscriptions contract. I think I figured out the correct way to form a resize_legacy_inscription_as_uauth transaction, my accounts seem to match up to a working resize, but is failing with > Program log: AnchorError occurred. Error Code: BadAuthority. Error Number: 6002. Error Message: Bad authority. My guess is this instruction is meant to be used while the user is creating the inscription, and once its created, I should instead use resize_legacy_inscription_as_holder - but that instruction is commented out. Here's an example of one of my attempts: https://solscan.io/tx/558XRXN72sDB4fkw4AYbGoSxi1bMGnx5r2HPu2HVTfALmq1aQ55U3aZTApXSurFxz7fUgeo6zZmERHhmcnr7PoV2 My accounts: image.png (view on web) <https://github.com/LibrePlex/libreplex-program-library/assets/22151537/a85a2991-3e5f-4e92-9582-df8f38667159> Working instruction i found on solscan during a Inscribe transaction <https://solscan.io/tx/Y9dYeonXPqbtkpnbuGaxAifELX9v6NuUggmXFoxSdQJcHKWanLXNpH7eF9jTjfiGMi3TcQckuLdx4wXUxfENgoE> : image.png (view on web) <https://github.com/LibrePlex/libreplex-program-library/assets/22151537/24c0a24d-1c83-4f77-94ad-e1a5df290394> Only real difference in accounts is the signer, so I think I'm not understanding how the authorization process works — Reply to this email directly, view it on GitHub <#70>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASEGJDKPTY5BO4NEY5H3TDYGFCWPAVCNFSM6AAAAAA7ZXH3FCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAYTANBSGUYTAMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[zpalmtree]

Thanks for the assistance. After some further investigation it looks like the signer of the transaction has to be the update authority defined in the metaplex nft metadata.

Do you think it would be possible to alter this to instead use the current holder of the token - or maybe that is the intent of the resize_legacy_inscription_as_holder?

My use case is reclaiming as much rent from an inscription minted/bought of a marketplace for the user currently holding the NFT/token.

Still trying to understand how this token standard functions, apologies if some of the questions seem stupid.

[zpalmtree]

Also seems like all the current inscriptions on the market are immutable, so we won't be able to use resize. Is there any rent that a user can reclaim if they no longer want an inscription they are holding?