News
Sierpe 1.5.2 — where it runs, and two fixes that widen the answer
We set out to answer one question: if you hand the site to someone who needs an indexer, where can they actually put it? The result is a new page, Where it runs, covering app platforms, the three hyperscalers, serverless (no), self-hosted from Kubernetes to a Raspberry Pi, and twenty-five Postgres providers — each with a verdict and the one setting that matters.
Sierpe 1.5.1 — a stalled backfill and a wolf-crying warning
Found by watching a real backfill on a real deployment, minutes after
1.5.0 shipped: the walk stopped 570 ledgers short of the data its
operator was waiting for, retrying the same request every 40 seconds,
logging unexpected end of JSON input forever.
Sierpe 1.5.0 — movements, and coverage that names its kind
This release started as a user question: “I sent 100 USDC and 69 XLM to my escrow and they do not show up — and I do not want to register Circle’s USDC contract just to see my own deposits.”
He was right to expect them and right to refuse the workaround. A payment
to a contract is emitted by the asset’s SAC, so transfers — which
attributes rows to the emitter — can never answer “what came into my
contract”. That is a different question, and 1.5.0 adds the resource that
answers it.
Sierpe 1.4.1 and 1.4.2 — fixes from the first real deployment
The first Basic-Auth deployment on a public domain found two bugs within an hour of going live. Both are the kind no test suite catches, because both live in the seams between the app and the world around it.
Sierpe 1.4.0 — Basic Auth for public deployments
Sierpe’s default deployment shape is private networking: no public domain, your backend reaching the instance over your platform’s internal network. That is the RabbitMQ rule of thumb — management surfaces do not face the internet — and it stays the recommendation.
Sierpe 1.3.0 — the appliance grows a face
An appliance you can only talk to with curl is only half an appliance. 1.3.0 adds a management interface — and keeps it as boring to deploy as the rest of the server.
Sierpe 1.2.0 — history below the retention wall
Stellar RPCs retain about seven days of events. Until now, Sierpe stopped at that wall and recorded what it could not reach as a declared gap. In 1.2.0 it goes through the wall.
Sierpe 1.1.0 — token transfers and trustlines
Sierpe 1.1.0 adds two data kinds beyond events and contract state, both under the same honesty contract as the rest of the API.
Sierpe 1.0.0 released
The first public release of Sierpe is out. Milestones M0 through M3 are complete and verified live against the Stellar testnet.