Add DA proof support to daprovider interface #3600

Tristan-Wilson · 2025-09-09T12:00:37Z

This is part of a series of changes for the Custom DA project.

Summary:

Added a new daprovider.Validator interface with methods for generating proofs for Custom DA systems.
Added a reference implementation of a Custom DA provider.
Added a daprovider factory that supports anytrust and referenceda modes. In a follow-up PR the nitro node startup sequence will be modified to use this. Currently only the separate daprovider server uses this.
Replaced the AnyTrust-specific (aka das) provider server with a unified provider server that works with anytrust or referenceda modes.
Extended the DA Client with new RPC methods for generating proofs.

Notes: The separate provider server executable is a thin RPC server wrapper around the anytrust and referenceda implementations. The idea is that people wanting to integrate their own DA system can use this as a guide for how to implement their own RPC service that lives outside the nitro codebase; we won't be including support for any additional DA implementations in provider server executable that we distribute. For legacy AnyTrust deployments we will most likely continue to have nitro spawn the daprovider server in-process to avoid needing to run an extra service, but by channeling everything through the JSON-RPC interface it reduces surface area of what we have to support.

The Reference DA (referenceda) implementation is a minimal working example of how one could implement a daprovider, including support for validating the certificate against trusted signers. It uses an in-memory data storage backend.

In various places there is commented out code related to the osp contract bindings that haven't yet been committed to a nitro-contracts branch that we want to use in nitro master.

This PR shouldn't change any existing functionality or behavior, except the daprovider executable (which isn't used in production) has some new configuration options:

 --mode               must be "anytrust" or "referenceda"
 --provider-server.*  server config eg address, port, etc
 --anytrust.*         was previosly called das-server
 --referenceda.*      referenceda specific options

As much as possible we will try to rename references to "das" to "anytrust". When we launched Anytrust, we only had one offchain data availability mode so we just called it "das" at the time.

This PR doesn't include new test code, but testing was done with the end-to-end block validator and challenge system tests on the custom-da branch.

This is part of a series of changes for the Custom DA project. Summary: - Added a new daprovider.Validator interface with methods for generating proofs for Custom DA systems. - Added a reference implementation of a Custom DA provider. - Added a daprovider factory that supports anytrust and referenceda modes. In a follow-up PR the nitro node startup sequence will be modified to use this. Currently only the separate daprovider server uses this. - Replaced the AnyTrust-specific (aka das) provider server with a unified provider server that works with anytrust or referenceda modes. - Extended the DA Client with new RPC methods for generating proofs. Notes: The separate provider server executable is a thin RPC server wrapper around the anytrust and referenceda implementations. The idea is that people wanting to integrate their own DA system can use this as a guide for how to implement their own RPC service that lives outside the nitro codebase; we won't be including support for any additional DA implementations in provider server executable that we distribute. For legacy AnyTrust deployments we will most likely continue to have nitro spawn the daprovider server in-process to avoid needing to run an extra service, but by channeling everything through the JSON-RPC interface it reduces surface area of what we have to support. The Reference DA (referenceda) implementation is a minimal working example of how one could implement a daprovider, including support for validating the certificate against trusted signers. It uses an in-memory data storage backend. In various places there is commented out code related to the osp contract bindings that haven't yet been committed to a nitro-contracts branch that we want to use in nitro master. This PR shouldn't change any existing functionality or behavior, except the daprovider executable (which isn't used in production) has some new configuration options: ``` --mode must be "anytrust" or "referenceda" --provider-server.* server config eg address, port, etc --anytrust.* was previosly called das-server --referenceda.* referenceda specific options ``` As much as possible we will try to rename references to "das" to "anytrust". When we launched Anytrust, we only had one offchain data availability mode so we just called it "das" at the time. This PR doesn't include new test code, but testing was done with the end-to-end block validator and challenge system tests on the custom-da branch.

ganeshvanahalli

minor suggestions

daprovider/factory/factory.go

daprovider/referenceda/certificate.go

ganeshvanahalli

LGTM

tsahee · 2025-09-16T00:33:12Z

