EvtLink, everiPay, everiPass

This documentation describes detail information about everiPass / everiPay / Payee QR Code.



everiPass / everiPay is a brand new way to do face-to-face payment or to validate ownership of a token (for example, to validate the ownership of a ticket when going through a gateway). People use their wallet app (or even a webpage) to generate a dynamic QR Code as a proof that he/she is the owner of specific token (both NFTs / FTs).

Here is a example UI of everiPass:


These QR Codes is encoded using a text which has a format called EvtLink. It is a compact format to contains all the information needed for transactions in a short text.

EvtLink is also used to generate payee QR Code. Payee QR Code is a static QR Code containing the address of the token receiver. It's another way to pay tokens based on everiToken. For detail, see highlights below.


everiPay / everiPass

everiPay/everiPass is a payment method born for face-to-face micropayments using everiToken public block chain.

everiPay/everiPass includes the standard of QR code generation and the definition of communication protocol. Based on everiToken public blockchain with seven characteristics:

  • Instant Clearance, A transaction is a settlement.
  • Decentralization: P2P payment, no centralized platform, no one can modify the data on chain, everyone can participate in pricing.
  • Most secure: The data and content in the block chain can not be forged or tampered with, so as to maximize the protection of user's property security.
  • Most Convenient: Even if you can’t connect to the Internet, you can complete the transaction. Payer / Payee doesn't need to input the amount of money manually. Payer and payee will receive notification as soon as the transaction is successful.
  • Compatible: everiPay/everiPass support all Tokens supported by everiToken, not only currency but also tokens and points, even a key to open a door, and you can use it almost everywhere, just with your phone.
  • Fast: The everiToken has achieved high TPS, we think that a transaction can be completed within 1 - 3 seconds considering the situation of equipment and network.
  • Standardization: Different with technologies from wallet side, EvtLink is a cross-wallet cross-chain cross-app standard directly made for the whole ecosystem, you can use any apps to create or parse it.

Based on the above seven characteristics, everiPay/everiPass can provide the most secure, most convenient and enjoyable services in face-to-face payments.

For everiPay / everiPass, payee must use a app that supports parsing EvtLink and pushing transactions to everiToken. It is easy as we provide easy-to-use APIs and code examples for developers. It is similar to add AliPay / WeChat support for your store, but even much easier.

Payee QR Code

Payee QR Code does not support many features comparing to everiPay, for example, payers must connect to Internet for payment, and payers & payees must input amount of money manually and they won't receive notification when payment is finished automatically.

However, payees don't need to use apps that supports this payment method. In fact, what payees needed to do is just using a wallet on their phone to check if they received the money from the payer. It is suitable for very small stores or persons.

Using everiPay instead of Payee QR Code is recommended for anyone who is able to.

How do users use everiPay / everiPass / payee QR Code

For everiPay

  1. The owner of some token (both NFTs and FTs) use his / her wallet app (or even a single webpage) to generate a series of QR codes (each of them represents a EvtLink).
    • The QR code will keep changing every several seconds. Old codes will expire very soon (currently about 20 seconds).
    • The QR code is made up of current time, the id of the token he / she wants to use and owner's signature for the link.
  2. Payee use a everiPass-compatible scanner / a mobile phone or any other kinds of QR code scanner to read the code and get the decoded EvtLink inside it. The link is then included in a transaction and pushed by the machine / phone / scanner.
  3. The BP received the transaction with the EvtLink inside and check the signatures and then execute actions in the link.

For everiPass {for-everipass}

Almost the same as everiPay except for:

  • Normally the scanner is fixedly installed on a gateway or some similar machine.
  • After scanning, no transfer is executed. The chain just check the ownership of the token to make sure he / she has the permission to pass the gateway / door. Destroying the token after scanning automatically is supported and optional.

For Payee QR Code

  1. Payees show Payee QR Code to the payer. The code could even be printed on a paper and paste it on the wall as it is static.
  2. The payer then scans the payee QR Code using their wallet app.
  3. The payer inputs the amount to pay and then executes transfer actions on the chain just in normal way.
  4. The payee refreshes his / her wallet and confirms the token is received.

Using everiPay instead of Payee QR Code is recommended for anyone who is able to.

For everiPay / everiPass

everiToken public chain use everipass action and everipay action to execute the transaction of evtLink. it also provides a struct named evt_link to represent EvtLink. For detail information, please refer to the API / ABI documentation of everiToken.

