# Blockphase project whitepaper

Version 0.1 — product and experience specification

## 1. Abstract

Blockphase is a read-only block rhythm observatory. It turns a stream of public block headers into one continuous visual rail so people can understand how a chain advances without first learning to read an explorer table.

The product is built around a simple promise: **watch the chain move, one block at a time.** A block arrives, links to its parent, and becomes part of a visible sequence. Blockphase does not trade, operate validators, control nodes, or claim that a block is meaningful merely because it exists.

## 2. The problem

Block explorers are useful for lookup, but their tables flatten time into rows. A visitor can find a block number or hash and still miss the behavior of the system:

- when a new head arrived;
- whether it links to the prior observed block;
- how much transaction activity the block contains;
- how the latest block becomes history as the chain advances;
- whether the public data source is delayed or unavailable.

Blockphase is not another explorer. It is the explanatory layer between raw block fields and a human sense of sequence.

## 3. The product

The primary experience is the **Blockfall Rail**: one persistent visual object that carries the story from beginning to end.

1. **Arrive** — a newly observed public block enters the rail.
2. **Link** — its parent hash is compared with the previously observed block hash.
3. **Advance** — the new block becomes the head and the previous head moves into visible history.

The homepage rail is an explanatory motion model, not a literal replay of fetched blocks. A separate telemetry readout supplies the factual current-head fields. When the configured public source cannot be reached, that readout must say so instead of inventing values.

## 4. Data translated into plain meaning

Blockphase uses a deliberately small public data model:

| Public field | Human meaning in Blockphase |
| --- | --- |
| Block height | Where the observed chain head is now |
| Timestamp | When the block was produced and the rhythm between arrivals |
| Transaction count | How much transaction activity is contained in the block |
| Block hash | The public identifier for the observed block |
| Parent hash | The link used to compare one observed block with the previous one |

Chain configuration, RPC endpoints, and network identifiers belong to the implementation layer. They may appear in a technical note or network footer, but they are not the product story.

## 5. User journey

### Discover

The homepage explains the product through the same moving rail the visitor will later use. The visitor first understands what a block is doing, not which endpoint the site calls.

### Observe

The homepage combines two clearly separated layers: live telemetry shows one factual public head, while the rail explains the `Arrive → Link → Advance` model. The current demo exposes the parent reference for inspection; it does not yet fetch the previous block and independently verify continuity.

### Inspect

The planned **Pulse** surface brings the latest twelve observed block headers into one focused workspace. A visitor can pause the motion, inspect a block, compare its parent link, and replay the recent sequence.

### Verify

When deeper transaction or address detail is needed, Blockphase hands the visitor to the official explorer instead of pretending to replace it.

## 6. Why it is useful

- **For builders:** see the current head's rhythm and parent reference before opening a low-level explorer view.
- **For operators and researchers:** review a compact recent sequence with explicit source and unavailable states.
- **For new users:** learn the relationship between height, time, activity, hash, and parent link through motion.
- **For the ecosystem:** provide a legible public observation surface without custody or transaction risk.

The value is comprehension, not speculation. Blockphase proves its usefulness when a visitor can explain how the observed chain advanced and can independently open the official record.

## 7. Product architecture

```text
Public block source
        ↓
Current-head telemetry
        ├── height · timestamp · transaction count
        └── hash · parent reference

Explanatory Blockfall Rail
        ↓
Planned twelve-block sequence in Pulse
        ↓
Official explorer for deeper verification
```

Browsing is read-only. Connecting a wallet is optional and may read only the selected public address and active chain ID. It is not required to observe blocks and must never be presented as proof that the user participated in the network.

## 8. Current state and roadmap

### Now — narrative demo

- Responsive presentation homepage
- Continuous explanatory Blockfall Rail motion
- `Arrive → Link → Advance` explanation
- One periodically refreshed public block header
- Honest public-data unavailable state
- Official network and explorer exits
- Reduced-motion and keyboard support

### Next — Pulse workspace

- Latest twelve observed block headers
- Pause and resume the recent sequence
- Block-by-block field inspection
- Parent-reference inspection
- Replay controls for the observed window

### Later — only after Pulse is validated

No later feature set is committed yet. Additional observation tools should be defined from Pulse usage and independently tested before they appear in public roadmap copy.

## 9. Boundaries

Blockphase does not:

- execute trades or transactions;
- operate or control validators or nodes;
- prove economic or consensus finality beyond what its documented public source returns;
- invent missing blocks, metrics, people, partners, or network claims;
- treat wallet connection as product value;
- replace the official block explorer.

## 10. Network relationship

Blockphase currently observes BOT Chain public block data. BOT Chain is the underlying network context, not the Blockphase product itself. The official logo, website, and explorer should therefore remain a compact trust and verification layer rather than dominate every section of the interface.

## 11. Product test

The website succeeds only if a first-time visitor can answer these questions without reading technical configuration:

1. What is Blockphase? — A read-only block rhythm observatory.
2. What does it do? — Turns recent public block headers into one continuous visual sequence.
3. How does it work? — Blocks arrive, link to their parents, and advance into history.
4. Where is the product used? — On the Blockfall Rail now and in the planned Pulse workspace for the latest twelve blocks.
5. What comes next? — A focused inspector and replay surface, followed only by validated observation tools.