bigchaindb / bigchaindb/cryptoconditions
Could Ed25519Fulfillment.sign() message arg be a string instead of bytes, or both?
Open
proposal
question
- Dominant language
- Python
- Stars
- 73
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Support for strings would be convenient.
Contributor guide
Research direction
Start by reading Ed25519Fulfillment.sign() and tracing how its message argument is used by existing callers. Check the current behavior for bytes, then define and test the expected behavior for string input. Done means string support is added without breaking existing byte-message behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100