lapce / lapce/lapdev

Crypto

Open
#12 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
2k
Forks
58
PR merge metrics
No merged PRs in 30d

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Domain
cloud, payments
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.