Nov 19, 2025

And you can see above I've also dealt with optional<> parameters, with defaults configured, and nullable<> parameters, where the json (or other) request can explicitly pass a null_t. In the former case, if the parameter is not provided, the default is injected into the method call. If a null is provided, the parameter will have no value (nullables get passed as a std::optional<T>). Optionals only trailing in the method signatures. All part of the magical dispatch, most of which is just compile time code. Very little actually happens at run time, and actually less than what was the case with the hand-rolled p2p dispatch. For example, the full dispatch map for each interface is defined and built statically, one for all connections to the node.