💬 josibake commented on pull request "refactor: Model the bech32 charlimit as an Enum":
(https://github.com/bitcoin/bitcoin/pull/30047#issuecomment-2100302186)
@theuni updated to remove `NO_LIMIT`. I also looked at a few alternatives to using an `Enum` but I think given the relatively simple usecase, an `Enum` works here with the benefit of not requiring an expansive refactor.

I'd be open to a more expansive refactor if there was a) conceptual buy in and b) additional use cases beyond supporting silent payments addresses (e.g. parsing bolt11/12 bech32 strings in Bitcoin Core, mercury layer bech32 addresses, etc).

⚠️ nimrare opened an issue: "libxcb-xinerama0 Library required by bitcoin-qt"
(https://github.com/bitcoin/bitcoin/issues/30061)
### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

I installed bitcoin core 26.1 on a Raspberry 5 (ARM Architecture) running Ubuntu 23.1. Upon running bitcoin-qt, I got the error that the library libxcb-xinerama0 is required but not installed.

It's easily fixed by installing it from the repositories (apt install libxcb-xinerama0), however, for a security conscious person this is a bit unsatisfying. Is there a reason this library is not
...

💬 hebasto commented on issue "libxcb-xinerama0 Library required by bitcoin-qt":
(https://github.com/bitcoin/bitcoin/issues/30061#issuecomment-2100340076)
> It's easily fixed by installing it from the repositories (apt install libxcb-xinerama0), however, for a security conscious person this is a bit unsatisfying.

It is expected: https://github.com/bitcoin/bitcoin/blob/43a66c55ec8770cf7c21112aac9b997f3f2fb704/contrib/devtools/symbol-check.py#L125

🤔 rkrux reviewed a pull request: "Test/rpc whitelistdefault test"
(https://github.com/bitcoin/bitcoin/pull/29858#pullrequestreview-2045275412)
Thanks for adding these tests.

Seems like this is in progress because there is test failure and a debugger is added.
Added few suggestions for now, will review again when the tests pass.

💬 rkrux commented on pull request "Test/rpc whitelistdefault test":
(https://github.com/bitcoin/bitcoin/pull/29858#discussion_r1593816229)
This test fails at this line, throwing 403 instead.
```
2024-05-08T10:36:33.356000Z TestFramework (INFO): Testing rpcwhitelistdefault=0 with no specified permissions
2024-05-08T10:36:34.102000Z TestFramework (ERROR): Assertion failed
Traceback (most recent call last):
File "/Users/aither/projects/bitcoin/test/functional/test_framework/test_framework.py", line 132, in main
self.run_test()
File "/Users/aither/projects/bitcoin/test/functional/rpc_whitelist.py", line 106, in run_test
...

💬 rkrux commented on pull request "Test/rpc whitelistdefault test":
(https://github.com/bitcoin/bitcoin/pull/29858#discussion_r1593808338)
Same string formatting nit can be applied here as well.
```
Use f'{x}' for string formatting in preference to '{}'.format(x) or '%s' % x.

💬 rkrux commented on pull request "Test/rpc whitelistdefault test":
(https://github.com/bitcoin/bitcoin/pull/29858#discussion_r1593806337)
`with specified`
Extra space between

💬 rkrux commented on pull request "Test/rpc whitelistdefault test":
(https://github.com/bitcoin/bitcoin/pull/29858#discussion_r1593813826)
This piece of code is duplicated in every test, good candidate for extracting out in a `getPermissions(user)` function.

💬 rkrux commented on pull request "Test/rpc whitelistdefault test":
(https://github.com/bitcoin/bitcoin/pull/29858#discussion_r1593810250)
Suggestion: The above test ending here can be put in a separate function so that there are mostly other test functions calls inside `run_test`.

💬 rkrux commented on pull request "Test/rpc whitelistdefault test":
(https://github.com/bitcoin/bitcoin/pull/29858#discussion_r1593818855)
Why is this path different than in other tests below?

📝 paplorinc converted_to_draft a pull request: "refactor: Speed up Base58 encoding/decoding by 400%/200% via preliminary byte packing"
(https://github.com/bitcoin/bitcoin/pull/29473)
Continuing the base conversion optimizations, started in [TryParseHex](https://github.com/bitcoin/bitcoin/pull/29458) and [IsSpace](https://github.com/bitcoin/bitcoin/pull/29602) and [Bech32](https://github.com/bitcoin/bitcoin/pull/29607).

-------

To mitigate the quadratic complexity inherent in the sequential byte division of the Base58 encoding process, this update aggregates characters into groups of 7 and 9, fitting them into 64-bit long integers.
This refinement utilizes the inherent
...

💬 0xB10C commented on pull request "contrib: Add asmap-tool":
(https://github.com/bitcoin/bitcoin/pull/28793#issuecomment-2100376287)
ACK 6abe772a17e09fe96e68cd3311280d5a30f6378b

Did some light code review & some testing of `encode` -> `decode` -> `encode` with kartograf generated `final_results.txt` file, `diff`, and the handling of invalid text and mutated binary input files.

💬 paplorinc commented on pull request "test: use assert_greater_than util":
(https://github.com/bitcoin/bitcoin/pull/30019#discussion_r1593896834)
> I see you are a newcomer too.

this isn't necessary...

```Python
assert_greater_than("0.001", balance - newbalance)
```
I wasn't suggesting comparing it to a string, of course, but to a decimal, as in the example I've provided, i.e.:
```Python
assert_greater_than(0.001, balance - newbalance)
```

This seems to be working for me, is it failing for you?

📝 brunoerg opened a pull request: "net: add ASMap info in `getrawaddrman` RPC"
(https://github.com/bitcoin/bitcoin/pull/30062)
This PR adds two new fields in `getrawaddrman` RPC: "mapped_as" and "source_mapped_as". These fields are used to return the ASN (Autonomous System Number) mapped to the peer and its source. With these informations we can have a better view of the bucketing logic with ASMap specially in projects like [addrman-observer](https://github.com/0xb10c/addrman-observer).

💬 brunoerg commented on pull request "net: add ASMap info in `getrawaddrman` RPC":
(https://github.com/bitcoin/bitcoin/pull/30062#issuecomment-2100435272)
ping @0xB10C

👍 rkrux approved a pull request: "test: use sleepy wait-for-log in reindex readonly"
(https://github.com/bitcoin/bitcoin/pull/30006#pullrequestreview-2045542646)
ACK [fd6a7d3](https://github.com/bitcoin/bitcoin/pull/30006/commits/fd6a7d3a13d89d74e161095b0e9bd3570210a40c)

Make and tests successful.
I found this answer helpful that explains how `yield` and `with` interact with each other: https://stackoverflow.com/a/35489897/12218815

💬 hebasto commented on pull request "refactor: remove remaining unused code from cpp-subprocess":
(https://github.com/bitcoin/bitcoin/pull/29961#issuecomment-2100521158)
https://github.com/bitcoin/bitcoin/pull/29961#discussion_r1582021758:

> The `Popen::poll()` function is used in #29868. I hope that an improved/fixed Windows implementation of the `Popen::retcode()`, which I don't have now, will allow to drop it.

That is no longer the case with [current](https://github.com/bitcoin/bitcoin/commit/b69b9e85e98cac2c7585c9b613185dc6c80320cc) implementation of #29868.

💬 edilmedeiros commented on pull request "test: use assert_greater_than util":
(https://github.com/bitcoin/bitcoin/pull/30019#discussion_r1593996196)
Oh, I see.

Still, better to leave to [preserve potential bugs](https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#refactoring) since this is refactoring.

💬 sipa commented on issue "libxcb-xinerama0 Library required by bitcoin-qt":
(https://github.com/bitcoin/bitcoin/issues/30061#issuecomment-2100544625)
@laanwj Does #29923 address this?

💬 kanzure commented on issue "Consideration of a Code of Conduct and/or written rules for moderation":
(https://github.com/bitcoin/bitcoin/issues/29507#issuecomment-2100549946)
Here is a "moderation guidelines" document that was created 5 days ago apparently: https://github.com/bitcoin-core/meta/blob/main/MODERATION-GUIDELINES.md as it seems directly related to the previous discussion in this issue, I thought I would bring it up. All previous comments here, I believe, still apply.

In https://github.com/bitcoin/bitcoin/issues/29507#issuecomment-1980365499 @ajtowns proposes a "Moderation Guidelines" document. I like the idea of writing about goals, explaining the avai
...