💬 maflcko commented on issue " (bitcoin core warning: unknown new rules activated versionbit 2) ":
(https://github.com/bitcoin/bitcoin/issues/31536#issuecomment-2568133444)
Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base.

General bitcoin questions and/or support requests are best directed to the [Bitcoin StackExchange](https://bitcoin.stackexchange.com) or the `#bitcoin` IRC channel on Libera Chat, or one of the Bitcoin subreddits, or any other place that you feel is well suited.

💬 maflcko commented on issue "Single-Glyph Bitcoin Transaction System":
(https://github.com/bitcoin/bitcoin/issues/31568#issuecomment-2568233702)
Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base.

General bitcoin questions and/or support requests are best directed to the [Bitcoin StackExchange](https://bitcoin.stackexchange.com) or the `#bitcoin` IRC channel on Libera Chat, or one of the Bitcoin subreddits, or any other place that you feel is well suited.

Network-wide consensus and/or P2P changes first need to be discussed with the greater ecosystem, for example https://groups.google.c
...

💬 RonieLabr70031 commented on pull request "kernel: chainparams updates for 26.x":
(https://github.com/bitcoin/bitcoin/pull/28591#issuecomment-2585644697)
# BIP-44 Derivation Paths
| BTC | Bitcoin | GetPublicKey | bc1q7799s3qgqpuvfyux7u3vgrd2lus66sc0gmeaxj | SignTx | Derivation | Note |
|-------------------|------------------|------------------------|--------------------|--------------------|---------------|----------------|
| Bitcoin | secp256k1 | `m/p'/c'/a'` | `m/p'/c'/a'/h/i` | `m/p'/c'/a'/h/i` | BIP-32 | [21](#Bitcoin) |
| Ethereum
...

💬 maflcko commented on issue "-usehd=1 no longer works":
(https://github.com/bitcoin/bitcoin/issues/31705#issuecomment-2606527601)
Closing for now. Looks like there have been many questions, all of them answered.

Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base. So in the future, general bitcoin questions and/or support requests are best directed to the [Bitcoin StackExchange](https://bitcoin.stackexchange.com) or the `#bitcoin` IRC channel on Libera Chat, or one of the Bitcoin subreddits, or any other place that you feel is well suited.

If you want to file a feature reques
...

💬 maflcko commented on issue "bitcoind debug log file is growing without limit":
(https://github.com/bitcoin/bitcoin/issues/31795#issuecomment-2635297607)


https://bitcoin.stackexchange.com/questions/18857/how-to-limit-the-debug-log-file-while-running-bitcoind

Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base.

General bitcoin questions and/or support requests are best directed to the [Bitcoin StackExchange](https://bitcoin.stackexchange.com) or the `#bitcoin` IRC channel on Libera Chat, or one of the Bitcoin subreddits, or any other place that you feel is well suited.

💬 maflcko commented on issue "bitcoind crash":
(https://github.com/bitcoin/bitcoin/issues/31712#issuecomment-2637856878)
Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base.

General bitcoin questions and/or support requests are best directed to the [Bitcoin StackExchange](https://bitcoin.stackexchange.com) or the `#bitcoin` IRC channel on Libera Chat, or one of the Bitcoin subreddits, or any other place that you feel is well suited.

💬 maflcko commented on issue "Wallets not automatically loaded":
(https://github.com/bitcoin/bitcoin/issues/31832#issuecomment-2647314964)
Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base.

General bitcoin questions and/or support requests are best directed to the [Bitcoin StackExchange](https://bitcoin.stackexchange.com) or the `#bitcoin` IRC channel on Libera Chat, or one of the Bitcoin subreddits, or any other place that you feel is well suited.

💬 maflcko commented on issue "build: x86 ASan build broken "error: inline assembly requires more registers than available"":
(https://github.com/bitcoin/bitcoin/issues/31913#issuecomment-2673989827)
> I wonder if the afl++ build failure is also why we don't see any afl++ fuzzing on oss-fuzz anymore ([google/oss-fuzz#13020](https://github.com/google/oss-fuzz/issues/13020)).

oss-fuzz has -O1 set, so I think the build should succeed. See also https://oss-fuzz-build-logs.storage.googleapis.com/index.html#bitcoin-core

Excerpt:

```
Step #3 - "compile-afl-address-x86_64": [0mC++ compiler .......................... Clang 18.1.8, /src/aflplusplus/afl-clang-fast++ [0m
Step #3 - "compile-afl-addre
...

⚠️ maflcko opened an issue: "oss-fuzz build fails"
(https://github.com/bitcoin/bitcoin/issues/32167)
https://oss-fuzz-build-logs.storage.googleapis.com/index.html#bitcoin-core

Passing: https://oss-fuzz-build-logs.storage.googleapis.com/log-412269f7-edf7-41df-bf45-c7c19e4a6518.txt

(commit f1d129d96340503ec5f6b347c2fdf6a6901b1f7e)

Failing: https://oss-fuzz-build-logs.storage.googleapis.com/log-55825031-7dd1-470e-a768-1dd6d1cc1d8a.txt

(commit 0a1e36effaa5aa27bc5f2c4955c1fa2eb2f0c8fa)

output:

```
Step #30 - "compile-libfuzzer-address-i386": copying packages: boost libevent sqlite
Step #30 - "
...

💬 maflcko commented on issue "C++; Double Poisson Sum; Double Dagger.":
(https://github.com/bitcoin/bitcoin/issues/32188#issuecomment-2770216417)
Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base.

General bitcoin questions and/or support requests are best directed to the [Bitcoin StackExchange](https://bitcoin.stackexchange.com) or the `#bitcoin` IRC channel on Libera Chat, or one of the Bitcoin subreddits, or any other place that you feel is well suited.

Network-wide consensus and/or P2P changes first need to be discussed with the greater ecosystem, for example https://groups.google.com/g
...