Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
314159265359879 opened this issue Aug 23, 2024 · 2 comments
Assignees
Labels

Comments

@314159265359879
Copy link

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
Copy link
Member

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

@github-project-automation github-project-automation bot moved this from Status: 🆕 New to Status: ✅ Done in Stacks Core Eng Oct 22, 2024
@blockstack-devops
Copy link
Contributor

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.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Oct 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Status: Status: ✅ Done
Development

No branches or pull requests

4 participants