SlowBearDigger to take over Monero Integrations pt. 3

SlowBearDigger to take over Monero Integrations pt. 3

This transfers Monero Integrations part 3 to SlowBearDigger and reallocates its existing 11 XMR.

Who

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

Status

The MoneroWP implementation is complete and pending review in PR 132. 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 complete the remaining MoneroPHP work, including compatibility, tests, documentation and a 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

• MoneroPHP maintenance: 2 XMR
• MoneroWP maintenance: 5 XMR
• Extensive technical review by @serhack: 2 XMR
• First three months of maintenance: 1 XMR
• Final three months of maintenance: 1 XMR

The review allocation covers @serhack's time for an extensive technical review of the MoneroPHP and MoneroWP changes.

Timeline

I aim to complete the implementation work within five months of the approved transfer.

The six-month maintenance period begins after the MoneroPHP and MoneroWP work is merged, with 1 XMR released after each three-month period.

If the work remains incomplete five months after approval, the community may reassign the unpaid funds.

Original proposal and previous updates

Deadline update: July 1, 2025

Prior to the deadline, the proposer MUST provide regular updates on their progress as per the CCS rules.

If the provided updates/progress (or lack thereof) is unsatisfactory, all remaining funds can be relinquished either before or after the deadline.

The community will then seek another person/team to take over. If this cannot be accomplished within a reasonable timeframe, the funds will be repurposed or reallocated to a similar proposal (subject to community consensus).

What?

I am SerHack, the author of Mastering Monero and security engineer; I am one of the maintainers for Monero integrations project. The project aims to provide a set of payment gateways and libraries (coded mainly in PHP, at the time of writing) for merchants and developers. As you might find on Github, the payment gateways are not in any third party companies, then no data is sent to any other website beside yours.

With this request, I would like to keep the two main repositories (PHP library and Woocommerce libraries) updated. I have set two main milestones.

Milestone 1: PHP library maintenance

I've listed all the possible issues I can fix or improve. Note that I would like to keep this library without any external dependencies (e.g. guzzle from composer) for security reasons. Honestly, I have some difficulties at trusting composer, but I'd like to discuss about this.

• Enable SSL validation by default for non loopback connections
• Daemon RPC Wrapper: "Other Methods"
• Make stable version on packagist
• Use code stype
• Remove dead code
• Library returns NULL when it receives a blank response or an error
• PHP 7.2 - json_encode() breaks transfer submission of certain amounts
• offline mnemonic support planned?
• Make sure we support the latest PHP versions and do not support PHP < 7.2
• General improvement

If you have any additional idea, feature request, or issue, please let me know!

Milestone 2: Monero Woocommerce payment gateway maintenance

Monero Woocommerce Payment Gateway had only 40 installations from Wordpress.org. This is partially my fault since the page was created to attract more merchants. As per Milestone 1, I have listed all the issues I would like to fix.

• Switch to subaddresses - This has already been implemented, but in a cryptic way. It needs some review.
• List of currencies vanishes
• Improve the upcoming release 3.0
• Decrypting payment id in Monero_Cryptonote results in infinite loop
• Feature request: checkout shutdown on timeout
• javascript disabled fall-back support
• One payment will cause all pending orders with the same value to be marked as paid.

Any other idea is really appreciated!

Why?

I would like to expand more this section since it is a subject close to my heart. Monero was created to be the most private cryptocurrency ever created; when I joined the Monero community, I had some difficulties at finding payment gateways that were private. Thus I've started this project.

Costs

If milestones are not modified, I'll ask 11 XMR (~700 euros) - fixed price.