Choose one response
Each wallet has one current reaction per content key. Repeating the same choice changes nothing and is rejected.
One reference.
One current reaction.
ECHORYN SIGNALS
Give a public discussion a lightweight response. Choose a reaction, replace it, or remove your own—without payments, rewards or financial voting.
The space between reading and replying
Sometimes a small response is enough.
Echoryn records a wallet’s current reaction to a public content key. It gives a discussion a compact response layer without turning it into a token economy.
It does not read the article, validate the claim, rank the author, or decide what is true. Your reaction is your signal—not an endorsement by a system.
Understand the modelA fixed vocabulary, not a score
These are the interface labels for the six fixed reaction values. No reaction carries more weight, rewards or financial rights.
A choice that stays yours
Each wallet has one current reaction per content key. Repeating the same choice changes nothing and is rejected.
Changing your reaction decrements its old tally and increments the new one. It is not an extra vote.
Only your wallet’s current reaction is cleared. Other wallets’ responses remain. Public transaction history is not erased.
A reference, not a content reader
Use a public 32-byte content key. The local interface can also derive a SHA-256 key from a public HTTPS link, entirely in your browser.
No article is fetched or checked. Known links can be guessed and hashed again; a content key is not encryption or a privacy guarantee.
Try a public referenceWhere a little signal helps
Make room for lightweight responses beside a proposal’s real discussion. A tally is not governance or an approval result.
Show curiosity or concern without pretending that a reaction verifies evidence or scientific quality.
React to a shared reference while keeping comments, revisions and moderation in the tools that already handle them.
Public and limited by design
A person may control multiple wallets. Counts describe wallet-level responses, not unique humans, truth, reputation or community consensus.
Content keys, reaction choices and author wallets would be public on a deployed network. There is no payment, custody, token, reward, administrator or moderation layer in this contract.
Today the interface is a local Demo. Public reads and writes stay disabled until a separately reviewed deployment is configured. Future writes would consume native network gas.
Before you react
No. A link is only a local reference used to derive its key. The page does not fetch, summarize, scan or validate its content.
Yes. Reacting with a different fixed value replaces your current response. Removing clears only your own current reaction, not public history.
Yes. The independent reaction page has an in-memory local practice with clearly labelled roles and tallies. It does not sign, spend gas or broadcast.
The project-specific contract and local tests are prepared. A selected network, gas review and separate deployment authorization are needed before public-chain use. No token or launch timing is promised.
Separate functional page. No wallet needed for local practice.