Cardano Node 11.1.3 Correct IPv4 Decoding

Cardano Node 11.1.3 come out on September 29, and e correct how di software dey read IPv4 addresses wey dem store for di ledger. Dis update follow Intersect earlier priority upgrade notice for stake pool operators and other organizations wey dey run Cardano infrastructure.

How di IPv4 Fix Take Work

Version 11.1.2 mistakenly change di byte order wey dem take decode IPv4 addresses. Di latest release restore di standard network byte order wey dem dey use before di 11.1.x series. Dem include di correction through version 1.9.0.1 of di cardano-ledger-binary library.

IPv4 address na four bytes, and di order of those bytes determine how dem go interpret di address. For Cardano, these addresses dey appear inside stake pool relay records. Relays dey exchange blocks and transactions with other nodes, so make sure say their address data correct dey important for network infrastructure.

Di release changelog place di correction inside di ledger component and e no list any change to di Network or Consensus components.

Which Cardano Operators E Concern

Intersect recommendation cover stake pool operators and other node operators. Their earlier upgrade guidance include infrastructure wey dey run for Mainnet, Preprod and Preview.

Cardano Node dey process and validate transactions, including ADA transfers, and e dey support block production by stake pools. Operators dey maintain and upgrade that infrastructure. Users wey delegate ADA to pool dey rely on di pool operator to manage di pool nodes.

Di IPv4 correction specifically address behavior wey 11.1.2 introduce. Di wider recommendation to run at least that version follow earlier issue wey dem identify for di Preprod testnet.

Intersect Upgrade Recommendation

Operators wey dey run versions wey older pass 11.1.2 suppose move directly to 11.1.3. Those wey already dey on 11.1.2 don meet Intersect stated minimum, while 11.1.3 add di IPv4 correction. Di announcement no specify any deadline to move between those two releases.

Intersect confirm say no ledger replay dey required, meaning say operators no need to recalculate ledger state from historical blocks as part of di update.

For operators wey dey upgrade from older releases, di migration requirements wey 11.1 series introduce still relevant. These include removal of di LMDB storage backend and di legacy tracing system. Operators wey still dey use LMDB must switch storage backends, and those wey rely on legacy tracing must migrate their monitoring setup.