AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 18 Bitcoin

Merge bitcoin/bitcoin#36285: refactor: Use static const over inline const to work around ld64 bug

Public commit record

What the developer wrote

Authored by merge-script

93/100 · Strong
Merge bitcoin/bitcoin#36285: refactor: Use static const over inline const to work around ld64 bug

fa8fefb29b6ce00c27638bc1c6f8ab5d58d48cb0 refactor: Use static const over inline const to work around ld64 bug (MarcoFalke)

Pull request description:

This partially reverts fa74f58a262096f25d5a3a4ec4951f4ce2a31792 to avoid initialization dependencies, which ld64 fails to handle properly.

Works around https://github.com/bitcoin/bitcoin/issues/36281 for now.

Obviously this will increase the bin size again (70kB for me), but this shouldn't matter much.

ACKs for top commit:
janb84:
ACK fa8fefb29b6ce00c27638bc1c6f8ab5d58d48cb0
sedited:
ACK fa8fefb29b6ce00c27638bc1c6f8ab5d58d48cb0

Tree-SHA512: a31f3f4503dbc1898f346a5ceb94de61d82fd5902feec65f3716dc785dc199223c66cf223dcbe8a434e0a05af04bc1b0e7a066c3361deded947691c501ab0228
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This is a build-compatibility fix, not a security patch. It changes how some constant data is stored internally so that Apple's macOS linker (ld64) can build Bitcoin Core correctly. The change avoids a linker bug that caused build failures, but it does not fix any vulnerability that could be exploited by an attacker.

Recommended action

No security action needed. Treat as a normal build/maintenance fix. If backporting, include only for users building on macOS with the affected toolchain.

Security signals we found

01

No security-relevant code logic changed

02

Change is a linker bug workaround, not a vulnerability fix

03

Constants remain read-only; no new attack surface introduced

04

Binary size increases slightly due to duplicated static data

Risk score

Why this scored 18/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 2/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.