September 21–27, 2026
Chronava

A weekly mission workspace with optional, minimal proof.

ChronavaPlan time. Prove progress.
Chronava on XBOT ChainExplorerStatusWhitepaperPrivacyTerms
Weekly mission workspaceWrite-ready configuration

Plan the week.
Keep the evidence.

Chronava turns one outcome into an editable week. Your schedule stays on this device; when it matters, you can create a receipt and choose what—if anything—to record publicly.

Local firstGoals and schedules stay in this browser.
Human editableEvery suggested mission remains yours to change.
Minimal proofPublic actions use hashes, not your private notes.
This week’s outcome
1 of 5 missions
20%

Monday, September 21, 2026

2 missions

Tuesday, September 22, 2026

0 missions

Wednesday, September 23, 2026

1 mission

Thursday, September 24, 2026

1 mission

Friday, September 25, 2026

1 mission

Saturday, September 26, 2026

0 missions

Sunday, September 27, 2026

0 missions

Map the smallest path

Monday, September 21, 2026

09:30 – 11:00

Date
Time→
Notes
Status
Color

Proof path

A four-stage workflow keeps each public action separate and reviewable. Using it is optional.

Write-ready configurationRead status

All four verified role addresses and the supported network are configured. Every action still requires an explicit wallet review.

  1. 01
    CommitSet the mission

    Register a receipt, deadline, and checkpoint target.

    missionCommitment
  2. 02
    Check inRecord progress

    Add minimal checkpoint hashes before the mission deadline.

    checkpointRegistry
  3. 03
    OptionalAdd a bond

    Choose an accountability deposit only if it suits the mission.

    commitmentBond
  4. 04
    CompleteCreate a badge

    Issue a completion record after the checkpoint target is reached.

    completionBadge

Bond terms, plainlyThe bond is optional and earns no yield. Under the current contract design, the same amount can be released to the mission owner after the checkpoint target is met or after the deadline passes. Release is a separate transaction and requires network gas; verify the deployed contract and parameters before using it.

Network costCommitment, checkpoint, and badge actions send 0 BOT to the contract, but every on-chain action can still require wallet-paid network gas.

Create a local receipt

Hash the current private schedule on this device before choosing any contract action.

Generate a receipt to prepare a contract action.

Arranging your week…