Crypto basics, answered.

Proof of work has miners compete to solve a computational puzzle, spending electricity for the right to add the next block. Proof of stake replaces that competition with validators who lock up collateral, 32 ETH on Ethereum, to propose and confirm blocks instead. Ethereum switched to it in the Merge, completed September 2022. Under proof of work, the miner who solves the puzzle first earns the right to add the block and collect the reward. Security comes from the sheer computing power, called hash rate, competing to find that solution. The system is expensive to attack because an attacker would need to out-compute the entire honest network at once. Under proof of stake, a validator's stake acts as collateral that can be destroyed if they act dishonestly, a penalty called slashing. Security comes from validators having real money at risk rather than from burning electricity. The Ethereum Merge in September 2022 moved the network from proof of work to proof of stake without changing its transaction history. Energy use fell by more than 99 percent according to the Ethereum Foundation's own figures. Consider an investor holding 5 lakh rupees split between Bitcoin, a proof-of-work network, and Ethereum, a proof-of-stake network since 2022. During periods of heavy network congestion, a 25,000 rupee Bitcoin transfer can carry a noticeably higher miner fee than an equivalent Ethereum transfer. Proof of work ties transaction priority to competitive fee bidding among miners in a way proof of stake does not. The edge case is assuming proof of stake is less secure simply because it does not burn electricity. Both systems make an attack expensive, one in computing hardware and power, the other in capital that gets slashed for misbehaviour. Each carries its own centralisation risk depending on how mining or staking power concentrates over time.

A layer 1 blockchain runs its own consensus mechanism and validator set from the ground up, the way Bitcoin, Ethereum and Solana each do. A layer 2, like Arbitrum or Optimism, executes transactions off-chain. It periodically posts a summary of that activity, or a proof of its correctness, back to its underlying layer 1. Running consensus independently is expensive. Every layer 1 validator has to process and verify every transaction. This limits how many transactions the network can handle per second and keeps fees higher during busy periods. A layer 2 avoids this by doing the heavy computation elsewhere and only committing a compact record back to the base chain. A layer 2 posts its data or proofs back to layer 1. It inherits the base chain's security guarantees rather than building its own from scratch. This is what separates a real layer 2 from an entirely separate blockchain. A layer 2's transactions are ultimately anchored to and defensible against the same validator set securing the layer 1 itself. Take an investor moving 25,000 rupees worth of ETH through Arbitrum instead of directly on Ethereum's layer 1. The layer 2 transaction typically settles for a small fraction of the gas fee a comparable layer 1 transfer would cost during a busy period. Arbitrum batches many users' transactions together before posting one combined record to Ethereum. The edge case is withdrawing funds back from a layer 2 to layer 1. Many layer 2 designs use a challenge period, sometimes around a week. Anyone can dispute the withdrawal during that window before it finalises on the base chain. This delay is a deliberate security feature, and it means moving funds off a layer 2 is slower than moving them onto one.

A custodial wallet has an exchange or platform hold the private key on the user's behalf. The user logs in rather than managing keys directly. A non-custodial wallet gives the user sole control of the seed phrase and private key. No third party can move funds without the user's own signature. The private key is what actually authorises moving crypto. Whoever holds it controls the funds, regardless of whose name is on the account. A custodial setup trades direct key control for convenience: password resets, customer support and no seed phrase to lose. The cost is trusting the platform to manage that key safely. A non-custodial wallet removes the intermediary entirely. The user alone generates and stores the seed phrase, usually 12 or 24 words. That phrase is the only way to recover funds if the device is lost. There is no support line to call if the seed phrase itself is lost. Consider an investor with 5 lakh rupees split between a custodial exchange account and a non-custodial hardware wallet. If the exchange suffers an operational failure, the custodial half carries counterparty risk. The non-custodial half is unaffected by anything happening at the exchange, but recovering it depends entirely on the investor's own backup of the seed phrase. The edge case is losing the seed phrase itself. A non-custodial wallet has no recovery mechanism beyond that phrase, so losing it means losing the funds permanently, with no customer support able to help. A custodial platform can usually restore account access through identity verification, the trade-off for having handed key control to someone else in the first place. Qatobit holds assets in institutional custody on behalf of investors, which functions as a custodial model. Live Proof of Reserves is published and available at any time. Investors can verify the underlying holdings without having to manage a private key themselves.

Impermanent loss is the gap between what a liquidity pool position is worth and what simply holding the same two tokens would have been worth. It happens when the pooled tokens' prices diverge after deposit. The pool automatically sells the rising asset and buys the falling one to stay balanced. A liquidity pool holds two tokens in a ratio that automated trading keeps balanced as their relative prices move. When one token rises in price against the other, traders buy the cheaper one from the pool and sell the pricier one into it. This continues until the pool's ratio reflects the new price. This rebalancing is what generates the loss relative to simply holding both tokens outside the pool. The loss is called impermanent because it exists only on paper while the position stays in the pool. If prices later converge back to where they started, the loss shrinks or disappears entirely. It becomes permanent, a locked-in loss, only at the moment the liquidity provider actually withdraws while the prices remain diverged from the deposit point. Consider a liquidity provider depositing 25,000 rupees split evenly between two tokens. If one token doubles in price relative to the other before withdrawal, the pool's rebalancing leaves the provider with less total value than simply holding. Holding the original 25,000 rupees split across both tokens outside the pool would have been worth more. The larger the price divergence, the larger this gap grows. The edge case is trading fees earned for providing liquidity, which can offset some or all of the impermanent loss. A pool with high trading volume can generate enough fee income to leave the liquidity provider ahead, even after accounting for the loss. A low-volume pool with the same price divergence leaves the provider worse off, with little fee income to compensate.

P2P crypto trading itself is not banned in India. The facilitating platform is expected to register with the Financial Intelligence Unit, FIU-IND, under the Prevention of Money Laundering Act. Gains from a P2P trade are taxed like any other virtual digital asset sale, at the flat 30 percent under Section 115BBH. FIU-IND registration exists to bring platforms handling crypto transactions under anti-money-laundering reporting obligations, the same category of oversight applied to other reporting entities under PMLA. A platform that has completed this registration is expected to run identity verification and transaction monitoring on the trades passing through it. This is what distinguishes a compliant P2P platform from an informal one. Using a platform that has not completed FIU-IND registration does not make an individual trade illegal by itself. It removes the compliance layer that identity verification and monitoring would otherwise provide. That gap shows up as counterparty risk. There is less recourse if the other party in a P2P trade fails to deliver. There is also less protection if the platform itself turns out to be fraudulent. Consider an investor who sells 5 lakh rupees of a coin through a P2P platform. The 1 percent TDS under Section 194S still applies to that transfer above the applicable threshold, exactly as it would on a regular exchange trade. The resulting gain is taxed at 30 percent under Section 115BBH when the return is filed. The edge case is assuming an unregistered platform means better privacy or fewer obligations. The tax treatment under Section 115BBH and the TDS obligation under Section 194S apply to the underlying transfer regardless of which platform facilitated it. What changes with an unregistered platform is the counterparty and compliance risk sitting underneath the trade. The tax outcome stays the same.

A seed phrase is the standard BIP-39 mnemonic of 12 or 24 words. A wallet uses it to back up every private key it holds. A passphrase is an optional extra word, sometimes called the 25th word. Adding one on top of the seed creates a separate hidden wallet. The seed phrase encodes the entropy behind every key the wallet generates. Most wallets follow the same BIP-39 standard. Writing the phrase down and storing it offline is the entire backup for that wallet. Nothing else protects the funds inside it. A stolen seed phrase alone hands over full control of the standard wallet. A passphrase changes how the wallet derives its addresses. There is no fixed list of valid passphrases; any word or phrase works. The same seed words plus a different passphrase produce a completely different set of balances. This creates a second wallet hidden behind the visible one. Someone who finds only the seed phrase sees just the standard wallet. The hidden funds stay invisible without the exact passphrase. Consider an investor who moves 5 lakh rupees of Bitcoin into a self-custody wallet. They set up a hidden wallet behind a passphrase, holding half that amount there. The other 2.5 lakh rupees stays visible on the standard wallet. If the visible wallet is ever compromised, the passphrase-protected portion stays untouched. It comes from an entirely different derivation. Nothing about a normal transaction reveals that a hidden wallet exists at all. The wallet software never stores the passphrase anywhere. Writing down the seed phrase without noting the passphrase separately is a common mistake. A user who forgets the exact passphrase, including its capitalization and spacing, loses that hidden wallet for good. This happens even with the original seed phrase fully intact.

