Skip to content

Tx Replay: Signer detects forks and updates state machine with replay transactions #5968

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

Closed
hstove opened this issue Mar 31, 2025 · 0 comments · Fixed by #6020
Closed

Tx Replay: Signer detects forks and updates state machine with replay transactions #5968

hstove opened this issue Mar 31, 2025 · 0 comments · Fixed by #6020
Assignees
Milestone

Comments

@hstove
Copy link
Contributor

hstove commented Mar 31, 2025

When a signer detects that a Bitcoin fork occurs, the signer constructs the transaction replay set by performing the following:

  • Determine the set of orphaned bitcoin blocks
  • Determine the set of orphaned stacks blocks
  • Go through each of those stacks blocks and generate a list of all transactions (in order)

Once the replay set is determined, the signer broadcasts and update to their local state machine with the replay set.

@github-project-automation github-project-automation bot moved this to Status: 🆕 New in Stacks Core Eng Mar 31, 2025
@hstove hstove self-assigned this Apr 9, 2025
@hstove hstove added this to the 3.1.0.0.8 milestone Apr 9, 2025
@hstove hstove moved this from Status: 🆕 New to Status: 💻 In Progress in Stacks Core Eng Apr 9, 2025
@aldur aldur modified the milestones: 3.1.0.0.8, 3.1.0.0.9 Apr 10, 2025
@aldur aldur modified the milestones: 3.1.0.0.9, 3.1.0.0.10 May 6, 2025
@hstove hstove moved this from Status: 💻 In Progress to Status: In Review in Stacks Core Eng May 7, 2025
@hstove hstove linked a pull request May 7, 2025 that will close this issue
@hstove hstove closed this as completed May 12, 2025
@github-project-automation github-project-automation bot moved this from Status: In Review to Status: ✅ Done in Stacks Core Eng May 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

2 participants