search

stacks-network / stacks-core

The Stacks blockchain implementation
https://docs.stacks.co
GNU General Public License v3.0
3.01k stars 671 forks source link

Make sure Atlas tracks attachments updates from BNSv2 as part of the Nakamoto upgrade #5109

Closed 314159265359879 closed 3 weeks ago

314159265359879 commented 2 months ago

Is your feature request related to a problem? Please describe. Atlas currently tracks the BNS contract for changes. It should start tracking BNSv2 attachement updates.

Describe the solution you'd like See quotes in additional context

Describe alternatives you've considered n.a.

Additional context Partial quote from @bilalanees98 (source)

  • Nodes are configured to track attachment events generated through (print …) statements on a smart-contract
  • Once attachments are logged, atlas contacts peers to check if any of them have the attachment data. This data is stored in something called AtlasDB

  • By default they are set to track .bns events here

    • This will have to be updated, nodes will have to track the new bns contract

Quote from @jcnelson (source)

By default they are set to track .bns events here

  • This will have to be updated, nodes will have to track the new bns contract

Can you open an issue on the Stacks blockchain repo so this gets done prior to BNSv2 going live? Presumably, this would be part of the Nakamoto release.

jcnelson commented 3 weeks ago

Seems this won't be necessary since BNSv2 stores the zone file directly in the contract.

blockstack-devops commented 2 weeks ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.