LootToken (ERC-20)

A plain ERC-20 deployed alongside the protocol contracts. Address and explorer link: Deployments.

Scope of this page

This page documents contract mechanics only. It makes no representation about value, distribution, or future use.

Properties

name()	LootFi
symbol()	LOOT
decimals()	18
totalSupply()	1,000,000,000 — fixed
Upgradeable	UUPS proxy, owner-authorized

The entire supply was minted once to the treasury address during initialization. There is no mint function callable after initialization, so the supply cannot increase.

There is no transfer tax, no rebasing, no reflection mechanism, no burn-on- transfer, and no staking module. It is a standard OpenZeppelin ERC20Upgradeable with ownership and UUPS upgradeability.

Current role in the protocol

LootToken plays no part in the deposit, mint, or withdrawal paths, and every marketplace fill today settles in native ETH.

It is allow-listed as a payment currency on the deployed LootMarket (allowedCurrency returns true for it), so the contract would accept an order priced in it. The LootFi app and API do not: they create, display and fill ETH-only orders. Treat ERC-20 orders as unsupported by the product even though the contract permits them — nothing in this interface will price one for you.

You can verify this yourself:

cast call 0xb455Da2D860FabCe8ee6B0DA96398c4CACf14229 \
  "allowedCurrency(address)(bool)" 0x5450869fF4AaFF503d3Fd643480dA3ce6782B994 \
  --rpc-url https://rpc.mainnet.chain.robinhood.com
# → false

The contract-level mechanism by which any ERC-20 could become a payment currency is setCurrencyAllowed, an owner-only function on LootMarket. That is a description of what the contract is capable of, not a statement that it will happen. See Admin & upgrades.

Symbol collision with LootSkins

LootSkins (the ERC-721) also reports symbol() = "LOOT". They are different standards at different addresses. Match on the contract address, never the symbol — a wallet or aggregator that keys on ticker alone will confuse them.