<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Beginner on Xing Ge Science Blog</title><link>https://blog.xinster.com/en/tags/beginner/</link><description>Recent content in Beginner on Xing Ge Science Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 08 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.xinster.com/en/tags/beginner/index.xml" rel="self" type="application/rss+xml"/><item><title>What Exactly Is a Blockchain? A Shared Public Ledger</title><link>https://blog.xinster.com/en/posts/web3/blockchain-101/</link><pubDate>Sat, 08 Aug 2026 00:00:00 +0000</pubDate><guid>https://blog.xinster.com/en/posts/web3/blockchain-101/</guid><description>In one line: a blockchain is a public ledger that everyone maintains together and no one can secretly tamper with.</description><content:encoded><![CDATA[<h2 id="the-bottom-line">The bottom line</h2>
<p>A blockchain is essentially a public, decentralized, extremely hard-to-tamper ledger. Think of it as a ledger book placed in a town square: everyone holds a copy; if someone wants to record an entry, most people must approve it, and once recorded, secretly changing it is nearly impossible.</p>
<h2 id="understanding-it-through-everyday-life">Understanding it through everyday life</h2>
<p>Imagine a village&rsquo;s bookkeeping:
Traditionally the village chief kept the books alone — whatever he wrote stood. That&rsquo;s centralization. If the chief erred, or was bribed to alter records, no one could challenge him.</p>
<p>Blockchain changes the game:</p>
<ol>
<li><strong>Everyone has a copy of the ledger</strong> — one posted at the bookkeeping office door, one in every household&rsquo;s drawer.</li>
<li><strong>Recording must be public</strong> — to record &ldquo;Zhang gave Li 10 yuan,&rdquo; you must announce it; the whole village checks, and only after confirming does each write it in their own copy.</li>
<li><strong>Pages are bound in order</strong> — the bottom of each page prints the &ldquo;fingerprint&rdquo; (hash) of the previous page. Try to alter one page and every page after it stops matching — you&rsquo;re caught instantly.</li>
</ol>
<p>These three together are the core mechanism of blockchain: distributed ledger + consensus + hash chain.</p>
<h2 id="what-problem-it-solves">What problem it solves</h2>
<p>Traditional trust relies on &ldquo;authority endorsement&rdquo; (banks, governments, platforms). Blockchain moves trust onto math and rules. As long as most participants are honest, the ledger is trustworthy — no need to know who the village chief is.</p>
<p>The cost is obvious too: slow, expensive, redundant storage. So it&rsquo;s unsuited to high-frequency micro-records like &ldquo;bought a bottle of water at the supermarket today,&rdquo; but ideal for records needing strong trust: asset ownership, contracts, provenance.</p>
<h2 id="in-one-line">In one line</h2>
<p>A blockchain = a public ledger anyone can read but no one can secretly alter. It isn&rsquo;t magic; what&rsquo;s magic is that it made &ldquo;strangers collaborating without trusting each other&rdquo; possible at scale for the first time.</p>
]]></content:encoded></item><item><title>Why Can LLMs "Talk"? Starting With a Word-Guessing Game</title><link>https://blog.xinster.com/en/posts/ai/llm-explained/</link><pubDate>Sat, 08 Aug 2026 00:00:00 +0000</pubDate><guid>https://blog.xinster.com/en/posts/ai/llm-explained/</guid><description>The essence of a large model is a machine fed massive text that is extremely good at playing &amp;#34;word chain.&amp;#34;</description><content:encoded><![CDATA[<h2 id="the-bottom-line">The bottom line</h2>
<p>A large model (like the GPT behind ChatGPT) is essentially a machine extremely good at playing &ldquo;word chain&rdquo;: give it an opening, it predicts the most likely next word based on &ldquo;experience,&rdquo; then the next&hellip; until a full answer forms. Its &ldquo;experience&rdquo; comes from the massive human text it has read.</p>
<h2 id="understanding-it-through-everyday-life">Understanding it through everyday life</h2>
<p>Imagine a child who read a hundred thousand books. You give them an opener: &ldquo;The weather is nice today, let&rsquo;s go to the park,&rdquo; and they&rsquo;ll most likely continue with &ldquo;for a walk&rdquo; or &ldquo;to play&rdquo; — because that&rsquo;s the most common pairing in the books they&rsquo;ve read.</p>
<p>A large model does exactly the same — just at staggering scale:</p>
<ul>
<li>The books it read: nearly the entire public internet (Wikipedia, papers, books, code&hellip;).</li>
<li>Its &ldquo;word-chain&rdquo; skill: not rote memorization, but learning the statistical patterns and deep structures between words.</li>
<li>Parameters: hundreds of billions of tunable knobs that together decide how the &ldquo;next word&rdquo; is chosen.</li>
</ul>
<h2 id="why-it-seems-to-understand">Why it seems to &ldquo;understand&rdquo;</h2>
<p>Play word-chain well enough and the illusion of &ldquo;understanding&rdquo; emerges — no, more precisely, genuine capability emerges: it can translate, write code, reason. Like a Go AI that only learned &ldquo;which move wins&rdquo; but ended up &ldquo;knowing&rdquo; Go.</p>
<p>But it has three essential limitations:</p>
<ol>
<li>It confidently makes things up (hallucination): it is never responsible for &ldquo;facts,&rdquo; only for &ldquo;plausibility.&rdquo;</li>
<li>Its knowledge has a cutoff date: it only knows what it read, not what happened after.</li>
<li>It doesn&rsquo;t truly &ldquo;think&rdquo;: no goals, no intent — it just computes the most reasonable continuation given an opener.</li>
</ol>
<h2 id="in-one-line">In one line</h2>
<p>A large model = a machine that read the entire web, pushed word-guessing to the extreme, and thereby gave rise to understanding and creativity. Used well, it&rsquo;s productivity; but know this: it never guarantees what it says is true.</p>
]]></content:encoded></item></channel></rss>