[3alpha]

Context

Fix the SPEC-M03 warning reported by the package specification checks. The legacy upstreamRepo, upstreamVersion and upstreamArg fields are deprecated.

Approach

Replace the legacy fields with upstream: [{ repo, version, arg }]: monero-project/monero, v0.18.5.4, UPSTREAM_VERSION.

Test instructions

Validate this branch with the SDK package-spec checker from the linked PR and confirm that no SPEC-M03 findings remain.

Verified locally:

• Loaded 1 package using the SDK, including merged variant manifests where present.
• SPEC-M03 findings: 1 → 0; total spec findings: 2 → 0; no new findings under other rules.
• Compared manifest schemas and effective compose against the default branch: no new schema failures or service runtime changes.
• git diff --check passes.

Container images were not built locally.

[tropibot]

Dappnode bot has built and pinned the built packages to an IPFS node, for commit: 26783dd

This is a development version and should only be installed for testing purposes.

1. Package monero.dnp.dappnode.eth

Install link

Hash: /ipfs/QmUcTut6eUgswGCiQPQYPR6e2taHEe5fq2WhArJhJsvLoG

(by dappnodebot/build-action)

[tropibot]

✅ Package harness passed

Baseline and candidate containers became stably running

Package	Verdict	Reason	Duration	Cleanup
monero.dnp.dappnode.eth	✅ Passed	Candidate containers stable (candidate_containers_stable)	2m 18s	✅ Passed

Run overview

Context	Value
Pull request	dappnode/DAppNodePackage-monero#52
Tested commit	26783dd070bc
Candidate artifact	Install on DAppNode · /ipfs/QmUcTut6eUgswGCiQPQYPR6e2taHEe5fq2WhArJhJsvLoG
Baseline request	automatic
Worker	dappnode-near-5
Run ID	gh-pr-52-26783dd070bc-4e7127aa48d84de6
Execution	2026-11-09T11:24:25.722729169+00:00 → 2026-11-09T11:26:44.220313602+00:00 (✅ Completed)

Baseline vs candidate

Check	Baseline	Candidate
Version	0.2.11	0.2.12
Install	✅ Passed · 10s	✅ Passed · 1m 20s
Hard check	✅ Passed · 3 stable samples	✅ Passed · 3 stable samples
Containers	1 observed	1 observed
Stabilization	10s	10s
Log collection	✅ Passed · 1 container	✅ Passed · 1 container

Container comparison

• Added: none
• Removed: none
• Baseline inventory: DAppNodePackage-monero.dnp.dappnode.eth
• Candidate inventory: DAppNodePackage-monero.dnp.dappnode.eth
• Baseline non-running states: none
• Candidate non-running states: none
• Deterministic regressions: ✅ none

Container inventory

Baseline

Container	Service	State	Image	Created
DAppNodePackage-monero.dnp.dappnode.eth	monero.dnp.dappnode.eth	✅ Running	monero.dnp.dappnode.eth:0.2.11	1794223478

Candidate

Container	Service	State	Image	Created
DAppNodePackage-monero.dnp.dappnode.eth	monero.dnp.dappnode.eth	✅ Running	monero.dnp.dappnode.eth:0.2.12	1794223560

Runtime analysis _advisory

✅ Clean — Heuristic and Nexus analysis: No likely new runtime regression is evident. The candidate initializes the Monero core, p2p server, and RPC server successfully. The DNSSEC warning for updates.moneropulse.org was already present in the baseline; only the resolver failure detail differs.

Analyzer	Status	Summary
Composite	✅ Clean	Heuristic and Nexus analysis: No likely new runtime regression is evident. The candidate initializes the Monero core, p2p server, and RPC server successfully. The DNSSEC warning for updates.moneropulse.org was already present in the baseline; only the resolver failure detail differs.
Heuristic	✅ Clean	No configured candidate-only suspicious signature was found
Nexus	✅ Clean	No likely new runtime regression is evident. The candidate initializes the Monero core, p2p server, and RPC server successfully. The DNSSEC warning for updates.moneropulse.org was already present in the baseline; only the resolver failure detail differs.
Baseline evidence	✅ Clean	No configured suspicious signature was found
Candidate evidence	✅ Clean	No configured suspicious signature was found

✅ No new runtime findings were reported.

Cleanup and diagnostics

Check	Result
Cleanup	✅ Passed
Leftover packages	none
Cleanup error	none

✅ No run errors were recorded.

---

_{Deterministic checks decide the verdict. Runtime log analysis is advisory. TropiBot publishes bounded summaries and never posts raw logs.}