Skip to content

Conversation

@maflcko
Copy link
Member

@maflcko maflcko commented Aug 2, 2021

Follow-up to #22570

@maflcko maflcko mentioned this pull request Aug 2, 2021
@maflcko maflcko added this to the 23.0 milestone Aug 2, 2021
Copy link
Member

Choose a reason for hiding this comment

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

(if I'm understanding your intention here)

Suggested change
`banlist.dat` is ignored. Bitcoin Core version 22.x is the only version that
`banlist.dat` is ignored. Bitcoin Core version 22.x is the last version that

Copy link
Contributor

Choose a reason for hiding this comment

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

it's the last version that can read .dat and the only version that can read .dat and write to .json, so you're both right :-) Maybe just split it into two separate clauses?

Copy link
Contributor

@vasild vasild left a comment

Choose a reason for hiding this comment

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

ACK fae540b70ae41db08a5999c621fdd896dca8d423

@flack
Copy link
Contributor

flack commented Aug 2, 2021

Does this need some more generic notice for upgrades from older versions? I.e. if you upgrade from .21 or earlier directly to 23.x, you will lose your banlist data, unless you upgrade to 22.x first and let it convert it, right?

@laanwj
Copy link
Member

laanwj commented Aug 2, 2021

if you upgrade from .21 or earlier directly to 23.x, you will lose your banlist data,

As I understand it you won't actually lose the data, it will just become inaccessible, but the .dat will still be there. Which is good. Someone who notices it later could ostensibly download 0.21.x and run it once to convert the file.

@flack
Copy link
Contributor

flack commented Aug 2, 2021

yes, but by the time they notice, a new json might already have been created with some new entries, and then you'd have to merge it somehow (or lose the new entries). Not a huge deal I guess, but it couldn't hurt to spell out that scenario in the release notes. At least then you'll have something to point to if someone opens a bug report about how their banlist is gone :-).

@maflcko maflcko force-pushed the 2108-docBanlistDatIgnore branch from fae540b to fa7a93a Compare August 2, 2021 15:46
@DrahtBot DrahtBot added the Docs label Aug 2, 2021
@maflcko
Copy link
Member Author

maflcko commented Aug 2, 2021

Pushed a more verbose version

Copy link
Contributor

@vasild vasild left a comment

Choose a reason for hiding this comment

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

ACK fa7a93ada2df8d88c9cd411b441110ae6ddec2c0

@maflcko maflcko force-pushed the 2108-docBanlistDatIgnore branch from fa7a93a to fa2c868 Compare August 2, 2021 15:54
Copy link
Contributor

@vasild vasild left a comment

Choose a reason for hiding this comment

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

ACK fa2c868

@tryphe
Copy link
Contributor

tryphe commented Aug 3, 2021

ACK fa2c868

Copy link
Contributor

@Zero-1729 Zero-1729 left a comment

Choose a reason for hiding this comment

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

ACK fa2c868

-----

* On startup, the list of banned hosts and networks (via `setban` RPC) in
`banlist.dat` is ignored and only `banlist.json` is considered. Bitcoin Core
Copy link
Member

@jonatack jonatack Aug 3, 2021

Choose a reason for hiding this comment

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

suggestions:

  • "(via the setban RPC or the GUI peers tab)"
  • "is now ignored and banlist.json is read instead.`
  • s/double check/verify/
  • s/22.x is/22.x was/ (if this is for the v23.0 release notes)

Copy link
Member Author

Choose a reason for hiding this comment

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

might do if I have to retouch. Otherwise this can be edited in the wiki in about 6 months

@maflcko maflcko merged commit 2b06af1 into bitcoin:master Aug 4, 2021
@maflcko maflcko deleted the 2108-docBanlistDatIgnore branch August 4, 2021 15:51
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Aug 4, 2021
….dat)

fa2c868 doc: Add release notes for 22570 (ignore banlist.dat) (MarcoFalke)

Pull request description:

  Follow-up to bitcoin#22570

ACKs for top commit:
  tryphe:
    ACK fa2c868
  vasild:
    ACK fa2c868
  Zero-1729:
    ACK fa2c868

Tree-SHA512: 58eef340b6211bcdecf3826ac145afd476c397f110daa6783521c0c1e1be1ffbd2d24ad20c77921abbe5cdb8e644d3cd64e14e2819746cf0e5123fb7cc445d63
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Aug 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants