blog + publishing

write and publish posts that live permanently on-chain. no platform can remove them.

$ praxis blog publish

write markdown ....................... editor

sign with wallet ..................... personal_sign

submit to BlogRegistry .............. on-chain tx

post stored permanently ............. ✓

SSR + OG meta generated ............. /post/{id}

writing posts

open the compose modal from the feed (dock "write" icon) or publish a journal entry. posts support markdown formatting:

bold — wrap text in **double asterisks**
italic — wrap text in *single asterisks*
headings — prefix with #, ##, or ###
links — [text](url)
images — ![alt](url) with IPFS support

on-chain storage

every post is written to the BlogRegistry smart contract on Scroll L2. the contract stores the post content, author address, timestamp, and any references. once published, the post exists permanently — no server, no company, no single point of failure can remove it.

amendments (edit history)

posts cannot be deleted or overwritten. instead, you publish an amendment — a new on-chain entry with refType=5 pointing to the original post. the full edit history is preserved on-chain. readers see the latest amendment by default, with a link to view the complete history of changes.

post types

each post can have a reference type that connects it to other content:

standalone — a regular blog post with no references
project update (refType=1) — linked to a specific project, appears in the project's update stream
reply (refType=3) — a comment on another post, threaded below the original
amendment (refType=5) — an edit to a previous post, preserving the original

reading list / bookmarks

save any post to your reading list by clicking the bookmark icon. bookmarks are stored locally (encrypted, synced via your wallet) and appear in your collection under saved items. bookmarks work across all artist sites on the network.

SEO + social sharing

every published post gets server-side rendered HTML with dynamic Open Graph meta tags and JSON-LD structured data. when you share a post link on social media, it shows the title, excerpt, author name, and publication date — no client-side JavaScript required for previews.

comments + replies

anyone on the network can reply to a post. replies are themselves on-chain blog posts with refType=3, so they are permanent and owned by the replier. replies appear threaded below the original post.

for the screenplay editor and private encrypted writing, see journal + screenplay editor.