You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 10, 2019. It is now read-only.
Is your feature request related to a problem? Please describe.
Transaction receipts are supposed to be signed by the operator to ensure the user that the operator has actually received their transaction. However, currently the operator just sends back the same encoded transaction that was originally sent.
Describe the solution you'd like
The operator should sign the transaction (perhaps hash of the hash of the transaction to avoid tricking the operator into signing a send...) before sending it back to the client.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Transaction receipts are supposed to be signed by the operator to ensure the user that the operator has actually received their transaction. However, currently the operator just sends back the same encoded transaction that was originally sent.
Describe the solution you'd like
The operator should sign the transaction (perhaps hash of the hash of the transaction to avoid tricking the operator into signing a send...) before sending it back to the client.
The text was updated successfully, but these errors were encountered: