You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How are we going to handle this on the Stacks side? One idea is an escrow contract from #17.
The escrow contract would need to:
associate the minted NFT with the user that sent the Bitcoin (thinking public key over address here)
provide the ability to claim using a fresh STX address (version 1)
provide the ability to do additional actions, e.g. transfer the NFT (version 2)
One random idea worth thinking through: most NFT mints use the uint as an identifier, but owl.link uses a stringfor the BNS name insead, which got me thinking - could we use a buff to store the public key or other relevant info?
The text was updated successfully, but these errors were encountered:
How are we going to handle this on the Stacks side? One idea is an escrow contract from #17.
The escrow contract would need to:
One random idea worth thinking through: most NFT mints use the
uint
as an identifier, but owl.link uses astring
for the BNS name insead, which got me thinking - could we use abuff
to store the public key or other relevant info?The text was updated successfully, but these errors were encountered: