While our main focus is still hyperchains, we made a new release. It is really important for the next SDK version - big thanks to @davidyuk . He identified and API bug, he prepared test case that exposes it and an actual fix in the core code ![]()
-
Fixes serialisation if
int-as-stringis enabled: numbers in lists gets
converted to strings,dry_runendpoint accepts balance as string. -
Introduces a State Channel option,
msg_forwarding :: boolean(), which enables forwarding of generic messages based on thefromandtoheaders.
Withoutmsg_forwarding: true, generic messages are discarded if thefromfield doesn’t match the peer pubkey and thetofield doesn’t match the
receiving FSM’s pubkey (thefromvalue is implicit and doesn’t need to be provided by the sender). Withmsg_forwardingenabled, the sending client
can optionally provide either a remotefromor a remoteto(currently not both at the same time). The receiving FSM will add anoticefield to
the report to the client: the notice value will be one ofdirect,please_forwardorforwarded, allowing the client to act accordingly.
Note that in order to forward a message, the client needs to have a State Channel open to the intended recipient, and copy the message to that
channel. An example can be found in theapps/channels/test/aesc_htlc_SUITE. -
Introduces a new HTTP endpoint for fetching peer pool stats: connected
(inbound and outbound), available for a new connection (verified and not yet
verified) and blocked peers. This is part of thenode-operatorgroup that
is bound to the internal interface and disabled by default. This new
endpoint is intended for the node operator to be monitoring its node’s
connectivity. -
Introduces a standalone binary artifact for supported platforms. Experimental.
It is deployed to the API nodes. Feel free upgrading your nodes in order to take advantage of the features.
We found a small problem with our infrastructure integration - we will likely publish 6.5.1 as well but it will not have any user-visible changes.