Make the boundary
the record.

A self-reported boundary.

People say “starting research” or “finished building” across disconnected chats. Chronyx offers one small public record under a wallet: a topic, a beginning and an ending. It supports intentional public activity without creating an account, a reward scheme or an employer-controlled attendance system.

One open interval per wallet.

Each wallet has a monotonically increasing interval count and at most one active interval. Starting with a nonzero bytes32 topic records that topic and a uint64 block timestamp. A second start is rejected while an interval is active.

Ending requires the exact active interval ID. It adds an end block timestamp and clears the active pointer, preserving topic and start time. A stale end prepared for an older interval cannot close a newer one. The present interface offers four short public labels, encoded directly to bytes32; it does not imply confidentiality, name resolution or a service that interprets the topic.

The actor is the sender.

Only msg.sender can start or end that sender’s interval. There is no author input, administrator, owner, proxy, upgrade key, custody or payment logic. Another wallet cannot close your interval. The immutable contract would require a separately reviewed new address for future rule changes, with old records preserved and migration clearly described.

Public data. Network Gas only.

The contract stores a wallet, topic bytes32, incremental interval ID, and start/end block timestamps. Starts and ends are nonpayable. There are no deposits, application fees, tokens, token approvals, rewards or payouts. A future deployed write consumes native network Gas; simply connecting a wallet does not.

The interface reviews the exact account, chain, contract, action, topic or expected interval ID, estimate, buffered Gas limit, fee cap and maximum network execution cost before requesting a wallet action. It rechecks the account, network, verified runtime code, active interval, balance and fees, rejects expired reviews, and validates the exact receipt and matching event. Chain-specific extra charges may be additional; the wallet is the final fee review.

Not proof of work or presence.

Block timestamps are not precision timing. An interval does not prove activity, attendance, productivity, completion, location, identity or duration quality. Anyone controlling a wallet may self-report. Public topics and timing can be correlated with other records; do not put sensitive routines, personal locations or confidential details into a public label.

Closing an interval changes active state but does not delete history. This local Demo provides no notification backend, team attendance system, reward, verified analytics or cross-chain indexing. Local tests are not an independent security audit.

Prepared locally. Not deployed.

This project includes a long website, a separate interval room, this paper, privacy guidance, same-project contract source, local temporary-chain tests and an unsigned deployment preview. No public chain, RPC, contract address or runtime identity is configured; real writes remain disabled.

The independent page offers clearly labelled memory-only practice that disappears on reload. It is not a chain receipt. After a separately authorized network and controlled-signer deployment, the existing adapter can be configured only with the verified address and runtime code hash. Deployment preview checks the public account, network, balance, Gas and bytecode without signing or broadcasting. Private keys must never enter this website, public API, source, logs or records.

Public history indexing and topic filtering could be added later with their own operational review. They are not current promises. The project’s X account is pending rather than substituted with another brand’s link.