You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an issue in the validator change metada storage
there is no size limit on the size you could store in the validator metadata fields
email / discordid / description / website / avatar
I think it may lead to problems, storage oversize, waste of BC space.
I made some tests on the the only limitation I had was the tx max size, but I was able to store 1MB of "A" in the description field
but my local campfire did not crashed
I have a client that writes the 1MB of data in the desciption field you need it
just hacked cli.rs to send 1MB instead of the command line arg it received
I think you should truncate the data to whatever size you think is good for the different fields
note: the class S bug has been reported this night
moniker Lankou
memo tpknam1qp657jtd7tzkadzua0wqr6f5cewrlrah08fn7ny92vcfjuh3lcehvnspw8y
The text was updated successfully, but these errors were encountered:
There is an issue in the validator change metada storage
there is no size limit on the size you could store in the validator metadata fields
email / discordid / description / website / avatar
I think it may lead to problems, storage oversize, waste of BC space.
namada/crates/proof_of_stake/src/storage.rs
Line 680 in 2535c9c
I made some tests on the the only limitation I had was the tx max size, but I was able to store 1MB of "A" in the description field
but my local campfire did not crashed
I have a client that writes the 1MB of data in the desciption field you need it
just hacked cli.rs to send 1MB instead of the command line arg it received
![image](https://private-user-images.githubusercontent.com/4283686/309746045-a0ad7fa9-503e-47d9-81fe-fa3dc679e127.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2MTExMDksIm5iZiI6MTczOTYxMDgwOSwicGF0aCI6Ii80MjgzNjg2LzMwOTc0NjA0NS1hMGFkN2ZhOS01MDNlLTQ3ZDktODFmZS1mYTNkYzY3OWUxMjcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxNSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTVUMDkxMzI5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDlhNDAyNmEyYzE0N2FiZDc1ZWZmNTk5ODQxZGUyNDk4OTA4YjZjYjViODQ4ZDJkYWQ2NTE0MDgzNTU1YTU1MSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.LX0xrh0_dtLRbOUYSyosGMhmL8R515RjHfeDgD5T2Yk)
I think you should truncate the data to whatever size you think is good for the different fields
note: the class S bug has been reported this night
moniker Lankou
memo tpknam1qp657jtd7tzkadzua0wqr6f5cewrlrah08fn7ny92vcfjuh3lcehvnspw8y
The text was updated successfully, but these errors were encountered: