Is your feature request related to a problem? Please describe.
It would be useful for simulations if transactions could be inferred from orderbook state changes from other exchanges, so the transactions could be replayed later. This would be useful for benchmarking especially, since it's realistic data with realistic timestamps.
Describe the solution you'd like
Potentially work out benchclient and create a new daemon (like opencxd but much more limited) since these orders would have to conform to our format and pass validation, so pubkeys, etc would most likely have to be filled in. This really just tests the matching engine so maybe a new daemon is all that's necessary, just remove validation.
Describe alternatives you've considered
This is sort of similar to backtesting but is more for benchmarking and simulations. Backtesting isn't quite what we want, since we might want to determine realistic overhead or hardware required for various operations and configurations.
Additional context
Collecting, timestamping, and replaying this data is generally helpful for testing.
Is your feature request related to a problem? Please describe. It would be useful for simulations if transactions could be inferred from orderbook state changes from other exchanges, so the transactions could be replayed later. This would be useful for benchmarking especially, since it's realistic data with realistic timestamps.
Describe the solution you'd like Potentially work out
benchclientand create a new daemon (likeopencxdbut much more limited) since these orders would have to conform to our format and pass validation, so pubkeys, etc would most likely have to be filled in. This really just tests the matching engine so maybe a new daemon is all that's necessary, just remove validation.Describe alternatives you've considered This is sort of similar to backtesting but is more for benchmarking and simulations. Backtesting isn't quite what we want, since we might want to determine realistic overhead or hardware required for various operations and configurations.
Additional context Collecting, timestamping, and replaying this data is generally helpful for testing.