-
Notifications
You must be signed in to change notification settings - Fork 11
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
Proposed existing payment method editing process and estimated timelines #207
Comments
What kind of edits would this process apply to? |
Here is an example bisq-network/bisq#4809 |
Also I am yet to propose removing phone number on Revolut now username has been added. The phone number is now redundant. |
Also Western Union issues that are preventing it being multi-currency bisq-network/bisq#4757 (comment) |
And the proposal to disallow Transferwise SEPA accounts bisq-network/bisq#4698 |
I think phone numbers for Revolut are only for legacy reasons / backward compatibility. |
Thanks I had someone sending me a WhatsApp about a trade I completed with them over a month ago on Revolut. If there is a way to remove phone number that would be great. If not no problems. |
Here is my work process for existing payment methods that are in need of consideration for editing: https://github.com/users/pazza83/projects/3 For reference this is a list of all payment methods that are in available on Bisq: https://github.com/users/pazza83/projects/2 |
For reference: National Bank Transfer - BSB |
For reference : Bank ID leaking |
Proposed existing payment method editing process and estimated timelines
Part of the Payment Method Maintainer role is to oversee changes to existing payment methods.
The proposal is closely linked with the #206
I have documented my proposal below for discussion / comments.
The below proposal has just been created from my current understanding of the role and is therefore, a work in progress, I welcome any feedback.
0-30 days
User requests changes to existing payment method on Bisq channel; GitHub, Twitter, Reddit, Telegram, KeyBase, Bisq Community etc
User directed to create issue on Bisq-Network>Growth>Issues using a new template to be created, or in some instances Payment Method Maintainer will create it on their behalf.
Issue of changes to existing payment method to be discussed by all interested stakeholders with regards to if payment method changes better meet the ‘requirements of a payment method'
Payment Method Maintainer recommends one of the following:
31-60 days
If Payment Method Maintainer recommends against the proposed changes to the existing payment method then user can submit proposal to the DAO for a vote.
If Payment Method Maintainer recommends the proposed payment method to be implemented they will @bisq-network/mediators and @bisq-network/arbitrators informing them of the intention to implement the proposed changes to the payment method along with the proposed changes of requirements; limits, aging, signing requirement, required fields, etc.
If @bisq-network/mediators or @bisq-network/arbitrators have concerns these can be discussed.
61-90 days
If Payment Method Maintainer recommends against a payment method to be changes, or if the DAO vote against changes to a payment method, this will be documented on the payment methods roadmap.
If Payment Method Maintainer recommends a payment method to be changes, or if the DAO vote for changing a payment method, the payment method changes will be prioritized for addition and added to the roadmap. The Payment Method Maintainer will then:
0-150 days from payment method being added
Once payment method changes have been included added Payment Method Maintainer will, if required, liaise with @bisq-network/growth to promote the payment method on various channels; website, wiki, twitter, reddit, telegram, Bisq community etc.
Once the payment method changes are live Payment Method Maintainer will assist with any snagging required during its first 6 months.
Payment Method Maintainer will then report on status, KPIs, metrics of any payment methods changes.
The text was updated successfully, but these errors were encountered: