Hi everyone,
I am SlowBearDigger, and I would like to volunteer to help maintain Monero Integrations.
have been doing more work around Monero merchant integrations, I enjoy it, and I would like to take responsibility for keeping that work functional and maintained inside the community repositories.
Work so far / things I have done
My current work includes:
- XMRPay and its related open source integrations, XMRPay is already functional and has helped solve a number of payment detection, settlement, node handling, reorg, authentication and platform integration issues.
- monerowhmcs PR #47, completed as a Monero bounty and merged after review by SerHack.
- moneromagento PR #15, also developed for an existing bounty. It is still waiting for review.
- monerowp PR #132, a little contribution currently waiting for review. if approved will replace the external xmrchain view-key detection with local PHP scanning against monerod and adds per-order subaddresses, confirmations, partial payments, node failover, WooCommerce Blocks and HPOS support.
- A Joomla integration that is in advanced private development. My intention is to finish testing it and offer it to Monero Integrations when it is ready to be published and reviewed.
Some of this integration work reuses compatible open-source components developed for XMRPay (thanks to monerophp ). That is intentional and will remain transparent, including the origin and licensing of the code.
When code is generally useful beyond XMRPay, I am happy to contribute the reusable parts upstream so they can live in the appropriate Monero Integrations project. I do not want community integrations to become unnecessarily dependent on a project controlled only by me.
I have also received a lot of support, testing, feedback and encouragement from the Monero community. I would like to return that support by helping maintain these projects over the long term.
What I am requesting
I would like repository-scoped Write access, beginning with monerowhmcs or whatever the community thinks is a good fit, so I can handle routine maintenance, compatibility patches, tests, CI, documentation and other smaller fixes.
If monerowp #132 is independently reviewed and accepted, I would also be willing to take responsibility for maintaining monerowp afterward.
I am not requesting access so I can merge my currently pending work myself.
The decisions on monerowp #132 and moneromagento #15 should remain with the existing maintainers and reviewers.
For the routine maintenance, Write access would allow me to prepare, test and merge straightforward fixes without requiring another maintainer to perform the final repository action every time.
Changes involving cryptography, payment detection, settlement behavior, shared architecture or protocol compatibility should still receive independent review.
AI and testing
I use AI extensively and openly during development. This is visible throughout my repositories and commit history.
AI is used for implementation, review, testing, adversarial analysis and finding edge cases.
The code is not considered correct simply because one or more models agree with it.
Depending on the change, validation includes regression tests, adversarial tests, fuzz and property tests, stress and reorg scenarios, parity checks between implementations, CI, real stagenet payments and working platform sandboxes.
Whatever I submit remains my responsibility.
When review identifies a problem, I address it and test the result again.
Existing and future bounties
The WHMCS and Magento work started as existing Monero Bounties before this proposal. They should remain separate from any maintainer role and be reviewed under their original criteria.
For any future bounty involving a repository I help maintain, I would disclose my role and would not participate in defining the bounty, reviewing my own submission, deciding acceptance or approving payout.
I would only participate when there is public pre-approval and an independent reviewer. Otherwise, I would abstain from that bounty.
Funding
I am offering this maintenance work voluntarily and without requesting CCS funding.
Anyone who wants to support my independent work may still do so, but donations would have no relationship to repository access, reviews, merges or technical decisions.
Hi everyone,
I am SlowBearDigger, and I would like to volunteer to help maintain Monero Integrations.
have been doing more work around Monero merchant integrations, I enjoy it, and I would like to take responsibility for keeping that work functional and maintained inside the community repositories.
Work so far / things I have done
My current work includes:
Some of this integration work reuses compatible open-source components developed for XMRPay (thanks to monerophp ). That is intentional and will remain transparent, including the origin and licensing of the code.
When code is generally useful beyond XMRPay, I am happy to contribute the reusable parts upstream so they can live in the appropriate Monero Integrations project. I do not want community integrations to become unnecessarily dependent on a project controlled only by me.
I have also received a lot of support, testing, feedback and encouragement from the Monero community. I would like to return that support by helping maintain these projects over the long term.
What I am requesting
I would like repository-scoped Write access, beginning with monerowhmcs or whatever the community thinks is a good fit, so I can handle routine maintenance, compatibility patches, tests, CI, documentation and other smaller fixes.
If monerowp #132 is independently reviewed and accepted, I would also be willing to take responsibility for maintaining monerowp afterward.
I am not requesting access so I can merge my currently pending work myself.
The decisions on monerowp #132 and moneromagento #15 should remain with the existing maintainers and reviewers.
For the routine maintenance, Write access would allow me to prepare, test and merge straightforward fixes without requiring another maintainer to perform the final repository action every time.
Changes involving cryptography, payment detection, settlement behavior, shared architecture or protocol compatibility should still receive independent review.
AI and testing
I use AI extensively and openly during development. This is visible throughout my repositories and commit history.
AI is used for implementation, review, testing, adversarial analysis and finding edge cases.
The code is not considered correct simply because one or more models agree with it.
Depending on the change, validation includes regression tests, adversarial tests, fuzz and property tests, stress and reorg scenarios, parity checks between implementations, CI, real stagenet payments and working platform sandboxes.
Whatever I submit remains my responsibility.
When review identifies a problem, I address it and test the result again.
Existing and future bounties
The WHMCS and Magento work started as existing Monero Bounties before this proposal. They should remain separate from any maintainer role and be reviewed under their original criteria.
For any future bounty involving a repository I help maintain, I would disclose my role and would not participate in defining the bounty, reviewing my own submission, deciding acceptance or approving payout.
I would only participate when there is public pre-approval and an independent reviewer. Otherwise, I would abstain from that bounty.
Funding
I am offering this maintenance work voluntarily and without requesting CCS funding.
Anyone who wants to support my independent work may still do so, but donations would have no relationship to repository access, reviews, merges or technical decisions.