Nodewatch Monero Payments for WooCommerce

1.1.4

• Check setup tests every configured node, up to 10, and reports health, response time and secondary-node warnings.
• Node settings use separate numbered cards with their own authentication fields.
• The diagnostic timeout scales with the number of nodes and remains filterable.
• Custom Monero RPC ports accumulate across scanners created during the same WordPress request.
• The checkout reports a copied address only after the browser confirms success. It uses a fallback when the Clipboard API is unavailable and reports failure honestly.

1.1.3

• Added None, HTTP Basic and HTTP Digest authentication for each Monero node.
• Credentials remain attached to their node during failover and are not returned in settings or diagnostics.
• Setup checks distinguish rejected credentials, unreachable nodes and unavailable Digest support.

1.1.2

• Hardening (Agent mode): Agent URLs are now enforced as localhost-only in the setup wizard, gateway settings, Blocks availability, and runtime client, closing an avoidable server-side request surface before WordPress.org review.
• Fix (remote node setup): WordPress’s wp_safe_remote_* only allows a short list of ports and silently blocks Monero RPC ports like 18081 (mainnet) and 38089 (stagenet), so pointing the plugin at a remote node failed until you hand-added an http_allowed_safe_ports filter. The plugin now whitelists the ports of your configured node(s) automatically (and only those; the safe-HTTP SSRF guard still protects every other host and port). Thanks to the tester who reported this. No settings change.

1.1.1

• Fix (payment detection): the per-output scan loop wrapped ownership and amount/commitment decoding in one catch, so an error while decoding an output that IS yours (e.g. a pruned node, a malformed blob) was indistinguishable from “not yours” and could report a real payment as unpaid. Ownership and decoding are now separated: an undecodable but owned output fails closed and is surfaced (found-but-unverified), never silently missed. Hardening only; no settings or data change.

1.1.0

• Non-custodial refunds (claim-link). Refund an order and the buyer gets a link to enter a Monero receive address (a tx never reveals the sender); you pay it by hand and mark it sent. Configurable link expiry with one-click reissue, address and network validation, and a reopen on a later refund so additional money is never stranded.
• Monero payments report and CSV export under WooCommerce (owed, received, overpaid, confirmations, state, refund status), spreadsheet-formula-injection safe.
• Resilient multi-node. Comma-separated nodes now genuinely fail over, and the block height is cross-checked across them (the lowest is used), so a lagging node can only delay a payment, never confirm it early.
• Critical fix: the order-completion and proof paths used a non-existent WordPress function for their lock; replaced with a real atomic mutex. Also: a watch order is no longer created in an unscannable state when the node is briefly unreachable (the checkout fails cleanly so the buyer retries), a wrong-network refund address is rejected, and a mempool double-spend is never credited.
• Tested PHP 7.4, 8.1 and 8.3 in CI.

1.0.1

• Security: burning-bug defence. The no-server scanner now deduplicates payments by the one-time output key, not by the transaction id. Two outputs that share a one-time key (a 2018-style burn, even across different transactions) are at most one spendable output, so they can never credit an order twice.
• Requires both GMP and BCMath. The pure-PHP verifier needs the BCMath extension (for base58) in addition to GMP (for the money math). The gateway now hides itself, and the settings warn, on a host missing either one, instead of failing after a buyer paid.
• Hardened the settlement math to be fully order-independent (a duplicate that disagrees on lock status can never change the verdict by row order).