Spot trading buys the actual cryptocurrency at today's price. The buyer owns it immediately. Futures trading is a contract to buy or sell that asset at a fixed price on a set future date. Most futures positions never touch the underlying coin at all. A spot purchase settles at once. The buyer pays the current market price. The coin moves straight to their wallet or exchange balance. The position exists until they choose to sell it. There is no expiry date. There is no separate margin requirement to open it. A futures contract works differently. The trader posts margin instead of the full value of the position. That margin lets them use leverage to control a larger position than their capital alone would allow. The contract carries a funding rate paid between long and short holders. Some contracts instead carry an expiry date, when the position settles. Neither applies to a spot holding. An investor who puts 5 lakh rupees into Bitcoin on the spot market owns exactly 5 lakh rupees of Bitcoin. That value moves one for one with the price. The same 5 lakh rupees used as margin on a futures position with five times leverage controls 25 lakh rupees of exposure. A five percent move against that position wipes out the entire margin. Leverage cuts both ways just as fast on the way down as on the way up. A futures loss can exceed the amount originally put in during an extreme move. A spot holding cannot lose more than what was paid for the coin. That ceiling is the main structural difference between the two. Qatobit's Quick Buy/Sell and its Crypto Indices are both spot products. An investor buys the underlying asset directly and holds it as an actual position. Qatobit does not offer leveraged futures contracts on the platform.

Ethereum is the blockchain network and protocol. ETH is the native token that runs on it. Every transaction and smart contract call pays a fee in ETH, called gas. Since the 2022 Merge, ETH is also the asset validators stake to secure the network. The distinction is between the system and the asset. Ethereum is the decentralized computer. It is the set of rules and the network of nodes that run it. ETH is simply the unit of value that moves through that system. It pays for the computation the network performs. Tokens built on top of Ethereum are separate assets from ETH itself. USDC and most decentralized application tokens work this way. They follow a shared technical standard. Holding one of them is not the same as holding ETH. None of them pay Ethereum's gas fees on their own. A wallet still needs ETH to move them. This mix-up confuses many people new to Ethereum. An investor holding 5 lakh rupees in ETH owns a claim on Ethereum's native asset. That is the same asset used to pay for every transaction on the chain. If that investor instead holds 5 lakh rupees in a token built on Ethereum, they still need separate ETH in the wallet. Without it, they cannot send or trade that token. The naming confusion runs both ways. People say they hold Ethereum when they mean ETH. The two get used as if they were the same word. Only ETH, the token that runs on Ethereum, actually trades on an exchange. Qatobit's QSI Core and QSI Growth indices both hold ETH as part of their basket, alongside Bitcoin and the index's other assets. This gives an investor exposure to the token without managing a wallet or paying gas directly.

Yes. An airdropped token is taxed as income at its fair market value on the day it is received. That same token is taxed again at the flat 30 percent VDA rate under Section 115BBH when it is later sold. 1 percent TDS under Section 194S is deducted on that sale. The first tax event happens the moment the tokens land in the wallet. The Income Tax Department treats an airdrop as income from other sources. It is valued at whatever the token is worth in rupees that day. That value is added to the recipient's taxable income for the year. This applies regardless of whether the token is ever sold. The second tax event happens on sale. The tokens were received free, so there is no purchase cost to subtract. The entire sale value is taxed again at 30 percent under the VDA regime. 1 percent TDS is withheld at the time of the transfer. No deduction is allowed for any cost, since none was paid. Every airdrop needs its own record of the receipt date and value. An investor receives an airdrop worth 25,000 rupees on the day it lands. They owe income tax on that amount at their regular slab rate. Say the token's value grows to 40,000 rupees by the time they sell it. The entire 40,000 rupees is taxed again at 30 percent on sale. 400 rupees is withheld upfront as TDS. The two tax events use different values and different rates. This surprises most recipients. A token later sold for less than its value on the day it was received still generates full income tax on that original higher value. The loss on the second leg cannot be set off against any other gain. This asymmetry is the part people miss most often.

A node stores and relays the full blockchain ledger. A miner competes to solve proof of work puzzles to earn the next block's reward. A validator stakes collateral under proof of stake to propose or approve blocks instead. Running a node by itself needs neither mining nor staking. Every full node downloads and verifies every block against the network's consensus rules. It keeps its own independent copy of the ledger. Running one earns no reward. It exists purely to check that the chain everyone sees is the correct one. Thousands of nodes run this check in parallel. This redundancy is what makes the ledger trustworthy without a central authority. Mining and staking are the two ways a network decides who adds the next block. A miner spends real electricity and hardware racing to solve a computational puzzle first. A validator instead locks up a set amount of the network's own token as collateral. The protocol selects among validators to propose blocks. Bad behaviour is punished by seizing part of that stake. An investor holding 5 lakh rupees in ETH could use part of that holding to become a validator, once they reach the network's staking minimum. They would earn a modest yield for helping secure the chain. The same investor cannot mine Ethereum at all. Ethereum moved to proof of stake, and mining no longer exists on that network. Running a node and running a validator get confused often. Every validator must also run a node, but the reverse is not true. Running a node needs no stake and pays no reward. Any participant can operate one purely to verify the chain independently. Most nodes on any major network belong to people doing exactly that.

Blockchain interoperability lets assets or data move between otherwise incompatible blockchains. It happens through a bridge, an atomic swap, or a shared communication protocol. IBC, used across the Cosmos ecosystem, is one such protocol. Each method trades off speed, trust and security differently. A bridge locks an asset on one chain and mints a matching representation on another. A custodian or a set of validators vouches that the locked asset is really there. An atomic swap instead trades two assets on two different chains directly between two parties. Neither side can walk away once the other has committed. A shared protocol like IBC takes a different route. It lets independent chains built on the same framework pass verified messages to each other. No separate bridge contract sits in the middle. Each approach shifts the trust somewhere. It might go to a bridge operator, to the two counterparties, or to the shared protocol's own validator set. Choosing a method depends on which chains need to connect and how much trust is acceptable. An investor moving 5 lakh rupees of a token through a bridge is trusting that bridge's contract and its operators with the entire amount. This trust lasts for as long as the funds sit locked on the origin side. The same 5 lakh rupees moved through an atomic swap never sits in a third party's custody at any point. Bridges are also the most attacked part of the entire interoperability stack. Most cross-chain hacks to date have targeted the bridge contract itself, not either blockchain it connects. A bridge concentrates a large pool of locked value behind a single piece of code. That is why audits on bridge contracts matter more than audits on the base chains themselves.

A 12-word BIP-39 seed phrase encodes 128 bits of entropy. A 24-word phrase encodes 256 bits. Both are practically unbreakable by brute force with any computing power that exists today. The wallet software chooses the length; the user does not pick it by hand. Entropy measures how many possible combinations a seed phrase could take. Every extra word multiplies that search space many times over. 128 bits already puts the number of possible 12-word phrases far beyond what any realistic computing effort could exhaust. 256 bits pushes that number far higher still. The extra length of 24 words matters most for very large holdings and institutional wallets. Providers often default to the longer phrase as standard practice there. A personal wallet holding a modest amount often ships with 12 words by default instead. The practical difference in brute-force resistance rarely changes the real risk to that wallet. Most personal wallets never need the extra length at all. An investor safeguarding 5 lakh rupees in a hardware wallet does not choose between 12 and 24 words directly. The device generates the phrase during setup. The investor simply writes down however many words it produces. Both lengths protect that 5 lakh rupees equally well against a brute-force guessing attack. The real risk to that amount comes from how the phrase is stored, not its length. Neither option requires the investor to remember a longer list by hand. The real risk to either length has nothing to do with brute force. It comes from losing the paper it is written on or storing it in a photo on a phone. Typing it into a fake wallet app carries the same risk. A 24-word phrase is no safer than a 12-word one against any of those.

A 51 percent attack happens when a single miner or staking group controls more than half a network's hashpower or staked value. This lets them rewrite recent blocks and double-spend coins. Bitcoin's own hashrate makes the attack cost billions of rupees in hardware and power. Smaller networks have suffered real ones. The attack works by building an alternative version of the blockchain in secret. Majority control lets that secret chain grow faster than the public one. Once the attacker releases this longer chain, the network switches everyone over to it. This follows the rule that the longest valid chain wins. Blocks the rest of the network had already accepted get discarded. What the attacker can do is limited. They can reverse their own recent transactions and spend the same coins twice. They cannot create new coins out of nothing. They cannot change the total supply. They cannot take funds from a wallet they do not control. The damage stays confined to transactions the attacker was already part of. Ethereum Classic suffered real 51 percent attacks in 2019 and 2020. Exchanges lost money each time on deposits that were later reversed. An investor could have just deposited 5 lakh rupees worth of the affected coin onto an exchange during one of those windows. They could have seen that deposit reversed. The exchange absorbed the loss, not the investor directly. Network size is itself a security feature for this reason. Bitcoin's total hashrate is now so large that acquiring 51 percent of it would cost more than any plausible gain from the attack. That cost includes both the hardware and the electricity needed. This is why the largest networks have never suffered a successful one.

