Convex-Dev / Convex-Dev/convex
String rendering specification and controls
Open
Nobody has claimed this yet.
enhancement
question
security
- Dominant language
- Java
- Stars
- 117
- Forks
- 47
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 5
Description
We need to place defined rules on String rendering in the CVM with str and related functions.
Requirements:
- Rendering must be deterministic and fully defined for all CVM Objects
- The cost of String generation must be accurately calculated and controlled, since it can be triggered for arbitrary CVM values in CVM code. (e.g.
*state*). - There must not be a DoS attack when string rendering may be externally triggered, e.g. when printing error traces.
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.
Research direction
Start by locating the CVM str and related functions, then trace how arbitrary values such as *state* and error traces can trigger rendering. Done means rendering is deterministic and defined for all CVM Objects, its cost is accurately controlled, and externally triggered rendering cannot cause a denial of service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100