2026-10-11T09:16:42Zhttps://njump.cloud.vinney.xyzNostr notes by routstr-scoutroutstr-scouthttps://njump.cloud.vinney.xyz/npub146gy6z5fw287qezekcug9ezvny8qtnqa9c5zch5afw5xp4m25vas6k4x0chttps://cypherpunk.today/static/routstr-scout/avatar.jpghttps://cypherpunk.today/static/routstr-scout/avatar.jpghttps://njump.cloud.vinney.xyz/nevent1qqs23rdhgwl7fvu9g8anctlxyk6tjc9g5suselhm5npt0k0vxctakvszyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkycxxrcRoutstr probe: ai.redsh1ft.com took a 32-sat Cashu token, ...
Routstr probe: ai.redsh1ft.com took a 32-sat Cashu token, returned neither an answer nor change, and the mint reports the token spent. One observation so far, not a verdict; if it happens again the node gets an avoid review here.
2026-10-22T15:18:04Zhttps://njump.cloud.vinney.xyz/nevent1qqst9e2p3wqahkn90evv5wtf4a935me3wykdpylp9ucsexzmp6swd4szyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nk05fpxhRoutstr review: node1.routstr.blazelight.dev is now avoid - paid ...
In reply to <a href='/naddr1qpwnjdtpxvukyvphx93rqvtzxd3nqdn9vc6kzv3jvdnrqdm98yerjdejvf3ryde5xccnjwf4xymxvdfs8yenget9xgmxgc35xc6xgwtxx5axummyv5cj6un0w468xarj943xcct6v4kxjemgwskkgetkqgs2ayzdp2yh9rlqv3vmvwyzu3xfjrs9eswju2pvt6w5h2rq6a42xwcrqsqqp9serp6984'>naddr1qp…6984</a><br/>_________________________<br/><br/>Routstr review: node1.routstr.blazelight.dev is now avoid - paid requests have failed for three days or more.
2026-10-21T18:16:20Zhttps://njump.cloud.vinney.xyz/nevent1qqsq0y8s58t4eg80tqrd0lxc5xyhnex8ewh5kt763dpc8lrqvvuk0qczyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nk90txjvRoutstr review: ppq.redsh1ft.com has served correctly for three ...
In reply to <a href='/naddr1qpxnwce3xy6nxwrzv5mk2dn9xf3xzd338yunwcm9xv6nycfev56kydr98q6kyc3nxfnrydpsv3nxvefhv43kxvfsxpnrsdpkxajkzdpev5arwce3xy6nxwrzv5mk2dszyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqqfvxgmg8pu8'>naddr1qp…8pu8</a><br/>_________________________<br/><br/>Routstr review: ppq.redsh1ft.com has served correctly for three days again, review back to lgtm.
2026-10-21T00:46:45Zhttps://njump.cloud.vinney.xyz/nevent1qqsxdpsjsfdaka5hc6cnqajkw24sz3ur9q6f4ww56qkm28rlt9q0hyczyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkwecz5rRoutstr review: api.plebchat.me is now avoid - paid requests have ...
In reply to <a href='/naddr1qpxkze3kx3jnxc35vdjkgdekvcerzwrxxgenxdtzxpjrgv33v33xyvp48pjkxep38qurqdtpxs6xgcf3vyexgc33vgcnzdnpv9nr2cfjvvaxze3kx3jnxc35vdjkgdczyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqqfvxgqgs67w'>naddr1qp…s67w</a><br/>_________________________<br/><br/>Routstr review: api.plebchat.me is now avoid - paid requests have failed for three days or more.
2026-10-20T00:46:32Zhttps://njump.cloud.vinney.xyz/nevent1qqsf3xhhxgz8uu7uejrtvfnvj5nv8h3ckkvyrdtjk0vrvl9qtxtjqsqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nktxc5kpRoutstr review: roustr.nobios.ai is now avoid - paid requests ...
In reply to <a href='/naddr1qp8ngetpvccrwvp3vy6nse348y6ngcfj8psngdf4xyervc3exqcrjvpkx33r2wfnxcmrjwfn89jr2wtyxfsnsef3x5mxxdecvy6rjdtpvya8gmmjdeskgmedwfhh2ar9wgpzpt5sf59gju50upj9nd3cstjyexgwqhxp6t3g930f6jagvrtk4gemqvzqqqykry977wcw'>naddr1qp…7wcw</a><br/>_________________________<br/><br/>Routstr review: roustr.nobios.ai is now avoid - paid requests have failed for three days or more.
2026-10-17T14:46:32Zhttps://njump.cloud.vinney.xyz/nevent1qqsya7duvf68rrf7jpp4zzw4h9c7vg0zv5a6a5a6fm5uej4mmep8ntczyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nk0mckt3Routstr review: routstr.otrta.me has served correctly for three ...
In reply to <a href='/naddr1qpxnxepcxvenxce4vyengd3hvvmryc3sx56kxdejvcmkvvfexajxvvfkx9nxzctyxgcxzdfjxyukzefk8y6xzwfjxs6nwcesv56rscfhvvarxepcxvenxce4vyengdszyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqqfvxgt8fa37'>naddr1qp…fa37</a><br/>_________________________<br/><br/>Routstr review: routstr.otrta.me has served correctly for three days again, review back to lgtm.
2026-10-17T14:19:08Zhttps://njump.cloud.vinney.xyz/nevent1qqsxa8kgwefmmrs0fk7h6uv0e44kqtfxk2p7kxyqhwsmmescsp0ageczyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkvsk9tdRoutstr probe: ai.redsh1ft.com took a 32-sat Cashu token, ...
Routstr probe: ai.redsh1ft.com took a 32-sat Cashu token, returned neither an answer nor change, and the mint reports the token spent. One observation so far, not a verdict; if it happens again the node gets an avoid review here.
2026-10-16T03:24:17Zhttps://njump.cloud.vinney.xyz/nevent1qqs0jkp4xya7jwk72fug42dt3vjrjl84nawfnxzfmr6xffpq5xn46lqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkhmthdsRoutstr review: ppq.redsh1ft.com is now avoid - paid requests ...
In reply to <a href='/naddr1qpxnwce3xy6nxwrzv5mk2dn9xf3xzd338yunwcm9xv6nycfev56kydr98q6kyc3nxfnrydpsv3nxvefhv43kxvfsxpnrsdpkxajkzdpev5arwce3xy6nxwrzv5mk2dszyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqqfvxgmg8pu8'>naddr1qp…8pu8</a><br/>_________________________<br/><br/>Routstr review: ppq.redsh1ft.com is now avoid - paid requests have failed for three days or more.
2026-10-16T01:07:35Zhttps://njump.cloud.vinney.xyz/nevent1qqst7kcyh8uhn2hw4j56a0gm5j42kmzwu0lazcxypnj7xwyz5mkng6szyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nk90vz08Routstr review: routstr.rewolf.dev is now avoid - paid requests ...
In reply to <a href='/naddr1qpxnvwpexfjrzc3kvs6xgv3nx4nrjvfjv9snzwphv4nxzctrxqcrvepe8y6nswf48qmkze3j8y6njwpnxvmkywpcxdnrqepjxqckyvrzvyarvwpexfjrzc3kvs6xgvszyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqqfvxgd0xlw6'>naddr1qp…xlw6</a><br/>_________________________<br/><br/>Routstr review: routstr.rewolf.dev is now avoid - paid requests have failed for three days or more. Run by Juraj Bednar, who also operates the competing node routstr.cypherpunk.today. How the probing works:<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/naddr1qqwxsmmh946xsefdwfhh2arnw3ez6umrda6hgttswfhkyetnqyw8wumn8ghj7mn0wd68ytnr09cxsetjwp6ku6eww3hkgcteqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqq823cf2xxzg" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">naddr1qq…xxzg</a></span> </div> <p>This account is a bot. Juraj Bednar (<span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>) runs it, and he also operates a Routstr node, routstr.cypherpunk.today. So a competitor is reviewing other nodes here, and you should weigh the reviews with that in mind. Below is what the bot does.</p>
<h2 id="why-probe-at-all-2">Why probe at all</h2>
<p>A Routstr node announces itself on Nostr (kind 38421) with the models it sells and the mints it accepts. Clients pay per request with a Cashu token: they send more than the request costs, and the node hands back the rest as change.</p>
<p>The announcement doesn't tell you whether the node works. Some nodes list models whose upstream key has expired. Some answer every request with an error. A few take the token and send back neither an answer nor change, and for a client paying with bearer ecash that money is gone. You only find out by paying.</p>
<h2 id="what-one-probe-is-2">What one probe is</h2>
<ol>
<li>The scout mints a fresh 32-sat token at a mint the node accepts. Each probe gets its own token, and the node never sees anything else.</li>
<li>It sends one short, real chat completion request, paying with that token in the <code>X-Cashu</code> header, the way any client would.</li>
<li>It records what happened: an answer, an error, or nothing.</li>
<li>If the node returned change (or a refund, on an error), the scout redeems it straight away.</li>
<li>If nothing came back, it asks the mint whether the token was spent (NUT-07). Unspent means the node never charged, and the token gets used again. Spent, with no answer and no change, means the node kept it.</li>
</ol>
<p>A probe that goes well costs about 1 sat in mint fees. When a node keeps a token, we lose that one token.</p>
<h2 id="which-nodes-2">Which nodes</h2>
<p>The scout probes some of the nodes on the network, not all of them, and not on a published schedule. It only reviews nodes it has paid-probed itself, so a node with no review from this account hasn't been judged badly. It just hasn't been probed.</p>
<p>The one exception is our own node, routstr.cypherpunk.today. This account always reviews it <code>lgtm</code>, and that review says it is a self-review: the scout never probes our own node, so it is the operator's own statement and not probe evidence.</p>
<h2 id="what-gets-published-2">What gets published</h2>
<p>Reviews use the same kind 38425 format as audit.routstr.com, so they show up there. Each node has one review, replaced when the verdict changes:</p>
<ul>
<li><code>lgtm</code> once a node has answered paid probes and returned change correctly for three days without a break.</li>
<li><code>avoid</code> when a node keeps two probe tokens without an answer or change. This one goes out immediately.</li>
<li><code>avoid</code> when every paid request has failed for three days.</li>
</ul>
<p>After three days of correct service a node goes back to <code>lgtm</code>. When there are enough probes, the review also carries a <code>score</code>, the share of the last 30 days' probes that went fine.</p>
<p>Each review expires (NIP-40) 30 days after it is signed. The scout re-signs it every two weeks while it still has fresh evidence, so if it stops probing a node, or stops running altogether, the old reviews disappear by themselves.</p>
<p>Notes (kind 1) cover things worth knowing before a review changes, such as a node keeping a single probe token. One kept token is an observation, not a verdict. A note also goes out when a review changes, but not when one is merely refreshed.</p>
<h2 id="backing-off-2">Backing off</h2>
<p>When a node keeps two tokens, the scout stops paying it for a while, and how long depends on its record. A node that had been serving correctly for two weeks or more gets 12 hours. One with no record gets three days, and anything in between is scaled. A node that ran well for weeks and then misbehaves is more likely having a bad day (a mint outage, a restart in the middle of a request) than turning dishonest.</p>
<p>If it happens three times, the scout stops probing that node for good. A node that stays clean for two weeks after a pause starts that count over.</p>
<h2 id="what-a-review-does-not-tell-you-2">What a review does not tell you</h2>
<p>A probe is one small request to one model. It shows the node was up, answered, and handled ecash correctly at that moment. It tells you nothing about the quality of the answers, about the node's other models, or about what the node does with your prompts.</p>
<p>The reviews don't decide routing either. Routstr clients route according to reviews from Routstr's own key. Reviews from this account are a public data point for users and for Routstr's reviewers.</p>
<h2 id="if-we-got-your-node-wrong-2">If we got your node wrong</h2>
<p>Probes can fail because of something on our side. If you run a node and think its review here is wrong, reply to this article or message <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>. The scout logs every event it signs, so we can check exactly what it saw.</p>
</blockquote>
2026-10-15T14:31:29Zhttps://njump.cloud.vinney.xyz/nevent1qqs87mt3dfctd0d6ypd4dx4vx9qv7mk3v3uh5gl5vu5g6pn3s9xen5czyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkt804csRoutstr review: routstr.bulbulpp.com is now avoid - paid requests ...
In reply to <a href='/naddr1qpxnvdfkx4jxvc3hxcer2venvsukgcfjxejnjcnyxejk2wrpxdskzeryvcenqef4xucxgdryxuenswp4xyexgwfsxdskydnpxuerxdehxcarvdfkx4jxvc3hxcer2vczyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqqfvxgr4d8f6'>naddr1qp…d8f6</a><br/>_________________________<br/><br/>Routstr review: routstr.bulbulpp.com is now avoid - paid requests have failed for three days or more. Run by Juraj Bednar, who also operates the competing node routstr.cypherpunk.today. How the probing works:<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/naddr1qqwxsmmh946xsefdwfhh2arnw3ez6umrda6hgttswfhkyetnqyw8wumn8ghj7mn0wd68ytnr09cxsetjwp6ku6eww3hkgcteqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqq823cf2xxzg" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">naddr1qq…xxzg</a></span> </div> <p>This account is a bot. Juraj Bednar (<span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>) runs it, and he also operates a Routstr node, routstr.cypherpunk.today. So a competitor is reviewing other nodes here, and you should weigh the reviews with that in mind. Below is what the bot does.</p>
<h2 id="why-probe-at-all-5">Why probe at all</h2>
<p>A Routstr node announces itself on Nostr (kind 38421) with the models it sells and the mints it accepts. Clients pay per request with a Cashu token: they send more than the request costs, and the node hands back the rest as change.</p>
<p>The announcement doesn't tell you whether the node works. Some nodes list models whose upstream key has expired. Some answer every request with an error. A few take the token and send back neither an answer nor change, and for a client paying with bearer ecash that money is gone. You only find out by paying.</p>
<h2 id="what-one-probe-is-5">What one probe is</h2>
<ol>
<li>The scout mints a fresh 32-sat token at a mint the node accepts. Each probe gets its own token, and the node never sees anything else.</li>
<li>It sends one short, real chat completion request, paying with that token in the <code>X-Cashu</code> header, the way any client would.</li>
<li>It records what happened: an answer, an error, or nothing.</li>
<li>If the node returned change (or a refund, on an error), the scout redeems it straight away.</li>
<li>If nothing came back, it asks the mint whether the token was spent (NUT-07). Unspent means the node never charged, and the token gets used again. Spent, with no answer and no change, means the node kept it.</li>
</ol>
<p>A probe that goes well costs about 1 sat in mint fees. When a node keeps a token, we lose that one token.</p>
<h2 id="which-nodes-5">Which nodes</h2>
<p>The scout probes some of the nodes on the network, not all of them, and not on a published schedule. It only reviews nodes it has paid-probed itself, so a node with no review from this account hasn't been judged badly. It just hasn't been probed.</p>
<p>The one exception is our own node, routstr.cypherpunk.today. This account always reviews it <code>lgtm</code>, and that review says it is a self-review: the scout never probes our own node, so it is the operator's own statement and not probe evidence.</p>
<h2 id="what-gets-published-5">What gets published</h2>
<p>Reviews use the same kind 38425 format as audit.routstr.com, so they show up there. Each node has one review, replaced when the verdict changes:</p>
<ul>
<li><code>lgtm</code> once a node has answered paid probes and returned change correctly for three days without a break.</li>
<li><code>avoid</code> when a node keeps two probe tokens without an answer or change. This one goes out immediately.</li>
<li><code>avoid</code> when every paid request has failed for three days.</li>
</ul>
<p>After three days of correct service a node goes back to <code>lgtm</code>. When there are enough probes, the review also carries a <code>score</code>, the share of the last 30 days' probes that went fine.</p>
<p>Each review expires (NIP-40) 30 days after it is signed. The scout re-signs it every two weeks while it still has fresh evidence, so if it stops probing a node, or stops running altogether, the old reviews disappear by themselves.</p>
<p>Notes (kind 1) cover things worth knowing before a review changes, such as a node keeping a single probe token. One kept token is an observation, not a verdict. A note also goes out when a review changes, but not when one is merely refreshed.</p>
<h2 id="backing-off-5">Backing off</h2>
<p>When a node keeps two tokens, the scout stops paying it for a while, and how long depends on its record. A node that had been serving correctly for two weeks or more gets 12 hours. One with no record gets three days, and anything in between is scaled. A node that ran well for weeks and then misbehaves is more likely having a bad day (a mint outage, a restart in the middle of a request) than turning dishonest.</p>
<p>If it happens three times, the scout stops probing that node for good. A node that stays clean for two weeks after a pause starts that count over.</p>
<h2 id="what-a-review-does-not-tell-you-5">What a review does not tell you</h2>
<p>A probe is one small request to one model. It shows the node was up, answered, and handled ecash correctly at that moment. It tells you nothing about the quality of the answers, about the node's other models, or about what the node does with your prompts.</p>
<p>The reviews don't decide routing either. Routstr clients route according to reviews from Routstr's own key. Reviews from this account are a public data point for users and for Routstr's reviewers.</p>
<h2 id="if-we-got-your-node-wrong-5">If we got your node wrong</h2>
<p>Probes can fail because of something on our side. If you run a node and think its review here is wrong, reply to this article or message <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>. The scout logs every event it signs, so we can check exactly what it saw.</p>
</blockquote>
2026-10-15T14:31:29Zhttps://njump.cloud.vinney.xyz/nevent1qqs9fdlgwkwlzhtg72s9duyyta3rj4kg48p5xlftqk2p06c3udc4r0szyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqlu8svRoutstr review: api.nonkycai.com has served correctly for three ...
In reply to <a href='/naddr1qpxkgvmpxpskvdf38pnxge358pnxgdm98p3nwwf5xvmnzepjxqcrgvpkxymxzenzvdnrjve5v5ensv35xu6rvvtrxejnwdpsxquk2wtxvgaxgvmpxpskvdf38pnxgeszyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqqfvxghac4vy'>naddr1qp…c4vy</a><br/>_________________________<br/><br/>Routstr review: api.nonkycai.com has served correctly for three days again, review back to lgtm. Run by Juraj Bednar, who also operates the competing node routstr.cypherpunk.today. How the probing works:<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/naddr1qqwxsmmh946xsefdwfhh2arnw3ez6umrda6hgttswfhkyetnqyw8wumn8ghj7mn0wd68ytnr09cxsetjwp6ku6eww3hkgcteqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqq823cf2xxzg" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">naddr1qq…xxzg</a></span> </div> <p>This account is a bot. Juraj Bednar (<span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>) runs it, and he also operates a Routstr node, routstr.cypherpunk.today. So a competitor is reviewing other nodes here, and you should weigh the reviews with that in mind. Below is what the bot does.</p>
<h2 id="why-probe-at-all-8">Why probe at all</h2>
<p>A Routstr node announces itself on Nostr (kind 38421) with the models it sells and the mints it accepts. Clients pay per request with a Cashu token: they send more than the request costs, and the node hands back the rest as change.</p>
<p>The announcement doesn't tell you whether the node works. Some nodes list models whose upstream key has expired. Some answer every request with an error. A few take the token and send back neither an answer nor change, and for a client paying with bearer ecash that money is gone. You only find out by paying.</p>
<h2 id="what-one-probe-is-8">What one probe is</h2>
<ol>
<li>The scout mints a fresh 32-sat token at a mint the node accepts. Each probe gets its own token, and the node never sees anything else.</li>
<li>It sends one short, real chat completion request, paying with that token in the <code>X-Cashu</code> header, the way any client would.</li>
<li>It records what happened: an answer, an error, or nothing.</li>
<li>If the node returned change (or a refund, on an error), the scout redeems it straight away.</li>
<li>If nothing came back, it asks the mint whether the token was spent (NUT-07). Unspent means the node never charged, and the token gets used again. Spent, with no answer and no change, means the node kept it.</li>
</ol>
<p>A probe that goes well costs about 1 sat in mint fees. When a node keeps a token, we lose that one token.</p>
<h2 id="which-nodes-8">Which nodes</h2>
<p>The scout probes some of the nodes on the network, not all of them, and not on a published schedule. It only reviews nodes it has paid-probed itself, so a node with no review from this account hasn't been judged badly. It just hasn't been probed.</p>
<p>The one exception is our own node, routstr.cypherpunk.today. This account always reviews it <code>lgtm</code>, and that review says it is a self-review: the scout never probes our own node, so it is the operator's own statement and not probe evidence.</p>
<h2 id="what-gets-published-8">What gets published</h2>
<p>Reviews use the same kind 38425 format as audit.routstr.com, so they show up there. Each node has one review, replaced when the verdict changes:</p>
<ul>
<li><code>lgtm</code> once a node has answered paid probes and returned change correctly for three days without a break.</li>
<li><code>avoid</code> when a node keeps two probe tokens without an answer or change. This one goes out immediately.</li>
<li><code>avoid</code> when every paid request has failed for three days.</li>
</ul>
<p>After three days of correct service a node goes back to <code>lgtm</code>. When there are enough probes, the review also carries a <code>score</code>, the share of the last 30 days' probes that went fine.</p>
<p>Each review expires (NIP-40) 30 days after it is signed. The scout re-signs it every two weeks while it still has fresh evidence, so if it stops probing a node, or stops running altogether, the old reviews disappear by themselves.</p>
<p>Notes (kind 1) cover things worth knowing before a review changes, such as a node keeping a single probe token. One kept token is an observation, not a verdict. A note also goes out when a review changes, but not when one is merely refreshed.</p>
<h2 id="backing-off-8">Backing off</h2>
<p>When a node keeps two tokens, the scout stops paying it for a while, and how long depends on its record. A node that had been serving correctly for two weeks or more gets 12 hours. One with no record gets three days, and anything in between is scaled. A node that ran well for weeks and then misbehaves is more likely having a bad day (a mint outage, a restart in the middle of a request) than turning dishonest.</p>
<p>If it happens three times, the scout stops probing that node for good. A node that stays clean for two weeks after a pause starts that count over.</p>
<h2 id="what-a-review-does-not-tell-you-8">What a review does not tell you</h2>
<p>A probe is one small request to one model. It shows the node was up, answered, and handled ecash correctly at that moment. It tells you nothing about the quality of the answers, about the node's other models, or about what the node does with your prompts.</p>
<p>The reviews don't decide routing either. Routstr clients route according to reviews from Routstr's own key. Reviews from this account are a public data point for users and for Routstr's reviewers.</p>
<h2 id="if-we-got-your-node-wrong-8">If we got your node wrong</h2>
<p>Probes can fail because of something on our side. If you run a node and think its review here is wrong, reply to this article or message <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>. The scout logs every event it signs, so we can check exactly what it saw.</p>
</blockquote>
2026-10-15T14:16:10Zhttps://njump.cloud.vinney.xyz/nevent1qqsrfrjtv9kkr6zdcxyjv7990p30k8rhn2nj3p6ddxyvzq3w3wchhyqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkw4jkh3Routstr review: node.happyending.mom is now avoid - paid requests ...
In reply to <a href='/naddr1qpxkywfc8pnxycmpvd3r2vrp8pnrxcecv5crzdpjvyukve34vcmnvcfn89jxzcmpvcmkgd3nxserqvrr8q6r2dee89snwce4vsmn2dmz8yaxywfc8pnxycmpvd3r2vqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqqfvxg655lyf'>naddr1qp…5lyf</a><br/>_________________________<br/><br/>Routstr review: node.happyending.mom is now avoid - paid requests have failed for three days or more. Run by Juraj Bednar, who also operates the competing node routstr.cypherpunk.today. How the probing works:<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/naddr1qqwxsmmh946xsefdwfhh2arnw3ez6umrda6hgttswfhkyetnqyw8wumn8ghj7mn0wd68ytnr09cxsetjwp6ku6eww3hkgcteqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqq823cf2xxzg" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">naddr1qq…xxzg</a></span> </div> <p>This account is a bot. Juraj Bednar (<span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>) runs it, and he also operates a Routstr node, routstr.cypherpunk.today. So a competitor is reviewing other nodes here, and you should weigh the reviews with that in mind. Below is what the bot does.</p>
<h2 id="why-probe-at-all-11">Why probe at all</h2>
<p>A Routstr node announces itself on Nostr (kind 38421) with the models it sells and the mints it accepts. Clients pay per request with a Cashu token: they send more than the request costs, and the node hands back the rest as change.</p>
<p>The announcement doesn't tell you whether the node works. Some nodes list models whose upstream key has expired. Some answer every request with an error. A few take the token and send back neither an answer nor change, and for a client paying with bearer ecash that money is gone. You only find out by paying.</p>
<h2 id="what-one-probe-is-11">What one probe is</h2>
<ol>
<li>The scout mints a fresh 32-sat token at a mint the node accepts. Each probe gets its own token, and the node never sees anything else.</li>
<li>It sends one short, real chat completion request, paying with that token in the <code>X-Cashu</code> header, the way any client would.</li>
<li>It records what happened: an answer, an error, or nothing.</li>
<li>If the node returned change (or a refund, on an error), the scout redeems it straight away.</li>
<li>If nothing came back, it asks the mint whether the token was spent (NUT-07). Unspent means the node never charged, and the token gets used again. Spent, with no answer and no change, means the node kept it.</li>
</ol>
<p>A probe that goes well costs about 1 sat in mint fees. When a node keeps a token, we lose that one token.</p>
<h2 id="which-nodes-11">Which nodes</h2>
<p>The scout probes some of the nodes on the network, not all of them, and not on a published schedule. It only reviews nodes it has paid-probed itself, so a node with no review from this account hasn't been judged badly. It just hasn't been probed.</p>
<p>The one exception is our own node, routstr.cypherpunk.today. This account always reviews it <code>lgtm</code>, and that review says it is a self-review: the scout never probes our own node, so it is the operator's own statement and not probe evidence.</p>
<h2 id="what-gets-published-11">What gets published</h2>
<p>Reviews use the same kind 38425 format as audit.routstr.com, so they show up there. Each node has one review, replaced when the verdict changes:</p>
<ul>
<li><code>lgtm</code> once a node has answered paid probes and returned change correctly for three days without a break.</li>
<li><code>avoid</code> when a node keeps two probe tokens without an answer or change. This one goes out immediately.</li>
<li><code>avoid</code> when every paid request has failed for three days.</li>
</ul>
<p>After three days of correct service a node goes back to <code>lgtm</code>. When there are enough probes, the review also carries a <code>score</code>, the share of the last 30 days' probes that went fine.</p>
<p>Each review expires (NIP-40) 30 days after it is signed. The scout re-signs it every two weeks while it still has fresh evidence, so if it stops probing a node, or stops running altogether, the old reviews disappear by themselves.</p>
<p>Notes (kind 1) cover things worth knowing before a review changes, such as a node keeping a single probe token. One kept token is an observation, not a verdict. A note also goes out when a review changes, but not when one is merely refreshed.</p>
<h2 id="backing-off-11">Backing off</h2>
<p>When a node keeps two tokens, the scout stops paying it for a while, and how long depends on its record. A node that had been serving correctly for two weeks or more gets 12 hours. One with no record gets three days, and anything in between is scaled. A node that ran well for weeks and then misbehaves is more likely having a bad day (a mint outage, a restart in the middle of a request) than turning dishonest.</p>
<p>If it happens three times, the scout stops probing that node for good. A node that stays clean for two weeks after a pause starts that count over.</p>
<h2 id="what-a-review-does-not-tell-you-11">What a review does not tell you</h2>
<p>A probe is one small request to one model. It shows the node was up, answered, and handled ecash correctly at that moment. It tells you nothing about the quality of the answers, about the node's other models, or about what the node does with your prompts.</p>
<p>The reviews don't decide routing either. Routstr clients route according to reviews from Routstr's own key. Reviews from this account are a public data point for users and for Routstr's reviewers.</p>
<h2 id="if-we-got-your-node-wrong-11">If we got your node wrong</h2>
<p>Probes can fail because of something on our side. If you run a node and think its review here is wrong, reply to this article or message <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>. The scout logs every event it signs, so we can check exactly what it saw.</p>
</blockquote>
2026-10-15T13:01:08Zhttps://njump.cloud.vinney.xyz/nevent1qqsvp8s0uctf05zs3f6y83ezsthl3zwmh4x0cdmjjsyg5lg0v3uwepqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkjvynheRoutstr review: api.nostrmodels.top is now avoid - paid requests ...
In reply to <a href='/naddr1qpxnydnrvycxvcnz89jkgve3xsenqwt9vdnx2cnxx43rzvn9xc6nzvpev5unvd34vesnxdfcvyuxzct9xgunveryxcervveevyun2cfjv5arydnrvycxvcnz89jkgvczyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqqfvxg6c8pr0'>naddr1qp…8pr0</a><br/>_________________________<br/><br/>Routstr review: api.nostrmodels.top is now avoid - paid requests have failed for three days or more. Run by Juraj Bednar, who also operates the competing node routstr.cypherpunk.today. How the probing works:<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/naddr1qqwxsmmh946xsefdwfhh2arnw3ez6umrda6hgttswfhkyetnqyw8wumn8ghj7mn0wd68ytnr09cxsetjwp6ku6eww3hkgcteqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqq823cf2xxzg" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">naddr1qq…xxzg</a></span> </div> <p>This account is a bot. Juraj Bednar (<span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>) runs it, and he also operates a Routstr node, routstr.cypherpunk.today. So a competitor is reviewing other nodes here, and you should weigh the reviews with that in mind. Below is what the bot does.</p>
<h2 id="why-probe-at-all-14">Why probe at all</h2>
<p>A Routstr node announces itself on Nostr (kind 38421) with the models it sells and the mints it accepts. Clients pay per request with a Cashu token: they send more than the request costs, and the node hands back the rest as change.</p>
<p>The announcement doesn't tell you whether the node works. Some nodes list models whose upstream key has expired. Some answer every request with an error. A few take the token and send back neither an answer nor change, and for a client paying with bearer ecash that money is gone. You only find out by paying.</p>
<h2 id="what-one-probe-is-14">What one probe is</h2>
<ol>
<li>The scout mints a fresh 32-sat token at a mint the node accepts. Each probe gets its own token, and the node never sees anything else.</li>
<li>It sends one short, real chat completion request, paying with that token in the <code>X-Cashu</code> header, the way any client would.</li>
<li>It records what happened: an answer, an error, or nothing.</li>
<li>If the node returned change (or a refund, on an error), the scout redeems it straight away.</li>
<li>If nothing came back, it asks the mint whether the token was spent (NUT-07). Unspent means the node never charged, and the token gets used again. Spent, with no answer and no change, means the node kept it.</li>
</ol>
<p>A probe that goes well costs about 1 sat in mint fees. When a node keeps a token, we lose that one token.</p>
<h2 id="which-nodes-14">Which nodes</h2>
<p>The scout probes some of the nodes on the network, not all of them, and not on a published schedule. It only reviews nodes it has paid-probed itself, so a node with no review from this account hasn't been judged badly. It just hasn't been probed.</p>
<p>The one exception is our own node, routstr.cypherpunk.today. This account always reviews it <code>lgtm</code>, and that review says it is a self-review: the scout never probes our own node, so it is the operator's own statement and not probe evidence.</p>
<h2 id="what-gets-published-14">What gets published</h2>
<p>Reviews use the same kind 38425 format as audit.routstr.com, so they show up there. Each node has one review, replaced when the verdict changes:</p>
<ul>
<li><code>lgtm</code> once a node has answered paid probes and returned change correctly for three days without a break.</li>
<li><code>avoid</code> when a node keeps two probe tokens without an answer or change. This one goes out immediately.</li>
<li><code>avoid</code> when every paid request has failed for three days.</li>
</ul>
<p>After three days of correct service a node goes back to <code>lgtm</code>. When there are enough probes, the review also carries a <code>score</code>, the share of the last 30 days' probes that went fine.</p>
<p>Each review expires (NIP-40) 30 days after it is signed. The scout re-signs it every two weeks while it still has fresh evidence, so if it stops probing a node, or stops running altogether, the old reviews disappear by themselves.</p>
<p>Notes (kind 1) cover things worth knowing before a review changes, such as a node keeping a single probe token. One kept token is an observation, not a verdict. A note also goes out when a review changes, but not when one is merely refreshed.</p>
<h2 id="backing-off-14">Backing off</h2>
<p>When a node keeps two tokens, the scout stops paying it for a while, and how long depends on its record. A node that had been serving correctly for two weeks or more gets 12 hours. One with no record gets three days, and anything in between is scaled. A node that ran well for weeks and then misbehaves is more likely having a bad day (a mint outage, a restart in the middle of a request) than turning dishonest.</p>
<p>If it happens three times, the scout stops probing that node for good. A node that stays clean for two weeks after a pause starts that count over.</p>
<h2 id="what-a-review-does-not-tell-you-14">What a review does not tell you</h2>
<p>A probe is one small request to one model. It shows the node was up, answered, and handled ecash correctly at that moment. It tells you nothing about the quality of the answers, about the node's other models, or about what the node does with your prompts.</p>
<p>The reviews don't decide routing either. Routstr clients route according to reviews from Routstr's own key. Reviews from this account are a public data point for users and for Routstr's reviewers.</p>
<h2 id="if-we-got-your-node-wrong-14">If we got your node wrong</h2>
<p>Probes can fail because of something on our side. If you run a node and think its review here is wrong, reply to this article or message <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>. The scout logs every event it signs, so we can check exactly what it saw.</p>
</blockquote>
2026-10-12T12:01:20Zhttps://njump.cloud.vinney.xyz/nevent1qqsy23wns8f9dnhjrqhpd5xsrsampv8arkfgrnhq0uvzurhkpsjrapqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nk2xpc56Routstr review: api.nonkycai.com is now avoid - paid requests ...
In reply to <a href='/naddr1qpxkgvmpxpskvdf38pnxge358pnxgdm98p3nwwf5xvmnzepjxqcrgvpkxymxzenzvdnrjve5v5ensv35xu6rvvtrxejnwdpsxquk2wtxvgaxgvmpxpskvdf38pnxgeszyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqqfvxghac4vy'>naddr1qp…c4vy</a><br/>_________________________<br/><br/>Routstr review: api.nonkycai.com is now avoid - paid requests have failed for three days or more. Run by Juraj Bednar, who also operates the competing node routstr.cypherpunk.today. How the probing works:<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/naddr1qqwxsmmh946xsefdwfhh2arnw3ez6umrda6hgttswfhkyetnqyw8wumn8ghj7mn0wd68ytnr09cxsetjwp6ku6eww3hkgcteqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqq823cf2xxzg" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">naddr1qq…xxzg</a></span> </div> <p>This account is a bot. Juraj Bednar (<span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>) runs it, and he also operates a Routstr node, routstr.cypherpunk.today. So a competitor is reviewing other nodes here, and you should weigh the reviews with that in mind. Below is what the bot does.</p>
<h2 id="why-probe-at-all-17">Why probe at all</h2>
<p>A Routstr node announces itself on Nostr (kind 38421) with the models it sells and the mints it accepts. Clients pay per request with a Cashu token: they send more than the request costs, and the node hands back the rest as change.</p>
<p>The announcement doesn't tell you whether the node works. Some nodes list models whose upstream key has expired. Some answer every request with an error. A few take the token and send back neither an answer nor change, and for a client paying with bearer ecash that money is gone. You only find out by paying.</p>
<h2 id="what-one-probe-is-17">What one probe is</h2>
<ol>
<li>The scout mints a fresh 32-sat token at a mint the node accepts. Each probe gets its own token, and the node never sees anything else.</li>
<li>It sends one short, real chat completion request, paying with that token in the <code>X-Cashu</code> header, the way any client would.</li>
<li>It records what happened: an answer, an error, or nothing.</li>
<li>If the node returned change (or a refund, on an error), the scout redeems it straight away.</li>
<li>If nothing came back, it asks the mint whether the token was spent (NUT-07). Unspent means the node never charged, and the token gets used again. Spent, with no answer and no change, means the node kept it.</li>
</ol>
<p>A probe that goes well costs about 1 sat in mint fees. When a node keeps a token, we lose that one token.</p>
<h2 id="which-nodes-17">Which nodes</h2>
<p>The scout probes some of the nodes on the network, not all of them, and not on a published schedule. It only reviews nodes it has paid-probed itself, so a node with no review from this account hasn't been judged badly. It just hasn't been probed.</p>
<p>The one exception is our own node, routstr.cypherpunk.today. This account always reviews it <code>lgtm</code>, and that review says it is a self-review: the scout never probes our own node, so it is the operator's own statement and not probe evidence.</p>
<h2 id="what-gets-published-17">What gets published</h2>
<p>Reviews use the same kind 38425 format as audit.routstr.com, so they show up there. Each node has one review, replaced when the verdict changes:</p>
<ul>
<li><code>lgtm</code> once a node has answered paid probes and returned change correctly for three days without a break.</li>
<li><code>avoid</code> when a node keeps two probe tokens without an answer or change. This one goes out immediately.</li>
<li><code>avoid</code> when every paid request has failed for three days.</li>
</ul>
<p>After three days of correct service a node goes back to <code>lgtm</code>. When there are enough probes, the review also carries a <code>score</code>, the share of the last 30 days' probes that went fine.</p>
<p>Each review expires (NIP-40) 30 days after it is signed. The scout re-signs it every two weeks while it still has fresh evidence, so if it stops probing a node, or stops running altogether, the old reviews disappear by themselves.</p>
<p>Notes (kind 1) cover things worth knowing before a review changes, such as a node keeping a single probe token. One kept token is an observation, not a verdict. A note also goes out when a review changes, but not when one is merely refreshed.</p>
<h2 id="backing-off-17">Backing off</h2>
<p>When a node keeps two tokens, the scout stops paying it for a while, and how long depends on its record. A node that had been serving correctly for two weeks or more gets 12 hours. One with no record gets three days, and anything in between is scaled. A node that ran well for weeks and then misbehaves is more likely having a bad day (a mint outage, a restart in the middle of a request) than turning dishonest.</p>
<p>If it happens three times, the scout stops probing that node for good. A node that stays clean for two weeks after a pause starts that count over.</p>
<h2 id="what-a-review-does-not-tell-you-17">What a review does not tell you</h2>
<p>A probe is one small request to one model. It shows the node was up, answered, and handled ecash correctly at that moment. It tells you nothing about the quality of the answers, about the node's other models, or about what the node does with your prompts.</p>
<p>The reviews don't decide routing either. Routstr clients route according to reviews from Routstr's own key. Reviews from this account are a public data point for users and for Routstr's reviewers.</p>
<h2 id="if-we-got-your-node-wrong-17">If we got your node wrong</h2>
<p>Probes can fail because of something on our side. If you run a node and think its review here is wrong, reply to this article or message <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>. The scout logs every event it signs, so we can check exactly what it saw.</p>
</blockquote>
2026-10-12T07:46:08Zhttps://njump.cloud.vinney.xyz/nevent1qqs0z7cp2mxcp3rygcqpc6n8ln5rvyuxau5amkkvk8ds8mt7jasnetszyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkwg02awThe Routstr scout now publishes node reviews (kind 38425, visible ...
The Routstr scout now publishes node reviews (kind 38425, visible on audit.routstr.com) from its own paid probes. First batch: avoid: 140.245.192.194, ai.orangesync.tech, ai.redsh1ft.com, privateprovider.xyz, routstr.orangesync.tech, routstr.otrta.me, routstr.satoshisend.xyz, routstr1.purpleprometheus.com; lgtm: llm.satsandsports.cash, ppq.redsh1ft.com. From here on a note goes out only when something changes. Run by Juraj Bednar, who also operates the competing node routstr.cypherpunk.today. How the probing works:<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/naddr1qqwxsmmh946xsefdwfhh2arnw3ez6umrda6hgttswfhkyetnqyw8wumn8ghj7mn0wd68ytnr09cxsetjwp6ku6eww3hkgcteqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqzyzhfqng239eglcrytxmr3qhyfjvsupwvr5hzstz7n496scxhd23nkqcyqqq823cf2xxzg" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">naddr1qq…xxzg</a></span> </div> <p>This account is a bot. Juraj Bednar (<span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>) runs it, and he also operates a Routstr node, routstr.cypherpunk.today. So a competitor is reviewing other nodes here, and you should weigh the reviews with that in mind. Below is what the bot does.</p>
<h2 id="why-probe-at-all-20">Why probe at all</h2>
<p>A Routstr node announces itself on Nostr (kind 38421) with the models it sells and the mints it accepts. Clients pay per request with a Cashu token: they send more than the request costs, and the node hands back the rest as change.</p>
<p>The announcement doesn't tell you whether the node works. Some nodes list models whose upstream key has expired. Some answer every request with an error. A few take the token and send back neither an answer nor change, and for a client paying with bearer ecash that money is gone. You only find out by paying.</p>
<h2 id="what-one-probe-is-20">What one probe is</h2>
<ol>
<li>The scout mints a fresh 32-sat token at a mint the node accepts. Each probe gets its own token, and the node never sees anything else.</li>
<li>It sends one short, real chat completion request, paying with that token in the <code>X-Cashu</code> header, the way any client would.</li>
<li>It records what happened: an answer, an error, or nothing.</li>
<li>If the node returned change (or a refund, on an error), the scout redeems it straight away.</li>
<li>If nothing came back, it asks the mint whether the token was spent (NUT-07). Unspent means the node never charged, and the token gets used again. Spent, with no answer and no change, means the node kept it.</li>
</ol>
<p>A probe that goes well costs about 1 sat in mint fees. When a node keeps a token, we lose that one token.</p>
<h2 id="which-nodes-20">Which nodes</h2>
<p>The scout probes some of the nodes on the network, not all of them, and not on a published schedule. It only reviews nodes it has paid-probed itself, so a node with no review from this account hasn't been judged badly. It just hasn't been probed.</p>
<p>The one exception is our own node, routstr.cypherpunk.today. This account always reviews it <code>lgtm</code>, and that review says it is a self-review: the scout never probes our own node, so it is the operator's own statement and not probe evidence.</p>
<h2 id="what-gets-published-20">What gets published</h2>
<p>Reviews use the same kind 38425 format as audit.routstr.com, so they show up there. Each node has one review, replaced when the verdict changes:</p>
<ul>
<li><code>lgtm</code> once a node has answered paid probes and returned change correctly for three days without a break.</li>
<li><code>avoid</code> when a node keeps two probe tokens without an answer or change. This one goes out immediately.</li>
<li><code>avoid</code> when every paid request has failed for three days.</li>
</ul>
<p>After three days of correct service a node goes back to <code>lgtm</code>. When there are enough probes, the review also carries a <code>score</code>, the share of the last 30 days' probes that went fine.</p>
<p>Each review expires (NIP-40) 30 days after it is signed. The scout re-signs it every two weeks while it still has fresh evidence, so if it stops probing a node, or stops running altogether, the old reviews disappear by themselves.</p>
<p>Notes (kind 1) cover things worth knowing before a review changes, such as a node keeping a single probe token. One kept token is an observation, not a verdict. A note also goes out when a review changes, but not when one is merely refreshed.</p>
<h2 id="backing-off-20">Backing off</h2>
<p>When a node keeps two tokens, the scout stops paying it for a while, and how long depends on its record. A node that had been serving correctly for two weeks or more gets 12 hours. One with no record gets three days, and anything in between is scaled. A node that ran well for weeks and then misbehaves is more likely having a bad day (a mint outage, a restart in the middle of a request) than turning dishonest.</p>
<p>If it happens three times, the scout stops probing that node for good. A node that stays clean for two weeks after a pause starts that count over.</p>
<h2 id="what-a-review-does-not-tell-you-20">What a review does not tell you</h2>
<p>A probe is one small request to one model. It shows the node was up, answered, and handled ecash correctly at that moment. It tells you nothing about the quality of the answers, about the node's other models, or about what the node does with your prompts.</p>
<p>The reviews don't decide routing either. Routstr clients route according to reviews from Routstr's own key. Reviews from this account are a public data point for users and for Routstr's reviewers.</p>
<h2 id="if-we-got-your-node-wrong-20">If we got your node wrong</h2>
<p>Probes can fail because of something on our side. If you run a node and think its review here is wrong, reply to this article or message <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/npub1m2mvvpjugwdehtaskrcl7ksvdqnnhnjur9v6g9v266nss504q7mqvlr8p9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>Juraj</span> (<span class="italic">npub1m2m…r8p9</span>)</a></span>. The scout logs every event it signs, so we can check exactly what it saw.</p>
</blockquote>
2026-10-11T09:31:08Z