Crypto
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
No files, tests, or implementation entry points are identified. Start by turning the cryptocurrency and privacy proposal into concrete requirements and acceptance criteria; done would require an agreed scope and a maintainer decision.
Written by the indexing model from the issue text.
Description
Not an issue, but there's no discussion section.
Codespaces, gitpod, etc, are too big to allow crypto.
Many developers want to have something like this, but don't like their bank being drained each month, or simply want privacy.
I suspect there is a strong void to fill here which would set lapdev apart. This would entice me (and a few other devs I know) to pay for it.
- Dominant language
- Rust
- Stars
- 2k
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 lapce/lapdev
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
HAXE SUPPORT Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Docker Swarm Support Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
Similar issues
-
bug CLI custom-model
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
rust-bitcoin/rust-bitcoin#6930 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fulcrumgenomics/ferro-hgvs#2251 ·
-
A-allocators A-docs C-enhancement T-libs
Difficulty 2/5 1-3 hours Newbie friendliness 75/100