wavesplatform / wavesplatform/gowaves
[V1.2][RIDE V4] Change run-time limits of RIDE functions
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 251
- Forks
- 73
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 28
Description
Specification
Data limits:
- String and ByteVector constructors - DataEntry value limit (32767 bytes)
- String and ByteVector concatenation - DataEntry value limit (32767 bytes)
- DataEntry key size - 400 bytes (as for protobuf Data transaction, instead of current 100 bytes)
- max available ByteVector - (106 + 165890) = 165996 bytes (body bytes of protobuf Data transaction)
Functions:
- sigVerify message - no limit (indirectly Data Transaction protobuf max size)
- rsaVerify message - no limit (indirectly Data Transaction protobuf max size)
Naming limits:
- user function and variable names length - 255 bytes (as for Callable functions)
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
Start by locating the RIDE V4 implementations for data construction and concatenation, DataEntry handling, signature verification, and user-function or variable naming. Compare those entry points with the protobuf Data transaction size rules mentioned in the specification. Done means all listed data, message, and naming limits are enforced consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100