diff --git a/src/openrpc/chains/_components/custom/methods.yaml b/src/openrpc/chains/_components/custom/methods.yaml index f47798a0d..a7ab3aaf8 100644 --- a/src/openrpc/chains/_components/custom/methods.yaml +++ b/src/openrpc/chains/_components/custom/methods.yaml @@ -2328,9 +2328,9 @@ components: ledgerRetentionWindow: { type: integer } example: status: "healthy" - latestLedger: 50000 - oldestLedger: 1 - ledgerRetentionWindow: 17280 + latestLedger: 64107174 + oldestLedger: 63070374 + ledgerRetentionWindow: 1036800 examples: - name: getHealth example params: [] @@ -2366,7 +2366,10 @@ components: getTransaction: name: getTransaction summary: Get transaction - description: Returns the details and status of a submitted transaction by its hash. + description: |- + Returns the details and status of a submitted transaction by its hash. + + Stellar-RPC will support querying within a maximum 60 days of recent ledgers. paramStructure: by-name x-compute-units: 40 params: @@ -2395,7 +2398,7 @@ components: - name: getTransaction example description: | Looks up a real successful Stellar mainnet transaction. Stellar RPC retains transactions - for ~14 days, so this hash will eventually age out and need to be replaced with a fresher one. + for ~60 days, so this hash will eventually age out and need to be replaced with a fresher one. params: - name: hash value: "86d85a0db4d7cdf2aa8e4b633e050e8c3c138deae7cac62ff4d4ff5fb732fe96" @@ -2403,7 +2406,10 @@ components: getTransactions: name: getTransactions summary: Get transactions - description: Returns a paginated list of transactions from the network. + description: |- + Returns a paginated list of transactions from the network. + + Stellar-RPC will support querying within a maximum 60 days of recent ledgers. paramStructure: by-name x-compute-units: 50 params: @@ -2438,7 +2444,7 @@ components: - name: getTransactions example description: | Returns one transaction starting at a recent mainnet ledger. Stellar RPC keeps roughly - the last 14 days of transactions; if the example ledger has aged out, replace `startLedger` + the last 60 days of transactions; if the example ledger has aged out, replace `startLedger` with a value within the current retention window (see `oldestLedger` from `getHealth`). params: - name: startLedger diff --git a/src/openrpc/chains/_components/stellar/methods.yaml b/src/openrpc/chains/_components/stellar/methods.yaml index edff3da3c..7b537a505 100644 --- a/src/openrpc/chains/_components/stellar/methods.yaml +++ b/src/openrpc/chains/_components/stellar/methods.yaml @@ -7,7 +7,7 @@ components: description: |- Clients can request a filtered list of events emitted by a given ledger range. - Stellar-RPC will support querying within a maximum 7 days of recent ledgers. + Stellar-RPC will support querying within a maximum 60 days of recent ledgers. Note, this could be used by the client to only prompt a refresh when there is a new ledger with relevant events. It should also be used by backend Dapp components to "ingest" events into their own database for querying and serving. @@ -114,7 +114,7 @@ components: description: | Returns up to 2 native XLM `transfer` contract events emitted from the Stellar Asset Contract (`CAS3J7GYLGXMF6TDJBBYYSE3HQ6BBSMLNUQ34T6TZMYMW2EVH34XOWMA`) starting near the current head. - Stellar RPC retains roughly the last 7 days of events, so `startLedger` may need to be bumped + Stellar RPC retains roughly the last 60 days of events, so `startLedger` may need to be bumped forward over time. The first topic `AAAADwAAAAh0cmFuc2Zlcg==` is the SCV-encoded `transfer` symbol. params: - name: startLedger @@ -494,7 +494,7 @@ components: - name: Two ledgers from a stable historical sequence description: | Returns two consecutive ledger summaries starting at sequence 60,000,000. - Unlike `getEvents` and `getTransactions` (which retain ~7 and ~14 days respectively), + Unlike `getEvents` and `getTransactions` (which retain ~60 days), Alchemy's Stellar mainnet RPC retains full ledger history back to genesis (ledger 2), so this example is stable indefinitely. params: