<oembed><type>rich</type><version>1.0</version><title>nomadshiba⚡⚡ wrote</title><author_name>nomadshiba⚡⚡ (npub1gk…sppqk)</author_name><author_url>https://yabu.me/npub1gkp4cdh5rktehjqjnqc09awey4302dpadlka6mes4fu5spes7fhqfsppqk</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>that&#39;s not running kaspa, it just a peeking node/relay.&#xA;&#xA;so you&#39;re trusting a handful of full real nodes for the entire history of the chain, since your pruned node doesn&#39;t replay anything.&#xA;&#xA;it just accepts a UTXO snapshot. if those archival nodes lie, you can&#39;t detect it if you weren&#39;t listening during that time.&#xA;&#xA;and if the ~317 node operators wanted to change the rules, what stops them? you just had a hard fork last month that the whole community &#34;smoothly&#34; complied with, and the installer you linked auto-updates itself. that&#39;s not a decentralized consensus, that&#39;s a dev team with a release schedule.&#xA;&#xA;also curious what the bandwidth looks like at 100 bps, since you&#39;re already throttled to 9 peers just to make 10 bps manageable on normal hardware.&#xA;&#xA;it sounds like another high-throughput-first crypto project, but with the illusion of node running.</html></oembed>