버그 바운티 보상은 심각도 및 취약점의 영향력에 따라 그룹화됩니다. 각 심각도 수준에 해당하는 취약점 유형에 대한 예시와 설명은 아래에서 확인할 수 있습니다. 지급 금액은 웹사이트/앱과 스마트 계약에 대해 별도의 척도가 있는 4단계 구조로 되어 있습니다.

직책 입력

헤드라인

직책

{{currentSectionTitle}}에 대해 더 알아보기

이름

제목을 입력해 주세요

취약점과 영향을 받는 자산에 대한 간략한 설명을 입력하세요.

주제

핵심 팀은 국제 사법 협력, 형사 사법 시스템, 자금 세탁 방지 및 부패 측면에서 낮은 종합 등급을 받은 국가에 위치하고 있습니다. 이러한 맥락적 데이터는 사기를 예방하고 완화하는 데 있어 어려움과 복잡성이 증가했음을 시사합니다.

핵심 팀은 국제 사법 협력, 형사 사법 시스템, 자금 세탁 방지 및 부패 측면에서 중간 등급을 받은 국가에 위치하고 있습니다. 이러한 상황별 데이터는 중간 수준의 지리적 책임성을 시사하며, 따라서 사기 위험을 줄이고 완화할 수 있습니다.

핵심 팀은 국제 사법 협력, 형사 사법 시스템, 자금 세탁 방지 및 부패 측면에서 가장 높은 종합 등급을 받은 국가에 위치해 있습니다. 이러한 상황별 데이터는 가장 높은 수준의 지리적 책임을 시사하며, 따라서 위험 감소 및 완화를 극대화합니다.

본 웹사이트에 제공된 정보는 투자 자문, 재정 자문, 거래 자문 또는 기타 어떠한 종류의 자문도 구성하지 않으며, 웹사이트의 콘텐츠를 그러한 목적으로 해석해서는 안 됩니다. CertiK는 어떠한 암호화폐의 매수, 매도 또는 보유도 권장하지 않습니다. 투자 결정을 내리기 전에 반드시 자체적인 실사를 수행하고 재정 고문과 상담하십시오.

취약점 제목

This guide explains blockchain forks—when a cryptocurrency’s network splits—from why they happen to the real risks they pose. You’ll learn key security threats like replay attacks and study past forks to understand their impact. Most importantly, we provide clear steps to protect your assets, turning a complex technical event into a matter of personal financial safety.

How forks happen and why users should care

Read and Learn

A blockchain is a shared digital ledger. __Consensus__ is the agreement by all network participants to follow the same rules to maintain a single truth. Think of it as a global club's rulebook. The key rules are:
- How to verify transactions.
- How to add new data.
- What makes the data valid? This "social contract" of following the same protocol is what creates trust and a unified record without a central authority.


The Ledger & Consensus (The "Social Contract")

A __fork__ occurs when the blockchain's single history splits into two potential paths. It's like a road dividing.
- __Temporary Fork__: Happens naturally when two blocks are found simultaneously; resolved quickly.
- __Permanent Fork__: Occurs when the community disagrees on the core rules (the protocol). The network splits, creating two separate blockchains that share history up to the split point but diverge afterward.

What is a Fork? (The technical split)

The key difference is __backward compatibility__.
- __Soft Fork__: A __tightening__ of rules. Blocks created under new rules are accepted by old-rule software. It's like adding a new "must be under 6ft tall" rule to a ride—older software still sees valid riders. One chain continues.
- __Hard Fork__: A __loosening__ or change of rules. New-rule blocks are __rejected__ by old software. This creates two separate, coexisting chains. Participation requires upgrading your software.


Soft Forks vs. Hard Forks (Backward compatibility)

Forks are tools for change. Their intent defines them:
- __Planned Upgrades__: Coordinated hard forks to add features, fix bugs, or improve efficiency (e.g., Ethereum's "London" upgrade). The community moves together.
- __Contentious Splits__: Disagreements on vision, philosophy, or governance lead to a permanent split. A minority group enforces different rules, creating a rival chain (e.g., Bitcoin Cash). This often results in a new cryptocurrency.


Why Forks Happen (Upgrades vs. Contentious Splits)

During a hard fork, you may hold coins on __both__ new chains. A __Replay Attack__ is a major danger:
- A transaction you sign on Chain A can be maliciously "replayed" on Chain B because the transaction data is valid on both.
- __Consequence__: You intend to send coins only on one chain, but they are stolen from the other. Your assets on the forked chain can be drained without your consent.


The Security Risk: Replay Attacks (How users lose money)

- __The DAO Hack / Ethereum (ETH) & Ethereum Classic (ETC)__: A hard fork was executed to reverse a major hack, creating ETH (new chain) and ETC (original chain purists). This is the classic example of a philosophical split over immutability vs. intervention.
- __Bitcoin (BTC) & Bitcoin Cash (BCH)__: A contentious hard fork over scaling. Bitcoin Cash advocated for larger blocks to increase transaction speed, splitting from Bitcoin's main development path.
- 

Real-World Case Studies

1. __Do Not Transact__: Avoid sending coins on either chain immediately after a fork until the networks stabilize.
2. __Use Protective Wallets__: Wait for your wallet provider to announce fork support and implement replay protection.
3. __Safeguard Private Keys__: Never enter your private keys or recovery phrase on unfamiliar websites claiming to "claim" forked coins.
4. __Wait and Research__: Let developers and exchanges handle the technical split. Research which new chain has community and economic support before interacting.

User Best Practices (How to stay safe during a fork)

Take the Quiz

To ensure all participants agree on a single, valid version of the ledger.

A rule change that is backward-compatible, where old nodes still accept new blocks.

A permanent split that always creates a new cryptocurrency.

A temporary divergence caused by slow internet speeds.

A mandatory upgrade that forces all nodes to split.

It is scheduled by core developers six months in advance.

It is supported by 100% of the network's miners. 

It arises from a fundamental disagreement within the community, leading to a permanent split. 

It reverses blocks on the new chain, destroying coins.

It allows a transaction signed for one chain to be fraudulently rebroadcast and validated on the other chain.

It steals the user's private keys directly from their wallet.

It changes the transaction amount after it is signed.