a7bff26fd6
Bumps [wandalen/wretry.action](https://github.com/wandalen/wretry.action) from 3.5.0 to 3.7.0. <details> <summary>Commits</summary> <ul> <li><a href="f8754f7974"><code>f8754f7</code></a> version 3.7.0</li> <li><a href="03db9837ed"><code>03db983</code></a> Merge pull request <a href="https://redirect.github.com/wandalen/wretry.action/issues/171">#171</a> from dmvict/docker_readme</li> <li><a href="d80901cd5c"><code>d80901c</code></a> Sync readme for new feature</li> <li><a href="e00d406ade"><code>e00d406</code></a> version 3.6.0</li> <li><a href="e00deaa9ba"><code>e00deaa</code></a> Merge pull request <a href="https://redirect.github.com/wandalen/wretry.action/issues/170">#170</a> from dmvict/pre_retry_action</li> <li><a href="8b50f3152e"><code>8b50f31</code></a> Update action, add option <code>pre_retry_command</code> to run command between retries</li> <li><a href="990f16983d"><code>990f169</code></a> Merge pull request <a href="https://redirect.github.com/wandalen/wretry.action/issues/167">#167</a> from Vampire/add-typing</li> <li><a href="aeb34f4d13"><code>aeb34f4</code></a> Add action typing</li> <li>See full diff in <a href="https://github.com/wandalen/wretry.action/compare/v3.5.0...v3.7.0">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Alex Kremer <akremer@ripple.com>
Clio
Clio is an XRP Ledger API server optimized for RPC calls over WebSocket or JSON-RPC. It stores validated historical ledger and transaction data in a more space efficient format, and uses up to 4 times less space than rippled.
Clio can be configured to store data in Apache Cassandra or ScyllaDB, enabling scalable read throughput. Multiple Clio nodes can share access to the same dataset, which allows for a highly available cluster of Clio nodes without the need for redundant data storage or computation.
📡 Clio and rippled
Clio offers the full rippled API, with the caveat that Clio by default only returns validated data. This means that ledger_index defaults to validated instead of current for all requests. Other non-validated data, such as information about queued transactions, is also not returned.
Clio retrieves data from a designated group of rippled nodes instead of connecting to the peer-to-peer network.
For requests that require access to the peer-to-peer network, such as fee or submit, Clio automatically forwards the request to a rippled node and propagates the response back to the client. To access non-validated data for any request, simply add ledger_index: "current" to the request, and Clio will forward the request to rippled.
Note
Clio requires access to at least one
ripplednode, which can run on the same machine as Clio or separately.
📚 Learn more about Clio
Below are some useful docs to learn more about Clio.
For Developers:
For Operators:
General reference material:
🆘 Help
Feel free to open an issue if you have a feature request or something doesn't work as expected. If you have any questions about building, running, contributing, using Clio or any other, you could always start a new discussion.