What is the required disk size to run the chain?
250-500GB per node - <200GB (Polkadot) + 5GB (Pendulum) and increasing.
Block data of mainnet or snapshots
We currently don't have a snapshot available. Any node would need to sync from scratch but that would not take long as Pendulum just started recently. You can use https://dot-rocksdb.polkashots.io/ to speed up the sync of the relay chain embedded node.
What is the block producing rate?
What is the precision of each transaction
How to create an account?
As Pendulum is a polkadot parachain, the account would also be created for Pendulum in the above process.
Where tdo I find the configuration file directory?
How to customize RPC Port and directory of block data?
Please follow our guideline for setting up an RPC or collator node, which should implicitly contain this information (https://pendulum.gitbook.io/pendulum-docs/build/node-operators/collators/set-up-collator)
--rpc-portis the parameter for RPC port and
-dis the directory for data. You can access the documentation on node parameters here: https://docs.substrate.io/reference/command-line-tools/node-template/
More API instructions?
How do you prevent forking?
This does not happen as the Polkadot relay chain does the consensus for the Pendulum parachain. So the measures to avoid this are the measures employed for Polkadot.
How to restore and recover accounts?
How does the networks avoid 51% attack?
Will there be rollbacks?
There can't be a rollback because our consensus happens on the Polkadot relay chain
Is there a timeout mechanism for a transaction in tx pool, and if so, how long does it deal?
Every transaction has an optional expiry time. After that they will be removed from the pool.