Anna Shaleva
Anna Shaleva
> Is Neo going to offer an MPC setup solution? I'm not aware of it, that's why I'm interested in the way how it's planned to be held. > The...
@doubiliu, thank you for the reply, I see that the library you've provided can be used by dApp developers to generate circuit-specific randomness. However, let's clarify the last thing: >...
Peer disconnection may happen due to a various set of reasons and sometimes it may be a WARN. What we may do wrt this logic is try to split WARN/INFO...
I need to check the code, we have a various set of peer disconnection reasons. Will be done when the task is taken to work.
Within the scope of this issue we should also apply `Required` flags functionality where needed and functionality that allows to require one flag from a set of flags. See https://github.com/nspcc-dev/neo-go/pull/3278#issuecomment-1869444068...
We have POC written by @fyrchik in https://github.com/nspcc-dev/neo-go/tree/neotest-coverage, so let's keep this branch linked for now.
The https://github.com/nspcc-dev/neo-go/pull/2887#discussion_r1086394998 should also be fixed within the scope of this issue.
We can also add generic wrappers for event-related methods that can be generated by RPC binding generator (`*EventsFromApplicationLog`, etc), see https://github.com/nspcc-dev/neo-go/pull/3008#discussion_r1202990441.
https://github.com/nspcc-dev/neo-go/issues/3100 can also be supported using generics.
GH jobs are OK, we may close this issue.