diff --git a/404.html b/404.html index 7e3ddc7bc..33b845957 100644 --- a/404.html +++ b/404.html @@ -4,7 +4,7 @@
$ starknet-devnet --dump-on block --dump-path <PATH>
--dump-on request
on startup. You can request dumping by sending POST
to /dump
or via JSON-RPC:--dump-on request
on startup. You can request dumping by sending POST
to /dump
or via JSON-RPC. Body is not required. Optionally custom path to a file can be provided.$ starknet-devnet --dump-on exit --dump-path <DEFAULT_PATH>
POST /dump
JSON-RPC
{
"jsonrpc": "2.0",
"id": "1",
"method": "devnet_dump"
}
POST /dump
{
// optional; defaults to the path specified via CLI if defined
"path": <PATH>
}
JSON-RPC
{
"jsonrpc": "2.0",
"id": "1",
"method": "devnet_dump",
"params": {
// optional; defaults to the path specified via CLI if defined
"path": <PATH>
}
}
If a dump path is not provided either via --dump-path
or in the request, the dump is included in the response body. This means that if you request dumping via curl, it will be printed to STDOUT, which you can then redirect to a destination of your choice.
GET /predeployed_accounts?[with_balance=true]
Alternatively, send a JSON-RPC request:
+JSON-RPC
{
"jsonrpc": "2.0",
"id": "1",
"method": "devnet_getPredeployedAccounts"
}
JSON-RPC
{
"jsonrpc": "2.0",
"id": "1",
"method": "devnet_getPredeployedAccounts",
"params": {
// optional; defaults to false
"with_balance": true | false
}
}