Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xmrSale Payment Processor Development - 30XMR #1

Closed
3 tasks done
plowsof opened this issue Jan 23, 2023 · 2 comments
Closed
3 tasks done

xmrSale Payment Processor Development - 30XMR #1

plowsof opened this issue Jan 23, 2023 · 2 comments
Labels
research not enough is known about the issue / people involved resolve a plan for resolving stagnant ccs proposals / redistributing the remaining funds

Comments

@plowsof
Copy link
Owner

plowsof commented Jan 23, 2023

  • Agree that the proposal has been abandoned long enough
  • Close it
  • Decide what to do with the remaining funds

Details to follow:
https://github.com/xmrsale/xmrSale 10 months last commit
https://xmrsale.org/ site has lost some functionality (donate example) signs of nobody home?
https://ccs.getmonero.org/proposals/xmrsale-2021.html history of going missing for several months shown in the comments

Current state of paymentGateways:
https://monerica.com/#merchant-services

my suggestion is to put the funds toward AcceptXMR - why and what? i will have to justify this but briefly,

  • community member who has contributed already to the ecosystem / created a similar project but with advantages
  • the main milestones of XMRsale have been achieved
  • it is now abandonware and fell behind the project it was forked from.
  • xmrSale is using monero-wallet-rpc (AND javascript) which is not the most reliable thing for using a remote node with
  • acceptxmr is NOT using blockexporer api. it can be pointed at any remote node. it does NOT use monero-wallet-rpc but instead its own rpc calls implemented here (viewkey/primary address only)
  • written in 'Rust' - our chance to support a none cpp developer in the ecosystem
  • acceptxmr can work with/without javascript

I must discuss the possibility of this with BusyBoredom (what we can get for 30XMR) - and the end result must be equal to what xmrsale provides OR better with some maintenance built in e.g. 80/20 split 24 xmr for tasks and 6 for maintenance

@plowsof plowsof added the resolve a plan for resolving stagnant ccs proposals / redistributing the remaining funds label Jan 23, 2023
@plowsof plowsof changed the title xmrSale Payment Processor Development 30XMR xmrSale Payment Processor Development - 30XMR Jan 23, 2023
@plowsof plowsof added the research not enough is known about the issue / people involved label Jan 25, 2023
@plowsof
Copy link
Owner Author

plowsof commented Feb 6, 2023

BusyBoredom of AcceptXMR has made a draft CCS https://repo.getmonero.org/monero-project/ccs-proposals/-/merge_requests/374

If the community see fit, this proposal can be merged directly to the WIP list, after closing xmrSale. AcceptXMR will then be funded entirely by the remaining funds of xmrSale.

@plowsof
Copy link
Owner Author

plowsof commented Mar 13, 2023

AcceptXMR moved to funding https://ccs.getmonero.org/proposals/busyboredom-standalone-acceptxmr.html , once funded this will close this issue

@plowsof plowsof closed this as completed Mar 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
research not enough is known about the issue / people involved resolve a plan for resolving stagnant ccs proposals / redistributing the remaining funds
Projects
None yet
Development

No branches or pull requests

1 participant