Brian Anderson
Brian Anderson
Just an idea. For some chains we are reporting inaccurate numbers and some chains regularly fail to keep up with block production. For each of these put a little github...
We are reporting stellar "operations", but operations are performed in a single atomic transaction. In this way stellar is like solana, but on solana we are reporting the transaction count,...
It's not clear what happens if a job panics. In https://github.com/Aimeedeer/realtps/issues/64 a job might have panicked. Probably it should be similar to when a job errors. Log something, wait a...
In the logs I see: ``` log/realtps-import.5.log:2022-10-31T11:49:48.719739180+00:00 INFO realtps_import::import - importing at least 3 blocks for chain karura log/realtps-import.5.log:2022-10-31T11:49:48.719747368+00:00 DEBUG realtps_import::helpers - fetching block 2965699 for chain karura log/realtps-import.5.log:2022-10-31T11:49:49.063628198+00:00 WARN...
Similar to stellar. https://xrpl.org/http-websocket-apis.html
I don't fully understand what it is but https://www.rosetta-api.org/ appears to be a standardized protocol for requisting block information, supported by a number of chains we don't have clients for....
As more people look at realtps and more chains are included, with more differing transaction models, we're going to need to be more specific about what we track. What we...
There's probably a memory leak in the import job. Recently the entire machine came down after the import process was killed, and just now I see it is using 30%...
We're tweaking the block_pace and rescan_delay for many chains now, and that configuration is hidden in the code. Change rpc_config.yml to be chain_config.yml and specify block_pace and rescan_delay there, allowing...
The import logic does not handle the case where our entire loaded chain is reorged. Here's the logic: ```rust let block_number_to_fetch_next = if let Some(prev_stored_block) = prev_stored_block { let chain_reorg...