just an echo of the params passed in, could still be useful when debugging
network
would enable clients to specify which network they are expecting and throw an error if they are connected to the wrong one. This failure would be silent and very frustrating otherwise
heartbeat
the heartbeat timeout that the server is configured with. incompatibility here (client heartbeat < server heartbeat) would cause a reconnect loop
maxConf
confirmation depth at which transactions are considered confirmed. if client > server in this config, the client will never fire a confirmed event
Also included a version v which could be a semver-style versioning of the wire protocol for devs (minor changes) or console warnings/thrown errors (major or breaking changes)
Changing the wire protocol for the initial event to piggy-back some configuration data that can cause issues if the client's config is incompatible
https://github.com/kadena-io/chainweb-sse/pull/4/files#diff-5a6a48a9df5bfafb9f9716accb2bb76c309a0f28c7230f846eb362a89085a29aR39
These are, in increasing order of importance:
type
+id
account
+k:abcdef..
network
heartbeat
maxConf
confirmed
eventAlso included a version
v
which could be a semver-style versioning of the wire protocol for devs (minor changes) or console warnings/thrown errors (major or breaking changes)