AlcorDocs

Account factory

Create an Antelope account on Telos, WAX or XPR with one token transfer: contracts, memo formats, fees, refusals.

The account factory creates a new account from one transfer. Send a listed token to the factory with a memo that names the account and carries its keys; the factory creates the account in the same transaction and sends it whatever is left after the fee. No account, signature or RAM is needed on the receiving side beforehand.

The code is the same contract on every network.

Networks

NetworkContractNames it makesNative token feeNames reserved while a deposit travels
Telosac<nick>.ac, nick 1–9 chars0.9953 TLOSyes — only ac can create *.ac
WAXal<nick>.al, nick 1–9 chars2.00000000 WAXyes — only al can create *.al
XPR Networkac.alcorplain names, 4–12 chars, no dot11.0000 XPRno — anyone can register a plain name first

Fees change. Always read them from the chain before sending (see Fees).

Create an account

One transfer to the factory, memo <account>:<owner key>:<active key>:

# Telos
cleos -u https://telos.greymass.com transfer alice ac "1.5000 TLOS" \
  "vasya.ac:PUB_K1_6MRy…:PUB_K1_5b3z…"

# WAX
cleos -u https://wax.greymass.com transfer alice al "3.00000000 WAX" \
  "vasya.al:PUB_K1_6MRy…:PUB_K1_5b3z…"

# XPR (plain name, no suffix)
cleos -u https://proton.greymass.com transfer alice ac.alcor "15.0000 XPR" \
  "vasya:PUB_K1_6MRy…:PUB_K1_5b3z…"

In the same transaction the factory runs:

eosio::newaccount   factory -> <account>   owner and active: one key each, threshold 1
eosio::buyrambytes  4096 bytes, paid by the factory
eosio::delegatebw   NET/CPU stake, not transferred (on XPR: eosio.proton::newaccres instead)
<token>::transfer   factory -> <account>   quantity - fee, memo "Welcome to Alcor"

Check the result with get_account <account>.

Memo rules

  • Name. a-z and 1-5 only, no dots in the nick. Telos and WAX: the suffix .ac / .al is required, the whole name is at most 12 characters. XPR: no suffix, 4–12 characters.
  • Keys. PUB_K1_, PUB_R1_ or PUB_WA_, checksum verified. The legacy EOS… form is refused — convert it to PUB_K1_ first.
  • Tail. Anything after the first | is ignored.
  • topup. A memo of exactly topup refills the factory's reserve and creates nothing. Do not use it by mistake.

Digits-only memo

For senders that allow only digits in a memo (many exchanges), the same request is exactly 108 digits:

<account name as uint64, zero-padded to 20 digits><K1 key: 33 bytes + 4 checksum bytes as one big-endian number, zero-padded to 88 digits>

The one K1 key becomes both owner and active. The 88-digit part is exactly the number the base58 of PUB_K1_… spells, so the checksum still catches a typo.

const BASE58 = '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'
const NAME_CHARS = '.12345abcdefghijklmnopqrstuvwxyz'

function nameToUint64(name) {
  let value = 0n
  for (let i = 0; i < name.length; i++) value |= BigInt(NAME_CHARS.indexOf(name[i])) << BigInt(64 - 5 * (i + 1))
  return value
}

export function numericMemo(account, k1Key) {
  if (!k1Key.startsWith('PUB_K1_')) throw new Error('the key must be PUB_K1_')
  let key = 0n
  for (const c of k1Key.slice(7)) key = key * 58n + BigInt(BASE58.indexOf(c))
  return nameToUint64(account).toString().padStart(20, '0') + key.toString().padStart(88, '0')
}

numericMemo('vasya.ac', 'PUB_K1_4yTp9kp2JsTudNPiZsJwTEdtK4QqAceoKwwMNYNTx1cMpFTRgW')
// '15686568569603096576' + 88 digits

A memo of digits only is always read this way; anything else is read as the text form.

Sending again to the same account

The factory remembers every account it made and the hash of its keys. A later transfer with the same name and the same keys is forwarded to that account in full, with no fee (memo Deposit to your Alcor account). The same name with other keys is refused as account name is taken.

Fees

Table fees, scope = the token's contract. Only a listed contract + symbol + precision pays; the same symbol from any other contract is refused.

# which token contracts are listed
curl -s https://wax.greymass.com/v1/chain/get_table_by_scope \
  -d '{"code":"al","table":"fees"}'

