Token markets run on claims. Most of them cannot be checked. This report examines five projects that have placed part of their record on public blockchains, in verified source code and locked positions, and it separates what a stranger can confirm from what still requires trust.
The problem this addresses
Anyone who has spent time in digital asset markets knows the pattern. A token appears with a promise, a website, and no way to test either. Sometimes the promise is honest. Often it is not. The difference rarely becomes clear until after the market has decided.
Public blockchains change one part of this. They do not make a project honest. They make certain statements mechanically checkable by anyone with a browser, at no cost, and without permission from the project. A fixed supply is either fixed in code or it is not. A pause function is either reachable or it is not. Liquidity is either held by an independent locker or it is not.
The wider context makes this more than a technical exercise. Regulators in several jurisdictions now ask issuers to disclose their control structures. Wallet security providers flag tokens that retain administrative powers. Exchanges and data platforms increasingly read the chain before they read a website. In that environment, the projects that publish a checkable record are answering the questions the market is already asking.
Four instruments of verification
Before the cases, a short list of what makes a token claim checkable at all.
- Verified source code. The contract source is published and matched to the deployed bytecode on a block explorer, so a reader can inspect the actual logic rather than a description of it.
- Role registers. Access control contracts record which addresses hold which powers. If an administrative role has no members, the function it gates cannot be called by anyone, whatever the marketing says.
- Transaction history. Burns, renouncements and liquidity operations are permanent public records with timestamps, written once and never edited.
- Locked liquidity. Independent locker contracts hold liquidity positions for fixed periods, and their holdings can be read directly from the chain.
BISA: a fund position with no administrator
BISA is a token on BNB Smart Chain that records a membership position in a digital asset trading fund. Its contract is an EIP 2535 diamond, a modular design in which functions are grouped into facets. The project published a technical and security document on 18 September 2026.
Three facts in that record stand out. First, supply: 2,500,000 tokens were issued and 1,900,000 of them, 76 percent, were sent to the dead address on 5 September 2026. Second, control: the operator renounced both of its administrative roles on 18 September 2026, and after those two transactions every role on the contract reads zero, including the roles governing minting and pausing. Third, liquidity: the main position, PancakeSwap V3 position 7287825, is held by a UNCX locker, and the largest pool is fully covered by the lock.
The document also does something less common. It separates the token from the fund in plain language, stating that the membership terms, including a 24 month commitment, are terms administered by the fund and are not written into the token code. A reader who assumes the code enforces the fund's rules would be wrong, and the project says so directly rather than letting the ambiguity sit.
The same precision applies to a detail that other projects quietly round off. The burn moved tokens to the dead address, so the contract keeps reporting a total supply of 2,500,000 while circulating supply is 600,000. Both numbers are public, and the document explains how to reconcile them instead of quoting only the convenient figure.
One control item remains outside the token: the upgrade right retained by the TokenFi launcher, which the project has publicly asked to have renounced, with the request record available. That is disclosed rather than hidden, and the disclosure itself is part of the story.
Astra Bitcoin: two contracts set up in opposite ways
Astra Bitcoin, ABTC, is a token on Ethereum with a fixed supply of 2,250,000 and a deliberately unusual structure: its two contracts are configured in opposite directions, and the project explains why.
The token contract, which holds user balances, is renounced. Its owner is the zero address, a value no person can control, so minting, pausing and ownership transfer are unreachable. The contract is an EIP 1167 minimal clone whose implementation is fixed in the bytecode rather than stored in an upgradeable slot, and both standard proxy slots are empty, so the code itself cannot be swapped out. There is no blacklist, no transfer fee and no transaction cap.
The sale contract, which handles payments, keeps an owner on purpose. The project's argument is direct: renouncing it would lock every payment inside it forever, strand unsold tokens, and remove the emergency stop for a stalled price feed. Instead of asking buyers to accept that on faith, the site publishes a set of 23 checks, run against live network state, that anyone can repeat from the block explorer. It also states plainly that ETH purchases rely on an honestly set manual rate, and offers stablecoin purchases that bypass the rate entirely at a constant 3.00 dollars per ABTC written into the contract.
The most unusual page in the record is a list of withdrawn claims. Earlier versions of the site described the token as tied to energy revenues, and later as redeemable against electricity bills. Those statements are withdrawn in writing, and the project states that no buyback or burn programme exists and that no listing is promised. Projects rarely publish corrections of their own marketing. This one has.
EUROFI: a community token with a locked floor
EUROFI's token, EURO, runs on Base, an Ethereum Layer 2. The project describes itself as a decentralized collective. Its token was minted once at 8,000,000 and 6,000,000 have since been burned, leaving a total supply of 2,000,000 with no mint function in the contract. Ownership is renounced.
Liquidity is locked with UNCX across five Uniswap v4 positions, covering EURO against ETH and USDC, for a period of about ten years according to the locker. The design intent, stated on the site, is a liquidity base that can deepen over time and cannot be quietly withdrawn.
The project's marketplace, the Bazaar, is running as a preview on a test network, and the site says so plainly: sample listings, no real money, with real trading described as a later step. The security page is careful with language in a way that deserves mention. EUROFI publishes a self review, automated static analysis and a public test suite, and labels it explicitly as not yet an independent third party audit, committing to publish a signed report when an external review completes. The site is operated by EUROFI SRL, Costa Rica.
Swedcoin: a five year record on Tron
Swedcoin, SWED, is a TRC 20 token on Tron first issued on 12 May 2021. Its supply is 77,999,993 with six decimals. At the time of writing it has 1,813 holders and 14,196 transfers, and its presale contract holds 10,956,298 tokens in a final phase priced at one SWED per TRX. The token trades with no meaningful market depth, and the project does not claim otherwise.
The interesting part of SWED is its stated scope. The product, a system for trust deeds on a public ledger, is described as under development, with no launch date attached to it. The project publishes no price projection and no return claim, and its public channels are project accounts rather than personal ones.
For a token of this age with that market profile, the discipline of claiming less is itself a form of disclosure. The token continues to exist on a public ledger with a stable supply and an active presale contract, and the project asks to be judged on that record rather than on promises about a future market.
KAMIRAI: an exchange token for a live aggregator
KAMIRAI is the token of Kyorai, a non custodial exchange aggregator on BNB Smart Chain that routes swaps across more than twenty venues. A share of the aggregator's trading fees is used to buy KAMIRAI on the open market and burn it. The design belongs to a familiar category: an exchange token whose supply is intended to shrink as the venue is used.
On chain, the token's control surface is closed. Ownership is renounced, the owner reads as the zero address, and every privileged function, including the ones controlling the burn switch and an older anti bot mechanism, reverts for any caller. The burn switch and the anti bot window are both off and cannot be turned on again. Total supply is 888,888,888,888, and 416,151,751,221 tokens, 46.8 percent, have been sent to the dead address. The token has more than 16,000 holders, and the largest holder outside contract and liquidity addresses holds a small share.
One limit remains, and it is disclosed: a maximum transaction amount set at 0.5 percent of supply. The cap is frozen by the renouncement and cannot be changed by anyone. For ordinary holders it is a practical ceiling on single transfers, and the project publishes it rather than leaving it to be discovered.
Independent material exists for this project as well. A smart contract audit by Cyberscope is publicly available, rating the contract well with a low risk classification, and a wallet security provider reviewed the token and confirmed that it carries no malicious flags in its systems.
What the five have in common
Read together, the five records share a shape: fixed or capped supplies, renounced or precisely disclosed control, liquidity positions held by independent lockers, verified source code, and public statements of what the tokens are not. Four of the five have gone further and published formal documents: a whitepaper, a self review, an audit, and a list of withdrawn claims.
None of this is a guarantee of commercial success. It is a different kind of claim: that the mechanical parts of each project can be inspected rather than believed.
What none of this proves
A verified contract is not a safe investment. Verification says that the rules cannot be changed quietly. It says nothing about whether the underlying business will work, whether a market will exist, or what a token will be worth. Three of the five projects publish audit or review material, and for the others the verification is limited to the code and the chain itself.
There is also a category of claim that blockchains cannot check at all: statements about future events, partnerships, products and intentions. A reader should treat those with the same skepticism they would apply anywhere else, and judge the projects in this report by what is already on chain and on the record.
How to check any token in a few minutes
- Open the token on a block explorer and confirm the source code is verified.
- Read the supply, check whether a mint function exists, and find out who, if anyone, can call it.
- Look for the owner. If it reads as the zero address, no administrative function can be called again. If it is a live address, read what that address can do.
- Find where the liquidity lives, whether a recognized locker contract holds it, and until when.
- Read the last few hundred transfers. Real distribution looks different from a loop of self transfers.
About the operator
BISA and Astra Bitcoin are issued or operated by 3-102-960698 SRL, a Sociedad de Responsabilidad Limitada registered with the National Registry of the Republic of Costa Rica, with Dr. Antoun Toubia as manager and legal representative. Registration is not a licence to offer a digital asset. EUROFI is operated by EUROFI SRL, Costa Rica. Swedcoin operates under the trading name The Swedish Trust. KAMIRAI is the token of the Kyorai aggregator.
Sources
Every figure in this report was taken from the projects' public contracts and websites on 18 September 2026, and can be checked at the addresses below.
- BISA: contract on BNB Smart Chain at 0x4EDcCcCac1C33367400a576b914cF79C1616Db95, whitepaper at bisa.io, security page at bisa.io/security
- Astra Bitcoin: token at 0x8C45bC48a451F48cca403ff2DDba2dA0EA68c404 and sale contract at 0x7F4875c4a43daF0c31E411c6317C2ca265DDf8A0 on Ethereum, documentation at astrabitcoin.com
- EUROFI: contract at 0x832BCceD5bD431b31663576490344EA1c0Bea295 on Base, documentation at eurofi.org
- Swedcoin: contract at TLomkn2JKndsKM5c8g8cKnzAiGpGyUUxaR on Tron, site swedcoin.io
- KAMIRAI: contract at 0x12bfe0251Eb64c6e26d1A264673593D6164ca213 on BNB Smart Chain, site kamirai.com, audit in the public Cyberscope audits repository