Add a config.toml file to configure parameters for db , network , solana etc

[Nagaprasadvr]

We need to support a configuration file to set certain parameters . This includes settings for transaction behavior, performance tuning, storage, RPC, and more.

A non-exhaustive list of configuration parameters that should be supported:

---

🔹 Transaction Settings

• priority_fee: Max priority fee (in micro-lamports) per CU.
• tx_retries: Number of times to retry a failed tx

---

🔹 Performance / Mining

• num_cores: Number of CPU threads to use.
• max_memory_mb: Max memory usage for mining.
• rocksdb_conn_pool_size: Limit for RocksDB read only connections.

---

🔹 Identity / Key Management

• keypair_path: Path to the signer keypair file.

---

🔹 Solana RPC Settings

• rpc_url: Solana RPC endpoint.
• ws_url: Optional WebSocket endpoint.
• commitment: RPC commitment level (processed, confirmed, finalized).

---

🔹 RocksDB / Storage

• rocksdb_primary_path: Path to RocksDB directory.
• rocksdb_secondary_path: Path for secondary DB (if applicable).
• rocksdb_cache_size_mb: Read cache size.

---

🔹 Network & Infra

• bind_address: IP and port to bind local service for json rpc.
• metrics_endpoint: Prometheus metrics output.

---

🔹 Logging & Debugging

• log_level: One of error, warn, info, debug, trace.
• log_path: Optional log file path.
• metrics_interval: Interval to flush logs or metrics.

---

[aarjn]

What about we use the name Tape.toml for configuration file instead of the config.toml. Like anchor has Anchor.toml

[Nagaprasadvr]

What about we use the name Tape.toml for configuration file instead of the config.toml. Like anchor has Anchor.toml

Yup works just need to build the logic and make it work

[aarjn]

Yeah, got it. Wait, I have a query: is this .toml file to be used while setting up the node?

[Nagaprasadvr]

Yeah that's the purpose of this

[aarjn]

Now it's clear. I will try to push a basic version and we can build on it.