The default behaviour should definitely be to verify transaction signatures as we currently do, but this is the slowest part of transaction processing so users may want to switch it off in some contexts at their own risk e.g. when fuzzing.
This is pretty easy to implement but we should think about how the API should look. Maybe a send_transaction_unverified method? We'd want to be sure we're not going to end up with a dozen send_transaction_* methods though
The default behaviour should definitely be to verify transaction signatures as we currently do, but this is the slowest part of transaction processing so users may want to switch it off in some contexts at their own risk e.g. when fuzzing.
This is pretty easy to implement but we should think about how the API should look. Maybe a
send_transaction_unverifiedmethod? We'd want to be sure we're not going to end up with a dozensend_transaction_*methods though