Impl Parameterized Deploys: Native Typed Parameters Support

[AndriiS-DevBrother]

Adds support for passing typed parameters (boolean, integer, string, bytes) directly to Rholang terms via URI-based injection, eliminating manual hex encoding for binary data.

Production Changes

Protocol (CasperMessage.proto)

• New RholangValue message: union of bool_value, int_value, string_value, bytes_value
• New DeployParameter message: named parameter with typed value
• Extended DeployDataProto with repeated DeployParameter parameters = 13

Scala Implementation

• RholangValueData / DeployParameterData: Domain models with validation
  • Max 50 parameters per deploy
  • Parameter names: alphanumeric + underscore, max 256 chars
  • String limit: 1MB, Bytes limit: 256MB
• NormalizerEnv: Injects parameters as rho:deploy:param:<name> URIs
• JSON API: Schema derivations for REST API support

Tests

New Scala Tests

Test File	Coverage
ParametrizedDeployDataSpec.scala	Validation, serialization, proto conversion for all parameter types
NormalizerEnvParametrizedSpec.scala	Parameter injection, value-to-Par conversion
MultiParentCasperDeploySpec.scala	Deploy API integration with parameters

New Python Integration Tests

Test	Description
test_deploy_binary_data_via_parameter	E2E test: 100KB binary data via parameters
test_deploy_encoded_binary_data	Baseline hex encoding comparison

Usage

new stdout(`rho:io:stdout`),
                myData(`rho:deploy:param:myData`),
                myInt(`rho:deploy:param:myInt`),
                myString(`rho:deploy:param:myString`),
                myBytes(`rho:deploy:param:myBytes`),
                myBool(`rho:deploy:param:myBool`)
            in {
                stdout!([ "accessing bytes", *myData.length()]) |
                stdout!([ "accessing int", *myInt]) |
                stdout!([ "accessing string", *myString]) |
                stdout!([ "accessing bool", *myBool])
            }

binary_data_length = 5 * 1024 * 1024  # 5MB
binary_data = bytes(i % 256 for i in range(binary_data_length))

parameters={"myData": binary_data, "myInt": 123, "myString": "test", "myBytes": binary_data, "myBool": True}

The usage of this new api is represented in integration-tests/test/test_parametrized_deploydata.py

Expected stdout:

["accessing bool", true]
["accessing int", 123]
["accessing string", "test"]
["accessing bytes", 5242880]

Breaking Changes

None. The parameters field is optional and defaults to empty.

[spreston8]

Nice work. Pretty much all my comments are just improvements in test coverage for these changes. I think implementing some of them would ensure robustness.

[YuriiO-DevBrother]

LGTM

[YuriiO-DevBrother]

Could this increase in 100x could be handled by nodes properly. As for me it seems like a huge exponential increase which potentially could be hard to achieve in practice. Taking into account that max binary size is limited to 256MB and MaxParameters number limited to 50 the increase to max value of 15GB should be enough.

[nashef]

You should store the large files on disk and then put the filename in LMDB. Otherwise your 256MB writes to the LMDB will block all other threads that want to make changes.