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
Stellar Core will have support a high-performance HTTP endpoint for retrieving ledger entries as part of their v22 in stellar/stellar-core#4350. Once stellar/go#5426 is complete, we can completely remove the implementation of getLedgerEntries and its database backing and replace it with a proxy to the Core client.
Acceptance Criteria
The database tables are dropped.
The implementation is a proxy to Core.
The returned JSON schema stays the same.
The performance is still acceptable.
The text was updated successfully, but these errors were encountered:
Shaptic
changed the title
Replace getLedgerEntries() implementation with a proxy to Core's /getledgerentrybulk.
Replace getLedgerEntries() with a proxy to Core's /getledgerentrybulk.
Aug 13, 2024
Shaptic
changed the title
Replace getLedgerEntries() with a proxy to Core's /getledgerentrybulk.
Replace getLedgerEntries() with a proxy to Core's /getledgerentry.
Aug 19, 2024
@2opremio this is blocked on Core actually providing this endpoint, but you can take it up if you want to assume the existence of Core's endpoint. I'm working on client support in stellar/go#5428 but again, no real Core yet.
Also note that we will still need entry ingestion + db snapshotting until P23.
Protocol 22: Replacing Endpoints
Epic: stellar/go#5433
References: Platform's issues for Protocol 22: projects/37#31
Stellar Core will have support a high-performance HTTP endpoint for retrieving ledger entries as part of their v22 in stellar/stellar-core#4350. Once stellar/go#5426 is complete, we can completely remove the implementation of getLedgerEntries and its database backing and replace it with a proxy to the Core client.
Acceptance Criteria
The database tables are dropped.
The implementation is a proxy to Core.
The returned JSON schema stays the same.
The performance is still acceptable.
The text was updated successfully, but these errors were encountered: