Foundation
Current Mainnet Block 0: The Starting Point of New Rules After New Bedford
We organize the previous BTCMobick ledger, the current mainnet height 0, and the February 2026 migration period as the flow marking the start of the new mainnet.
The previous ledger and the current mainnet are part of the same project narrative but rely on different data sources for verification. The previous ledger is verified through the previous explorer and previous mainnet migration records, while the current mainnet is verified via the current node headers and explorer.
The current mainnet height 0 is not Bitcoin’s block 0. It is the reference block where the BTCMobick current ledger started under new rules after the New Bedford transition, recorded with the header timestamp of 2026-01-11 00:00:00 UTC.
The migration period is confirmed at several block heights on February 16, 2026 UTC. Therefore, the interface should display the previous mainnet block 556760 as a past record alongside the current height 0 as the new mainnet starting point.
Plain words
First-time terms
- Mainnet
- The primary ledger network that is actively operated.
- Height 0
- Not Bitcoin’s block 0, but the new starting block of the current BTCMobick mainnet.
- Migration
- The process of moving from the previous structure to the new structure.
Learning objectives
- Explain the previous ledger and current mainnet separately.
- Understand that the current mainnet height 0 is a new starting point different from Bitcoin’s block 0.
- Read the migration period as a verifiable list of blocks rather than a single date statement.
Current Height 0 Different from Bitcoin’s Block 0
The BTCMobick current mainnet height 0 hash is 000000002f614682b2b4014d4948eeccf606221496572b2e7e6864404c36a163.
The timestamp is recorded as 2026-01-11T00:00:00.000Z, and since it is a genesis-type block, the previous block hash is represented by 64 zeros. This does not mean rewriting Bitcoin’s genesis but is the new reference point for the BTCMobick current mainnet.
Migration Window
On February 16, 2026 UTC, blocks at heights 4864, 4867, and 4889 are confirmed on the current mainnet.
Each block is timestamped 2026-02-16T14:16:13.000Z, 2026-02-16T14:21:38.000Z, and 2026-02-16T14:45:43.000Z respectively. This corresponds to the evening hours of February 16, 2026 in Korean time.
How to Read the Previous and Current Ledgers Together
BTCMobick includes the Bitcoin parent ledger, the previous BTCMobick mainnet, and the current mainnet after New Bedford. A thorough explanation separates these roles rather than treating them as one chain.
Additional data to collect includes the reference block of the previous explorer, height 0 of the current explorer, blocks in the migration window, and migration records. Users should be provided with links specifying 'where and what to verify.'
Verification questions are simple: Is this value evidence of a past fork, the current ledger state, or the migration process? These questions ensure accuracy in explaining the current mainnet.
Current Mainnet Block 0 Is a New Reference Point
The current BTCMobick mainnet height 0 is not a rewriting of Bitcoin’s genesis. It is the reference point where the ledger users see after New Bedford started under new rules.
Previous mainnet records are verified through past migration records and explorers, while current transactions and balances are verified based on the current mainnet. The key of this lesson is not to mix these two views.
Memory Points
Points to remember
Current Height 0 Is Not Bitcoin’s Genesis
The current BTCMobick mainnet height 0 is a different reference point from Bitcoin’s block 0. It is the block where the ledger after New Bedford started under new rules.
Therefore, when reading the current ledger, do not consider it a restart of Bitcoin’s entire history. It shows where the current BTCMobick operating ledger begins.
Missing this distinction mixes the roles of the previous mainnet, migration records, and current mainnet.
Migration Records Are a Window to Past Data
The previous mainnet block 556760 record is not viewed as a block directly continued by the current mainnet. It is read as a window to verify past ledger data.
Users must check both the explorer name and ledger name. Even under the same BTCMobick name, the previous explorer and current mempool cover different scopes.
Developing the habit of reading with ledger names is a fundamental basis for later transaction lookups and source pages.
Practice
Separate Timeline by Ledger
- On the source page, display the previous mainnet entry and the current ledger entry separately.
- Next to previous mainnet block 556760, write 'Previous Mainnet Migration Record,' and next to current height 0, write 'New Mainnet Starting Point.'
- List the timestamps of height 0 and heights 4864, 4867, 4889 in chronological order.
- Summarize in one sentence including both 'previous ledger' and 'current mainnet.'
Learners can explain the fork in the previous ledger and the restart of the current mainnet without mixing them.
Label Previous and Current Ledgers
- Divide the previous mainnet migration record and current mainnet starting point into two columns.
- Write which explorer or data to check in each column.
- Write reasons why the current height 0 should not be confused with Bitcoin’s block 0.
Learners can guide users by separating past migration records and the current mainnet reference point.
Key takeaways
- The fork in the previous ledger and the current mainnet height 0 are different verification axes.
- The current mainnet height 0 is not Bitcoin’s block 0 but the new starting point after New Bedford under new rules.
- Migration explanations are safer when showing block heights and timestamps rather than just a single date.
- The BTCMobick current mainnet should be read separately from previous records and current reference points.
Quiz
Quiz
Why do we separate the previous ledger and current mainnet?
What is the current mainnet height 0 in simple terms?
What is a good way to explain migration?
Evidence and statusSources connected
This localized lesson keeps the same source IDs as the Korean curriculum. Use the source library for ledger checks and official references.
- claim-mainnet-first-block
- claim-fork-height-sensitive
- claim-current-mainnet-boundary