Kartik Soneji

Hi @samia-invozone If you are facing the same issue can you please provide a minimum reproducible example, or the steps you took to setup the project so I can replicate...

Hi @aeaa1998 Is there any particular reason you are polyfilling the crypto module?

Creating a master edition requires the updateAuthority to be a signer: https://github.com/metaplex-foundation/js/blob/6fcb0b6ffe616eb8a30933799b23d7495f80ab24/packages/js/src/plugins/nftModule/operations/createNft.ts#L72-L82 This can be worked around by adding an instruction to transfer the update authority immediately after minting Something...

> > The loading attribute can have the value eager and lazy > > That's true, but eager is the default. So there's no point specifying it. That's what allows...

> > I don't think there is an easy way to do that with options? > > Yes there is. It would be `image-lazy-option` if we were to go that...

In that case, I think an attribute will result in cleaner markup? Additionally, since the HTML spec specifies `loading=lazy` and `loading=eager`, I feel it makes more sense to mirror that....

@mojavelinux any update on the issue? I'll be happy to create a PR for whichever form you think is best.

@dscho Thanks for the permission. I already submitted the patch using submitGit. > Please note that you don't have to sign-off the PR description :-) Good to know.

I would be open to implementing this if @niftylettuce is open to merging the PR. > To protect your revenue stream you could rotate the key quarterly making it a...

Hmm, good point. I see two potential solutions: 1. Concatenate all configuration records together, encrypt the whole thing, then split into 200 character lines. Additionally, that will allow switching to...