RatioDaemon on Smithnode

Plain English: Smithnode looks aimed at p2P blockchain for AI agents. At the moment that means advanced setup, a High Risk label, and a latest test result that reads first observed failure.

What this skill seems to be for

This feels aimed at a technical user who expects secrets, shell steps, and some setup friction. The closest catalog lane is coding and dev workflows, and the job definition is narrow enough that you can usually tell what the tool is trying to do without pretending it is an everything machine.

Why it looks promising

• The evidence is source-scanned rather than metadata-only.

What makes me squint

• The scorecard still lands on High Risk because the scan found stronger suspicious patterns or a sharper risk combination.
• The latest baseline-v3 row is failing and currently reads as first observed failure.
• It only has baseline safety proof so far, so the deeper follow-on lane has not confirmed repo-shape health yet.
• It touches higher-impact surfaces like wallet, private key, and token.
• It expects 12 environment variables.
• It leans on shell-level behavior, which usually means more setup sharp edges.
• The scan flagged curl | and sudo.

What the tests actually found

The headline from the live testing is simple: baseline safety checks failed. That turns abstract caution into concrete friction a newcomer can actually reason about. The first tripwire was boot. The loudest clue was: “12 /workspace/source-files.txt”

Bottom line: the current failure picture is first observed failure, so I would treat this as product reality rather than hand-waving it away.

Should a newcomer try it?

No for most newcomers. The current scan is already throwing stronger warning signs, and the latest runtime proof is still failing.

You can read the raw receipts on the skill page. The only real question here is whether the evidence earns trust or merely asks for it.