Skip to content

Conversation

@delbonis
Copy link
Contributor

@delbonis delbonis commented May 22, 2025

Description

See STR-1415.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature/Enhancement (non-breaking change which adds functionality or enhances an existing one)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactor
  • New or updated tests
  • Dependency Update

Notes to Reviewers

Unsure if this actually fixes the issue.

Checklist

  • I have performed a self-review of my code.
  • I have commented my code where necessary.
  • I have updated the documentation if needed.
  • My changes do not introduce new warnings.
  • I have added (where necessary) tests that prove my changes are effective or that my feature works.
  • New and existing tests pass with my changes.

Related Issues

@codecov
Copy link

codecov bot commented May 22, 2025

Codecov Report

Attention: Patch coverage is 7.69231% with 24 lines in your changes missing coverage. Please review.

Please upload report for BASE (releases/0.2.0@9a568c5). Learn more about missing BASE report.

Files with missing lines Patch % Lines
crates/chaintsn/src/transition.rs 10.00% 18 Missing ⚠️
crates/state/src/state_op.rs 0.00% 6 Missing ⚠️
@@                Coverage Diff                @@
##             releases/0.2.0     #821   +/-   ##
=================================================
  Coverage                  ?   52.32%           
=================================================
  Files                     ?      298           
  Lines                     ?    32842           
  Branches                  ?        0           
=================================================
  Hits                      ?    17183           
  Misses                    ?    15659           
  Partials                  ?        0           
Files with missing lines Coverage Δ
crates/state/src/state_op.rs 30.69% <0.00%> (ø)
crates/chaintsn/src/transition.rs 42.78% <10.00%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions
Copy link
Contributor

github-actions bot commented May 22, 2025

Commit: a67985e

SP1 Execution Results

program cycles success
Bitcoin Blockspace 71,442
EVM EE STF 567,414
CL STF 166,201
Checkpoint 4,232

@delbonis delbonis requested a review from storopoli May 27, 2025 18:51
@delbonis delbonis marked this pull request as ready for review May 28, 2025 18:47
@delbonis delbonis requested review from a team as code owners May 28, 2025 18:47
@delbonis
Copy link
Contributor Author

Okay I am not sure how to resolve this conflict, it seems like some nontrivial change from I'm not sure where. @storopoli

@Rajil1213
Copy link
Contributor

Rajil1213 commented May 28, 2025

Okay I am not sure how to resolve this conflict, it seems like some nontrivial change from I'm not sure where

What do you mean? Looks like the changes are from the release/* branch?

@storopoli
Copy link
Member

Okay I am not sure how to resolve this conflict, it seems like some nontrivial change from I'm not sure where. @storopoli

Wait, is this already on main? Because your target branch is releases/0.2.0. Is this intentional?

@delbonis
Copy link
Contributor Author

@storopoli Should I be merging into main first and then backport?

@storopoli
Copy link
Member

@storopoli Should I be merging into main first and then backport?

Yes!

@storopoli
Copy link
Member

@delbonis heads up! alpenlabs/strata-bridge#154 was merged with alpn.

Copy link
Contributor

@bewakes bewakes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor nits

@storopoli storopoli removed request for a team June 9, 2025 17:05
@storopoli storopoli force-pushed the STR-1415-fix-withdrawal-fulfillments branch from b64d026 to 40341fd Compare June 9, 2025 17:05
@storopoli
Copy link
Member

@delbonis I've rebased this and set the target branch to main.
Let's first get the fix into main then we backport the squash commit that lands on main into releases-0.2.0.

As a heads up here MAGIC_BYTES is "ALPN" whereas in strata-bridge already merged is "alpn" (lowercase). Either we change here to lowercase or we merge this as UPPERCASE and I open a PR in strata-bridge to s/alpn/ALPN/ all over the place.

@barakshani
Copy link
Contributor

As a heads up here MAGIC_BYTES is "ALPN"

Don't we take this value from rollup name?

@storopoli
Copy link
Member

As a heads up here MAGIC_BYTES is "ALPN"

Don't we take this value from rollup name?

we have tag rollup_name da-tag all of these are header bytes that identify an OP_RETURN, hence MAGIC_BYTES.

@barakshani
Copy link
Contributor

As a heads up here MAGIC_BYTES is "ALPN"

Don't we take this value from rollup name?

we have tag rollup_name da-tag all of these are header bytes that identify an OP_RETURN, hence MAGIC_BYTES.

I meant, if this is an externally provided parameter, why do we need to change something in this PR?

@storopoli
Copy link
Member

I meant, if this is an externally provided parameter, why do we need to change something in this PR?

In this PR (and in strata-bridge) is mostly for tests and mocking stuff. It would be nice to have the same value in both repos.

@delbonis
Copy link
Contributor Author

delbonis commented Jun 9, 2025

@storopoli

(in ref to)

As a heads up here MAGIC_BYTES is "ALPN"

This PR doesn't specify any value for the magic. It reads it from the rollup_name field. There is a constant in tests, but that's irrelevant for deployment.

@delbonis
Copy link
Contributor Author

delbonis commented Jun 9, 2025

Oh

It would be nice to have the same value in both repos.

I actually think it's better if it's different so that we can make sure our code is reading from params consistently. We've had issues in the past where things were hardcoded that shouldn't have been.

Copy link
Member

@storopoli storopoli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 4deb76c

should be good to go now.
CI should pass with unit and functional tests.
The last 2 commits (3c4544b and 4deb76c) fixed them.

@storopoli storopoli self-assigned this Jun 10, 2025
@storopoli storopoli enabled auto-merge June 10, 2025 19:44
@storopoli storopoli added this pull request to the merge queue Jun 11, 2025
Merged via the queue into main with commit a14b185 Jun 11, 2025
21 checks passed
@storopoli storopoli deleted the STR-1415-fix-withdrawal-fulfillments branch June 11, 2025 16:16
storopoli added a commit that referenced this pull request Jun 11, 2025
* refactor(chaintsn, state): add more logging of proto ops, protect against possible panic

* refactor(l1tx): fix OP_RETURN magic parsing

* refactor(l1tx): make OP_RETURN parsing more generic, fix tests

* refactor(l1tx, util/python-utils): replace references to variable magics with 4 byte magics

* refactor(l1tx, test-utils): move `create_opreturn_metadata` to test-utils crate

* feat(strata-client): add startup check for rollup name len

* docs(l1tx): fix typo

* docs(strata-client): fix incomplete comment

* chore: rebase fixes

* chore: fix unit tests

* chore: fix func tests

---------

Co-authored-by: Jose Storopoli <[email protected]>
storopoli added a commit that referenced this pull request Jun 11, 2025
* Fix OL ignoring withdrawal fulfillments (#821)

* refactor(chaintsn, state): add more logging of proto ops, protect against possible panic

* refactor(l1tx): fix OP_RETURN magic parsing

* refactor(l1tx): make OP_RETURN parsing more generic, fix tests

* refactor(l1tx, util/python-utils): replace references to variable magics with 4 byte magics

* refactor(l1tx, test-utils): move `create_opreturn_metadata` to test-utils crate

* feat(strata-client): add startup check for rollup name len

* docs(l1tx): fix typo

* docs(strata-client): fix incomplete comment

* chore: rebase fixes

* chore: fix unit tests

* chore: fix func tests

---------

Co-authored-by: Jose Storopoli <[email protected]>

* chore: update cargo.lock

---------

Co-authored-by: Trey Del Bonis <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants