HiveAuth
HomeGitHub
  • Introduction
    • Authentication
    • Signing and Broadcasting Transactions
    • Why use Hive Authentication Services?
  • Support
  • Developer documentation
    • Protocol description
      • Authentication
      • Transactions
      • Challenge
    • HAS for Applications
      • Connection
      • Encryption key (auth_key)
      • Authentication
        • Authentication request
        • Authentication payload
        • Authentication approval
        • Authentication refusal
        • Errors
        • Expiration
      • Transactions
        • Transaction request
        • Feedback to user
        • Transaction approval
        • Transaction refusal
        • Errors
        • Expiration
      • Challenge
        • Challenge request
        • Feedback to user
        • Challenge approval
        • Challenge refusal
        • Errors
        • Expiration
      • Attach
  • HAS for Wallets (PKSA)
    • Connection
    • Server Encryption Key retrieval
    • Proof of Key
    • Account registration
    • Authentication
      • Authentication payload
      • Authentications request
      • Feedback to user
      • Authentication approval
      • Authentication refusal
      • Errors
    • Transactions
      • Transaction request
      • Feedback to user
      • Transaction approval
      • Transaction refusal
      • Errors
    • Challenge
      • Challenge request
      • Feedback to user
      • Challenge approval
      • Challenge refusal
      • Errors
  • Tutorials
    • App code example
      • HAS Wrapper library
      • HTML code example
      • .NET code example
    • PKSA code example
      • Service Mode
  • Resources
    • Materials
Powered by GitBook
On this page
  1. HAS for Wallets (PKSA)
  2. Transactions

Transaction approval

PreviousFeedback to userNextTransaction refusal

Last updated 1 year ago

If the user approves the transaction request, the PKSA must check if the App requested it to broadcast the transaction to the blockchain.

If so, it must try to do it and inform the HAS upon success or failure.

If not, the PKSA must inform the HAS of the user's approval and return a signed transaction object.

In both cases, it will send the following message:

sign_ack

{
    cmd: "sign_ack",
    uuid: string,
    data : object,
    broadcast: boolean,
    pok: string
}
  • uuid: the transaction request identifier

  • data: the transactions id (txid) if broadcast is true or a signed transaction object (signed_tx) if broadcast is false.

  • broadcast: true if the transaction was broadcasted by the PKSA, otherwise false

  • pok: the uuid encrypted using the account private key and the HAS server public key (see )

Proof of Key