Sending to BNS names

[314159265359879]

---- Stacks ---- Sending to a BNS name on stacks can still direct to an address that is holding the BNSv1 name after the BNSv2 name has been transferred.

I think we should only send to the address holding the BNSv2 name from now on.

Here is an example (address displayed is holding only the BNSv1 name, not the BNSv2 name):

Expected address (holding BNSv2 name): SP3TMEPFJJBVKVFVHYZTY0D3VXPQ8JMQ2DWP49H90

---- Bitcoin ---- Sending to BNS names on Bitcoin is supported through bitcoin addresses stored in zonefiles. I think we may need users to send a new transaction to create these updates for the BNSv2 names if they do not reset when a BNSv2 name is transferred and the BNSv1 name remains in the old address.

Upon registering a .locker a Stacks and Bitcoin address are registered with the name. Right now these are not yet found by the API we use, should they?

[linear[bot]]

LEA-1721 Sending to BNS names

[314159265359879]

I see Phillip just posted this he's working on a document with more details about the migration and updates in BNSv2 to zonefiles:

https://discord.com/channels/621759717756370964/895784652630032384/1305685686065823816

[alter-eggo]

@314159265359879 re: stacks address, I've checked cristina.btc, and seems wallet shows right address? check bns v2 api: https://api.bnsv2.com/names/cristina.btc

[alter-eggo]

@314159265359879 SP3TMEPFJJBVKVFVHYZTY0D3VXPQ8JMQ2DWP49H90 this address owns cristina.stx, not cristina.btc 🤔

[314159265359879]

@alter-eggo that is silly, I see it now too ( will edit the first post). and the current wallet is resolving cristina.stx to the BNSv1 owner

[alter-eggo]

@314159265359879 I believe we can close this one right ?

[camerow]

Yeah, I believe this one is done! Thanks @alter-eggo