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
Protocol 23 comes with complicated state archival changes for which we will be delegating all state management to Captive Core. In particular, all the state querying will happen through HTTP calls to Captive Core.
As a side effect, we no longer need to manage state (i.e. ledger entry values). Thus we need to remove:
All state book-keeping code from the ingestion code.
The state table (ledger_entries) from the database. This will require a SQL migration. We should confirm the migration works with a full DB using pubnet to ensure there are no issues.
The (unreleased) --stellar-captive-core-http-query-port flag (currently defaulting to 0) since Captive Core's query port needs to be enabled by default for RPC to work. Alternatively, we can leave the flag but make it default to a non-zero value (note that even if we remove the flag, the value is still configurable by the captive core config file).
The text was updated successfully, but these errors were encountered:
More context: #353
Protocol 23 comes with complicated state archival changes for which we will be delegating all state management to Captive Core. In particular, all the state querying will happen through HTTP calls to Captive Core.
As a side effect, we no longer need to manage state (i.e. ledger entry values). Thus we need to remove:
ledger_entries
) from the database. This will require a SQL migration. We should confirm the migration works with a full DB using pubnet to ensure there are no issues.--stellar-captive-core-http-query-port
flag (currently defaulting to 0) since Captive Core's query port needs to be enabled by default for RPC to work. Alternatively, we can leave the flag but make it default to a non-zero value (note that even if we remove the flag, the value is still configurable by the captive core config file).The text was updated successfully, but these errors were encountered: