Authors & Reviewers
Who writes, verifies, and maintains Solana content on SwapKing. Every page on this site has a defined owner.
Why this page exists
Search engines and readers both need to know who is behind a website that touches on finance. This page lists the roles responsible for producing and maintaining SwapKing content. It is not a list of bylines with photos — it is a list of functional responsibilities so that if something on the site is wrong, you know which role to contact and what that role controls.
SwapKing is a small operation. Instead of dozens of named writers, we operate three functional desks, each with a defined scope. Content passes through at least two of them before publication. If you want to know how a page was produced, see the Editorial Policy. If you want to know what we mean when we say "best rate" or "under 2 seconds," see the Methodology page.
1. Lead Analyst
Scope: Market data, quote methodology, routing behavior, and all numeric claims on the site.
Owns: The Methodology page, all liquidity notes and slippage guidance on pair pages, all quantitative claims about Solana DEX routing, and the price/liquidity data displayed in the swap widget.
Responsibility: Ensure every numeric claim on SwapKing is either (a) sourced from a named third-party data provider at the time of publication, or (b) explicitly labeled as an estimate with a stated method. The Lead Analyst is also responsible for removing outdated numbers when they no longer reflect current Solana market conditions.
Contact: [email protected] with the subject line "Data correction."
2. Security Researcher
Scope: The Security page, the Status page, the How Swap Works explainer, and all guide content relating to wallet safety, scam tokens, honeypots, and rug pulls.
Responsibility: Review any security-relevant claim before publication. Maintain the incident history on the Status page. Triage incoming security reports at [email protected]. When a third-party Solana dependency degrades, the Security Researcher updates the Status page and coordinates with the Lead Analyst on any user-facing warning.
Contact: [email protected].
3. Technical Editor
Scope: Accuracy of Solana terminology, SPL mint addresses, and internal linking across the site.
Responsibility: Before any page is published, the Technical Editor verifies that: every SPL mint address quoted matches a live Solana account; every Solana DEX named on the page currently operates; every internal link resolves to a live URL; the language used for "authority," "freeze authority," "mint authority," "slippage," "price impact," and similar terms matches the definitions on the Methodology page.
Contact: [email protected] with the subject line "Content correction."
What every page passes through
Before publication, each page on SwapKing is reviewed against the following checklist:
- Factual accuracy. Every number, every mint address, every DEX name is verified against a live source.
- No absolute claims. The page does not use the words "safe," "best," "guaranteed," or "risk-free" without a stated scope and method.
- No financial advice. The page does not recommend buying, selling, or holding any token.
- No predictions. The page does not forecast prices or market direction.
- Consistent definitions. Any term that also appears on the Methodology page uses the same definition.
- Working internal links. Every link resolves to a live URL on this domain.
- No external solicitations. The page does not direct users to social media, paid services, or third-party offers.
What we do not claim
SwapKing does not employ a newsroom. We do not have on-the-ground reporters. We do not have a research department that publishes long-form investigative pieces. What we do have is a narrow, defined scope: explain how non-custodial Solana swaps work, publish live rates, and route SPL token swaps through the deepest available liquidity. Our content exists to support that scope. Anything outside it — price predictions, token ratings, market forecasts — is outside our remit and is not published.
Corrections
If you find an error on any page, write to [email protected] with the URL and a short description. Substantive corrections are made on the page and logged on the Editorial Policy page. Minor copy edits are not logged.
Related
Editorial Policy · Methodology · Security · Status · About