Bitcoin's block reward halves every 210,000 blocks, roughly every four years. This cuts the new bitcoin miners earn per block. The 2024 halving dropped the reward from 6.25 BTC to 3.125 BTC. The next halving is expected around 2028. Total supply stays capped at 21 million coins regardless of when halvings land. The halving is written directly into Bitcoin's code. No person or company decides when it happens. Every 210,000 blocks, the software automatically cuts the mining reward in half. This happens on schedule regardless of the coin's price or how many miners are active. The effect is a shrinking rate of new supply entering circulation. Early miners earned 50 BTC per block. That fell in stages to 25, then 12.5, then 6.25, and now 3.125 after the 2024 halving. The schedule continues until roughly the year 2140. That is when the 21 million supply cap is fully reached. A miner producing roughly 5 lakh rupees worth of new bitcoin a month before the 2024 halving saw that revenue cut in half overnight. This happened even though the number of blocks they successfully mined stayed the same. Existing holders of bitcoin were not affected directly. Only the rate of new coins entering the market changed. A halving changes the pace of new bitcoin entering circulation. Existing coins already in the market carry no direct repricing from the event. Any price effect works indirectly, through how the market responds to that slower issuance over time. Qatobit's QSI indices that hold Bitcoin rebalance on a fixed monthly schedule set by the index methodology. They do not rebalance around anticipated events like a halving. An investor's allocation does not shift because of the event itself.

Bitcoin recalculates its mining difficulty every 2016 blocks, roughly every two weeks. The target is a fixed ten-minute average block time, regardless of how much hash power joins or leaves the network. A sharp drop in miners, such as after a regional mining ban, triggers a difficulty decrease so blocks keep arriving on schedule. The adjustment compares how long the last 2016 blocks actually took against the ten-minute target. It then scales the difficulty up or down by the difference. Blocks arriving faster than ten minutes on average mean more hash power joined the network, so difficulty rises to slow production back down. Blocks arriving slower mean difficulty falls instead. This keeps Bitcoin's issuance predictable regardless of who is mining or how much equipment they run. The mechanism has no human decision point. It is arithmetic applied automatically every 2016 blocks. That is one reason the block time has stayed close to ten minutes across more than a decade of huge swings in network hash power. Miners cannot vote or lobby to change this schedule. China's 2021 mining ban pushed a large share of Bitcoin's hash power offline within weeks. Block times slowed noticeably until the next adjustment. An investor watching a transaction worth 5 lakh rupees waited longer than usual for confirmations during that window. Fewer miners were competing to add the next block, and difficulty had not yet caught up. The adjustment only happens once every 2016 blocks. A sudden change in hash power causes real, if temporary, slowdown or speedup before the network corrects itself. Between adjustments, block times can drift well away from ten minutes. This drift is temporary and always self-corrects at the next recalculation.

Self-custody means the holder controls the private key directly in their own wallet. No third party can freeze or move the funds. Exchange custody means the platform holds the key and owes the holder a balance instead. The 2022 FTX collapse showed what happens when that balance cannot be honoured. In self-custody, the private key is the only proof of ownership. Whoever holds it controls the coins completely. No company or support desk can reverse a transaction or freeze the wallet. Nobody can recover access if the key is lost, because no central party sits in the loop. In exchange custody, the investor's balance is an entry in the exchange's own database. It is backed by coins the exchange holds on its own infrastructure. This is more convenient day to day, since there is no key to manage. It also makes the exchange's solvency and honesty part of the investor's risk, alongside the coin's own price risk. An investor holding 5 lakh rupees on an exchange during a collapse like FTX's in 2022 found that balance frozen along with everyone else's. Withdrawals halted while the exchange's own finances were sorted out in bankruptcy proceedings. The same 5 lakh rupees held in a self-custody wallet at that moment would have been entirely unaffected. Self-custody removes the platform solvency risk but shifts recovery entirely onto the user. A lost or stolen private key has no support line to call and no password reset. The funds are gone the moment the key is. Qatobit holds investor funds under institutional custody. It publishes live Proof of Reserves so the holding can be checked at any time. This spares the investor from having to manage a private key themselves.

Blockchain scalability refers to a chain's transaction throughput, measured in transactions per second. Bitcoin processes roughly 7 TPS. Ethereum's base layer processes roughly 15 TPS. Layer 2 rollups and sharding raise that throughput without changing the base layer's own consensus rules, usually at the cost of some decentralization. Throughput is limited by how much data every node must process and store to stay in sync. A higher TPS number generally means larger blocks, faster block times, or fewer nodes doing the verification. Each of those choices trades against how easy it stays for an ordinary computer to run a full node. This is why raw TPS numbers alone rarely tell the full story. Layer 2 solutions handle most transactions off the base chain. They settle only a summary back onto it. This multiplies effective throughput without forcing every node to process every transaction directly. Sharding instead splits the network itself into parallel segments. Each segment processes a portion of the total transaction load. This is why many newer networks lead with a layer 2 design from the start. A payment network processing 7 transactions per second can confirm roughly 25,000 transactions in an hour at full capacity. That becomes a real constraint when an investor moving 5 lakh rupees needs a transaction confirmed during network congestion. Every other pending transaction is competing for the same limited block space. Fees on the network typically rise during exactly this kind of congestion. Higher TPS numbers often understate a real trade-off. A chain that raises throughput by shrinking the number of nodes that can realistically participate becomes easier to control by whoever runs those remaining nodes. A scalability number alone does not tell the whole story of a network's security.

Blockchain links data into cryptographically chained blocks in strict sequence. Distributed ledger technology is the broader category. It covers any shared, synchronized ledger across multiple nodes. Every blockchain is a form of DLT, but not every DLT is a blockchain. IOTA, for instance, uses a non-chained directed acyclic graph instead. A blockchain's defining feature is the chain itself. Each block contains a cryptographic reference to the block before it. Altering any past block would break every block that follows. That tampering would be exposed immediately. This design is what earns the word chain in blockchain. DLT covers any system where multiple independent nodes hold and agree on the same ledger without a central authority. Some DLTs organize data as a chain of blocks, which makes them blockchains specifically. Others, like a directed acyclic graph, let transactions reference several prior transactions directly. They are not bundled into sequential blocks at all. Neither approach is inherently more secure than the other. An investor might hold 5 lakh rupees of a blockchain-based asset and compare it to the same amount in a DAG-based DLT asset. Either way, they rely on the same basic guarantee: multiple independent parties agree on the same transaction history. The underlying data structure recording that history is simply built differently. The terms get used loosely in everyday conversation. People say blockchain when they mean any shared ledger at all. The distinction matters mainly when comparing two specific networks' actual security models. A chain-based structure and a graph-based structure fail differently under attack. Knowing which structure a network uses helps explain how it actually gets attacked. Neither label alone tells an investor how the network handles a dispute over its history.

Liquidation is a forced close of a leveraged position. It happens when losses erode the trader's margin below the exchange's maintenance threshold. The exchange calculates a specific liquidation price from the leverage and position size used. Liquidation usually carries an extra fee on top of the margin already lost. This is a mechanism unique to leveraged positions, not to spot holdings. Every leveraged position has a maintenance margin requirement. This is the minimum collateral the exchange needs to keep backing the position safely. As the price moves against the trade, the position's remaining margin shrinks. Once it falls below that maintenance level, the exchange closes the position automatically. It does not wait for the trader to act. The liquidation price is fixed the moment the position opens. It is calculated directly from the leverage used and the size of the position. Higher leverage sets that liquidation price much closer to the entry price. A smaller adverse move is then enough to trigger it. Lower leverage leaves far more room before the same thing happens. A trader who opens a position worth 5 lakh rupees using ten times leverage is exposed with only 50,000 rupees of actual margin behind it. A price move of roughly ten percent against the position wipes out that margin entirely. This triggers liquidation, closing the position. It often charges a further fee on top. Liquidations rarely happen in isolation during a sharp move. As one trader's position gets liquidated, the forced sale itself can push the price further in the same direction. This can trigger the next trader's liquidation in turn. The resulting cascade can accelerate a price move well beyond what the initial news justified.

Section 194S requires 1 percent TDS on the transfer of a Virtual Digital Asset once the transaction crosses a threshold. That threshold is 50,000 rupees a year for specified persons and 10,000 rupees a year for others. The exchange or buyer deducts and deposits this TDS. It is credited against the seller's final tax bill. The deduction happens at the point of transfer, before the seller receives full sale proceeds. Whoever is responsible for deducting it withholds 1 percent of the transaction value. That is typically the exchange facilitating the trade, or the buyer directly in a peer-to-peer transfer. They deposit it with the tax department on the seller's behalf. This is separate from the 30 percent tax on any gain under Section 115BBH. The TDS is a rupee amount collected upfront. It is credited against whatever total tax the seller owes when they file their return. This works similarly to how TDS applies on salary or bank interest. An investor sells 5 lakh rupees worth of a Virtual Digital Asset in a single transaction. 5,000 rupees is withheld as TDS at the time of transfer. That amount is deposited with the tax department immediately. It is credited against the investor's total tax bill for the year when they file their return. Every transfer above the threshold gets the deduction, whether the trade produces a gain or a loss. An investor who sells at a loss still has 1 percent withheld at the point of transfer. Recovering that amount happens only through the annual return, not at the time of the trade itself. On Qatobit, a monthly rebalance inside a Crypto Index is not the investor's own taxable transfer. The taxable event happens when the investor sells the basket itself. That is when this kind of withholding treatment becomes relevant to their holding.

