Implement Blind Transfers
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- blockchain
Research direction
Start with the unchecked items in the issue breakdown and review the linked secp256k1prp, graphene_pr65, and fee_calc work. The issue names no repository files or tests, so identify the relevant Storage, GrapheneObject, and fee-calculation entry points before proceeding. Done means the remaining checklist items are implemented and blind transfers work end to end.
Written by the indexing model from the issue text.
Description
After shedding some tears, I've managed to get blind transfers working. Sadly, the whole affair is not a matter of a simple/single pull-request. (Although if you think otherwise, please take a look here)
Here's the breakdown:
- PrivateKey class needs a few new crypto methods. graphene_pr64
- PublicKey class needs a few new crypto methods (secp256k1 dependency there). graphene_pr66
- Pedersen/Rangeproof commitments must be implemented. I've wrapped libsecp256k1-zkp from bitshares-core to do this. secp256k1prp (Ideally, a pure-python implementation is required)
- Storage class must be expanded to keep the receipts/balances.
- Few
GrapheneObjects must be read from wire bytestream back into memory. graphene_pr65 - Local fee calculator must be added. fee_calc
- Dominant language
- Python
- Stars
- 162
- Forks
- 164
- PR merge metrics
- No merged PRs in 30d
Contributor 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 bitshares/python-bitshares
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
bitshares/python-bitshares#331 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
bitshares/python-bitshares#320 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
bitshares/python-bitshares#316 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
bitshares/python-bitshares#315 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
bitshares/python-bitshares#314 ·
All issues in bitshares/python-bitshares
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·