eosio-enterprise / eosio-enterprise/chappe
Enable custom message types rather than just the random one
Open
- Dominant language
- Go
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
Research direction
The issue has no body, file names, tests, or entry points. Start by reading the repository structure and existing message-generation code to determine how the random message type is selected; the scope and completion criteria for supporting custom message types need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100