What problem does your feature solve?
The current config_setting table is missing settings that were added to the XDR during the protocol 23 release. The full XDR includes three new keys, however the Hubble table stops parsing at EvictionIterator
What would you like to see?
Update the config_setting schema to parse the following structures under ConfigSetting ledger entry type:
ContractParallelCompute - one new field: LedgerMaxDependentTxClustersContractLedgerCostExt - 2 fields: TxMaxFootprintEntries and FeeWrite1Kb. Caution, this field also shows up under ContractLedgerCost. We may need to research how and if this field is differentContractScpTiming - 5 new fields:
- LedgerTargetCloseTimeMilliseconds
- NominationTimeoutInitialMilliseconds
- NominationTimeoutIncrementMilliseconds
- BallotTimeoutInitialMilliseconds
- BallotTimeoutIncrementMilliseconds
This requires code changes to the following files:
Shout out to @drebelsky for discovering this!
What problem does your feature solve?
The current
config_settingtable is missing settings that were added to the XDR during the protocol 23 release. The full XDR includes three new keys, however the Hubble table stops parsing atEvictionIteratorWhat would you like to see?
Update the
config_settingschema to parse the following structures underConfigSettingledger entry type:ContractParallelCompute- one new field:LedgerMaxDependentTxClustersContractLedgerCostExt- 2 fields:TxMaxFootprintEntriesandFeeWrite1Kb. Caution, this field also shows up underContractLedgerCost. We may need to research how and if this field is differentContractScpTiming- 5 new fields:This requires code changes to the following files:
Shout out to @drebelsky for discovering this!