StatryxSet
Choose a short text. A changed status replaces your current message and advances its revision.
A short signal. A clear owner.
Stay Current
Set, revise or clear your own public wallet status.
One current text, not a conversation.
Original video unavailable. Its original-frame poster remains visible.
The smallest useful update
One wallet.
One current status.
Statryx gives a wallet a short public status it can update itself. A simple way to keep one text current, without turning every change into a post, a thread or a message.
The current message, update time and revision belong to that wallet's state. The author is always the transaction sender—not an identity typed into a form.
“Reviewing the build.”
A short text chosen by the wallet. Not verified availability, proof of activity or a promise of delivery.
A simple lifecycle
Set it. Revise it.
Clear it when you choose.
Revise
Use the same action for the next text. Sending the exact current value is rejected as no change.
Clear
An empty string clears your current message. It does not erase the earlier public events or reset the revision.
A real boundary, not a headline trick
Small in bytes.
Not just characters.
140UTF-8 bytes maximum
A letter, a Chinese character and an emoji can take different amounts of space. The independent status page counts the actual UTF-8 bytes before you review.
- 140 ASCII letters
- 140 bytes · fits
- 46 copies of “界”
- 138 bytes · fits
- 47 copies of “界”
- 141 bytes · too long
Own the text. Know its limits.
A public signal.
Not a private note.
The useful part is deliberately narrow. The boundaries should be just as clear.
Only your own state
There is no administrator or substitute-author method to edit another wallet's status.
No identity guarantee
A status does not verify a person, a real-world activity, availability or the truth of its text.
Public history remains
Clearing the current message does not make earlier public events private or remove third-party copies.
Network Gas only
No payment, token approval, fee collection or reward. A future deployed update consumes native network Gas.
Before you write
Clear enough
to decide.
Can I update onchain in this Demo?
No public network, contract address or verified runtime is configured. Real reads, Gas estimates and writes stay disabled. The separate status page offers clearly labelled page-memory practice instead.
Does connecting my wallet publish a status?
No. Connecting requests a public account only. A future update needs a separate exact-message review and wallet confirmation. The homepage never contains an editor.
Why is sending the same text rejected?
The contract records a change. The exact same current message—including an already-empty status—does not change state and is rejected.
What might come next?
A separately reviewed deployment and optional read-only history. There is no feed, messenger, notification backend, availability verification or private storage running now.
Keep the update small
Your next status.
Your own words.
Try the mechanics locally and inspect the prepared boundary.
No public transaction is available.
