My questions must have gotten lost in the pack:
Two questions:
1.) Will the command_server functionality on the development branch be merged into master and rolled out with 0.8.8.5?
2.) If not, has any or all of the following fixes been incorporated into the development branch?: the spam attack patch; block 202612 attack patch; block 202612 attack mitigation and fork fix (via a whole new block blob hash checkpointing system)
Either one of these items would help move things forward on the Monero Client .NET GUI.
Reason being is that, at the moment, we can't use the test version of Monero Client .NET because it requires the command_server functionality in the daemon to properly function. Unfortunately, the latest available bitmonerod.exe binary from the development branch that has this also doesn't have the aforementioned patches incorporated into it, meaning that we can't use it anymore.
On the other hand, the most recent version of Monero Client .NET that does NOT require the binary from the development branch also contains a number of bugs (that have since been fixed in the test version) that make it annoying to use.
1.) Will the command_server functionality on the development branch be merged into master and rolled out with 0.8.8.5?
2.) If not, has any or all of the following fixes been incorporated into the development branch?: the spam attack patch; block 202612 attack patch; block 202612 attack mitigation and fork fix (via a whole new block blob hash checkpointing system)
Either one of these items would help move things forward on the Monero Client .NET GUI.
Reason being is that, at the moment, we can't use the test version of Monero Client .NET because it requires the command_server functionality in the daemon to properly function. Unfortunately, the latest available bitmonerod.exe binary from the development branch that has this also doesn't have the aforementioned patches incorporated into it, meaning that we can't use it anymore.
On the other hand, the most recent version of Monero Client .NET that does NOT require the binary from the development branch also contains a number of bugs (that have since been fixed in the test version) that make it annoying to use.
Anyone?
