<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>News on Sierpe</title>
		<link>https://sierpe-web.vercel.app/news/</link>
		<description>Recent content in News on Sierpe</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 21 Aug 2026 22:30:00 +0000</lastBuildDate>
		
			<atom:link href="https://sierpe-web.vercel.app/news/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Sierpe 1.5.2 — where it runs, and two fixes that widen the answer</title>
				<link>https://sierpe-web.vercel.app/news/sierpe-1-5-2-released/</link>
				<pubDate>Fri, 21 Aug 2026 22:30:00 +0000</pubDate>
				<guid>https://sierpe-web.vercel.app/news/sierpe-1-5-2-released/</guid>
				<description>&lt;p&gt;We set out to answer one question: if you hand the site to someone who&#xA;needs an indexer, where can they actually put it? The result is a new&#xA;page, &lt;a href=&#34;https://sierpe-web.vercel.app/docs/platforms/&#34;&gt;Where it runs&lt;/a&gt;, covering app platforms, the&#xA;three hyperscalers, serverless (no), self-hosted from Kubernetes to a&#xA;Raspberry Pi, and twenty-five Postgres providers — each with a verdict&#xA;and the one setting that matters.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Sierpe 1.5.1 — a stalled backfill and a wolf-crying warning</title>
				<link>https://sierpe-web.vercel.app/news/sierpe-1-5-1-released/</link>
				<pubDate>Fri, 21 Aug 2026 20:00:00 +0000</pubDate>
				<guid>https://sierpe-web.vercel.app/news/sierpe-1-5-1-released/</guid>
				<description>&lt;p&gt;Found by watching a real backfill on a real deployment, minutes after&#xA;1.5.0 shipped: the walk stopped 570 ledgers short of the data its&#xA;operator was waiting for, retrying the same request every 40 seconds,&#xA;logging &lt;code&gt;unexpected end of JSON input&lt;/code&gt; forever.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Sierpe 1.5.0 — movements, and coverage that names its kind</title>
				<link>https://sierpe-web.vercel.app/news/sierpe-1-5-0-released/</link>
				<pubDate>Fri, 21 Aug 2026 18:00:00 +0000</pubDate>
				<guid>https://sierpe-web.vercel.app/news/sierpe-1-5-0-released/</guid>
				<description>&lt;p&gt;This release started as a user question: &lt;em&gt;&amp;ldquo;I sent 100 USDC and 69 XLM to&#xA;my escrow and they do not show up — and I do not want to register&#xA;Circle&amp;rsquo;s USDC contract just to see my own deposits.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;He was right to expect them and right to refuse the workaround. A payment&#xA;to a contract is emitted by the &lt;strong&gt;asset&amp;rsquo;s&lt;/strong&gt; SAC, so &lt;code&gt;transfers&lt;/code&gt; — which&#xA;attributes rows to the emitter — can never answer &amp;ldquo;what came into my&#xA;contract&amp;rdquo;. That is a different question, and 1.5.0 adds the resource that&#xA;answers it.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Sierpe 1.4.1 and 1.4.2 — fixes from the first real deployment</title>
				<link>https://sierpe-web.vercel.app/news/sierpe-1-4-1-and-1-4-2-released/</link>
				<pubDate>Thu, 20 Aug 2026 23:30:00 +0000</pubDate>
				<guid>https://sierpe-web.vercel.app/news/sierpe-1-4-1-and-1-4-2-released/</guid>
				<description>&lt;p&gt;The first Basic-Auth deployment on a public domain found two bugs within&#xA;an hour of going live. Both are the kind no test suite catches, because&#xA;both live in the seams between the app and the world around it.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Sierpe 1.4.0 — Basic Auth for public deployments</title>
				<link>https://sierpe-web.vercel.app/news/sierpe-1-4-0-released/</link>
				<pubDate>Thu, 20 Aug 2026 22:40:00 +0000</pubDate>
				<guid>https://sierpe-web.vercel.app/news/sierpe-1-4-0-released/</guid>
				<description>&lt;p&gt;Sierpe&amp;rsquo;s default deployment shape is private networking: no public&#xA;domain, your backend reaching the instance over your platform&amp;rsquo;s internal&#xA;network. That is the RabbitMQ rule of thumb — management surfaces do not&#xA;face the internet — and it stays the recommendation.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Sierpe 1.3.0 — the appliance grows a face</title>
				<link>https://sierpe-web.vercel.app/news/sierpe-1-3-0-released/</link>
				<pubDate>Thu, 20 Aug 2026 22:00:00 +0000</pubDate>
				<guid>https://sierpe-web.vercel.app/news/sierpe-1-3-0-released/</guid>
				<description>&lt;p&gt;An appliance you can only talk to with curl is only half an appliance.&#xA;1.3.0 adds a management interface — and keeps it as boring to deploy as&#xA;the rest of the server.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Sierpe 1.2.0 — history below the retention wall</title>
				<link>https://sierpe-web.vercel.app/news/sierpe-1-2-0-released/</link>
				<pubDate>Thu, 20 Aug 2026 21:00:00 +0000</pubDate>
				<guid>https://sierpe-web.vercel.app/news/sierpe-1-2-0-released/</guid>
				<description>&lt;p&gt;Stellar RPCs retain about seven days of events. Until now, Sierpe stopped&#xA;at that wall and recorded what it could not reach as a declared gap. In&#xA;1.2.0 it goes through the wall.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Sierpe 1.1.0 — token transfers and trustlines</title>
				<link>https://sierpe-web.vercel.app/news/sierpe-1-1-0-released/</link>
				<pubDate>Thu, 20 Aug 2026 19:00:00 +0000</pubDate>
				<guid>https://sierpe-web.vercel.app/news/sierpe-1-1-0-released/</guid>
				<description>&lt;p&gt;Sierpe 1.1.0 adds two data kinds beyond events and contract state, both&#xA;under the same honesty contract as the rest of the API.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Sierpe 1.0.0 released</title>
				<link>https://sierpe-web.vercel.app/news/sierpe-1-0-0-released/</link>
				<pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://sierpe-web.vercel.app/news/sierpe-1-0-0-released/</guid>
				<description>&lt;p&gt;The first public release of Sierpe is out. Milestones M0 through M3 are&#xA;complete and verified live against the Stellar testnet.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
