Skip to content

SlowBearDigger to take over Monero Integrations pt. 3

SlowBearDigger requested to merge SlowBearDigger/ccs-proposals:slowbeardigger-integrations-takeover into master

SlowBearDigger to take over Monero Integrations pt. 3

This transfers Monero Integrations part 3 to SlowBearDigger, with the original scope and payouts.

Who

I'm SlowBearDigger, developer of XMRPay. My updates to MoneroMagento and MoneroWHMCS have been merged.

Work

The MoneroWP implementation is submitted in PR 132, pending review and merge. It addresses the original CCS issues, adds WooCommerce Blocks and HPOS support, and replaces the xmrchain dependency with local PHP payment scanning. It includes regression tests and a stagenet demo.

I'll take care of the remaining MoneroPHP work covered by the original proposal, including compatibility, tests, documentation and the stable Packagist release.

Payment detection

The scanner builds on MoneroPHP's cryptographic code. The merchant supplies a primary address, private view key and a trusted Monero node. WordPress derives a subaddress for each order and reads transaction data through daemon RPC.

Using the private view key a and the output's applicable transaction public key R, it derives K = 8aR. For output index i, it computes:

k = Hs(encode(K) || varint(i)); P = kG + D

Here D is the order subaddress's public spend key, G is the curve base point and Hs is Keccak-256 reduced modulo the scalar order. Matching P identifies the receiving output. For the compact RingCT amount format, k also allows the scanner to decrypt the amount and reconstruct its commitment, V = mask·G + amount·H, using Monero's commitment generator H. It checks that commitment before counting the output toward the order, applying the configured confirmation requirement and handling partial payments in integer piconero.

The view key stays on the merchant's server; the scanner cannot spend funds. The node is still trusted for chain inclusion and confirmation information.

Merchants need the PHP extensions and a working scheduler, but no wallet file, monero-wallet-rpc service or local node. Reducing that setup work makes accepting Monero more practical for existing stores.

Milestones

The original issue lists and completion conditions apply.

  • Monero PHP library maintenance: 4 XMR
  • Monero Woocommerce payment gateway maintenance: 7 XMR

Timeline

I aim to complete both milestones within five months of the approved transfer. MoneroWP is available for review now. I'll track the original issue lists in monthly updates, linking the fixes and tests and noting anything awaiting maintainer review.

If the milestones remain incomplete five months after approval, the community may reassign the unpaid funds.

After both milestones are accepted, I'll spend six months maintaining the delivered work, updating inactive Monero Integrations gateways and gradually adding this payment detection method where it fits. Priorities will follow community demand and access to platform testing. Monthly updates will continue during this period. No further funding is needed for this work.

I'm happy to discuss the proposal and make adjustments based on community feedback.

Merge request reports