http://planet.i2p?i2paddresshelper=W0omtMApOdlTkgJoct08QnzDkeb~xc60df5Cx3k3qqOFmyEkRB65NdpSdvldI5STmXmXlZe68f8Hu1dfBMmKvfpBFMpP-mRVYuHbEa4N1dRkp3AOswZFO51lSC~MVPMZKGHAv0cfv5WFaJ9nfuaR7iYYWJF11xotoPTMbJdB-I3XPC8rxHI-73ATlOD4cU9oZ6BYcBE0dun9zw4IHBcRpnFRx~s-TkevNfPnBqujB-NNgA8a5s~QUj0h3FwwUWsNB8f1Uwy~DwoQh7pMp6dsZ3umEyBn2HaXZasSmbzB30qkQRs9vrAtIFdIzCQ~8gI2cHdHEPgExUQX~xlM8QZEgokoexilIPG53Co1kKARN0uCSxu8uCcP0FriGejPp3vdWdopxFLi2Oph4SMwKgD~QSLb54u-ZXlvBXLrKyr1xZC~KkDv45D4z8WN4kYjSpglcQGTEURWnYEDjVmS7oIrAiI7D-60cJ0qXfV2i7AjxmWaws4a41vV9hWJuRAzhZtYBQAEAAcAAA== rel=
p=3760 The automated migration from ECIES-only or ECIES+ElGamal to ECIES+MLKEM768 triggered some latent bugs in our leaseset lookup code (IterativeSearchJob). Results for lookups from destinations that did NOT support ElGamal would sometimes be misrouted. This bug was more likely to be hit at startup and on low-powered or low-bandwidth routers (Android, hidden mode, class L, firewalled, ...)