# op-reth import-receipts-op This imports non-standard RLP encoded receipts from a file. The supported RLP encoding, is the non-standard encoding used for receipt export in . Supports import of OVM receipts from the Bedrock datadir. ```bash $ op-reth import-receipts-op --help Usage: op-reth import-receipts-op [OPTIONS] Options: --datadir The path to the data dir for all reth files and subdirectories. Defaults to the OS-specific data directory: - Linux: `$XDG_DATA_HOME/reth/` or `$HOME/.local/share/reth/` - Windows: `{FOLDERID_RoamingAppData}/reth/` - macOS: `$HOME/Library/Application Support/reth/` [default: default] --chunk-len Chunk byte length to read from file. [default: 1GB] -h, --help Print help (see a summary with '-h') Database: --db.log-level Database logging level. Levels higher than "notice" require a debug build Possible values: - fatal: Enables logging for critical conditions, i.e. assertion failures - error: Enables logging for error conditions - warn: Enables logging for warning conditions - notice: Enables logging for normal but significant condition - verbose: Enables logging for verbose informational - debug: Enables logging for debug-level messages - trace: Enables logging for trace debug-level messages - extra: Enables logging for extra debug-level messages --db.exclusive Open environment in exclusive/monopolistic mode. Makes it possible to open a database on an NFS volume [possible values: true, false] The path to a receipts file for import. File must use `HackReceiptFileCodec` (used for exporting OP chain segment below Bedrock block via testinprod/op-geth). Logging: --log.stdout.format The format to use for logs written to stdout [default: terminal] Possible values: - json: Represents JSON formatting for logs. This format outputs log records as JSON objects, making it suitable for structured logging - log-fmt: Represents logfmt (key=value) formatting for logs. This format is concise and human-readable, typically used in command-line applications - terminal: Represents terminal-friendly formatting for logs --log.stdout.filter The filter to use for logs written to stdout [default: ] --log.file.format The format to use for logs written to the log file [default: terminal] Possible values: - json: Represents JSON formatting for logs. This format outputs log records as JSON objects, making it suitable for structured logging - log-fmt: Represents logfmt (key=value) formatting for logs. This format is concise and human-readable, typically used in command-line applications - terminal: Represents terminal-friendly formatting for logs --log.file.filter The filter to use for logs written to the log file [default: debug] --log.file.directory The path to put log files in [default: /logs] --log.file.max-size The maximum size (in MB) of one log file [default: 200] --log.file.max-files The maximum amount of log files that will be stored. If set to 0, background file logging is disabled [default: 5] --log.journald Write logs to journald --log.journald.filter The filter to use for logs written to journald [default: error] --color Sets whether or not the formatter emits ANSI terminal escape codes for colors and other text formatting [default: always] Possible values: - always: Colors on - auto: Colors on - never: Colors off Display: -v, --verbosity... Set the minimum log level. -v Errors -vv Warnings -vvv Info -vvvv Debug -vvvvv Traces (warning: very verbose!) -q, --quiet Silence all log output ```