11.3.2 Service Node update
This release fixes recent issues observed on the chain since the hard fork:
- fixes a deadlock that could cause oxend to hang (and need to be forcibly restarted), most frequently encountered when using an l2 proxy.
- fixed a bug that did not properly clean up "zombie" records, and would prevent proper signature generation for claims and unlocks as a result.
- improves the reliability of pulse quorums properly validating incoming events from Arbitrum.
- Tweaks the default L2 provider settings to improve compatibility with provider free tiers:
- The default
l2-max-logs
option is decreased from 1000 to 500, for compatibility with some free tier offerings (such as Alchemy). Under normal operations this will not increase credit usage, but will use more credits upon oxend restart. (If you provider supports more, feel free to increase the value in your oxen.conf). - The default for the
l2-update-cooldown
option is now increased to 1.25s, to help avoid request per second rate limits imposed by some providers' free tiers (notably Infura), most commonly during oxend startup when it is fetching recent L2 events. Previously the option was disabled by default and oxend would try to request logs as fast as the responses arrive from the provider, but this could hit rate limits.
- The default
- Make oxend more robust against L2 failures. Previously failed L2 requests could end up leaving oxend in a state where it wanted to deny L2 transactions (because it failed to fetch them -- possibly because of rate limiting). Oxend now delays pulse participations and proofs until the L2 logs catch up rather than sending bad data to the network.
- Fix an issue with how RPC responses are being returned that causes problems in current Session clients.
While this is not a mandatory update, it is strongly recommended for all Service Nodes operators to update as soon as possible to avoid deadlocks and to improve network reliability.
Updating service nodes
For service node operators using Debian 11+ and Ubuntu 20.04+, the upgraded packages are available from our APT repository. Static binaries for other users are available below. Note that Ubuntu 20.04 support will be dropped in the near future, and operators on 20.04 should start planning to upgrade to 22.04 or 24.04.
Signatures for static release binaries
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Signed SHA256 hashes of release files. These are signed using Jason's GPG
key available at:
- the oxen-io/oxen-core repository, at /utils/gpg_keys/Jason.asc
- OpenPGP key servers (Jason Rhinelander <jason@session.foundation>, A88D4262)
- https://imaginary.ca/public.gpg
- https://github.com/jagerman.gpg
a5259693db75185dc16d0299a5c7903d2dd41872907cc95c9a14dbd02fdb9817 oxen-linux-x86_64-11.3.2.tar.xz
b12c5ca79f22fd37967a6b218a3af72d95c67c499a09c6d637774abc0db56e81 oxen-macos-arm64-11.3.2.tar.xz
775651decf75c06408a04922c4591d8e1c695fbf47e3ef681910dc53b23f60d6 oxen-macos-x86_64-11.3.2.tar.xz
1abac52d05c2096995217acaa8d694f5b84942d2dc7abd3dfdf3b78bf03b7c67 oxen-win-x64-11.3.2.zip
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEZjYdjjyW5Bxty3BRxJks56iNQmIFAmhAiSMACgkQxJks56iN
QmLbLxAAiXUCRRSV9TFt1BTVAtzcJI7lTc4JsixlaacMjaVVxuzekwkwdutmvH0O
0+jRJtxt5T+vyHx6/6Sr1tgVUB/liLPSZ7Dl3gswjTFS33/ymZc6d79C0wHVhvCA
r+kflncT5ZxRnPFPratf7IWmJu2e0C4ajf11OsdTF0cnX7nvM153jSQHnD1Fdksb
vtE3jnhy6o2RS0seGe7wx2eMWhQNGG7MbiPC58AMc9s54Y0VBEX4p6gTLivGF0Yg
oQmqoxE5Q7G+Pzqux3PZvn0LVQxWsADjOkAOpZz01spMh3WsZSSPWpI4Gp+IOB68
M+rhdulNFRHbhrDV4LtrxbPQRoUdpCANiDNYKW4IaN6My71IyYA6t963zz75hIoQ
imcvX7MF5bodiC7dHKRxYDYHQbYatelMr/jHiMZANX67crSzb+Wgk5b7qxV7ieUk
fbzWdvCWRrlqanPktChuO2CjlQKj724ie5vNv3aYEzEH9mVBbWpFG4JFKHkxgEy9
JNmKwr5f0RVO1W5pSeaSVmJvD0XhNca254UtdGRHt3RKPthUao3Tjh7AbUMrmOvF
Kn65dRXKDdwME4LHEBeE2hqkyEs87Tw2ZbuKtROcDm7zopvW1DTToSsr2MblYvf9
162jqEOeA5sHix9sz23XJvAInxNJ23jGaC5uvZvWWxDxmK/r5gg=
=Hoxj
-----END PGP SIGNATURE-----