Here is the technically process of payments via everiPay / everiPass:

  1. The payer select a kind of token to use, and the wallet of the payer show a series of dynamic QR Codes consisting of a unique 128-bit LinkId, a signature of the payer and the symbol of the token for payment.

    Note that the LinkId shouldn't be changed during QR Code changing unless related transaction is executed. Else the risk of duplicate payment can't be ignored. The chain doesn't allow two actions with EvtLink with a same LinkId.

  2. The wallet of payers should then continuously querying transaction id related with the LinkId by calling a API called get_trx_id_for_link_id until it returns a valid transacion id. After that the wallet should change the LinkId the next time it shows QR Code. And the wallet should show the transaction result by querying this transaction id. Wallets of payers don't need to send transactions directly.
  3. Meanwhile, the payee scans for the QR Code using their phone, scanner or smart gateway. After EvtLink is scanned and parsed, it should be wrapped in a a action and then be pushed to the chain. After that, all the chain nodes will synchronize the result so get_trx_id_for_link_id will return the transaction id instead of 404.

For Payee QR Code

Payee QR Code is equal to a payee's address. The wallet of the payer will commit a transaction to transfer the balance of selected token to this address. It's the same to normal transfer transactions.

Development based on evtjs

evtjs has full support for EvtLink and everiPay / everiPass / payee code. It is recommended to use evtjs as the groundwork to build your project.

EvtLink is the class you should use to create or parse EvtLink. The function pushTransaction of class APICaller should be used to push everiPay action onto the chain. For detail, please see the documentation of evtjs project.

We also publish the structure of EvtLink so you can process it manually.

Each EvtLink has the struct as below:


-base42signaturesList is required for everiPass / everiPay and not necessary for payeeCode.

[https://evt.li/] is optional prefix and will be ignored when parsing EvtLink. The purpose of adding this prefix is to guide people who didn't use suitable scanners to download a wallet of everiToken, or to know what the QR Code is made for.

We use base42 encoding because this encoding of QR Code is very efficient.

base42 Encoding

Base42 is a encoding for binary-to-string convertion. It is similar to hexadecimal encoding, but instead use 42 as its base and correspondingly use a different alphabet. The chars in the alphabet are matched with the chars in encoding of QR Code's alphanumeric mode so it's efficient. Thereby the size of QR Code could be smaller.

Below is the alphabet of base42:


Note that the index of a char (from zero) means the value of the char too. So A is 10 and : is 41.

For binary starts with one or more zero, you should add 0 to encoded result.

For example, for this byte array:

[ 0, 0, 0, 2, 41, 109, 0, 82, 0 ]

The encoded result is 000AD1KQVMO. The count of prefixed zero is the same as the count of prefixed zero in original byte array.

Segments Stream

Segments stream is a binary structure which contains one or more segment with a flag as the header:


Flag is the place to set some proterties of the link. Different flag can be added together. So 7 means ( 1 + 2 + 4 ). This table shows the detail:

flag meaning
1 protocol version 1 (required)
2 everiPass
4 everiPay
8 should destory the NFT after validate the token in everiPass
16 payee's QR code

Below is the struct of each segment:


typeKey is a unsigned byte.

Different typeKey has different data types for its value.

from to (included) data type
0 20 1-byte unsigned integer
21 40 2-byte unsigned integer (BE)
41 90 4-byte unsigned integer (BE)
91 155 string
156 165 uuid
166 180 byte string
180 255 remained

Here is a brief reference of common used typeKey for convenient.

typeKey flag description of value
42 (uint32) unix timestamp in seconds
43 (uint32) max allowed amount for everiPay
44 (uint32) symbol id to be paid in everiPay (for example: "1" for EVT)
45 (uint32) symbol id to be received in PayeeCode (for example: "1" for EVT)
91 (string) domain name to be validated in everiPass
92 (string) token name to be validated in everiPass
94 (string) max allowed amount for payment (optionl, string format remained only for amount >= 2 ^ 32)
95 (string) public key (address) for receiving points or coins
96 (string) count to receive in PayeeCode, should use decimal with proper precision
156 (uuid) link id(128-bit)


Signatures is encoded using compact binary format (fixed 65-byte for a signature). If it is a multisign, the decoded base42signaturesList will put them one by one. There is no length prefix or separator during them:

<65-byte sign><65-byte sign><65-byte sign><65-byte sign>...

Each signature has a fixed 65-byte length, first byte is for recoverParam, and is followed by a 32-byte big integer for r and then a 32-byte big integer for s:



Here is an examples of valid EvtLink (everiPass):


Use evtjs we can parse this link and get its structure by parseEvtLink, the result should be like this:

  "flag": 11, 
  "segments": [
      "typeKey": 42, 
      "value": 1532709368
      "typeKey": 91, 
      "value": "nd1532709365718"
      "typeKey": 92, 
      "value": "tk3065418732.2981"
      "typeKey": 156, 
      "value": {
        "type": "Buffer", 
        "data": [
  "publicKeys": [
  "signatures": [

In this example there are 3 signatures in it. We can get public keys that are used to sign on the link using evtjs's parseEvtLink. It has a flag of 11 (1 + 2 + 8) which means version 1, everiPass and auto destory.