spike(payments): Stripe Connect stablecoin payouts for workers vs on-chain payouts
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 66/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- payments
Research direction
Read Stripe's Connect stablecoin payout documentation and compare it with the on-chain payout approach in issue #8, covering onboarding and KYC, countries, fees, supported networks, custody, and failure modes. Recommend Connect only, on-chain only, or worker's choice, and open follow-up implementation issues if justified. Done means the comparison and recommendation are written.
Written by the indexing model from the issue text.
Description
Summary
Compare paying worker earnings through Stripe Connect stablecoin payouts against our own on-chain payouts.
Estimated size: S
Motivation
Connect payouts could cover KYC and off-ramp for workers, but add a Stripe account requirement and fees.
Proposal
- Read Stripe's Connect stablecoin payout docs (https://docs.stripe.com/connect/stablecoin-payouts) and compare with #8: onboarding and KYC, countries, fees, supported networks, custody, failure modes.
- Recommend one of: Connect only, on-chain only, or worker's choice.
Acceptance criteria
- A written comparison and recommendation.
- Follow-up implementation issues opened if justified.
Dependencies
- #8
- #10 (Connect phase)
Part of #1 (see also #10). Ground rules for all issues in this roadmap are listed there (testnet-first, no secrets in the repo, chain logic behind the registry, tests and docs with every PR).
- Dominant language
- Python
- Stars
- 2
- Forks
- 4
- Avg merge
- 6h 54m
- Merged PRs (30d)
- 7
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from QMeshPy/distributed-quantum
-
enhancement good first issue helia storage tier-1
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
QMeshPy/distributed-quantum#53 ·
Maintainers usually reply within 1 day
-
chain-integration enhancement payments research-spike tier-2
Difficulty 4/5 3-5 days Newbie friendliness 55/100
QMeshPy/distributed-quantum#78 ·
Maintainers usually reply within 1 day
-
chain-integration enhancement payments tier-2
Difficulty 5/5 Over a week Newbie friendliness 35/100
QMeshPy/distributed-quantum#76 ·
Maintainers usually reply within 1 day
-
documentation good first issue kubo storage tier-1
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
QMeshPy/distributed-quantum#75 ·
Maintainers usually reply within 1 day
-
enhancement kubo storage tier-2
Difficulty 4/5 3-5 days Newbie friendliness 56/100
QMeshPy/distributed-quantum#74 ·
Maintainers usually reply within 1 day
All issues in QMeshPy/distributed-quantum
Similar issues
-
[Bug]: Revit selector reads process ids 2000-2099 as years (flaky AgentClientTests.AYearOrAProcessIdSelectsTheHost)Possibly taken @Wurschdhaud claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
pyrevitlabs/pyRevit#3817 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
521xueweihan/HelloGitHub#4074 ·
-
follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Helm chart: allow setting ingressClassName on the IngressPossibly taken @commarla claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
pgadmin-org/pgadmin4#10658 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100