Keeper Wallet

en | ru

Keeper Wallet is an extension that allows users to securely interact with Waves-enabled web services from the Chrome browser.

Seed phrases and private keys are encrypted and stored within the extension and cannot be accessed by online dApps and services, making sure that users' funds are always protected from hackers and malicious websites. Completion of a transaction doesn't require entering any sensitive information.

Keeper Wallet is designed for convenience, so users can sign transactions with just a couple of clicks. Users can create multiple wallets and switch between them easily. And if a user ever forgets the password to the account, it can be recovered from the seed phrase.

Keeper Wallet API

On browser pages that operate under the http/https (not worked local pages with file:// protocol) with Keeper Wallet extension installed, KeeperWallet global object becomes available.

WavesKeeper global object is deprecated and is not recommended for future use.

In KeeperWallet you will find the following methods:

• auth
• publicState
• signAndPublishCancelOrder
• signAndPublishOrder
• signAndPublishTransaction
• signCancelOrder
• signOrder
• signTransaction
• signRequest
• signTransactionPackage
• signCustomData
• verifyCustomData
• notification
• encryptMessage
• decryptMessage
• resourceIsApproved
• resourceIsBlocked
• on

All methods, except for "on" operate asynchronously and return promises.

In code, you can use TypeScript types

On initialize window.KeeperWallet has not api methods. You can use KeeperWallet.initialPromise for waiting end initializing api. Example:

KeeperWallet.initialPromise.then(keeperApi => {
  /*...init app*/
  keeperApi.publicState().then(state => startApp(state));
});

In Keeper Wallet, for greater security and ease of use, each new website using API has to be allowed by the user. At the first attempt to use API (except "on"), the user will see a request to allow that website's access to Keeper Wallet. If the user agrees to allow access, the website is considered trusted and can use API on its pages. Otherwise, the website is blocked, and an error message will be displayed in response to all requests {message: "Api rejected by user", code: 12}. The users won't see new notifications. To grant access, the user will mark the website as trusted in the interface.

Description of methods

publicState

If a website is trusted, Keeper Wallet public data are returned.

Example:

KeeperWallet.publicState()
  .then(state => {
    console.log(state); //displaying the result in the console
    /*...processing data */
  })
  .catch(error => {
    console.error(error); // displaying the result in the console
    /*...processing errors */
  });

or

const getPublicState = async () => {
  try {
    const state = await KeeperWallet.publicState();
    console.log(state); // displaying the result in the console
    /*... processing data*/
  } catch (error) {
    console.error(error); // displaying the result in the console
    /*... processing errors */
  }
};

const result = await getPublicState();

REPLY

{
    "initialized": true,
    "locked": true,
    "account": {
        "name": "foo",
        "publicKey": "bar",
        "address": "waves address",
        "networkCode": "network byte",
        "balance": {
            "available": "balance in waves",
            "leasedOut": "leased balance"
        }
    },
    "network": {
        "code": "W",
        "server": "https://nodes.wavesnodes.com/",
        "matcher": "https://matcher.waves.exchange/"
    },
    "messages": [],
    "txVersion": {
        "3": [ 2 ],
        "4": [ 2 ],
        "5": [ 2 ],
        ...
    }
}

Description of query return fields

• initialized - boolean keeper initialized
• locked - boolean keeper in wait mode
• account – current account, if the user allowed access to the website, or null
• network – current Waves network, node and matcher addresses
• messages – signature request statuses
• txVersion – available transaction versions for each type

Possible errors

• { message: "Init Keeper Wallet and add account" } – Keeper Wallet is not initialized
• { message: "Add Keeper Wallet account" } – Keeper Wallet accessed, but there are no accounts
• { message: "User denied message" } – the user denied the website operation with Keeper Wallet

notification

Send message to keeper. Ypu can send message only 1 time in 30 sec for trusted sites with send permission.

notification facilitates input of the following data

• title - string (20 chars max) (required field)
• message - string (250 chars max) (optional field)

return Promise

Example:

KeeperWallet.notification({
  title: 'Hello!',
  message: 'Congratulation!!!',
});

Possible errors

• {message: "Incorrect notification data", data: "title has more than 20 characters", code: "19"} - Incorrect notification title
• {message: "Incorrect notification data", data: null, code: "19"} - Incorrect notification data
• {message: "Can't sent notification", data: {msg: "Min notification interval 30s. Wait 28.017s."}, code: "18"} - try to send later, you can send 1 message in 30 sec
• {message: "Api rejected by user", code: 12} the user denied the request or the website is not trusted.

encryptMessage

You can encrypt string messages to account in Waves network. You need have recipient publicKey.

KeeperWallet.encryptMessage(*string to encrypt*, *public key in base58 string*, *prefix is secret app string need for encoding*)

Example:

KeeperWallet.encryptMessage(
  'My message',
  '416z9d8DQDy5MPTqDhvReRBaPb19gEyVRWvHcewpP6Nc',
  'my app'
).then(encryptedMessage => {
  console.log(encryptedMessage);
});

Possible errors

• { message: "Init Keeper Wallet and add account" } – Keeper Wallet is not initialized
• { message: "App is locked" } – Keeper Wallet is locked
• { message: "Add Keeper Wallet account" } – Keeper Wallet accessed, but there are no accounts
• { message: "User denied message" } – the user denied the website operation with Keeper Wallet

decryptMessage

You can decrypt string messages from account in Waves network to you. You need have sender publicKey and encrypted message.

KeeperWallet.decryptMessage(*string to decrypt*, *public key in base58 string*, *prefix is secret app string need for encoding*)

Example:

KeeperWallet.decryptMessage(
  '**encrypted msg**',
  '416z9d8DQDy5MPTqDhvReRBaPb19gEyVRWvHcewpP6Nc',
  'my app'
).then(message => {
  console.log(message);
});

Possible errors

• { message: "Init Keeper Wallet and add account" } – Keeper Wallet is not initialized
• { message: "App is locked" } – Keeper Wallet is locked
• { message: "Add Keeper Wallet account" } – Keeper Wallet accessed, but there are no accounts
• { message: "User denied message" } – the user denied the website operation with Keeper Wallet

on

Allows subscribing to Keeper Wallet events.

Supports events:

• update – subscribe for updates of the state

Example:

KeeperWallet.on('update', state => {
  //state object as from KeeperWallet.publicState
});

If a website is not trusted, events won't show.

auth

This is a method for obtaining a signature of authorization data while verifying Waves' user. It works the same way as Web Auth API.

Example:

const authData = { data: 'Auth on my site' };
KeeperWallet.auth(authData)
  .then(auth => {
    console.log(auth); //displaying the result on the console
    /*...processing data */
  })
  .catch(error => {
    console.error(error); // displaying the result on the console
    /*...processing errors */
  });

or

const getAuthData = async authData => {
  try {
    const state = await KeeperWallet.auth(authData);
    console.log(state); // displaying the result on the console
    /*... processing data */
  } catch (error) {
    console.error(error); // displaying the result on the console
    /*... processing errors */
  }
};

const authData = { data: 'Auth on my site' };
getAuthData(authData);

auth facilitates input of the following data

• name – name of the service (optional field)
• data – a string line with any data (required field)
• referrer – a websites' full URL for redirect (optional field)
• icon – path to the logo relative to the referreror origin of the website (optional field)
• successPath – relative path to the website's Auth API (optional field)

Example

const authData = {
  data: 'Generated string from server',
  name: 'My test App',
  icon: '/img/icons/waves_logo.svg',
  referrer: 'https://waves.exchange/',
  successPath: 'login',
};

KeeperWallet.auth(authData)
  .then(data => {
    //data – data from Keeper Wallet
    //verifying signature and saving the address...
    console.log(data);
  })
  .catch(error => {
    //processing the error
  });

If the verification is successful, Keeper Wallet will return to the promise an object containing data for signature verification:

• host – a host that requested a signature
• name – the name of an application that requested a signature
• prefix – a prefix participating in the signature
• address – an address in Waves network
• publicKey – the user's public key
• signature - signature
• version – API version

ERRORS

• {message: "Invalid data", data: "[{"field":"data","type":"string","message":"field is required"}]", code: 9} – signature data contain errors
• {message: "User denied message", code: 10} – the user denied the request
• {message: "Api rejected by user", code: 12} - the website is not trusted

signTransaction

A method for signing transactions in Waves' network.

Example:

const txData = {
  type: 4,
  data: {
    amount: {
      assetId: 'WAVES',
      tokens: '1.567',
    },
    fee: {
      assetId: 'WAVES',
      tokens: '0.001',
    },
    recipient: 'test',
  },
};
KeeperWallet.signTransaction(txData)
  .then(data => {
    //data – a line ready for sending to Waves network's node (server)
  })
  .catch(error => {
    //Processing errors
  });

API returns lines, not an object, as in javascript precision is lost in operation with 8-byte integers.

A description of supported transaction types is below.

In the example, we are signing a transaction for transferring WAVES to the alias testin Waves' network.

REPLY

{
  "version": 2,
  "assetId": "",
  "amount": 156700000,
  "feeAssetId": "",
  "fee": 100000,
  "recipient": "recipient",
  "attachment": "",
  "timestamp": 1548770230589,
  "senderPublicKey": "public key",
  "proofs": ["signature"],
  "type": 4
}

ERRORS

• {message: "User denied message", code: 10} – The user denied the request.
• {message: "Api rejected by user", code: 12} – The website is not trusted.
• {message: "Invalid data", data: "Reason", code: 9} – invalid/incomplete request data.

signAndPublishTransaction

This is similar to "signTransaction", but it also broadcasts a transaction to the blockchain.

Example:

const txData = {
  type: 4,
  data: {
    amount: {
      assetId: 'WAVES',
      tokens: '1.567',
    },
    fee: {
      assetId: 'WAVES',
      tokens: '0.001',
    },
    recipient: 'test',
  },
};

KeeperWallet.signAndPublishTransaction(txData)
  .then(data => {
    //data - a line ready for sending to Waves network's node (server)
  })
  .catch(error => {
    //processing errors
  });

REPLY

A reply from Waves network returns as a line containing the entire past transaction.

ERRORS

• Same as signTransaction
• {message: "Failed request", data: "Error description", code: 15} – a request was signed but not broadcast

signTransactionPackage

A package transaction signature. Sometimes several transactions need to be simultaneously signed, and for users' convenience, up to seven transactions at ones could be signed. Only certain types of transactions are permitted:

• 3 – issues a token
• 4 – transfer a token
• 5 – reissues a token
• 6 – burns a token
• 8 – leases WAVES
• 9 – cancels the leasing
• 10 – creating an alias for an address in Waves network
• 11 – mass transfer
• 12 - adds, modifies and deletes data entries in the sender's account data storage
• 13 - assigns the dApp script or account script to the sender's account
• 14 - configures sponsorship
• 15 - modifies the asset script
• 16 - calls the function from a dApp script

Example:

const name = 'For Test';
const tx = [
  {
    type: 4,
    data: {
      amount: {
        assetId: 'WAVES',
        tokens: '1.567',
      },
      fee: {
        assetId: 'WAVES',
        tokens: '0.001',
      },
      recipient: 'test',
    },
  },
  {
    type: 4,
    data: {
      amount: {
        assetId: 'WAVES',
        tokens: '0.51',
      },
      fee: {
        assetId: 'WAVES',
        tokens: '0.001',
      },
      recipient: 'merry',
    },
  },
];

KeeperWallet.signTransactionPackage(tx, name);

Sign two transaction:

• Transfer 1.567 WAVES to the alias test
• Transfer 0.1 WAVES to the alias merry

REPLY

A unit of two lines – transactions that are signed and ready to broadcast.

ERRORS

Same as in signTransaction

Transactions**

Every user of Waves' network has a state (balances, assets, data, scripts), and every past transactions changes these data.
In Keeper Wallet API it is different from NODE REST API.

signTransaction, signAndPublishTransaction accept transactions as follows

{
    type: number, //transaction type
    data: {
        ... //transaction data
    }
}

Legend keys

• • optional field, data are automatically supplied from KeeperWallet.
    [x,y] – length limit from x to y.
    [,x] – length limit to x.
    [y,] – length limit from y.
    [x-y] – number from x to y. x/y - x or y. (JLM) - JAVA LONG MAX = 9 223 372 036 854 775 807
    MoneyLike - price

MoneyLike could look as:

• { tokens: 1, assetId: "WAVES" }
• { coins: 100000000, assetId: "WAVES" };

In both messages, the same price of 1 WAVES is indicated. You can easily convert coinsinto tokensand back, if you know in what asset the price is indicated, and you have received its precision tokens = coins / (10 ** precision)
If the field contains other types than MoneyLike, for instance, string/MoneyLike , the sum is indicated as a number in  coins.

Type 3 ISSUE – token issue**

• name [4, 16] string – token name,
• description [0, 1000] string – token description,
• quantity [0 - (JLM)] number/string - quantity,
• precision [0 - 8] number - precision,
• reissuable true|false – re-issuable,
• *fee MoneyLike -fee
• *script string – smart asset
• *senderPublicKey string – sender's public key in base58
• *timestamp number/string – time in ms

Example:

KeeperWallet.signAndPublishTransaction({
  type: 3,
  data: {
    name: 'Best Token',
    description: 'Greate token',
    quantity: 1000000,
    precision: 2,
    reissuable: true,
    fee: {
      tokens: '1',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log("Hurray! I've created my asset!!!");
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

In case of a success, we are issuing a new asset in the quantity of 1,000,000, and your balance will show 10,000.00 Best Token

Type 4 TRANSFER – asset transfer**

• amount MoneyLike - amount,
• recipient string – recipient's address or alias
• attachment[,140 bytes] string or byte Array – additional info in text
• *fee MoneyLike - fee
• *senderPublicKey string – sender's public key in base58
• *timestamp number/string – time in ms

Example:

KeeperWallet.signAndPublishTransaction({
  type: 4,
  data: {
    amount: { tokens: '3.3333333', assetId: 'WAVES' },
    fee: { tokens: '0.001', assetId: 'WAVES' },
    recipient: 'merry',
  },
})
  .then(tx => {
    console.log("Hurray! I've been able to send WAVES!!!");
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

Type 5 REISSUE – token reissue**

• assetId string - "asset ID",
• quantity [0 - (JLM)] number/string/MoneyLike - quantity,
• reissuable false – deny reissue
• *fee MoneyLike -fee
• *senderPublicKey string – sender's public key in base58
• *timestamp number/string – time in ms

Example:

KeeperWallet.signAndPublishTransaction({
  type: 5,
  data: {
    quantity: 1000,
    assetId: '8LQW8f7P5d5PZM7GtZEBgaqRPGSzS3DfPuiXrURJ4AJS',
    reissuable: true,
    fee: {
      tokens: '1',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log("Hurray! I've reissued my asset!!!");
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

In case of a success, we are re-issuing a new asset in the quantity of 1,000,000, and your balance will show 10,000.00 Best Token

Type 6 BURN – burning tokens**

• assetId string – asset ID,
• amount [0 - (JLM)] number/string/MoneyLike - quantity,
• *fee MoneyLike -fee
• *senderPublicKey string - sender's public key in base58
• *timestamp number/string – time in ms

Example:

KeeperWallet.signAndPublishTransaction({
  type: 6,
  data: {
    amount: 1000,
    assetId: '8LQW8f7P5d5PZM7GtZEBgaqRPGSzS3DfPuiXrURJ4AJS',
    fee: {
      tokens: '0.001',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log("Hurray! I've burned unneeded tokens!!!");
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

In case of a success, 1,000 coins are burned.

Type 8 LEASE - Leasing**

• recipient string – recipient's address or alias,
• amount [0 - (JLM)] number/string/MoneyLike - quantity,
• *fee MoneyLike -fee
• *senderPublicKey string - sender's public key in base58
• *timestamp number/string – time in ms

Example:

KeeperWallet.signAndPublishTransaction({
  type: 8,
  data: {
    amount: 1000,
    recipient: 'merry',
    fee: {
      tokens: '0.001',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log("Hurray! I've been able to lease tokens!!!");
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

In case of a success, 0.00001000 WAVES is leased.

Type 9 LEASE CANCEL – cancel leasing**

• leaseId string – leasing transaction ID,
• *fee MoneyLike -fee
• *senderPublicKey string - sender's public key in base58
• *timestamp number/string – time in ms

Example:

KeeperWallet.signAndPublishTransaction({
  type: 9,
  data: {
    leaseId: '6frvwF8uicAfyEfTfyC2sXqBJH7V5C8he5K4YH3BkNiS',
    fee: {
      tokens: '0.001',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log("Hurray! I've cancelled leasing!!!");
  })
  .catch(error => {
    console.error('Something went wrong ', error);
  });

In case of a success, the leasing transaction is cancelled.

Type 10 CREATE ALIAS – creating an alias for an address**

• alias[4, 30] string - alias. Alias Requirements
• *fee MoneyLike -fee
• *senderPublicKey string - sender's public key in base58
• *timestamp number/string – time in ms

Example:

KeeperWallet.signAndPublishTransaction({
  type: 10,
  data: {
    alias: 'test_alias',
    fee: {
      tokens: '0.001',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log('Hurray! Now I have an alias!!!');
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

In case of a success, an alias (another name) is created.

Type 11 MASS TRANSFER - a mass transfer of an asset**

• totalAmount moneyLike – total to be sent // instead of calculating the amount you may insert { assetId: "ID of the asset to be sent", coins: 0},
• transfers  a mass of objects { recipient: string - address/alias, amount: number/string/moneyLike }
• *fee MoneyLike -fee
• attachment [,140 bytes в base58] string – additional info
• *senderPublicKey string - sender's public key in base58
• *timestamp number/string – time in ms

Example:

KeeperWallet.signAndPublishTransaction({
  type: 11,
  data: {
    totalAmount: { assetId: 'WAVES', coins: 0 },
    transfers: [
      { recipient: 'alias1', amount: '200000' },
      { recipient: 'alias2', amount: '200000' },
    ],
    fee: {
      tokens: '0.002',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log("Hurray! I've sent hi to my friends!!!");
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

In case of a success, 0.002 WAVES will be sent to alias1 and alias2.

Type 12 DATA TRANSACTION - saving data**

• data  mass of objects
  • type "binary"/string/"integer"/"boolean" - type,
  • key string – field name
  • value /string/string/number/boolean depends on the type
• *fee MoneyLike - fee
• *senderPublicKey string - sender's public key in base58
• *timestamp number/string – time in ms

Field:

KeeperWallet.signAndPublishTransaction({
  type: 12,
  data: {
    data: [
      {
        key: 'string',
        value: 'testVdfgdgf dfgdfgdfg dfg dfg al',
        type: 'string',
      },
      {
        key: 'binary',
        value: 'base64:AbCdAbCdAbCdAbCdAbCdAbCdAbCdAbCdAbCdAbCdAbCd',
        type: 'binary',
      },
      { key: 'integer', value: 20, type: 'integer' },
      { key: 'boolean', value: false, type: 'boolean' },
    ],
    fee: {
      tokens: '0.01',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log("Hurray! I've saved data!!!");
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

In case of a success, new data will be stored in the state.

Type 13 SET SCRIPT – scripting an account**

• script string - script
• *fee MoneyLike -fee
• *senderPublicKey string - sender's public key in base58
• *timestamp number/string – time in ms

For cancelling a script the field script has to be null. Script development on RIDE

Example:

KeeperWallet.signAndPublishTransaction({
  type: 13,
  data: {
    script: '',
    fee: {
      tokens: '0.04',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log("Hurray! I've cancelled a script!!!");
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

In case of a success, the script will be removed from the account.

Example 2:

KeeperWallet.signAndPublishTransaction({
  type: 13,
  data: {
    script:
      'base64:BQkACccAAAADCAUAAAACdHgAAAAJYm9keUJ5dGVzCQABkQAAAAIIBQAAAAJ0eAAAAAZwcm9vZnMAAAAAAAAAAAAIBQAAAAJ0eAAAAA9zZW5kZXJQdWJsaWNLZXmfT++m',
    fee: {
      tokens: '0.01',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log("Hurray! I've added a script!!!");
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

In case of a success, a new script will be added to the account, allowing any transactions without a signature (be careful!).

Type 14 Sponsored Fee Transaction - Sponsorship**

• minSponsoredAssetFee MoneyLike – fee price in the asset.
• *fee MoneyLike - fee
• *senderPublicKey string - sender's public key in base58
• *timestamp number/string – time in ms

Example:

KeeperWallet.signAndPublishTransaction({
  type: 14,
  data: {
    minSponsoredAssetFee: {
      assetId: '6frvwF8uicAfyEfTfyC2sXqBJH7V5C8he5K4YH3BkNiS',
      tokens: 0.1,
    },
    fee: {
      tokens: '1',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log("Hurray! I've become a sponsor!!!");
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

In case of a success, a transfer fee can be paid in the asset.

Type 15 SET ASSET SCRIPT – setting a script to an asset**

• assetId string – asset ID
• script string – script
• *fee MoneyLike – fee
• *senderPublicKey string - sender's public key in base58
• *timestamp number/string – time in ms

It's now impossible to cancel a script, you can only add a new script. Script development on RIDE

Example:

KeeperWallet.signAndPublishTransaction({
  type: 15,
  data: {
    assetId: '',
    script: 'base64:BQbtKNoM',
    fee: {
      tokens: '0.01',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log('Hurray! I have reset a script to the asset!!!');
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

In case of a success, the asset's script will be reset.

Type 16 SCRIPT INVOCATION - call account script function**

• dApp string – address script account
• call object –
  • function string function name
  • args array
    • type "binary"/string/"integer"/"boolean" - type,
    • value /string/string/number/boolean - value for type
• *fee MoneyLike – fee
• *payment array MoneyLike
• *senderPublicKey string - public key in base58
• *timestamp number/string - number/string – time in ms

Example:

KeeperWallet.signAndPublishTransaction({
  type: 16,
  data: {
    fee: {
      tokens: '0.05',
      assetId: 'WAVES',
    },
    dApp: '3N27HUMt4ddx2X7foQwZRmpFzg5PSzLrUgU',
    call: {
      function: 'tellme',
      args: [
        {
          type: 'string',
          value: 'Will?',
        },
      ],
    },
    payment: [{ assetId: 'WAVES', tokens: 2 }],
  },
})
  .then(tx => {
    console.log('Ура! Я выполнил скрипт!!!');
  })
  .catch(error => {
    console.error('Что-то пошло не так', error);
  });

In case of a success, invoke script function tellme in testnet account 3N27HUMt4ddx2X7foQwZRmpFzg5PSzLrUgU

Calculating transaction fees**

signOrder**

Keeper Wallet's method for signing an order to the matcher. As input, it accepts an object similar to a transaction like this:

{
    type: 1002,
    data: {
        ...data
    }
}

• *version 1,2,3
• amount MoneyLike - amount
• price MoneyLike - price
• orderType 'sell'/'buy' – order type
• matcherFee MoneyLike - fee (0.003 WAVES minimum),
• matcherPublicKey string - the public key of the exchange service
• expiration string/number – the order's expiration time
• *timestamp string/number - current time
• *senderPublicKey string - public key in base58

Example:

KeeperWallet.signOrder({
  type: 1002,
  data: {
    matcherPublicKey: '7kPFrHDiGw1rCm7LPszuECwWYL3dMf6iMifLRDJQZMzy',
    orderType: 'sell',
    expiration: Date.now() + 100000,
    amount: {
      tokens: '100',
      assetId: 'WAVES',
    },
    price: {
      tokens: '0.01',
      assetId: '8LQW8f7P5d5PZM7GtZEBgaqRPGSzS3DfPuiXrURJ4AJS',
    },
    matcherFee: {
      tokens: '0.03',
      assetId: 'WAVES',
    },
  },
})
  .then(tx => {
    console.log("Hurray! I've signed an order!!!");
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

REPLY: A line with data for sending to the matcher.

ERRORS:

• { message: "User denied message", code: 10 } – the user rejected the request
• { message: "Api rejected by user", code: 12 } – The website is not trusted
• { message: "Invalid data", data: "Reason", code: 9 } - invalid/incomplete request data

signAndPublishOrder

Keeper Wallet's method for creating an order to the matcher is identical to signOrder, but it also tries to send data to the matcher.

REPLY: the matcher's reply line about successful creation of an order.

ERRORS:

• Same as for signOrder
• {message: "Failed request", data: "Error description", code: 15} – a request has been signed, but not sent to the matcher

signCancelOrder

Keeper Wallet's method for signing cancellation of an order to the matcher. As input, it accepts an object similar to a transaction like this:

{
    type: 1003,
    data: {
        ...data
    }
}

• id string – order ID
• *senderPublicKey - string - sender's public key in base58

Example:

KeeperWallet.signCancelOrder({
  type: 1003,
  data: {
    id: '31EeVpTAronk95TjCHdyaveDukde4nDr9BfFpvhZ3Sap',
  },
});

REPLY: A data line for sending to the matcher.

ERRORS:

• { message: "User denied message", code: 10 } – the user rejected the request
• { message: "Api rejected by user", code: 12 } – The website is not trusted
• { message: "Invalid data", data: "Reason", code: 9 } - invalid/incomplete request data

signAndPublishCancelOrder

Keeper Wallet's method for cancelling an order to the matcher. It works identically to signCancelOrder, but also tries to send data to the matcher. For api need know also 2 field priceAsset and amountAsset from order.

Example:

KeeperWallet.signAndPublishCancelOrder({
  type: 1003,
  priceAsset: '8LQW8f7P5d5PZM7GtZEBgaqRPGSzS3DfPuiXrURJ4AJS',
  amountAsset: 'WAVES',
  data: {
    id: '31EeVpTAronk95TjCHdyaveDukde4nDr9BfFpvhZ3Sap',
  },
})
  .then(() => {
    console.log("Hurray! I've cancelled an order");
  })
  .catch(error => {
    console.error('Something went wrong', error);
  });

REPLY: Data that came from the matcher

ERRORS:

• Same as for signCancelOrder
• {message: "Failed request", data: "Error description", code: 15} – a request has been signed, but not sent to the matcher

signRequest

Keeper Wallet's method for signing typified data, for signing requests on various services. As input, it accepts an object similar to a transaction like this:

{
    type: number,
    data: {
        ...data
    }
}

Currently, the method supports the following types:

1001 – signing data for a request to the matcher for your orders

• timestamp number/string
• *senderPublicKey string public key in base58

Example:

KeeperWallet.signRequest({
  type: 1001,
  data: {
    timestamp: 234234242423423,
  },
});

REPLY: a line with a signature in base58.

ERRORS:

• { message: "User denied message", code: 10 } – the user rejected the request
• { message: "Api rejected by user", code: 12 } – The website is not trusted
• { message: "Invalid data", data: "Reason", code: 9 } - invalid/incomplete request data

signCustomData

Method Keeper Wallet for sign custom data for different services, it accepts an object:

version 1

• version 1
• binary string 'base64:....'

Note: This method adds the [255, 255, 255, 1] prefix to the signed bytes. This was done to make it impossible to sign transaction data in this method, which can lead to unauthenticated transactions and phishing. For the details check serializeCustomData method in waves-transactions library.

Example:

KeeperWallet.signCustomData({
  version: 1,
  binary: 'base64:AADDEE==',
});

REPLY:

   {
        version: 1,
        binary: 'base64:AADDEE==',
        signature: '...',
        publicKey: '...'
   }

ERRORS:

• { message: "User denied message", code: 10 } – the user rejected the request
• { message: "Api rejected by user", code: 12 } – The website is not trusted
• { message: "Invalid data", data: "Reason", code: 9 } - invalid/incomplete request data

version 2

• version 2
• data Array of
  • type "binary"/string/"integer"/"boolean" - field type,
  • key string - field name
  • value /string/string/number/boolean

Bytes to sign: [255, 255, 255, 2, ...(from data Array to bin)] waves-transaction library

Example:

KeeperWallet.signCustomData({
  version: 2,
  data: [{ type: 'string', key: 'name', value: 'Mr. First' }],
});

REPLY:

   {
        version: 2,
        data: [{ type: 'string', key: 'name', value: 'Mr. First' }]
        signature: '...',
        publicKey: '...'
   }

ERRORS:

• { message: "User denied message", code: 10 } – the user rejected the request
• { message: "Api rejected by user", code: 12 } – The website is not trusted
• { message: "Invalid data", data: "Reason", code: 9 } - invalid/incomplete request data

verifyCustomData

Validate custom data:

{
    version: 1,
    binary: 'base64:AADDEE==',
    signature: '...',
    publicKey: '...'
}

or

{
    version: 2,
    data: [{ type: 'string', key: 'name', value: 'Mr. First' }],
    signature: '...',
    publicKey: '...'
}

Example:

KeeperWallet.verifyCustomData({
  version: 1,
  binary: 'base64:AADDEE==',
  publicKey: '3BvAsKuGZe2LbSwKr9SA7eSXcNDKnRqN1j2K2bZaTn5X',
  signature:
    '2bLJYR68pwWrUUoatGbySz2vfY76VtzR8TScg1tt5f9DVDsFDCdecWrUiR4x6gFBnwF4Y51uszpouAwtSrg7EcGg',
}).then(result => {
  console.log(result);
});

REPLY: true/false

• { message: "User denied message", code: 10 } – the user rejected the request
• { message: "Api rejected by user", code: 12 } – The website is not trusted

resourceIsApproved

Check allow API status for your origin

Example:

KeeperWallet.resourceIsApproved().then(result => {
  console.log(result);
});

REPLY: true/false

resourceIsBlocked

Check block API status for your origin

Example:

KeeperWallet.resourceIsBlocked().then(result => {
  console.log(result);
});

REPLY: true/false