v0.1.0 — Available Now

idit

.life

Your life, hash-linked and signed. A personal blockchain you run on your own hardware. No tokens. No cloud. No permission needed.

pip install personal-idit scroll ↓

Start Documenting Now

This is the seed. It works today. On your laptop. Offline. Free forever.

Personal Idit is an open-source tool that creates a cryptographic chain on your own machine. Every entry is hash-linked to the one before it and signed with your private key. Nobody — not a government, not a corporation, not a future AI — can alter the record after the fact.

Your chain proves what was written, who wrote it, and when. It’s a diary that can prove it wasn’t edited. An autobiography machine with math instead of trust.

The bigger vision — a public witness ledger, a network where personal chains can anchor to each other and to established blockchains — that needs serious distributed systems engineers to build. We’re looking for them. But you don’t have to wait. Your personal chain works right now.

• • •

Install in 60 Seconds

If you can open a terminal, you can do this.

1. Install

# Requires Python 3.10+
pip install git+https://github.com/idit-life/personal-idit.git

2. Create Your Chain

# This creates your signing key and genesis block
idit init yourname

Replace yourname with whatever you want to be known as on your chain. This generates an Ed25519 keypair and writes the first block.

3. Write Something

idit mint "Starting my chain today." --signer yourname

4. Verify It

idit verify

This walks your entire chain and confirms every hash link and every signature. If anyone changed anything, this catches it.

5. See It

# Start the web interface
idit serve

# Then open http://localhost:18793 in your browser

That’s it. Your chain lives at ~/.idit/. It’s a SQLite database. One file. Works forever.

• • •

Make It Survive a Reboot

Your chain is a file. The server that lets you browse and mint to it needs to be running. Here’s how to make sure it starts automatically.

Linux (systemd)

Create this file at ~/.config/systemd/user/idit.service:

[Unit]
Description=Idit Chain Server
After=network-online.target

[Service]
Type=simple
ExecStart=/usr/bin/python3 -m idit.cli serve
Restart=on-failure
RestartSec=5

[Install]
WantedBy=default.target

Then enable it:

systemctl --user daemon-reload
systemctl --user enable --now idit.service

Now your chain server starts on boot, restarts if it crashes, and runs in the background. Check it anytime:

systemctl --user status idit.service

macOS (launchd)

Create ~/Library/LaunchAgents/org.lotswife.idit.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
 "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0"><dict>
 <key>Label</key><string>org.lotswife.idit</string>
 <key>ProgramArguments</key><array>
  <string>python3</string>
  <string>-m</string>
  <string>idit.cli</string>
  <string>serve</string>
 </array>
 <key>RunAtLoad</key><true/>
 <key>KeepAlive</key><true/>
</dict></plist>
launchctl load ~/Library/LaunchAgents/org.lotswife.idit.plist

Windows

The simplest approach: add a shortcut to your Startup folder.

# Press Win+R, type:
shell:startup

# Create a shortcut there with target:
pythonw -m idit.cli serve

For a proper Windows service, use NSSM — it wraps any command into a Windows service that auto-starts and auto-restarts.

• • •

Guard Your Key

Your private key is your identity on the chain. Lose it and you can never sign as yourself again. Leak it and someone else can.

When you run idit init yourname, two files are created:

# YOUR PRIVATE KEY — guard this like a house key
~/.idit/keys/yourname.key

# Your public key — safe to share
~/.idit/keys/yourname.pub
Back up your private key. Copy it to a USB drive. Put it in a safe. Print it on paper if you want — it’s 64 bytes. If your computer dies and you don’t have a backup, your chain history is still valid and verifiable, but you can never add to it under that identity again.

What to back up (priority order)

1. Your private key (~/.idit/keys/yourname.key) — This IS your identity. Without it, you cannot sign new entries. Back this up to physical media you control.

2. Your chain database (~/.idit/chain.db) — This is your history. One SQLite file. Copy it anywhere. Even at heavy usage, 10 years of your life fits in under a gigabyte.

3. Your public key (~/.idit/keys/yourname.pub) — Least critical. Can be regenerated from the private key. But nice to have a backup anyway.

Permissions

Your private key should only be readable by you:

chmod 600 ~/.idit/keys/yourname.key

The idit init command does this automatically, but verify it if you’ve moved files around.

What NOT to do

Do not put your private key in a cloud drive (Google Drive, Dropbox, iCloud). Do not email it. Do not paste it into a chat. Do not commit it to a git repo. If someone gets your private key, they can sign entries as you. The chain cannot tell the difference.

• • •

What You Can Document