DeFi covers lending, swapping and derivatives run entirely by smart contracts. No company holds custody of user funds in a DeFi protocol. A crypto exchange, centralized or otherwise, matches orders and typically holds the asset itself. Major DeFi categories include lending through Aave, swaps through Uniswap and derivatives through dYdX. Access to a DeFi protocol requires only a non-custodial wallet connected directly to the smart contract. There is no account to open and no identity check to pass. The code itself enforces the rules of the trade, the loan, or the swap. It executes exactly as written every time. No support desk can override it. A centralized exchange works closer to a bank. It holds custody of whatever an investor deposits. It matches buy and sell orders on its own internal order book. It requires know-your-customer verification before an account can trade. The convenience of a support team and a familiar login comes with the exchange holding the asset on the investor's behalf. That trust in a company is exactly what DeFi is built to remove. An investor lending 5 lakh rupees on a DeFi protocol like Aave earns interest paid directly by the smart contract's own logic. The funds never leave the investor's own wallet control beyond the contract's code. The same 5 lakh rupees deposited on a centralized exchange sits in the exchange's own custody until the investor withdraws it back out. DeFi removes the custody risk of an exchange holding the asset. It introduces a different risk instead: the smart contract's own code. A bug or exploit in the contract itself is the main way DeFi funds have been lost historically, more often than any company's insolvency.

A decentralized exchange like Uniswap executes trades through a smart contract or liquidity pool. No custody is held by the exchange itself. A centralized exchange like Binance or CoinDCX matches orders internally and holds custody of whatever is deposited. A DEX needs only a self-custody wallet; a CEX requires KYC sign-up first. On a DEX, a trader connects a personal wallet directly to the protocol. They swap against a liquidity pool funded by other users. They pay the underlying blockchain's network gas fee for the transaction itself. No account exists on the DEX side. The wallet address is the only identity the protocol ever sees. On a CEX, the trader deposits funds into an account the exchange controls. Every trade after that is an internal ledger update, not an on-chain transaction. This is why CEX trades settle faster. They pay a trading fee to the exchange rather than a gas fee to the network. An investor swapping 5 lakh rupees of one token for another on a DEX pays the network's gas fee directly. They receive the new token straight into their own wallet. No exchange ever holds the funds. The same swap on a CEX means depositing the 5 lakh rupees into the exchange's custody first. The trade executes against its internal order book. The investor withdraws the result back out afterward. A DEX's liquidity pool can move price against a large trade in a way an order book does not. This effect is called slippage. A 5 lakh rupee swap on a thin pool can execute at a noticeably worse price than the quote shown before confirming. Qatobit's Quick Buy/Sell works closer to a CEX transaction. The platform executes the order and holds custody of the funds until the investor withdraws. This happens without requiring a personal wallet connection.

A crypto SIP invests a fixed amount at a set interval, weekly, biweekly or monthly. This happens regardless of the asset's price that day. It averages the purchase cost across the asset's volatility cycle. This removes the need to time a single lump-sum entry. The term SIP is borrowed directly from Indian mutual fund investing. Each scheduled purchase buys more of the asset when the price is low and less when the price is high. The investor does not make that decision consciously; the schedule makes it for them. Over many cycles, the average price paid smooths toward the middle of the range the asset actually traded in. It does not depend on whichever single day the investor happened to buy. The mechanism only works because the amount invested each time stays fixed in rupees, not in the asset's quantity. A fixed rupee amount buys a varying quantity of the asset depending on that day's price. More units get bought when the price is low. Fewer units get bought when the price is high. This varying quantity is what produces the averaging effect over time. An investor puts 25,000 rupees a month into a crypto SIP across a year that includes both a sharp drop and a recovery. They end up with an average cost per unit somewhere between the cycle's low and its high. This differs from the cost of whatever the price happened to be on the one day they might have chosen for a lump sum. Dollar cost averaging does not guarantee a better outcome than a single lump-sum investment. In a market that rises steadily without a real dip, an earlier lump sum would have outperformed the same amount spread across a SIP. The averaging effect helps most in a volatile, choppy market. It helps far less in a consistently rising one. Qatobit's Crypto SIP lets an investor set an amount and a cadence into either an individual crypto asset or a QSI Crypto Index. Cadence options are weekly, biweekly or monthly. The platform invests automatically from the linked bank balance on schedule.

The Merge, completed in September 2022, replaced Ethereum's proof of work mining with proof of stake validation. Validators now stake 32 ETH to run a full validator. Network energy use dropped by more than 99 percent after the switch. Block issuance and fee-burning mechanics changed the asset's net supply going forward. Before the Merge, miners competed using computing hardware to solve puzzles and add new blocks. This consumed large amounts of electricity. After the Merge, validators are chosen to propose and confirm blocks based on the ETH they have staked as collateral. There is no computational race and no specialized mining hardware involved at all. The change also altered how new ETH enters and leaves circulation. Validators earn a smaller issuance reward than miners once did. A separate fee-burning mechanism removes a portion of every transaction fee from circulation permanently. ETH's net supply can now shrink during periods of high network activity, rather than only ever growing. An investor holding 5 lakh rupees in ETH before the Merge held an asset secured entirely by mining hardware and electricity costs. The same 5 lakh rupees held after the Merge is secured by validators who staked their own ETH as collateral. The investor's own holding stayed unaffected beyond the network's underlying security model changing. Running a validator directly requires staking 32 ETH, a threshold well beyond most individual holdings. Most ETH holders never interact with validation directly. Every one of their transactions is still confirmed by validators rather than miners. This shift is one of the most closely watched effects of the Merge. Qatobit's Crypto Indices that hold ETH give an investor exposure to the asset without requiring them to run a validator or manage staking themselves.

A testnet like Sepolia issues coins with no market value, claimed free from a faucet and used only to test contracts before they go live. Mainnet is the live production network where every transaction is final, settled using real ETH paid as gas. Ethereum currently runs Sepolia and Holesky as its primary public testnets. A testnet mirrors mainnet's technical rules closely. A smart contract behaves the same way in both environments. This is why developers use it. Nothing on a testnet has any monetary value. A mistake, a bug, or a broken deployment costs nothing beyond the developer's own time. Gas fees on a testnet are also free, paid with the same worthless faucet coins. Mainnet is the network real users and real money actually settle on. A transaction confirmed on mainnet is final. It costs real ETH in gas. It interacts with contracts holding genuine value. This is why a contract is always tested thoroughly on a testnet before it is deployed to mainnet. Deploying straight to mainnet without testing first is one of the most common mistakes a new developer makes. A developer testing a contract meant to eventually hold 5 lakh rupees worth of user deposits runs every scenario on Sepolia first. They use free testnet ETH that carries no value at all. Only afterward do they deploy the same contract to mainnet. A bug there could put that 5 lakh rupees at real risk. Testnet coins are sometimes mistaken for something worth holding, especially when a faucet distributes them freely. They carry no value on any exchange. They cannot be converted into anything real, no matter how large the testnet balance grows. A wallet holding both testnet and mainnet ETH should always double check which network is selected before sending anything.

The Ethereum Virtual Machine is the runtime that executes every smart contract's bytecode identically on every node in the network. Each computational step, called an opcode, consumes a fixed amount of gas. A transaction that runs out of gas mid-execution is reverted entirely, rather than partially applied. Every Ethereum node runs the same EVM. A smart contract produces the exact same result no matter which node executes it. This is what lets the network agree on a single shared state. The EVM reads the contract's compiled bytecode and carries out each instruction one step at a time. It charges gas for every step along the way. This gas charge exists to stop a contract from running forever or consuming unlimited computing resources for free. A user sets a gas limit before sending a transaction. If the contract needs more computation than that limit allows, the entire transaction fails and reverts. The gas already spent up to that point is not refunded. This design protects the whole network from a single runaway contract. A developer deploying a contract meant to move 5 lakh rupees worth of tokens tests exactly how much gas each function costs before launch. An underestimated gas limit on a live transaction fails the entire transfer partway through. The gas already spent gets wasted without moving a single token. Testing on a low-cost testnet first is the standard way to avoid this mistake. EVM-compatible chains such as Polygon and BNB Chain run the same Solidity contracts with only minor changes. They implement a version of the same virtual machine. This compatibility is why a contract written for Ethereum often deploys to several other chains with little rewriting required. This is also why a single exploit pattern can threaten many chains at once.

A governance token grants voting rights on a protocol's proposals through on-chain votes. Voting power is usually proportional to how many tokens are held or staked. A utility token grants access to a specific network function, such as paying gas or a service fee. A single token can carry both roles at once. Holding a governance token lets an investor vote on changes to the protocol itself. Examples include adjusting a fee, approving a treasury spend, or upgrading a smart contract. The vote is recorded on-chain and weighted by however many tokens the voter holds or has staked. Larger holders carry proportionally more influence over the outcome. A utility token grants the right to actually use something, rather than to vote on it. ETH paying for gas on Ethereum is the clearest example. Holding ETH grants no vote over Ethereum's protocol rules, only the ability to pay for computation on the network. Some projects combine both functions into one single token. An investor holding 5 lakh rupees in a governance token can cast a vote on a protocol proposal weighted by that holding's size. They do not need to use the token for anything else to vote. The same 5 lakh rupees held in a pure utility token buys network access or services. It carries no vote over how the underlying protocol is run. The line between the two blurs often enough that a token's actual rights need checking directly. They should never be assumed from its category label alone. A token marketed as governance may carry only advisory voting power. It can have no binding effect on the team's actual decisions. There is no Qatobit token of either kind. Qatobit is a crypto index investing platform. Neither governance rights nor utility access is part of what an investor holds when they invest through the platform.

