-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathabout.html
More file actions
219 lines (211 loc) · 11.4 KB
/
Copy pathabout.html
File metadata and controls
219 lines (211 loc) · 11.4 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>About & Editorial Policy | Kaspa Explained</title>
<meta name="description" content="About Kaspa Explained: editorial policy, source weighting, corrections, disclosures, and what the site refuses to cover.">
<meta name="robots" content="index,follow,max-snippet:-1,max-image-preview:large">
<link rel="canonical" href="https://kaspaexplained.com/about">
<link rel="icon" href="kaspa-favicon.svg?v=20260512-real-k" type="image/svg+xml">
<link rel="icon" href="favicon.svg?v=20260512-k4" type="image/svg+xml">
<link rel="icon" href="favicon.ico" sizes="any">
<link rel="icon" href="favicon.png" type="image/png">
<link rel="apple-touch-icon" href="apple-touch-icon.png">
<link rel="manifest" href="site.webmanifest">
<meta name="application-name" content="Kaspa Explained">
<meta name="apple-mobile-web-app-title" content="Kaspa Explained">
<meta name="theme-color" content="#09090b">
<meta property="og:title" content="About & Editorial Policy | Kaspa Explained">
<meta property="og:description" content="How Kaspa Explained handles source weighting, corrections, disclosures, and status-sensitive claims.">
<meta property="og:type" content="article">
<meta property="og:url" content="https://kaspaexplained.com/about">
<meta property="og:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
<meta property="og:image:type" content="image/png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Kaspa Explained - proof-of-work blockDAG guide">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="About & Editorial Policy | Kaspa Explained">
<meta name="twitter:description" content="How Kaspa Explained handles source weighting, corrections, disclosures, and status-sensitive claims.">
<meta name="twitter:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
<meta name="dateModified" content="2026-06-25">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "AboutPage",
"name": "About & Editorial Policy",
"url": "https://kaspaexplained.com/about",
"dateModified": "2026-06-25",
"description": "How Kaspa Explained handles source weighting, corrections, disclosures, and status-sensitive claims."
}
</script>
<link rel="stylesheet" href="styles.css?v=20260627-next-card-fix">
<script defer src="nav.js?v=20260606-anchor-clearance"></script>
</head>
<body>
<a class="skip-link" href="#top">Skip to content</a>
<header class="site-header">
<nav class="nav" aria-label="Primary">
<a class="brand" href="/" aria-label="Kaspa Explained home">
<span class="brand-mark" aria-hidden="true"></span>
Kaspa Explained
</a>
<button class="nav-menu-button" type="button" aria-expanded="false" aria-controls="primary-links">Menu</button>
<div id="primary-links" class="nav-links">
<a href="/what-is-kaspa">What is Kaspa</a>
<a href="/status">Live now</a>
<a href="/kaspa-claims-checker">Check claims</a>
<a href="/skeptical-case">Risks</a>
<a href="/build-on-kaspa">Build</a>
<a href="/sources">Sources</a>
</div>
<button class="theme-toggle" type="button" aria-label="Switch theme">Light</button>
<a class="nav-cta" href="/toccata-status">Toccata status</a>
</nav>
</header>
<main id="top" tabindex="-1" class="sources-page">
<section class="sources-hero section">
<p class="eyebrow">Editorial policy</p>
<h1>About Kaspa Explained</h1>
<p class="lead">Kaspa Explained is an independent Kaspa explainer that separates network status, technical claims, risks, and sources. It does not publish price targets or exchange rumors.</p>
</section>
<section class="section">
<p class="eyebrow">Method</p>
<h2>How the site works</h2>
<div class="method-strip">
<article>
<span>Who</span>
<p>Kaspa Explained is independently maintained. It covers protocol status, tradeoffs, and context with source links.</p>
</article>
<article>
<span>How</span>
<p>Updates start from the strongest available source for the claim: code, releases, KIPs, research papers, protocol docs, and direct technical context before public summaries or social posts.</p>
</article>
<article>
<span>Why</span>
<p>The site exists to make Kaspa understandable without treating targeted upgrades, roadmap architecture, research, or community expectations as shipped network behavior.</p>
</article>
</div>
<div class="actions">
<a class="button primary" href="/sources">Open source hierarchy</a>
<a class="button" href="/claims-reference">Claims reference</a>
<a class="button" href="/kaspa-claims-checker">Check a claim</a>
</div>
</section>
<section class="section">
<p class="eyebrow">Disclosure</p>
<h2>Maintainer and conflicts</h2>
<p>This site is independently maintained and Kaspa-focused. It has no official Kaspa role and provides no wallet, exchange, mining, price-target, or paid-promotion service.</p>
<p>The maintainer may hold KAS or use Kaspa-related tools. The site publishes editorial research. Status-sensitive claims should still be checked against primary sources before publication, investment, or production decisions.</p>
</section>
<section class="section">
<p class="eyebrow">Editorial policy</p>
<h2>What the site does</h2>
<div class="reference-grid">
<article>
<h3>Explain, then label status</h3>
<p>Kaspa ideas are separated into what works now, what is targeted, what is roadmap, and what is research. That distinction keeps future architecture separate from shipped software.</p>
</article>
<article>
<h3>Match sources to claims</h3>
<p>Code, releases, KIPs, research papers, protocol documentation, and direct technical posts carry shipped-feature claims. Community articles, interviews, learning libraries, and X posts provide context but weaker evidence for activation status.</p>
</article>
<article>
<h3>Keep crypto in its lane</h3>
<p>The site does not argue that blockchains fix every database, payment, legal, privacy, or real-world verification problem. Kaspa is evaluated where people need one shared record without one operator controlling it.</p>
</article>
</div>
</section>
<section id="corrections" class="section">
<p class="eyebrow">Corrections</p>
<h2>Corrections</h2>
<p>If a status claim is wrong or stale, the correction should update both the visible page and the source list. When the correction changes the reader's decision, the page should say what changed.</p>
<div class="reference-grid">
<article>
<h3>Highest priority</h3>
<p>Wrong live/roadmap/research status, wrong activation timing, broken source hierarchy, or wording that implies investment advice.</p>
</article>
<article>
<h3>Normal priority</h3>
<p>Broken links, unclear explanations, stale comparison wording, glossary gaps, missing cross-links, or diagrams that could be clearer.</p>
</article>
<article>
<h3>Request path</h3>
<p>Open a correction issue with the page URL, exact claim, better source, and wording that should change.</p>
</article>
</div>
<div class="actions">
<a class="button primary" href="https://github.com/parker2017code/kaspa-explained/issues/new?template=stale-claim.yml">Open correction issue</a>
<a class="button" href="/sources">Open sources</a>
</div>
</section>
<section class="section">
<p class="eyebrow">Disclosures</p>
<h2>Boundaries</h2>
<ul class="limit-list">
<li>Not an official Kaspa website.</li>
<li>Not financial, investment, legal, tax, or trading advice.</li>
<li>Not a price target, exchange-listing tracker, or market-timing guide.</li>
<li>Not a claim that every roadmap item will ship or attract users.</li>
<li>Not a substitute for reading primary technical sources before making status-sensitive claims.</li>
</ul>
</section>
<section class="next-step section" aria-label="Suggested next step">
<p class="eyebrow">Next step</p>
<h2>Where to go next</h2>
<p>Use status for shipped-vs-roadmap claims, sources for evidence weight, or Start Here when the reader needs the full crypto foundation first.</p>
<div class="actions">
<a class="button primary" href="/status">Open status</a>
<a class="button" href="/sources">Open sources</a>
<a class="button" href="/start-here">Start here</a>
</div>
</section>
<!-- related-links:start -->
<section class="section site-related" aria-labelledby="related-links-title">
<p class="eyebrow">Keep reading</p>
<h2 id="related-links-title">Next pages</h2>
<div class="site-related-grid">
<a href="/ai-guidance"><span>Previous</span><strong>Ask about Kaspa with sources</strong><p>Open ChatGPT, Claude, Perplexity, or Grok with a Kaspa prompt that checks sources, status labels, and unsupported claims.</p></a>
<a href="/status"><span>Status</span><strong>Kaspa current status</strong><p>A compact status page for Kaspa: what is live, what is targeted, what is roadmap, what remains research, and which common claims need context.</p></a>
<a href="/sources"><span>Sources</span><strong>Sources for Kaspa Explained</strong><p>Source hierarchy, public reference map, and credited external learning resources used by Kaspa Explained.</p></a>
</div>
</section>
<!-- related-links:end -->
</main>
<footer class="footer">
<div class="footer-grid">
<p><strong>Independent Kaspa explainer.</strong> Claims are labeled live, targeted, roadmap, research, unsupported, or wrong. Not investment advice.</p>
<nav class="footer-nav-groups" aria-label="Footer">
<div class="footer-link-group" aria-label="Learn">
<span>Learn</span>
<a href="/start-here">Start here</a>
<a href="/what-is-kaspa">Kaspa 101</a>
<a href="/overview">90-second overview</a>
<a href="/glossary">Glossary</a>
</div>
<div class="footer-link-group" aria-label="Verify">
<span>Verify</span>
<a href="/status">Status</a>
<a href="/kaspa-claims-checker">Claims checker</a>
<a href="/toccata-status">Toccata status</a>
<a href="/skeptical-case">Skeptical case</a>
<a href="/sources">Sources</a>
</div>
<div class="footer-link-group" aria-label="Build">
<span>Build</span>
<a href="/build-on-kaspa">Build on Kaspa</a>
<a href="/builder-guide">Builder guide</a>
<a href="/kaspa-app-ideas">App ideas</a>
</div>
<div class="footer-link-group" aria-label="Site">
<span>Site</span>
<a href="/search">Search</a>
<a href="/about">About</a>
<a href="/about#corrections">Corrections</a>
</div>
</nav>
</div>
</footer>
</body>
</html>