Somebody sent you a link. Should you trust it?

There is a group of connected software projects. Some work today. Some are finished but switched off. Some are just a name on a slide. They look almost identical from the outside, and telling them apart is the whole job.

This is the same research as the main guide, written for someone who has never bought a token or read a contract. Every plain sentence has the evidence underneath it, so you can check rather than believe.

Anyone can say anything. Few things leave a receipt.

A team can announce a product on a Monday. The announcement costs them nothing and proves nothing. What proves something is a thing you can go and look at yourself — a working site, a page of public code, a record on a public ledger nobody can quietly edit later.

Twelve words, and what each one does not mean

blockchain

A shared record that thousands of computers keep a copy of. Entries already written stay put.Does not mean the software reading and writing those entries is fixed. The record is permanent; the rules operating on it often are not.

a chain

One particular record. Paxeer is a chain, and each has an ID so your wallet knows which it is talking to.Paxeer has two: 125 for wallets and hyperpax_125-1 underneath. Both are right — one chain, an EVM surface on a Cosmos base.

token

An entry saying who owns how much of something. Making one takes minutes and costs almost nothing.Does not mean anyone is using it, or that its rules are locked.

contract address

The token’s real name, as a long string.Names, tickers, logos and supply figures can all be copied exactly. The address cannot.

explorer

A free website that lets you read the record. No account, wallet or money needed.Does not mean what you see there measures use. See checkpoint.

checkpoint

On this stack most agent activity is designed never to touch the chain; it is folded into one periodic summary.So the transaction count on the explorer counts checkpoints, not activity. An empty explorer here is not evidence in either direction.

upgradeable

A contract that can be swapped for entirely different code later, at the same address.The address you bookmarked stays valid; the behaviour behind it can change. SID on Paxeer is one of these.

verified (on an explorer)

Someone published the source and the explorer confirmed it matches what is deployed.Unverified means nobody outside the team can read what the contract does. SID on Paxeer is unverified — proxy and implementation both.

agent

A program you give a job to, which then takes several steps on its own.Less “chatbot that answers”, more “assistant that goes and does the task”.

open source

The instructions for building the thing are published for anyone to read.Does not mean you may use it. A licence decides that, separately.

testnet

A practice version, using play money.Real-looking screenshots often come from one.

validator

A machine that produces blocks.How many there are, and who runs them, decides how hard a chain is to stop. Paxeer currently shows four, none publicly identified.

Five labels, and what each one means for you

A sixth mark, Empty, sits next to Live on a few cards. It means the door opens and the shelves are bare. “You can open it” and “there is anything in it” are separate questions, so they get separate marks.

What each one is

One sentence each. The label tells you whether you can use it today; the small print is how that was checked.

Four checks and one non-check

1. Match the address, character for characterFake copies exist with the same name, the same ticker and a similar supply. The usual tells do not work here — the real SID also has a ~989M supply and revoked authorities, and its on-chain name is literally “Sidiora Markets”, which is what the fakes use too. Copy the address from a source you trust and paste it. Never search for the name.
2. Open the explorer and look for two thingsFirst, whether there is code at that address at all — if there is none, there is no product there, just an entry. Second, whether it says verified. Unverified means the source has not been published, so nobody outside the team can read what it actually does. Twenty seconds, no account needed.
3. Check who can change itAn upgradeable contract shows up on the explorer as a proxy: a small piece of code that forwards everything to a second address. Whoever holds the key can point it somewhere else, and the token then behaves differently at the address you bookmarked. Not automatically bad — plenty of legitimate projects do it. Something to know before rather than after.
4. Read what the team says about itselfThe most useful sentences here are the ones where the builders admit what is not finished. When a team publishes its own failing tests, believe that over any announcement.