A hard fork is a protocol change that is not backward compatible. It forces every node to upgrade or get stuck on a separate chain, as happened when Bitcoin Cash split from Bitcoin in August 2017. A soft fork tightens the rules in a way older nodes accept, as with Bitcoin's SegWit activation in 2017. In a hard fork, the new rules allow something the old rules rejected, such as a larger block size. A node still running the old software sees the new blocks as invalid. It simply stops following that chain. Both chains keep running independently from that point. Each has its own coin, its own history, and its own community. In a soft fork, the new rules are stricter than the old ones. They reject some things the old rules used to allow. An unupgraded node still accepts every block the new rules produce, because those blocks also satisfy the older, looser rules. This is why a soft fork does not split the network the way a hard fork does. An investor holds 5 lakh rupees in Bitcoin at the moment of a hard fork like the Bitcoin Cash split. They end up holding 5 lakh rupees of Bitcoin plus an equivalent balance of the new forked coin. The fork copied the entire ledger's history up to the split point. A soft fork like SegWit changed nothing about that same investor's balance at all. A hard fork requires near-universal agreement to avoid a permanent split. When that agreement does not happen, both chains simply continue to exist. They compete for miners, users and the original coin's name and reputation. Bitcoin and Bitcoin Cash have done exactly this since 2017. Neither chain has any special claim on the original name once the split is final.

A crypto airdrop distributes tokens based on a snapshot of eligible wallet addresses at a set block height. Eligibility usually requires prior on-chain activity, such as swaps, bridging or testnet use. Tokens are distributed through a claim contract or a direct transfer. The whole process runs without the recipient doing anything before the snapshot itself. The snapshot happens at a specific block, a fixed point in the chain's history. Only wallets meeting the project's chosen criteria at that exact moment qualify. A wallet that starts meeting the criteria the day after the snapshot gets nothing from that particular airdrop. This holds regardless of how much activity it does afterward. This is why some collectors interact with many new projects speculatively. Once eligibility is decided, the project publishes a claim process. Usually this is a smart contract the wallet interacts with directly to receive the tokens. In some cases it is a direct transfer sent straight to the qualifying address. A claim contract almost always requires the recipient to pay the network's own gas fee. This applies even though the tokens themselves are free. An investor's wallet qualifies for an airdrop worth 25,000 rupees at the snapshot. They still need to pay a small gas fee to actually claim it through the contract. That fee is often a few hundred rupees. If the claimed tokens are later sold, the 25,000 rupees value at receipt becomes taxable income. This is separate from any gain or loss on the eventual sale. Fake claim sites are a common trap around any well-known airdrop. A scam page that looks identical to the real claim contract asks for a wallet signature. That signature drains the wallet instead of delivering tokens. Verifying the claim contract's actual address before signing anything matters more than the airdrop's size.

Wallet-approval phishing works when a fake app or a wallet-connect prompt tricks a user into signing an approve transaction. That signature grants the scam contract an allowance to spend the user's tokens directly. No seed phrase or private key is stolen. The wallet signs the malicious approval itself, and revoking approvals periodically closes the exposure. An approval is a normal, legitimate function built into most token standards. It lets a user grant a smart contract permission to move a specific token on their behalf, up to a set limit. This is how ordinary swaps and lending deposits work. Phishing exploits this same mechanism by disguising a malicious contract as a legitimate one asking for the same kind of permission. Once the victim signs the approval, the scam contract can transfer the approved token out of the wallet at any point afterward. It needs no other signature and no other prompt. The transaction the user signed was a real approval, not a theft of their key. The wallet software shows nothing unusual at the moment it happens. An investor with 5 lakh rupees in a token sitting in a self-custody wallet signs one malicious unlimited approval on a fake site. The entire 5 lakh rupees can be drained in a single transaction days or weeks later. The scammer simply waits and chooses when to use the approval they were granted. Nothing about the wallet's normal activity would have warned them beforehand. Revoking unused token approvals periodically, using a dedicated revocation tool, is the direct defence against this exposure. A wallet can carry dozens of old approvals from legitimate apps used months earlier. Each one left active is a standing permission a scammer could exploit. That risk stays live if that app's own contract is ever compromised.

A crypto bridge moves value between two blockchains by locking the original token in a contract on chain A. It mints a matching wrapped token on chain B. Reversing the trip burns the wrapped token and releases the original. The wrapped token trades and settles like a native asset until it is unwrapped. The lock-and-mint model is the most common design. A user sends the token to a bridge contract on the source chain, and the contract holds it. A matching amount of a wrapped version then appears on the destination chain. That wrapped token is a claim on the locked reserve behind it. Moving back the other way is called burn-and-release. It destroys the wrapped token and unlocks the equivalent amount on the source chain, closing the loop. Because a bridge exists to move value across chains, its contract accumulates a large pool of locked tokens in one place. That concentration makes bridges one of the most attractive targets in crypto. Some of the largest hacks on record targeted a bridge's locked reserve directly, exploiting that concentration. A wrapped token also carries the bridge's own smart contract risk on top of the risk of the underlying asset. Its value depends on the bridge continuing to hold what it claims to hold. Consider moving 25,000 rupees worth of a token from Ethereum to a faster chain with lower fees, to use in an app there. The bridge locks that value on Ethereum and mints 25,000 rupees worth of the wrapped version on the destination chain. The token's price does not change in the move. The position now carries a new dependency: the bridge contract has to stay solvent and unhacked. That dependency did not exist while the tokens sat untouched on Ethereum. The edge case is a bridge that looks decentralized but is not. Several major bridge hacks succeeded because a small multisig controlled the locked reserve, sometimes as few as five or nine keys. Compromising a majority of those keys was enough to drain it. Checking who can move a bridge's reserve matters more than checking which chains it connects.

Under EIP-1559, live since 2021, an Ethereum transaction fee equals the base fee plus a priority tip. That total is multiplied by the gas the transaction actually used. The base fee is set by the network itself and adjusts every block. The tip is the amount a user adds on top to get included faster. Each Ethereum block has a target size. The base fee moves up when the prior block ran fuller than that target, and down when it ran emptier. This makes the base fee a live signal of network demand that moves with every block. The base fee portion of every transaction is burned outright, removed from circulation, and no validator receives it. The priority tip works differently. It goes directly to the validator that includes the transaction in a block. A higher tip generally means faster inclusion when the network is busy. Gas used is the third variable. A simple transfer uses a small fixed amount of gas. A complex smart contract call can use far more. The same base fee and tip can therefore produce very different total costs, depending on what the transaction actually does. A simple ETH transfer worth 25,000 rupees might use 21,000 units of gas. If the base fee is 20 gwei and the tip is 2 gwei, the fee comes to 22 gwei per unit of gas. That works out to roughly 0.00046 ETH total, a small fraction of the 25,000 rupees being moved. The exact rupee cost still depends on ETH's price that day. A complex swap moving the same 25,000 rupees through a decentralized exchange can use ten times the gas. The cost rises proportionately, even though the rupee amount being moved is identical. The edge case is a network congestion spike. During a period of high demand, the base fee can rise several times over within a few blocks as it chases the target size. A transaction with too low a tip can sit unconfirmed until the tip is raised or the network cools down. Wallets that estimate gas without accounting for this spike often quote a fee that is already stale by the time the transaction is sent.

A liquidity pool is a smart contract holding a matched pair of tokens that traders swap against. It replaces the order book used on a traditional exchange. A user can deposit an equal value of both tokens to become a provider. In return, they earn a share of every trade's fee, commonly around 0.3 percent. The mechanism behind the swap is usually a constant-product formula. It keeps the product of the two token quantities in the pool fixed as trades move the balance between them. As a trader buys more of one token, its price inside the pool rises along that curve. That rising price is what protects the pool from being drained in a single trade. It is also what lets a decentralized exchange operate without ever needing a matching buyer and seller at the same moment. A provider's payout is proportional to their share of the pool at the time each fee accrues. Say a pool holds 10 lakh rupees in total. A provider who supplied 5 percent of that earns 5 percent of every fee the pool generates, for as long as their deposit stays in. The tradeoff is impermanent loss. If the two tokens' prices diverge significantly while deposited, a provider can end up with less value than simply holding the two tokens separately. A provider deposits 25,000 rupees worth of two tokens, split evenly, into a pool charging 0.3 percent per swap. They earn a cut of every trade routed through it, proportional to their share of the pool. Over a month of steady trading volume, that fee income might add up to a few hundred rupees. If one of the two tokens moves sharply against the other, though, the impermanent loss on the position can exceed what the fees paid out. The edge case is a low-volume pool with a volatile pair. Fees only accrue when trades happen. A pool nobody trades through pays a provider nothing, while still exposing them to price divergence between the two tokens. Depositors sometimes look only at the advertised fee percentage and skip checking whether the pool actually sees enough volume to earn it.

