nervosnetwork / nervosnetwork/neuron
[FR] Allow CCC DApps to use Neuron for identity and signatures
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 204
- Forks
- 95
- Avg merge
- 8d 9h
- Merged PRs (30d)
- 4
Description
Hello Neuron folks,
Could you consider letting CCC-enabled websites use Neuron for identity and signatures?
Would this make sense for Neuron?
Keep up the Great Work,
Phroi
P.S.: The original request also included sharing Neuron's embedded Light Client. After the Quantum Purse discussion and working through how DApps could have their own Light Client, I would now keep Neuron's Light Client internal. Related issues: Quantum Purse #119, CCC #357, and Pocket Node #430.
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.
Research direction
No implementation files, tests, or entry points are identified. Start by reviewing the linked CCC #357, Quantum Purse discussion, and Cellora discussion to establish the intended identity and signature integration boundaries. Done requires an agreed scope and concrete acceptance criteria for CCC DApps using Neuron.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, blockchain, cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100