Who reviews the Zelcore Academy, what a review checks, how often it happens, and how we handle corrections.
The Zelcore Academy publishes guidance about money: how to hold it, how to avoid losing it, and what the rules say. Advice like that is worth only as much as the process behind it, so this page describes that process in enough detail that you can hold us to it.
It covers who reviews our articles, what a review actually checks, how often it happens, and what we do when we get something wrong. It applies to every article in the Academy and every post in the Newsroom.
Reviews are carried out by the InFlux Technologies editorial team and attributed by role rather than by name. Four roles cover the subject areas we publish in, and each one signs off only within its own scope.
Security Editor — seed phrases and key management, phishing and approval scams, hardware wallets, and anything written in response to an incident.
Regulation Editor — MiCA, the GENIUS Act, travel-rule obligations, exchange listing rules, and tax treatment.
DeFi Editor — staking and yield, swaps and bridges, tokenised assets, and the risks specific to each.
Wallet & Product Editor — how-to walkthroughs, coin and chain guides, and any description of how Zelcore itself behaves.
A byline is only a trust signal if the person behind it is accountable and findable. Rather than attach a name to work it does not fully describe, we publish the role that reviewed the piece and the organisation that stands behind it: InFlux Technologies, the company that also builds the Flux network. If you need to reach the person responsible for a specific article, write to us and we will route it to the editor who signed it off.
A review is not a proofread. An editor re-reads the article against its sources and against the current state of the product and the rules, and works through the same seven checks every time.
Every claim carrying a date, a number or a rule is re-checked against the primary source it cites — not against a secondary summary of it.
Every outbound link still resolves, and still points at what the article says it points at.
Product details match the current Zelcore release: platform availability, feature names, fee behaviour. Features that exist on one platform and not another are described as such.
Rules named in the article are still in force, in the jurisdictions the article names.
No security guidance has been superseded — a practice that was sound a year ago sometimes is not.
The standing disclaimer on the article is still the right one for its subject.
Internal links still resolve, the pillar the article belongs to still links back to it, and nothing points at a slug that has since moved.
Review frequency follows the subject, because regulation and security age faster than a chain explainer does.
Regulation and tax: every six months, or within fourteen days of a rule change we have covered.
Security: every six months, or immediately after an incident that affects the advice given.
DeFi: every twelve months.
Everything else: every twelve months.
Any article, at any time: when a reader reports an error.
A published cadence is a promise, and promises about process are easy to make and easy to quietly drop. Ours is backed by a report that lists every article past its review window, grouped by the role responsible, so an overdue piece is visible rather than forgotten. An article that has never been reviewed counts as overdue from the day it is published.
Each article carries a date at the top, and the wording of that line is deliberate.
"Last updated" means the article was edited on that date. It does not claim that anyone re-read the whole piece against its sources.
"Last reviewed by the Security Editor" — or whichever role applies — means an editor completed the full pass described above and signed off on it.
Most of the academy currently says "last updated", because we began recording review sign-off in September 2026 and are working through the archive by cadence, oldest and highest-risk first. We would rather show you an honest edit date than imply a review that did not happen.
We publish daily, and some of what we publish will be wrong. What matters is what happens next.
Report an error to [email protected]. Quoting the sentence helps.
Factual errors are corrected within five business days of us confirming them, and sooner when the error could cost a reader money.
A material correction — one that changes the advice, the facts or the conclusion — is noted at the foot of the article with its date. We do not silently rewrite a piece and leave it looking as though it always said the new thing.
Typographical fixes, formatting and link repairs are made without a note.
If we cannot verify a reported error, we say so rather than leaving the report unanswered.
These are the rules an article meets once it has been through a review pass. Much of the existing archive was written without inline citations and does not meet them yet; adding sources is part of what a review pass does, which is why we work through the backlog by risk rather than all at once.
Regulation is cited to the text of the regulation or the regulator, not to a news report about it.
Security incidents are cited to the disclosing party, the affected project, or an on-chain record that a reader can check.
Where a number changes over time — a fee, a supported-asset count, a block time — the article says when it was accurate.
We do not describe Zelcore as audited, open-source or used by a particular number of people, because those are claims we are not in a position to substantiate. Where a security property matters, we describe the mechanism instead.
Hardware wallet support is always described per platform, because Ledger and Trezor pairing is a desktop feature and a reader acting on a phone would otherwise be misled.
Nothing in the Academy is financial, investment, legal or tax advice, and no article should be read as a recommendation to buy, sell or hold anything. Articles covering regulation, tax, security and DeFi carry a standing notice to that effect, shown above the body of the piece.
Zelcore is a self-custody wallet: we never hold your keys and cannot recover an account, reverse a transaction or see your balance. Our support team will never ask for your seed phrase, and no article will ever ask you to enter it anywhere but your own wallet.