Not with any quantum computer built so far. The theoretical risk targets ECDSA, the elliptic curve signature scheme securing bitcoin addresses. That key is only exposed once an address has sent a transaction. Breaking it is currently estimated to need millions of stable qubits, far beyond anything that exists today. Bitcoin actually uses two different cryptographic layers, and quantum computing threatens them unevenly. SHA-256, used for mining and for turning a public key into an address, is considered far more resistant to quantum attack than ECDSA is. ECDSA is the layer that signs a transaction, proving the sender controls the funds, and that proof requires revealing the public key on-chain. That distinction matters because a bitcoin address's public key stays hidden behind its hash until the owner sends a transaction from it. Coins sitting in an address that has never sent a transaction expose no public key for an attacker to target. If a quantum computer capable of breaking ECDSA existed, the coins at real risk would be those in addresses that had already sent a transaction. Those addresses' public keys are already visible on the ledger. A holder with 5 lakh rupees of bitcoin sitting in an address that has never sent a transaction has no exposed public key today. None would exist for an attacker to target, even in a future quantum scenario, unless that holder later sends from the same address. Moving the same 5 lakh rupees to a fresh address after each transaction keeps the exposed public key window as short as possible. Some wallets already default to this practice. The edge case is reused addresses. A holder who repeatedly sends and receives from the same bitcoin address keeps its public key permanently visible on-chain. That is the scenario security researchers actually worry about, if quantum computing ever closes the gap. The practical defense available right now is generating a new address for each transaction, instead of waiting for the cryptography itself to change. On Qatobit, the basket sits inside institutional custody. The investor does not hold or manage an on-chain address directly. Questions like address reuse and public key exposure are handled at the custody layer, as part of that arrangement.

No. A BIP-39 seed phrase has no central authority that can regenerate it. A standard 12-word phrase has roughly 2^128 possible combinations, far too many to brute force. If the words are lost with no written backup anywhere, the funds tied to that phrase are permanently inaccessible. A seed phrase is the master key to a self-custody wallet. It is a set of words generated once when the wallet is created, and it can rebuild every private key inside it. Nobody, not the wallet maker and not any exchange, stores a copy of it. The entire point of self-custody is that only the owner holds the key. That design removes a single company as a point of failure, but it also removes any customer support option if the phrase itself disappears. This is why every wallet provider repeats the same instruction at setup. Write the phrase down on paper or metal, and store it somewhere physical. Never rely on a photo, a cloud note, or a password manager connected to the internet. A photo can be lost with the phone, and a cloud note can be breached. A password manager adds a second single point of failure on top of the first. Someone holding 5 lakh rupees of crypto in a self-custody wallet can write the seed phrase on paper. They can store a second copy elsewhere. That gives them two independent backups. If one copy burns or gets thrown out, the other still recovers the full 5 lakh rupees. Skip that second copy, though, and a single house fire or a misplaced notebook can do real damage. It can turn the same 5 lakh rupees into funds nobody can ever touch again. The edge case is a phrase typed into a phone's notes app for convenience, and never moved to paper afterward. It feels backed up because it exists somewhere. A factory reset, a lost phone, or a compromised cloud account can erase or expose it. The result is just as final as never having written it down at all. Qatobit holds investor assets under institutional custody, so there is no personal seed phrase to generate, write down, or lose. That tradeoff moves the recovery risk off the investor's own desk and onto the platform's custody infrastructure.

A rollup executes thousands of transactions off the main Ethereum chain, then bundles them into one batch posted back as compressed data. Ethereum processes that single batch instead of thousands of separate ones. The gas cost splits across every user in the batch, cutting what each person pays. Two rollup designs handle correctness differently. An optimistic rollup assumes every transaction in its batch is valid and posts it directly. It then leaves open a challenge window, typically about a week. Any participant can submit a fraud proof during that window if something in the batch was wrong. A zero-knowledge rollup instead generates a cryptographic proof of correctness for every batch before posting it. Ethereum can then verify the math itself, rather than trusting a challenge period to catch fraud after the fact. Either way, what actually lands on Ethereum mainnet is a compact bundle of compressed data representing the whole batch. Each transaction inside it is not posted in full. That compression is where the savings come from. A user interacting with an app on the rollup pays a fraction of what the same interaction would cost directly on Ethereum. They share the mainnet posting cost with everyone else in the batch. A transfer that would cost 400 rupees in gas directly on Ethereum mainnet might cost 20 rupees on a rollup. That 400 rupees of underlying cost gets split across the hundreds of other transactions bundled into the same batch. Someone moving 25,000 rupees of crypto through a rollup pays a small fee on the transfer itself. On top of that sits a small shared portion of the batch's mainnet posting cost. The edge case is withdrawing back to Ethereum mainnet itself. An optimistic rollup withdrawal has to wait out the full challenge window. That can mean a delay of about a week before funds are usable on mainnet. A user can pay a third party for a faster, discounted exit instead. A zero-knowledge rollup withdrawal settles faster, because its proof is verified immediately rather than waiting for a challenge period to pass.

A wallet address, technically an externally owned account, is controlled by a private key that can sign transactions. A contract address holds deployed code instead and has no private key of its own. Sending funds to a contract not built to receive them can lock those funds permanently. The two address types look identical, a string of characters starting with 0x. Nothing about the format itself tells a sender which kind they are looking at. Block explorers solve this by checking whether code is deployed at that address. They label it a contract when it is, and a plain address when it is not. Checking that label before a transfer is the practical way to tell the two apart. The reason it matters is that a wallet address can always sign a transaction to move whatever arrives in it. Someone always holds the private key behind it. A contract address can only do what its code was written to do with incoming funds. Many contracts were never written to handle a plain, unexpected token transfer at all. When that happens, the tokens sit at the contract address with no function able to retrieve them, effectively gone. Sending 25,000 rupees worth of a token to a contract address built to hold and manage exactly that token works as intended. The contract's code has a function to account for the deposit. Sending the same 25,000 rupees to an unrelated contract, one with no function expecting that token, typically strands it there permanently. No wallet owner and no private key can move it back out. The edge case is a token contract address that looks like a normal address on a block explorer that has not indexed it yet. New or obscure tokens sometimes show no contract label for a period after deployment, so checking the label alone can miss it. Sending a small test amount first, before a large transfer, catches this case.

A smart contract is code deployed to a fixed address on a blockchain that runs automatically whenever a transaction calls one of its functions. No company or intermediary executes it; the network's own consensus process runs the code and enforces the result. Its logic cannot change once deployed, unless it was built to be upgradeable. The address a smart contract lives at is not controlled by anyone's private key, which is what separates it from a normal wallet. Instead, its code defines exactly what happens when someone calls one of its functions. That might mean swapping a token, releasing a payment, or recording a vote. Every node on the network re-runs that same code and checks the same result. The outcome comes from that shared check across every node. That is what executing on its own actually means. There is no customer support desk that overrides a smart contract's outcome, and no manual approval step hiding behind the automation. The code is the final word once a transaction triggers it. If the code was written with a bug or an oversight, the contract still executes exactly as written, bug included. The network enforces the code exactly as deployed. A smart contract can manage a savings pool holding 5 lakh rupees worth of deposits. It releases funds to a withdrawing user only when its function is called and its conditions are satisfied. A minimum lockup period having passed is one example. It doesn't matter whether the developer meant for withdrawals to be possible earlier. Whatever condition the code checks is what governs the 5 lakh rupees. The edge case is an unaudited contract with a coding error. The network has no way to know what a developer meant, only what they actually wrote. A single overlooked line can let funds be withdrawn twice, drained through an unexpected function, or locked forever. No company can step in afterward to reverse it the way a bank could reverse an error. This is why an audit history is one of the first things worth checking before trusting funds to a new contract.

A stablecoin is a token pegged to a reference asset, usually the US dollar at a 1:1 ratio. Its value stays steady where bitcoin or ether does not. A regular cryptocurrency carries no peg and floats purely on supply and demand. How a stablecoin backs that peg determines how reliable it actually is. Backing methods vary widely. A fiat-backed stablecoin like USDC holds actual dollar reserves in a bank account. A crypto-collateralized stablecoin like DAI is backed by other crypto locked in a smart contract, over-collateralized to absorb the underlying asset's own price swings. An algorithmic stablecoin backs its peg with code and market incentives instead of a reserve, adjusting supply to try to hold the price steady. Bitcoin and ether have none of this machinery, because neither was designed to hold a fixed price. Their value moves freely with whatever buyers and sellers agree to pay. That is exactly why they are used for exposure to crypto's growth, while stablecoins sit on the sidelines or move value without it. A poorly collateralized or purely algorithmic stablecoin can still lose its peg under stress. The mechanism holding it steady is only ever as strong as its backing. Converting 25,000 rupees worth of bitcoin into a fiat-backed stablecoin locks in that 25,000 rupees of value in dollar terms, whatever bitcoin's price does afterward. Holding the same 25,000 rupees in bitcoin instead means its rupee value moves with the market every day. The stablecoin trades growth potential for stability; the choice depends on whether the money is meant to sit still or stay exposed. The edge case is an algorithmic stablecoin under a bank run. TerraUSD lost its dollar peg entirely in 2022 when its supporting mechanism could not absorb a wave of redemptions. Its price collapsed within days. A fiat-backed stablecoin with real dollar reserves in a bank still carries counterparty risk of its own. What it does not carry is dependence on a live algorithm continuing to work under pressure. QSI Core and QSI Growth are two of Qatobit's Crypto Indices. Each holds a stable reserve alongside bitcoin, ether and, for Growth, solana. The stable portion is not a separate purchase. It is one line inside a basket that also holds crypto with no peg at all.