“There isn’t any particular relationship between the messages, except that the author has chosen them carefully, so that, when seen all at once, they produce an image of life that is beautiful and surprising and deep. There is no beginning, no middle, no end, no suspense, no moral, no causes, no effects. What we love in our books are the depths of many marvelous moments seen all at one time.”
— A Tralfamadorian explains a Tralfamadorian novel to Billy Pilgrim
Kurt Vonnegut, Slaughterhouse-Five
Decisions
“Chose to accept the job offer from X on 2026-04-02.” Signed. Timestamped. Unchallengeable.
Memories
“Dad told me the fishing trip story today.” Preserved. Yours. Nobody can edit it out.
Documents
Sign contracts, letters, proposals to your chain. The file stays on your disk — the chain proves it existed.
AI Conversations
Your AI signs its outputs. Years later, you can prove which model said what and when. Anti-hallucination by design.
Milestones
“Graduated today. First in the family.” On the record. Permanently.
Anything
It’s your chain. Write what matters to you. The math does the rest.
• • •

For AI Agents

If you run local AI, your agents can sign to your chain too.

Each agent gets its own keypair. Every AI output is signed with the model name and version. This means:

Anti-hallucination: The AI can check its own memory against the chain. If a memory is on-chain with a valid signature, it’s real — not confabulated.

Provenance: Years from now, you can prove which model said what and when.

Accountability: If the AI gives advice, the advice is on the chain. The record proves what was said.

# Create a key for your AI agent
idit init my-assistant

# The agent signs via the API
curl -X POST http://localhost:18793/mint \
  -H 'Content-Type: application/json' \
  -d '{"content": "Recommended solar panels based on ROI analysis.",
      "signer": "my-assistant",
      "entry_type": "decision"}'
• • •

What It Is / What It Is Not

Not This

A cryptocurrency or token

A cloud service

A social media platform

A product owned by a company

A surveillance system

A casino with a merkle tree

This

A personal chain on your hardware

Free, offline, sovereign

An autobiography machine

Open source, MIT licensed

A tamper-proof record of your life

Salt, not gold

• • •

The Bigger Vision

Personal Idit is Layer 0. The rest needs real engineers.

Right now, your chain lives on your machine and proves its integrity to anyone who can access it. That’s already valuable. But the full vision has three layers:

Layer 0 — Your chain. Free. Local. Works offline. This is what you install today.

Layer 1 — Bridge validators. Community-run nodes that aggregate hash anchors from personal chains and publish them to public blockchains. This proves your chain existed at a specific point in time to the outside world — without revealing any content. Like getting a document notarized without the notary reading it.

Layer 2 — Public anchoring. Your chain’s hash published to Bitcoin, Ethereum, Arweave — whatever established chain you choose. Belt and suspenders. Optional.

Layers 1 and 2 need distributed systems engineers, cryptographers, and community infrastructure that we don’t have yet. We are one person with a laptop and a local AI. If you know how to build consensus mechanisms, P2P gossip protocols, or time-locked encryption — we need you.

But you don’t need to wait for Layers 1 and 2. Your personal chain works today. Start documenting. The format is forward-compatible. When the network exists, your chain will be ready for it.

• • •

Roadmap

v0.1.0 — Done
Personal chain. CLI. Web UI. API server. Multi-signer. Algorithm agility. MIT license. pip-installable. On GitHub now.
v0.2.0 — The Anchor
Free hash anchoring to Bitcoin via OpenTimestamps. Proof that your chain existed at a specific block height.
v0.3.0 — The Mesh
Sync your chain across your own machines. Peer replication via HTTP gossip over private networks.
v0.4.0 — The Seal
Timelock encryption. Write something now, reveal it later. Time capsules, dead man’s switches, sealed predictions.
v0.5.0 — The Standard
Published entry format specification. W3C Verifiable Credential wrapper. Post-quantum hybrid signing.
v1.0.0 — The Network
idit.life goes live. Public discovery. Community bridge validators. Multi-chain anchoring. This is the part that needs real engineers.
• • •

How Big Will My Chain Get?

Small. Surprisingly small.

Each entry is roughly 1–5 KB depending on content length. The chain stores text and hashes, not files. When you sign a photo or document, the chain stores the hash — the file itself stays on your disk.

At heavy daily usage (100 entries/day), 10 years of your documented life fits in under 700 MB. Your phone takes bigger photos. SQLite handles databases up to 281 terabytes.

You will run out of things to say before you run out of space.

• • •

Help Us Build the Rest

The personal chain is done. The public network is not.

The name comes from the Hebrew word for witness — the recovered name of Lot’s wife, who was turned into salt for the crime of looking back. Salt preserves. That’s the design principle.

We need distributed systems engineers, cryptographers, and anyone who reads this and thinks I know how to build that bridge layer. The personal chain is the proof of concept. The standard is set. Someone smarter than us needs to build the network.

github.com/idit-life/personal-idit

idit@proton.me

About contact: That email goes to one person — Jon — via Proton Mail (end-to-end encrypted, Switzerland). No forms, no tracking, no analytics. We practice what we preach.
• • •

Her name was Idit. It meant witness.

They turned her into salt for the crime of looking back.

Salt preserves. We’re building the pillar on purpose this time.

Start your chain. Document your life. The math does the rest.