daprovider/util.go

+
 // KnownHeaderBits is all header bits with known meaning to this nitro version
-const KnownHeaderBits byte = DASMessageHeaderFlag | TreeDASMessageHeaderFlag | L1AuthenticatedMessageHeaderFlag | ZeroheavyMessageHeaderFlag | BlobHashesHeaderFlag | BrotliMessageHeaderByte
+const KnownHeaderBits byte = DASMessageHeaderFlag | TreeDASMessageHeaderFlag | L1AuthenticatedMessageHeaderFlag | ZeroheavyMessageHeaderFlag | BlobHashesHeaderFlag | BrotliMessageHeaderByte | DACertificateMessageHeaderFlag


This changes behavior of replay.wasm.
It should either only be added later - or the current change should modify replay.wasm to specifically exclude DACertificateMessageHeaderFlag

Good point. I agree the best thing to do seems to be to take it out of the known headers for now.

daprovider/validator.go

cmd/daprovider/daprovider.go

daprovider/server/provider_server.go

tsahee · 2025-09-16T01:11:11Z

daprovider/server/provider_server.go

+		writer:    writer,
+		validator: validator,
+	}
+	if err = rpcServer.RegisterName("daprovider", server); err != nil {


Since you have 3 separate interfaces (reader/writer/validator) and each has their own rpc functions - it might make sense to have 3 separate provider server objects - one for wrapping each interface - and to have here 3 separate calls to rpcServer.RegisterName - even if all 3 objects register to the same namespace.
Not a must.

I haven't done this yet but it should be an easy enough change. Either tomorrow or in a future PR.

I'm already dreading the merge conflicts of this PR back to custom-da especially around provider_server so I think I'll defer this change til after this is merged to master, and then master is merged back to custom-da.

tsahee · 2025-09-16T01:26:30Z

daprovider/validator.go

+	// The proof format depends on the implementation and must be compatible with the Solidity
+	// IDACertificateValidator contract.
+	// certHash is the keccak256 hash of the certificate.
+	GenerateReadPreimageProof(ctx context.Context, preimageType arbutil.PreimageType, certHash common.Hash, offset uint64, certificate []byte) ([]byte, error)


For calls that will be wrapped by rpc calls - please return Promises. See for example validator/interface.go
promises make it more visible in code that a function call could take long, and they handle context well on both sides.

Done now for all methods except Store, which is being heavily reworked on the custom-da branch and we can do later.

…-interface

We will add DACertificateMessageHeaderFlag back to KnownHeaderBits in a future PR; removing it for now avoids changing the replay binary unnecessarily when merging in this PR.

daprovider.Readers are now registered with their respective header bytes at initialization. For external DA providers where the RPC client is used this becomes single call at init to daprovider_getSupportedHeaderBytes. Where previously in the inbox and block validator components we had loops over each provider, checking each provider if they handle that type of message, we now just check if we have a provider registered for that message. This means less RPC calls and makes the interface that providers need to implement a bit simpler, with room for taking it out completely for CustomDA if we can detect from other config that the external provider is expected to be a CustomDA provider.

We moved the contents of dasserver to provider_server on the custom-da branch and I accidentally left dasserver in place on this branch when moving things across. I don't want to bring over the changes to the daprovider construction logic in node.go yet so I just made the das_migration.go file which we'll delete later.

In normal execution we only care about the payload, and in validation we only care about the preimages (we will reconstruct the payload using the preimages). This change separates these concerns and simplifies the signatures of these methods.

For DAS and ReferenceDA we almost always want to validate the certificate. The only time we don't is in the replay binary when we want to panic instead if it's invalid on the first read of the message, otherwise we want to ignore it and assume it's already valid. So this means that it doesn't make sense for validateSeqMsg to be part of the reader API at all, which is great because it means we can simplify the API. We can pass into the reader at construction time how to handle this because in replay it always constructs a new (fake, non-network calling) reader for each invocation.

…-interface

tsahee

Generally looking good. Just getting initial comments out.

Have not yer reviewed:
cmd/daprovider
daprovider/factore
daprovider/referenceda
daprovider/server/das_migrations.go
daprovider/server/provider_server

tsahee · 2025-09-30T22:01:04Z

daprovider/reader.go

+	batchBlockHash common.Hash,
+	sequencerMsg []byte,
+) containers.PromiseInterface[PayloadResult] {
+	promise := containers.NewPromise[PayloadResult](nil)


the canonical way (which we should make easier) is something like:

ctx, cancel: context.WithCancel(context.Background) promise := NewPromise[..](cancel)

and then use that ctx in the go thread..

Not critical for now, but should open a different task to handle that

we should create a thin wrapper fot those two lines, create a func that gets parent context and returns promise and promise-context (the promise-context being cancellable with promise's cancel)

Looks like we're using Promise incorrectly in a lot of places in the codebase (passing in a nil cancel func). I made a new function NewPromiseWithContext as you described and used in the places where this PR uses Promises. We can do a separate change on master later to use it elsewhere.

tsahee · 2025-09-30T22:19:55Z

arbnode/batch_poster.go

-			dapReaders = append(dapReaders, daprovider.NewReaderForBlobReader(&simulatedBlobReader{kzgBlobs}))
+			if err := dapReaders.SetupBlobReader(daprovider.NewReaderForBlobReader(&simulatedBlobReader{kzgBlobs})); err != nil {
+				return false, fmt.Errorf("failed to register simulated blob reader: %w", err)
+			}


why do we need to create a new registry and not just use b.dapReaders?

When batch correctness checking is enabled and we're using 4844 we need to use a simulated blob reader because the blobs have not been posted yet. We don't want to register the simulated reader with the main registry used by the batch poster, so we create a copy of it.

I had missed that I needed to exclude copying the normal blob reader to the new registry, I added that now. Registering another reader for the same header byte is a runtime error.

For a later PR: we can implement a dapReaders-wrapper that returns it's own fake-blobreader for blob header, and passes through any other function to the wrapped dasReader.
This will be simpler and easier to understand.

tsahee · 2025-09-30T22:30:23Z

daprovider/server/provider_server.go

+// Copyright 2024-2025, Offchain Labs, Inc.
+// For license information, see https://github.com/OffchainLabs/nitro/blob/master/LICENSE.md
+
+package dapserver


better name the dir dapserver as well, to prevent having to rename on import

Can we defer this change til after this PR gets merged? Further renamings are annoying to merge back into the big custom-da PR.

tsahee · 2025-09-30T22:49:47Z

daprovider/daclient/daclient.go

-	if err := c.CallContext(ctx, &isValidHeaderByteResult, "daprovider_isValidHeaderByte", headerByte); err != nil {
-		log.Error("Error returned from daprovider_isValidHeaderByte rpc method, defaulting to result as false", "err", err)
-		return false
+func (c *Client) GetSupportedHeaderBytes(ctx context.Context) ([]byte, error) {


seems like this one should also return a promise

(instead of getting a ctx parameter)

Changed it to use Promise

tsahee · 2025-09-30T23:35:19Z

daprovider/validator.go

+// Copyright 2024-2025, Offchain Labs, Inc.
+// For license information, see https://github.com/OffchainLabs/nitro/blob/master/LICENSE.md
+
+package daprovider


I think the interface can live in the parent directory "daprovider", since it's just an interface

Maybe you left a comment on the wrong file here? It's already in daprovider. In any case, I'd like to defer further moves/renamings til after this gets merged unless they're critical.

github-actions · 2025-10-01T09:55:13Z

❌ 12 Tests Failed:

Tests completed	Failed	Passed	Skipped
1961	12	1949	0

View the top 3 failed tests by shortest run time

TestVersion30

Stack Traces | 7.480s run time

... [CONTENT TRUNCATED: Keeping last 20 lines]
=== CONT  TestVersion30
    precompile_inclusion_test.go:90: goroutine 558794 [running]:
        runtime/debug.Stack()
        	/opt/hostedtoolcache/go/1.25.1/x64/src/runtime/debug/stack.go:26 +0x5e
        github.com/offchainlabs/nitro/util/testhelpers.RequireImpl({0x4077670, 0xc0b322bc00}, {0x4035900, 0xc1190c8930}, {0x0, 0x0, 0x0})
        	/home/runner/work/nitro/nitro/util/testhelpers/testhelpers.go:29 +0x55
        github.com/offchainlabs/nitro/system_tests.Require(0xc0b322bc00, {0x4035900, 0xc1190c8930}, {0x0, 0x0, 0x0})
        	/home/runner/work/nitro/nitro/system_tests/common_test.go:1722 +0x5d
        github.com/offchainlabs/nitro/system_tests.testPrecompiles(0xc0b322bc00, 0x1e, {0xc0d6c3fdb0, 0x6, 0x48df94?})
        	/home/runner/work/nitro/nitro/system_tests/precompile_inclusion_test.go:90 +0x371
        github.com/offchainlabs/nitro/system_tests.TestVersion30(0xc0b322bc00?)
        	/home/runner/work/nitro/nitro/system_tests/precompile_inclusion_test.go:67 +0x798
        testing.tRunner(0xc0b322bc00, 0x3cc0800)
        	/opt/hostedtoolcache/go/1.25.1/x64/src/testing/testing.go:1934 +0xea
        created by testing.(*T).Run in goroutine 1
        	/opt/hostedtoolcache/go/1.25.1/x64/src/testing/testing.go:1997 +0x465
        
    precompile_inclusion_test.go:90: �[31;1m [] execution aborted (timeout = 5s) �[0;0m
�[38;5;48;1myay!! we validated block 13 in 192.59ms�[0;0m
--- FAIL: TestVersion30 (7.48s)

TestVersion40

Stack Traces | 7.670s run time

... [CONTENT TRUNCATED: Keeping last 20 lines]
=== PAUSE TestVersion40
=== CONT  TestVersion40
    precompile_inclusion_test.go:90: goroutine 558795 [running]:
        runtime/debug.Stack()
        	/opt/hostedtoolcache/go/1.25.1/x64/src/runtime/debug/stack.go:26 +0x5e
        github.com/offchainlabs/nitro/util/testhelpers.RequireImpl({0x4077670, 0xc0b322bdc0}, {0x4035900, 0xc10ce6b7d0}, {0x0, 0x0, 0x0})
        	/home/runner/work/nitro/nitro/util/testhelpers/testhelpers.go:29 +0x55
        github.com/offchainlabs/nitro/system_tests.Require(0xc0b322bdc0, {0x4035900, 0xc10ce6b7d0}, {0x0, 0x0, 0x0})
        	/home/runner/work/nitro/nitro/system_tests/common_test.go:1722 +0x5d
        github.com/offchainlabs/nitro/system_tests.testPrecompiles(0xc0b322bdc0, 0x28, {0xc111615df8, 0x5, 0x39?})
        	/home/runner/work/nitro/nitro/system_tests/precompile_inclusion_test.go:90 +0x371
        github.com/offchainlabs/nitro/system_tests.TestVersion40(0xc0b322bdc0?)
        	/home/runner/work/nitro/nitro/system_tests/precompile_inclusion_test.go:71 +0x64b
        testing.tRunner(0xc0b322bdc0, 0x3cc0808)
        	/opt/hostedtoolcache/go/1.25.1/x64/src/testing/testing.go:1934 +0xea
        created by testing.(*T).Run in goroutine 1
        	/opt/hostedtoolcache/go/1.25.1/x64/src/testing/testing.go:1997 +0x465
        
    precompile_inclusion_test.go:90: �[31;1m [] execution aborted (timeout = 5s) �[0;0m
--- FAIL: TestVersion40 (7.67s)

TestArbOSVersion50

Stack Traces | 7.740s run time

... [CONTENT TRUNCATED: Keeping last 20 lines]
=== PAUSE TestArbOSVersion50
=== CONT  TestArbOSVersion50
    precompile_inclusion_test.go:90: goroutine 558796 [running]:
        runtime/debug.Stack()
        	/opt/hostedtoolcache/go/1.25.1/x64/src/runtime/debug/stack.go:26 +0x5e
        github.com/offchainlabs/nitro/util/testhelpers.RequireImpl({0x4077670, 0xc0c2192000}, {0x4035900, 0xc1685b5e00}, {0x0, 0x0, 0x0})
        	/home/runner/work/nitro/nitro/util/testhelpers/testhelpers.go:29 +0x55
        github.com/offchainlabs/nitro/system_tests.Require(0xc0c2192000, {0x4035900, 0xc1685b5e00}, {0x0, 0x0, 0x0})
        	/home/runner/work/nitro/nitro/system_tests/common_test.go:1722 +0x5d
        github.com/offchainlabs/nitro/system_tests.testPrecompiles(0xc0c2192000, 0x32, {0xc0c6801e88, 0x3, 0x5bd9880?})
        	/home/runner/work/nitro/nitro/system_tests/precompile_inclusion_test.go:90 +0x371
        github.com/offchainlabs/nitro/system_tests.TestArbOSVersion50(0xc0c2192000?)
        	/home/runner/work/nitro/nitro/system_tests/precompile_inclusion_test.go:75 +0x3ef
        testing.tRunner(0xc0c2192000, 0x3cbf6e8)
        	/opt/hostedtoolcache/go/1.25.1/x64/src/testing/testing.go:1934 +0xea
        created by testing.(*T).Run in goroutine 1
        	/opt/hostedtoolcache/go/1.25.1/x64/src/testing/testing.go:1997 +0x465
        
    precompile_inclusion_test.go:90: �[31;1m [] execution aborted (timeout = 5s) �[0;0m
--- FAIL: TestArbOSVersion50 (7.74s)

📣 Thoughts on this report? Let Codecov know! | Powered by Codecov

tsahee

many refactor suggestions, but those can be done in a separate PR to keep merge overhead down.
Also - I'm not done going over referenceDA but comments there should be easy to fix later if needed

tsahee · 2025-10-01T23:27:15Z

daprovider/factory/factory.go

+	l1Client     *ethclient.Client
+}
+
+func NewDAProviderFactory(


I think this adds more complexity then clarity.
It's a little hard to chase around.
I think a "CreateReferenceDAFactory in referenceda dir, and "CreateAnyTrustFactory" in anytrust package (or actually naming both just "CreateFactory" and using package name to tell them apart) would be clearer

especially since you already need the sub-packages with the configs inside them to create the factory.

tsahee · 2025-10-01T23:28:57Z

daprovider/factory/factory.go

+}
+
+type AnyTrustFactory struct {
+	config       *das.DataAvailabilityConfig


It seems like this config (and some more code) should be moved from "das.DataAvailabilityConfig" to a separate anytrust package and become something like anytrust.Config?

tsahee · 2025-10-01T23:44:06Z

daprovider/server/das_migration.go

+// - *http.Server: The HTTP server instance
+// - func(): Cleanup function to stop the DAS lifecycle manager
+// - error: Any error that occurred during initialization
+func NewServerForDAS(


AFAIU: the name "anytrust" also belongs somewhere here and/or in the package?

tsahee · 2025-10-01T23:53:37Z

daprovider/referenceda/certificate.go

+	"github.com/offchainlabs/nitro/util/signature"
+)
+
+// Certificate represents a ReferenceDA certificate with signature


worth adding a small comment explaining what the referenceDA does

tsahee · 2025-10-02T00:03:50Z

daprovider/referenceda/reference_reader.go

+	}
+
+	// Validate certificate - always validate for ReferenceDA
+	// TODO: Uncomment the following once we have merged customda contracts changes.


can we add the ReferenceDA contract in contract-local, which is used for testing?
I know we need changes in the contracts as well, but the referenceDA should probably only be here.

tsahee · 2025-10-02T00:05:46Z

daprovider/referenceda/reference_reader.go

+	sequencerMsg []byte,
+) containers.PromiseInterface[daprovider.PreimagesResult] {
+	promise, ctx := containers.NewPromiseWithContext[daprovider.PreimagesResult](context.Background())
+	go func() {


now I think we can also encapsulate further with something like

func LaunchPromisethread[T any](parent context.Context, threadfunc func(ctx context) (T, error)) *PromiseInterface[T]

not urgent, and we could keep both :)

very much like stopwaiter.LaunchPromiseThread, but without the stopwaiter encapsulation

Tristan-Wilson requested review from ganeshvanahalli and tsahee September 9, 2025 12:00

Tristan-Wilson assigned ganeshvanahalli Sep 9, 2025

Merge branch 'master' into customda-daprovider-interface

06c5f87

ganeshvanahalli requested changes Sep 11, 2025

View reviewed changes

daprovider/factory/factory.go Outdated Show resolved Hide resolved

daprovider/referenceda/certificate.go Show resolved Hide resolved

Reduce code duplication in factory, more cert validation

9f415d7

Tristan-Wilson requested a review from ganeshvanahalli September 12, 2025 15:45

Tristan-Wilson and others added 2 commits September 12, 2025 17:47

Merge branch 'master' into customda-daprovider-interface

3e28ae0

Fix for interface change on master

3a79a18

ganeshvanahalli previously approved these changes Sep 12, 2025

View reviewed changes

ganeshvanahalli assigned tsahee and unassigned ganeshvanahalli Sep 12, 2025

tsahee requested changes Sep 16, 2025

View reviewed changes

tsahee assigned Tristan-Wilson and unassigned tsahee Sep 16, 2025

Merge remote-tracking branch 'origin/master' into customda-daprovider…

7ac666a

…-interface

Tristan-Wilson dismissed ganeshvanahalli’s stale review via 7ac666a September 22, 2025 08:18

Tristan-Wilson added 9 commits September 22, 2025 14:34

Remove DACert flag from KnownHeaderBits for now

c1f5d1d

We will add DACertificateMessageHeaderFlag back to KnownHeaderBits in a future PR; removing it for now avoids changing the replay binary unnecessarily when merging in this PR.

Remove preimageType from daprovider.Validator

08e9cec

Move daprovider api types to own go pkg

931d0c9

Use Promises with daprovider.Reader iface

1f5b050

Split rpc payload and preimage methods

51456b6

In normal execution we only care about the payload, and in validation we only care about the preimages (we will reconstruct the payload using the preimages). This change separates these concerns and simplifies the signatures of these methods.

Use Promises with Validator interface

162ff10

Tristan-Wilson assigned tsahee and unassigned Tristan-Wilson Sep 25, 2025

Merge remote-tracking branch 'origin/master' into customda-daprovider…

6de2dd9

…-interface

Add missing import

87712d4

Tristan-Wilson requested a review from tsahee September 26, 2025 05:30

Tristan-Wilson mentioned this pull request Sep 26, 2025

Custom da merge customda daprovider interface #3712

Draft

Tristan-Wilson and others added 2 commits September 29, 2025 10:26

Resgister DAS reader with both flag variants

0f97322

Merge branch 'master' into customda-daprovider-interface

165b171

tsahee reviewed Oct 1, 2025

View reviewed changes

Tristan-Wilson added 2 commits October 1, 2025 11:39

Use cancelable promises

bd1faaa

Fix reader registration for batch correctness checking

5847196

Use promise for GetSupportedHeaderBytes too

1a3e4f7

Tristan-Wilson requested a review from tsahee October 1, 2025 10:03

tsahee approved these changes Oct 2, 2025

View reviewed changes

tsahee assigned Tristan-Wilson and unassigned tsahee Oct 2, 2025

tsahee added the design-approved label Oct 2, 2025

Add DA proof support to daprovider interface #3600

Are you sure you want to change the base?

Add DA proof support to daprovider interface #3600

Conversation

Tristan-Wilson commented Sep 9, 2025

Uh oh!

ganeshvanahalli left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

ganeshvanahalli left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

tsahee left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Oct 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

❌ 12 Tests Failed:

Uh oh!

tsahee left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

github-actions bot commented Oct 1, 2025 •

edited

Loading