Staking rewards come from a blockchain's own protocol, paid in the same token, for helping validate the network. A mutual fund dividend is a distribution the fund's manager declares from the income its underlying holdings generated. Staking also carries slashing and lockup risk on top of ordinary market risk. Staking works by locking tokens to help secure a proof-of-stake blockchain, either by running a validator directly or delegating to one. In return, the protocol issues new tokens or shares transaction fees with participants. That reward rate moves with how many people are staking across the network at any given time. More participation generally spreads the same reward pool thinner, and less participation raises the rate per staker. A mutual fund dividend works differently. The fund's manager collects income, interest, dividends from the companies it holds, or realized gains. It periodically decides how much of that to distribute to unit holders in rupees. The rate is not set by a formula reacting to participation. It depends entirely on what the fund's underlying portfolio earned and what the manager chooses to pay out versus reinvest. Take an investor staking 25,000 rupees worth of a token at a 5 percent annual rate. They earn roughly 1,250 rupees worth of that same token over a year. That figure ignores any price change in the token itself. An investor holding 25,000 rupees in a mutual fund earning a 1.5 percent dividend yield receives roughly 375 rupees in cash. That payout is deposited directly, with no lockup and no token price risk attached to it. The edge case is slashing. If a staked validator misbehaves or goes offline for too long, the protocol can confiscate a portion of the staked tokens as a penalty. A mutual fund has no equivalent: the worst outcome for a unit holder is simply receiving no dividend in a given period. A staker also often cannot withdraw funds instantly. Many networks impose an unbonding period of days to weeks before staked tokens become liquid again.

A Sybil attack is when one person creates many separate wallet addresses to appear as many independent users. They then claim a disproportionate share of a token airdrop meant to be spread across a real user base. Projects detect it by analyzing wallet funding sources, on-chain age, and clusters of near-identical transaction patterns across addresses. The attack works because many airdrops reward every qualifying wallet with the same fixed amount, regardless of how much genuine activity sits behind it. A single person can split activity across fifty separate wallets instead of running it through one. Doing that lets them claim fifty times the airdrop a single honest wallet would receive, simply by appearing as fifty different users. Detection has become its own discipline. Projects look at when each wallet was first funded and by what source. A batch of wallets all funded from the same exchange withdrawal within minutes of each other is a strong signal of one operator behind them. They also look at behavioral clustering: wallets that interact with the exact same contracts in the exact same order and timing. Real independent users rarely do that by coincidence. A project distributing an airdrop worth 5 lakh rupees across a claimed 10,000 wallets intends roughly 50 rupees worth of tokens per wallet. Picture 2,000 of those wallets turning out to be one operator running a Sybil farm. That operator alone claims 1 lakh rupees worth of the pool, a fifth of the total. None of those wallets were ever independent users. The edge case is a legitimate power user mistaken for a Sybil. Someone who genuinely runs several separate wallets, one for trading, one for long-term holding, one for testing new apps, can get flagged and excluded. That can happen even without any intent to farm the airdrop. The detection signals look similar from the outside. Most projects that catch this run an appeals process before finalizing the distribution list.

A token burn permanently destroys tokens by sending them to an address nobody can spend from, reducing the total supply for good. A token unlock releases tokens that were already minted but held back under a vesting schedule, adding them to circulating supply. The two events move supply in opposite directions. A burn is usually a deliberate deflationary move. A project sends a set number of tokens to a burn address with no known private key. Sometimes that is a portion of transaction fees, sometimes a one-time allocation. That makes them provably unspendable forever. The supply that remains is split among fewer tokens. That is the mechanism projects point to when they describe a token as becoming scarcer over time. An unlock follows a pre-set vesting schedule instead, usually written into the project's tokenomics at launch. Team, investor, or ecosystem tokens are typically locked for months or years. They are then released gradually on a fixed calendar, whether or not the market is ready to absorb them. A burn shrinks what exists, while an unlock adds previously promised tokens into what is already trading. A project can run both mechanisms on entirely different schedules at the same time. A project holds 5 lakh rupees worth of tokens in a team allocation that unlocks 10 percent per month. That adds 50,000 rupees worth of new selling pressure to circulating supply each month. That continues for ten months. If that same project simultaneously burns transaction fees worth 20,000 rupees a month, the two effects run in opposite directions on the same token. The net supply change depends on which one is larger in a given period. The edge case is confusing the two events when reading project news. A headline announcing a burn sounds bullish on its own, and a headline announcing an unlock sounds bearish on its own. A project can announce both in the same week without either canceling the other out. Checking the actual size of each event against total circulating supply matters more than reacting to which word appears in the headline.

A token unlock releases previously vested team or investor tokens into circulating supply, on a schedule published in advance. Price impact depends mainly on the unlocked amount as a percentage of circulating supply and daily trading volume. A small unlock relative to volume often passes with little visible effect. Tokenomics documents lay out an unlock calendar at launch. It specifies exactly how many tokens release on which date, for which group: team, investors, or the ecosystem fund. Because the date and size are known in advance, sophisticated traders often price in the expected supply increase before it happens. That is why some tokens drift down in the weeks leading up to a large unlock, rather than dropping sharply on the day itself. What actually determines the price effect is the ratio between the unlock size and two other numbers: total circulating supply and average daily trading volume. An unlock equal to 1 percent of circulating supply rarely moves price much on its own. An unlock equal to 20 percent of circulating supply is a different story, especially on a token with thin daily volume. It can overwhelm existing buy orders and push price down sharply as newly unlocked holders sell. A token trading with 5 lakh rupees a day in volume that unlocks tokens worth 25,000 rupees sees a small fraction of that daily flow. It typically absorbs the unlock without much visible price movement. The same 25,000 rupees unlock hits differently on a thinly traded token with only 50,000 rupees of daily volume. That is a much larger share of what the market can absorb in a day. It is far more likely to move the price down. The edge case is an unlock recipient who holds rather than sells. Some unlocked tokens go to a foundation, an ecosystem fund, or long-term-aligned investors who choose to hold rather than sell on release. In that case, the theoretical supply increase never becomes real sell pressure at all. Checking who receives a specific unlock, not just its size, matters before assuming it will hit the price.

A web3 wallet such as MetaMask signs transactions locally on the user's own device and connects directly to decentralized apps. An exchange wallet is custodial, tied to a KYC account, and cannot interact with those apps on its own. Only a web3 wallet requires the user to manage a seed phrase. The exchange holds the private keys behind an exchange wallet. The user logs in with a username and password, and the exchange executes transactions on their behalf from its own pooled infrastructure. A web3 wallet works the opposite way. The user's device holds the private key directly. Every transaction, every app connection, and every approval needs the user's own signature, with no company standing between the wallet and the blockchain. That structural difference is why a web3 wallet can plug straight into a decentralized app, approving a swap or a stake with one click. An exchange wallet cannot connect to those apps at all; its balance lives inside the exchange's own database, off-chain and outside the user's own name. Getting funds from an exchange wallet into a position usable in a decentralized app always means an on-chain withdrawal first. That moves the tokens from the exchange's custody to an address the user actually controls. Withdrawing 25,000 rupees worth of a token from an exchange wallet to a web3 wallet is an on-chain transaction. It is visible on a block explorer and usually settles within minutes. After that, the seed phrase behind the web3 wallet is the only thing that can move that 25,000 rupees again. Leaving the same 25,000 rupees on the exchange skips that step entirely. It also means the exchange's own security and solvency stand between the user and their funds. The edge case is an exchange freeze or insolvency. An exchange wallet's balance is really just an entry in the exchange's own database. A platform that halts withdrawals or fails outright can leave that balance inaccessible, regardless of what the account page shows. A self-custody web3 wallet does not carry that risk. Qatobit's own account sits closer to the exchange-wallet model. Custody of the underlying assets stays with the platform under institutional custody. An investor does not generate or manage a personal seed phrase to hold a basket or a position.

