Coinmarketcap is a manual transaction log for building a first portfolio position

Manual CoinMarketCap entry versus an Ethereum wallet balance

A CoinMarketCap portfolio entry is an editable accounting record, while an Ethereum wallet balance comes from on-chain state. Recording 0.25 ETH in a portfolio creates a tracked position; receiving 0.25 ETH at an Ethereum address changes an actual wallet balance after a valid blockchain transaction.

This distinction determines the entire first-position workflow. A manual entry requires no wallet connection, private key, seed phrase, token approval, or blockchain fee. It also has no power to buy ETH, transfer an ERC-20 token, or prove that an address controls an asset. CoinMarketCap uses the supplied quantity, transaction type, price, date, fee, and notes to calculate the portfolio view.

Coinbase, Kraken, Uniswap, MetaMask, and Ledger record or expose different parts of real asset activity. An exchange account reflects trades and custody on that venue; Uniswap submits swaps through smart contracts; MetaMask manages account access; Ledger devices protect signing keys. The manual portfolio sits outside those settlement mechanisms and provides a separate performance ledger.

What must be ready before the first position is logged?

The first CoinMarketCap position requires a signed-in account, a portfolio, an identifiable asset, and the facts of the transaction. Keep the asset quantity, unit price, transaction date, transaction type, and any relevant fee available before opening the entry form.

Asset identity matters because tickers are not unique. ETH refers to Ether, while an ERC-20 asset such as USDC exists through token contracts on supported networks. Select the asset page associated with the intended project rather than relying on a ticker alone. Bitcoin uses 8 decimal places and one bitcoin contains 100,000,000 satoshis; Ether uses 18 decimal places and one ETH contains 1,000,000,000,000,000,000 wei. Those fixed units explain why small fractional quantities remain meaningful.

The portfolio's display currency provides the denomination for totals and performance. It does not change BTC into dollars or convert an ERC-20 balance on Ethereum. It simply gives the ledger a common reporting unit, so the entered acquisition price and the displayed market value can be compared consistently.

Which transaction mode creates the position?

The Buy transaction type creates a positive tracked holding in the selected asset. Transfer In also adds quantity, but it describes assets received from elsewhere rather than an acquisition at a chosen purchase price; the correct mode preserves the meaning of the ledger.

For a first manual buy, follow one primary action sequence:

1. Open the intended portfolio and choose Add Transaction.
2. Search for and select the exact cryptocurrency.
3. Choose Buy as the transaction type.
4. Enter the quantity, unit price, date, and fee shown by the original record.
5. Save the transaction, then open the asset position to inspect it.

A purchase of 2 SOL belongs under Solana, while 250 USDC requires the correct USD Coin asset selection. Solana's native unit is the lamport, and 1 SOL equals 1,000,000,000 lamports. USDC follows the token implementation of its issuing network; a manual CoinMarketCap entry does not bridge tokens or select a destination chain.

How does the saved transaction become a portfolio position?

A saved CoinMarketCap buy increases the asset's tracked quantity and contributes its cost to the position. The portfolio then combines that ledger data with market pricing to display value and performance, while the transaction history retains the individual entry.

The position should show the selected asset, the newly recorded quantity, an acquisition-cost basis derived from the entry, and a market value based on the platform's pricing data. A first buy needs only 1 saved transaction to establish the position. Later buys add lots to the same asset record, whereas a sell reduces the tracked quantity and a transfer describes movement in or out.

Bitcoin's protocol defines 1 BTC as 100,000,000 satoshis, allowing a portfolio entry to represent quantities down to 0.00000001 BTC. Ethereum instead uses 18 decimal places for its native unit, while the ERC-20 standard exposes a token's decimal setting rather than imposing one universal display precision. CoinMarketCap's form may round what it shows, so the saved quantity should be checked against the transaction detail rather than inferred from a shortened portfolio card.

How should the first result be checked?

The first result is confirmed by matching the asset name, quantity, transaction type, date, and entered price against the source record. Portfolio value alone is insufficient because it moves with the asset's market price after the entry is saved.

Open the position and inspect the underlying transaction. The quantity should equal the purchased amount, and Buy should appear as the mode. Check that the price is a per-unit figure rather than the total amount paid. Confirm the display currency as well: entering a euro-denominated purchase as though it were denominated in U.S. dollars produces a coherent-looking but incorrect ledger.

Exactly 2 monetary components belong in a basic acquisition record: the asset cost and the transaction fee. Network fees use chain-native units - for example, Ethereum gas is paid in ETH - while exchange trading fees follow the venue's own record. Enter the fee once. Folding it into the unit price and also filling the fee field counts the same cost twice.

Worked example: one hypothetical ETH purchase

A hypothetical CoinMarketCap entry shows how quantity, unit price, and fee form the first position. Every changing input below is illustrative rather than a live ETH price, exchange quote, or current network charge.

Assume a hypothetical Buy entry contains 0.40 ETH, a hypothetical unit price of $2,000, and a hypothetical fee of $8. The asset cost is 0.40 × $2,000 = $800. Adding the $8 fee gives a total recorded cost of $808, while the resulting tracked quantity remains 0.40 ETH.

The effective cost per ETH in this hypothetical record is $808 ÷ 0.40 = $2,020. If a hypothetical later reference price were $2,100, the displayed position value would be 0.40 × $2,100 = $840. Against the $808 recorded cost, the hypothetical difference would be $32. These calculations describe the portfolio ledger only; no ETH changes addresses and no Ethereum transaction receives a block confirmation.

Who benefits from a manual first-position workflow?

A manual first-position workflow suits someone who wants a compact ledger without connecting an exchange account or blockchain address. It also fits a test portfolio, a small number of holdings, or an acquisition whose original record is already available.

The method becomes less convenient as transaction volume rises because every buy, sell, transfer, and fee needs consistent treatment. Bitcoin, Ethereum, Solana, and assets traded through Coinbase, Kraken, or Uniswap can all produce records with different units and cost components. Manual entry remains reliable when each portfolio event is copied from its source rather than reconstructed from memory, as described in Coinmarketcap watchlist.

A clean exit from the tracker has 2 meanings. Recording a Sell reduces the tracked holding while preserving the event history; deleting the original transaction erases that ledger event and recalculates the position as though it had never been entered. Use Sell when representing an actual disposal. Use Delete only to remove a duplicate, a test record, or an entry placed in the wrong portfolio. The follow-on topic is treated in Coinmarketcap alerts.