a9eb5a7d2b
We need to be able to sign more than just transactions to make DApps work properly. This change separates signing requests from the transactions and make it more general to prepare to intoduce different types of signing requests. This change is designed to preserve status APIs, so it is backward-comparible with the current API bindings. |
||
---|---|---|
.. | ||
README.md | ||
errors.go | ||
notifications.go | ||
pending_requests.go | ||
pending_requests_test.go | ||
request.go | ||
result.go |
README.md
sign
sign
package represents the API and signals for sending and receiving
signature request to and from our API user.
When a method is called that requires an additional signature confirmation from a user (like, a transaction), it gets it's sign request.
Client of the API is then nofified of the sign request.
Client has a chance to approve the sign request (by providing a valid password) or to discard it. When the request is approved, the locked functinality is executed.