Use shared_future - develop #7043

heifner · 2019-04-01T20:32:37Z

Change Description

Since transaction_metadata future is accessed from multiple threads, use a shared_future which is thread safe.
Simplified recover_key usage and removed storage of sig_cpu_usage and signing_keys since they are stored in the shared_future.

…ifferent chain_id. Restores old behavior.

heifner added 4 commits April 1, 2019 16:30

Use shared_future instead of future since accessed across threads

fe39667

Simplify key recovery future logic

5b5a0a7

Calculate recovery keys instead of asserting if start not called or d…

3a2d2a2

…ifferent chain_id. Restores old behavior.

Add test for recover_keys without start_recover_keys

bdce0de

arhag approved these changes Apr 2, 2019

View reviewed changes

heifner merged commit 91c7806 into develop Apr 2, 2019

heifner deleted the sign-key-future-dev branch April 2, 2019 12:49