massa
massa copied to clipboard
The Decentralized and Scaled Blockchain
**Describe the bug** When we call `add_staking_secret_keys` with an array of strings as parameters, we got this error: ```json { "jsonrpc": "2.0", "error": { "code": -32602, "message": "Invalid params: invalid...
# Redundant information in the response. Separate `get_addresses` to some different methods, and add pagination like: The main problem, `get_addresses` returns too much information, if we will request in batch...
We have some methods naming inconsistency between client/server. E.g `node_add_staking_secret_keys` in massa-client vs `add_staking_secret_keys` in massa-node. **Expected behavior** We should define a clear naming convention for public interfaces methods.
Nodes use around ~7-8 Go of RAM in the testnet under 3 ktxps. It was as high as 15 Go when the testnet was unstable. We need to investigate where...
If an operation is strictly bigger than MAX_BLOCK_SIZE, it is considered invalid => ignore and ban sender
## Rationale Block producers consume the following resources when adding an operation `op` to their block: * block space: capacity = MAX_BLOCK_SIZE, consumed: `op.serialized_data.len()` * block gas: capacity = MAX_BLOCK_GAS,...
Let's see this example : ``` block size = 1000 max gas per block = 1000 priority = (max_gas * gas_price + fee) / size Operation 1: max_gas = 1000...
Migrate [jsonrpc](https://github.com/paritytech/jsonrpc/) is deprecated and not maintained to [jsonrpsee](https://github.com/paritytech/jsonrpsee).