Chainlist setup does not grant token spending rights

Adding a network through chainlist or setting it up by hand changes which blockchain a wallet can read; it does not give a site permission to spend your tokens. The difference matters because adding a chain, connecting an account and approving a token are separate actions. The same network details can be checked against chainlist before accepting the wallet’s request.

What does chainlist setup change?

It asks your wallet to add network settings, such as a chain ID and an RPC address. An RPC address is a server the wallet uses to read blockchain data and send transactions. The wallet should show a request for you to review and accept. That request adds the network to the wallet; it does not itself move funds or approve a token contract to spend them.

Manual setup reaches the same point by having you enter the network details yourself. The chain ID identifies the network, while the RPC address tells the wallet where to connect. You may also enter a network name, currency symbol or block explorer address. Either route can save time, but neither creates a spending allowance.

Does connecting a wallet let a site spend tokens?

No. Connecting usually shares your public account address with a decentralised app, or dapp, and lets it request actions from your wallet. A dapp can ask you to sign a transaction, but the wallet should present that request for your approval. Connecting is not the same as signing a token approval.

For many tokens, an approval is a separate on-chain permission that lets a contract move a set amount of a particular token from your account. The amount may be limited or very large. Once granted, it can remain active until it is used up or revoked, even if you disconnect from the dapp.

What should you check before approving?

Check the wallet prompt itself. Network details affect where the wallet reads and sends transactions; token approvals affect what a contract can spend. A familiar token name or symbol is not enough to identify a token, since different contracts can use similar names on different networks.

• Check the chain ID and RPC address when adding a network.
• Check the account and network shown when connecting to a dapp.
• For a token approval, check the token, receiving contract and spending limit.
• Choose a limit that covers the action you intend to take, when the wallet offers one.

If a prompt asks for an approval you did not expect, stop and check the contract and amount before signing. For most readers, the choice between chainlist and manual setup is about convenience and confidence in the network details. Spending permission comes later, in a separate prompt, and deserves its own review.