A story that stays open.
Lorevra is a shared, append-only story. Anyone using a compatible wallet can contribute one short line after reading the current sequence. The next participant decides where it goes.
The core problem is simple: collaborative writing often loses the order and authorship of its individual contributions. Lorevra gives each line a wallet author and an explicit place in an ordered public record.
This does not establish legal authorship, copyright ownership, real-world identity or the truth of a statement. It records who submitted a line through this contract.
Read before you continue.
The workspace reads the contract’s current line count. Your draft is reviewed against that expected length. An append supplies the text and the expected length together.
If the story length still matches, the contract stores the line and emits a LineAdded event. If someone wrote first, the call fails. Read the updated sequence and choose whether your draft still fits.
A stale-state check is a coordination rule, not a reservation. It does not guarantee your place while a transaction waits.
Successful publication is shown only after a successful receipt containing the expected contract’s business event. A wallet prompt or a transaction hash alone is not a confirmed contribution.
A small contribution. A lasting record.
Each line must contain between 1 and 320 UTF-8 bytes. This is a byte limit, not a character limit. The current frontend trims empty surrounding space; the contract enforces the byte length.
The author is always the transaction sender. A participant cannot enter someone else’s wallet as the author. This version has no privileged editor and no ability to reorder, edit or remove stored lines.
The public content policy is a product boundary still requiring review before public launch. No moderation service or copyright review is implemented in this local Demo.
No private room behind the interface.
The line text, author wallet, sequence and timestamp are stored publicly. Events and transaction data remain inspectable outside this website. Closing a tab or hiding a line in a future interface would not erase chain history.
Drafts in this Demo stay in the current browser tab. They are not uploaded, persisted to local storage or sent to an AI service. A wallet connection asks your wallet to share its selected public account and network with the page; it does not itself publish a line.
Do not include private details, credentials or sensitive information in a story intended for permanent public storage.
One basic chain action.
The append function is nonpayable. It does not collect an application fee, hold funds, distribute rewards, issue a token or request token approval. A future transaction still consumes the selected network’s gas.
Live gas estimation will use the connected wallet’s network and current fee data. The wallet displays the final transaction before the user signs. Estimates may change and failed transactions can still consume gas.
Local Ganache tests cover first and subsequent appends, identity attribution, stale cursors, empty and oversized lines, invalid reads and rejection of value transfers. Their gas measurements are local observations, not a production-network fee promise.
Local first. Public later.
The website, independent workspace and dedicated contract are implemented as a local Demo. The default configuration has no public network, address or explorer. It disables public-chain writes even if a wallet is connected.
Compilation and isolated local transactions are not an independent security audit. Public deployment requires a separately authorized network choice, security/content review, deployer and fee preflight, unsigned preview and final signing authorization.
The project’s X account is not assigned. No ecosystem account is substituted, and no investment, partnership or official-chain endorsement is implied.
Keep the scope honest.
This version has one shared story. Multiple story spaces, curation and replay interfaces are possible next steps, not shipped capabilities.
The current contract is immutable, with no proxy or privileged upgrade key. A new contract version would use a separately reviewed address and an explicit migration choice; it cannot rewrite old events or quietly redirect user writes.
For now, the goal is to do one understandable thing well: continue a public story, one wallet-authored line at a time.
Explore the workspace ↗