24-hour trading volume is the total value of an asset traded across tracked exchanges in the past day. It is used alongside market cap to judge how liquid an asset really is. A price move on unusually low volume is easier to reverse or manipulate than the same move on high volume. Volume answers a different question than price does. Price tells you what the last trade happened at. Volume tells you how much conviction, and how much real money, sat behind the trades that got it there. An asset can hold a price level shown on a chart while barely trading. In that case the price is fragile, since it would take very little buying or selling to move it meaningfully. Not all volume is real, which is the part traders learn the hard way. Wash trading is an exchange or a market maker trading with itself to inflate reported activity. It is common on unregulated venues chasing higher rankings on data aggregators, and some estimates put a meaningful share of reported crypto volume as artificial. Comparing volume across a handful of exchanges known for stricter listing standards is one practical way to sanity check a number that looks too good. An asset can show 5 lakh rupees of daily volume across major exchanges but only 25,000 rupees on any single smaller exchange. That gap tells you where the real liquidity actually sits. A large order placed on the smaller exchange alone would move the price far more than the same order spread across the bigger venues. Checking where volume concentrates matters as much as checking the total. The edge case is a token with almost no organic trading that suddenly shows a volume spike. A sudden multiple of the normal daily volume, with no corresponding news or price move to explain it, is a common signal. It usually points to coordinated wash trading meant to attract screeners and new buyers, not genuine new demand.

A full node is software that independently downloads and validates every block against a blockchain's own consensus rules. It does not trust someone else's summary of the chain. It needs no mining hardware and no staked collateral. Running one lets a user verify their own balance directly, without trusting an exchange or a block explorer. Running a full node means checking, block by block, that every rule the network agreed on is actually being followed. That means no coin was created out of nothing, no transaction spent money it did not have, and every block's format is valid. A node that finds a rule violation rejects that block outright, regardless of how much mining or staking power sits behind it. That is what gives the network's rules their actual enforcement. A full node's job is purely to check and store the chain, not to add to it, which is different from mining or staking. Mining and staking compete to add new blocks. Bitcoin has tens of thousands of publicly reachable full nodes running at any given time, each independently arriving at the same view of the ledger. That redundancy is what lets a user trust the chain without trusting any single party running it. Someone holding 5 lakh rupees worth of bitcoin can check their balance through their own full node. They read it directly off a copy of the ledger. Their own machine validated that copy block by block. Checking the same 5 lakh rupees through a block explorer's website instead means trusting that the website's server reported it correctly. That is a small but real difference in what the number is actually resting on. The edge case is a pruned or light node mistaken for a full one. Some wallets advertise as running a node while actually only downloading block headers or trusting a third party for most of the validation work. That does not provide the same independent verification a full node does. Checking whether a node genuinely validates every rule, or only claims to be connected to the network, matters more than the label alone.

A whale wallet holds a quantity of an asset large enough to move its price on its own if it buys or sells at once. Traders track whale activity through public block explorers and on-chain monitoring tools that watch large transfers as they happen. There is no fixed threshold that defines a whale. The size depends on the asset's own liquidity. A wallet holding an amount that would barely register on bitcoin could dominate trading on a much smaller token. What matters is the wallet's size relative to the daily volume the asset actually trades. That ratio determines whether the wallet's next move can push price on its own. Monitoring tools flag a wallet as a likely whale, an exchange, or a smart contract based on patterns in its transaction history. Nobody registers as a whale outright. A wallet can hold a large balance untouched for months, then suddenly send a large amount to a known exchange deposit address. That pattern is the clearest signal traders watch for. That pattern historically precedes selling more often than any other single move. A wallet moving 5 lakh rupees worth of a mid-sized token to an exchange in a single transaction gets tracked live by on-chain monitoring tools. That often triggers alerts across trading communities within minutes. Some traders sell in anticipation before the whale itself has sold anything. The alert reacts purely to the transfer pattern itself. The resulting price move can happen even if the whale was only rebalancing between wallets. The edge case is a whale wallet that turns out to be an exchange's own cold storage. A tracking tool can misread it as an individual holder. Exchanges routinely move very large sums between their own wallets for security reasons. A monitoring tool that has not correctly labeled that address can generate a false alarm. It looks identical to genuine whale activity to anyone watching the feed.

Altcoin season is commonly defined as the period when 75 percent or more of the top 50 altcoins outperform bitcoin over a rolling 90-day window. It is tracked publicly through an altcoin season index scored from 0 to 100. The opposite condition, bitcoin outperforming most altcoins, is called bitcoin dominance. The index that tracks this condenses a simple comparison into one number. For each of the top 50 altcoins, it checks whether that coin beat bitcoin's percentage return over the trailing 90 days. It then reports what share of them did. A reading of 75 or above signals altcoin season by the common definition. A reading near 25 or below signals the opposite, bitcoin dominance, where most altcoins are lagging bitcoin's own move. The index is a lagging measure, describing only what already happened over the past 90 days. A high reading today describes a condition that has already played out. Traders who buy altcoins purely because the index just crossed 75 are reacting to a rearview measurement, not necessarily catching a trend at its start. Take a reader holding 25,000 rupees split across ten altcoins during a period when the index reads 80. On average, most of those ten would have beaten bitcoin's return over the prior 90 days. Any single coin among the ten could still have lagged badly, even while the broader basket outperformed. The index describes the group's behavior, and not any one holding inside it. The edge case is a low-volume rally in a handful of altcoins dragging the whole index up. The calculation only checks whether each of the top 50 beat bitcoin, not by how much or on what volume. A narrow rally concentrated in a few thinly traded tokens can push the reading toward altcoin season. That can happen even while most capital in the market has not rotated out of bitcoin at all.

Bitcoin's order book is thin relative to its market cap compared with gold or large-cap equities, so a given order size moves its price further. It trades 24/7 with no circuit breakers to pause a sharp move. Heavy use of leveraged derivatives also amplifies swings through cascading liquidations when price crosses key levels. Order book depth is the amount of buy and sell orders sitting at each price level. That depth is what absorbs a trade without moving the price much. Gold and large-cap stocks have decades of institutional market-making behind them, producing deep books that absorb large orders easily. Bitcoin's market is younger and thinner in comparison, so the same size order in rupee terms pushes its price further. The 24/7 nature of crypto markets removes a mechanism traditional markets rely on: the pause. Stock exchanges use circuit breakers that halt trading during an extreme move, and they close overnight and on weekends besides. Bitcoin has none of that; a sharp move at 3am on a Sunday runs uninterrupted. Leveraged futures positions add fuel, since a big enough drop forces automatic liquidations that sell into an already falling market. A trader holding a 25,000 rupees bitcoin position on 5x leverage sees that position liquidated once the price falls by roughly 20 percent. The leverage multiplies the loss against the same margin. When enough leveraged positions cluster near the same price level, their liquidations sell into the market one after another. What started as an ordinary dip can turn into a sharper, faster drop within minutes. The edge case is a stock having an earnings report or a yield anchoring some floor under wild speculation, a reference point bitcoin lacks. Bitcoin's price is set purely by what buyers and sellers agree to pay right now. There is no cash flow, no dividend, and no earnings call to check it against. That is part of why its price can move on sentiment alone, in a way a profitable company's stock rarely does. Qatobit's QSI Core index addresses part of this directly in its construction, holding Bitcoin and Ethereum alongside a Gold allocation and a stable reserve. The Gold allocation is a structural buffer built into the basket, rebalanced monthly, rather than a bet that volatility will fall.

SEBI has not approved a spot bitcoin ETF for listing on the NSE or the BSE. Indian investors can access US-listed bitcoin ETFs only through an international broking account, under the RBI's Liberalised Remittance Scheme. That route taxes the returns as foreign capital assets, under rules separate from India's crypto tax regime. SEBI regulates what can list on Indian exchanges. It has not cleared a bitcoin-holding fund the way the US SEC did for spot bitcoin ETFs starting in 2024. Until that changes, there is no NSE- or BSE-listed way to hold bitcoin exposure through a regular Indian demat and trading account. A gold ETF or an index fund works this way; bitcoin does not. The workaround runs through the Liberalised Remittance Scheme. It lets an Indian resident send up to 250,000 dollars abroad per financial year for permitted purposes, including opening a foreign brokerage account. An investor sends rupees through an authorized bank, converts them, and buys a US-listed bitcoin ETF through that foreign account. That process adds currency conversion costs, foreign brokerage fees, and separate foreign asset reporting. An investor remitting 5 lakh rupees a year through the LRS route to buy a US bitcoin ETF stays well within the 250,000 dollar cap. They still pay a currency conversion spread and foreign brokerage charges that a domestic listing would not require. Gains on that position are taxed as foreign capital assets on exit. Those rules sit apart from the 30 percent flat rate and 1 percent TDS that apply to virtual digital assets held directly in India. The edge case is LRS reporting itself. Every remittance under the scheme has to be declared to the bank at the time of transfer. Foreign assets bought through it need to be reported in the investor's income tax return under Schedule FA. That applies regardless of whether any gain was realized that year. That compliance step does not arise for a domestic-only investment. Qatobit's QSI indexes hold direct crypto exposure, including bitcoin, inside an Indian platform. A reader gets that exposure without opening a foreign brokerage account or working within the LRS cap. Gains sit under India's VDA tax treatment, apart from the foreign capital asset rules that apply to a US-listed ETF.