blocknodehub
blocknodehub
encounter the same problem
we have the same problem.
> thanks for reporting, we'll be looking into it I also have this problem, you can't get trace data through the transaction hash, but you can get trace data through...
However, there is no snapshot data for the latest version (oasis-4)
I used statesync to start up, but I couldn't sync the data Config: mode: client common: data_dir: /mnt/rosemain/node/data log: format: JSON level: cometbft: info cometbft/context: error default: info consensus: state_sync:...
I see what this means, the pre-V4 data is almost completely discarded, but the block height does not start at 0. Thank you very much
> @blocknodehub seems like you are using slow disks. We recommend to use NVM SSD. @ianlapinskii where you this error? http-ton-api? But I have observed disk usage and the performance...
> @blocknodehub well, logs explicitly mentioned that operations (most of them disk intensive) are slow. Note, that for now IOPS are more important that overall read/write speed measured in bytes/sec....
> @blocknodehub well, logs explicitly mentioned that operations (most of them disk intensive) are slow. Note, that for now IOPS are more important that overall read/write speed measured in bytes/sec....