# fees for one token contract
curl -s https://wax.greymass.com/v1/chain/get_table_rows \
  -d '{"code":"al","scope":"eosio.token","table":"fees","json":true}'
# {"rows":[{"fee":"2.00000000 WAX"}], ...}

Listed on 2026-11-20:

Factoryeosio.tokenwrap.alcor (bridged tokens)
Telos acTLOSUSDT, USDC, ETH, BNB, POL, SOL, SUI, NEAR, GRAM, WAX, XPR, A, EASY
WAX alWAXUSDT, USDC, ETH, BNB, POL, SOL
XPR ac.alcorXPRUSDT, USDC, ETH, BNB, SOL

The amount sent must be at least the fee; everything above it lands on the new account.

From another chain

Bridged tokens (wrap.alcor) reach the factory through the Alcor bridge: the deposit carries the factory's memo, and the bridge delivers it to the factory with that memo.

  • Telos factory (ac) — deposit on the source chain with telosTo = ac and the factory memo as the deposit memo.
  • WAX (al) and XPR (ac.alcor) — deposit to the hop on Telos; the factory memo goes after the hop memo's second |: <hop memo to the factory>|<factory memo>. Take the hop memo template from the bridge's /v1/routes (how.deposit.memo) with <account> set to the factory's contract.

The whole deposit memo must fit 256 bytes. When the text memo does not, use the digits-only memo.

If the factory refuses a bridged deposit, it is bounced back to the sender's chain about an hour later.

With a deposit address

The simplest sign-up for a user with no wallet: your app makes the keys, the user picks a name, and you show them an address. The first deposit to it, on any network the answer lists and straight from an exchange too, creates <nick>.ac on Telos and puts the rest on it. The user needs no gas and signs nothing. Telos only, for now.

curl -X POST https://telos.alcor.exchange/api/bridge/v1/deposit-addresses \
  -H 'content-type: application/json' \
  -d '{ "chain": "telos", "to": "ac", "leg": "vasya.ac:PUB_K1_6MRy…:PUB_WA_4d4B…" }'
  • leg is the factory memo, text or 108 digits, exactly as in Create an account. It is hashed into the address as sent: no spaces, no trimming. The digits form is shorter and gets an address on more networks.
  • The answer is that of an ordinary deposit address, plus account, the name it creates. tokens lists only what the factory takes, and least already includes the factory fee.
  • 400 NAME_TAKEN: the name is someone else's, ask for another. 400 INVALID_REQUEST: the factory would refuse the memo. Show the message.
  • The address stays the account's. Later deposits to it reach the account whole.

GET /v1/deposit-addresses/<address> adds accountState: free (not created yet), created (created, with these keys) or taken (someone else registered the name before the deposit arrived). In that last case the deposit comes back to the address and waits under held, with code: "NAME_TAKEN". Let the user choose another name:

curl -X POST https://telos.alcor.exchange/api/bridge/v1/deposit-addresses/<address>/rename \
  -H 'content-type: application/json' -d '{ "account": "petya.ac" }'

The money goes on to the new name about two days later. Show the new name's own address for further deposits.

The keys are the account. Generate them on the user's device, keep the private keys there, and send only the public keys. Anyone who has seen a private key owns the account.

Refusals

Every check fails the whole transfer: the tokens never leave the sender.

MessageCause
this token does not pay for accountscontract + symbol not in fees
token precision does not match its listingsame symbol, different precision
deposit is below the account feequantity < fee
memo must be <nick>.ac:<owner key>:<active key>empty memo, or not three parts
account name must end with .acwrong or missing suffix (Telos; .al on WAX)
account name is longer than 12 charactersname too long
nick cannot contain a dota.b.ac
character is not in allowed character set for namesuppercase, 0, 6–9, other characters
key must be PUB_K1_, PUB_R1_ or PUB_WA_unknown prefix or legacy EOS…
key is not valid base58 / key is too short / key has the wrong lengthmalformed key
numeric memo must be 108 digitsa digits-only memo of another length
account name is takenthe name exists, and not as this factory's account with these keys

Checklist for an agent

  1. Pick the network and its factory from Networks.
  2. Check the name is free: get_account <name> must fail.
  3. Read the fee for the token you will send from fees.
  4. Build the memo: text form, or digits-only if the sender allows only digits.
  5. Send at least the fee. After the transaction, get_account <name> shows the new account with your keys.
  6. No wallet to send from? Ask for a deposit address instead of steps 3–5, and show it.

On this page