Wrong owner of bns name

[friedger]

Describe the bug
The endpoint https://stacks-node-api.mainnet.stacks.co/v1/names/ape.mega shows SPC0KWNBJ61BDZRPF3W2GHGK3G3GKS8WZ7ND33PS as owner. However, the nft is owned by SPV48Q8E5WP4TCQ63E9TV6KF9R4HP01Z8WS3FBTG through tx https://explorer.stacks.co/txid/0xf9f9144793f6d4da9aba92a54ab601eb23bfe7f44c1edb29c2920bf5e7d2ac16?chain=mainnet

To Reproduce
Compare the two links provided

Expected behavior
the endpoint should show SPV48Q8E5WP4TCQ63E9TV6KF9R4HP01Z8WS3FBTG as owner

[rafaelcr]

Thanks @friedger ... this looks like it's caused by the API not handling a name-register and name-transfer in the same transaction. I'll take a further look.

[blockstack-devops]

🎉 This issue has been resolved in version 6.0.0-beta.9 🎉

The release is available on:

• npm package (@beta dist-tag)
• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[badonyx]

The endpoint is not consistently showing the correct address still. Oddly it is switching back and forth when I fetch the endpoint a few times.

[rafaelcr]

@0xbabo that behavior is part of our normal release process... we're deploying the API v6 right now (which contains the fix) but we do a rollout so we can slowly send traffic into the new env. If everything looks good we do the full switch, which as far as I can see is going along fine and will happen perhaps tomorrow.

[badonyx]

Thanks for the update. Probably worth noting that this actually resulted in 2 erroneous NFT transfers just last night, but I think I can contact the Ryder address owners to sort it out.

[blockstack-devops]

🎉 This issue has been resolved in version 6.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