`Receiver::scan_transaction()` => make `secp` a struct member?

[pythcoiner]

an secp context is initiated at each call of Receiver::scan_transaction(), so for ever scanned transaction, i'm wondering if it can be some performance improvements by making it a struct member?

[Sosthene00]

Yes that's a bit wasteful, but I don't know if the best solution is to make it a struct member, or to pass it as an argument to the function and let the caller handle it.

[cryptoquick]

You can also use a once cell to keep the global context global. It's part of the standard library now.

[pythcoiner]

You can also use a once cell to keep the global context global. It's part of the standard library now.

i'm not sure about having it as global, how will it behave if call concurently through a binding to another language?