Add Canary wallet monitoring app

[schjonhaug]

Description

Adds Canary - a Bitcoin wallet monitoring and early warning system for cold storage.

Features:

• Watch-only wallet monitoring via output descriptors
• Instant notifications via ntfy push notifications
• Transaction detection with RBF/CPFP awareness
• Balance alerts (threshold-based notifications)
• Deep wallet scanning for comprehensive history
• Multi-language support

Canary connects to the local Electrum server (electrs) to monitor wallets without requiring private keys.

Checklist

• tested successfully on local MyNode, if yes, list the device(s) below

List of test device(s)

• PC (MyNode)

[schjonhaug]

@tehelsper , do you have any time soon to take a look at this?

[tehelsper]

I should be able to get to it in the next release. I've got a couple quick comments. Thanks!

• Can you update to v1.4.0? Looks like you have a new release out.
• Can you update the install script to use the VERSION for the version? Apps like albyhub might be a good example.

[schjonhaug]

I can update this to v1.4.0, but I’d prefer not to do that yet without testing it on a real myNode device first. v1.4.0 adds new self-hosted behavior around local Mempool integration, and I haven’t had a chance to validate that path on actual myNode hardware yet. ntfy should be fine since it’s configured in Canary’s settings and defaults to ntfy.sh, but local Mempool support on myNode likely deserves a proper follow-up so Canary can detect and use the local instance cleanly.

Since I have tested the integration itself on a real myNode box with the current Canary build, I think the safer path for this PR is to keep it on the tested version for now, and then do a follow-up bump to v1.4.0 once I can verify the myNode-specific Mempool behavior properly.

[schjonhaug]

Retested Canary on a fresh myNode machine and updated this branch to v1.4.0.

Validation summary:

• Built and sideloaded the updated package successfully
• Verified Canary installs and runs correctly on myNode
• Confirmed the app is reachable after install

Changes included in this update:

• Bump Canary backend/frontend image tags to v1.4.0
• Update app metadata to v1.4.0
• Add the missing scaffold required by myNode's dynamic app loader
• Remove the empty hook
• Add and to avoid systemd timing out during first-time image pulls / restart cleanup

This has now been pushed to the PR branch for review.

[tehelsper]

How is this 3010 port being used? That's already taken by RTL.

[tehelsper]

This also specifically uses the version tagged 1.4.0, it could use latest if the install process always:

• Removes old versions
• Installs new version
• Tags new version as latest

The install_albyhub.sh script might offer a good pattern for how to do this.

[tehelsper]

This still removes the old version. Look at install_albyhub.sh lines 24-25 to see if they can help remove old images generically rather than a specific version.

[tehelsper]

Try using {VERSION} rather than the specific tag here, that way the app can be updated just by updating the JSON file that manages the app.

[schjonhaug]

Thanks for the feedback, I've addressed the requested changes and pushed the updates to the PR branch.

What changed:

• Moved Canarys internal backend off port 3010 to 3004 to avoid the RTL conflict
• Updated the install flow to use the app VERSION from the JSON-managed metadata
• Removed hardcoded version tags from the service and switched it to stable local image tags
• Updated install/uninstall to remove Canary images generically rather than targeting a specific old version
• Mirrored the same package changes into the standalone canary-mynode repo to keep it in sync

The PR branch has been updated and is ready for another look.

[tehelsper]

This link won't work on all devices. Some don't support mynode.local or it could refer to a different device if there is more than one on the same network.

I recommend an Info page to display any app-info, like default logins or something. The generic version of that page has an Open button that will auto launch the app in a separate window based on the current URL.

Try

    "app_tile_button_text": "Info",
    "app_tile_button_href": "/app/canary/info",

[schjonhaug]

Thanks, that makes sense. I updated the Canary tile to use the generic info page instead of a hardcoded mynode.local URL:

"app_tile_button_text": "Info",
"app_tile_button_href": "/app/canary/info"

I also mirrored the same metadata change into the standalone canary-mynode package and rebuilt the sideload tarball.

[tehelsper]

Merged and I'm testing it now. I'm planning on using a new helper function I just added to cleanup the containers and I'm thinking there may be a cleaner way to start/stop the dual container setup. Maybe that can be done in a follow-up PR.

[tehelsper]

I made some updates to launch via docker-compose and I added an option to open the app directly rather than having to go through the info page. See this commit: 578afed

Seems to be working well! Nice app!

[schjonhaug]

Thanks again for the review and the follow-up compose changes.

While sideload-testing Canary on the current released myNode v0.3.43, I found two compatibility issues that are fixed in a small follow-up PR: #1001

The fixes keep the new direct-open behavior for master, while preserving backwards-compatible tile metadata for v0.3.43 and making the Canary install scripts resolve docker-compose.yml from the installed app directory reliably.

I tested the rebuilt package on an actual myNode v0.3.43 device and confirmed Canary installs as v1.4.0, the service turns green, and the Open button loads the app on port 3005.