docs(v2): Rollups 2.0 migration, community tools, and self-hosted updates - #353
docs(v2): Rollups 2.0 migration, community tools, and self-hosted updates#353riseandshaheen wants to merge 4 commits into
Conversation
📖 Docs preview is readyPreview: https://cartesi.github.io/docs/pr-preview/pr-353/ Built from commit |
…ted guides Align v2.0 docs with JSON-RPC, unified outputs, and the current community stack; refresh lastUpdated markers on reviewed pages.
5cb4f72 to
08cc5d5
Compare
Update Application, portals, consensus, and withdrawal docs for input-box DA, claim staging, MachineValidityProof, Erc portal renames, deposit refunds, and GitHub release artifacts; point contract links at alpha.9. Co-authored-by: Cursor <cursoragent@cursor.com>
Align Authority-first EW deploy, recovery caveats, and compose with the validated Sepolia flow, and drop alpha-specific intro noise and a stale migration note. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
| $SALT \ | ||
| --rpc-url "$RPC_URL" | ||
| ``` | ||
| 1. Relay the application address using `DAppAddressRelay`. |
There was a problem hiding this comment.
I think this was also true for other assets, right? ERC1155 and ERC721
|
|
||
| :::warning Production Warning | ||
| **This self-hosted approach should NOT be used in _production_.** | ||
| This guide explains how to run a Cartesi Rollups node locally on your machine for development and testing on **testnet**. |
There was a problem hiding this comment.
I'm thinking if we should have an alternate section on how to deploy an application with step by step
- calculateAddresses
- newApplication
- deployContracts
as alternatives
Do you think a section should be added here somewhere?
|
|
||
| ### Use dedicated database roles | ||
|
|
||
| The sample compose shares one Postgres role (`postgres`) and one database (`rollupsdb`). For any longer-lived deployment, create a dedicated database user per service, grant only the tables that service needs, and do not use the superuser in application containers. Give Postgres a named volume, and back it up. Inputs live in the InputBox on L1, so a node can be rebuilt from chain plus the **exact** snapshot that produced the registered template hash — keep that published snapshot, not only a local rebuild. |
There was a problem hiding this comment.
Worth adding a defense-in-depth note here: give each role a Postgres CONNECTION LIMIT (and run the public JSON-RPC/inspect API under a read-only role with a low limit) so external read traffic can't exhaust max_connections and starve the pipeline services. As a redundant client-side bound you can also cap the pool in the DSN with ?pool_max_conns=N on CARTESI_DATABASE_CONNECTION.
| "type": "link", | ||
| "label": "PRT", | ||
| "href": "https://arxiv.org/abs/2212.12439" | ||
| } |
There was a problem hiding this comment.
https://cartesi.io/cartesi_whitepaper.pdf
Cartesi whitepaper could be added here too
|
Great work! |
2 participants
Summary