FAQ

• Cloud Platform Account Security

During the creation of a rollup, users are required to enter the Access Key/Secret Key (abbreviated as AK/SK) of the cloud platform. RedPine uses AK/SK to call the cloud platform's API for resources and does not store them in the backend. For security reasons, it is recommended that users set minimal permissions for AK/SK. Users can also delete the corresponding AK/SK after creating resources in RedPine and recreate them when needed.

Regarding user permission settings, please refer to Cloud Platform IAM (opens in a new tab).

• Security of Chain Private Keys

When selecting Testnet and Mainnet in the Network, during the creation of a rollup Appchain, users are required to upload the chain's private key to the host. Throughout this process, RedPine does not come into contact with the private key. The security of the private key is ensured by the cloud computing platform. It is recommended to use a keystore, a file generated by encrypting the private key. After uploading the keystore to the host, it needs to be decrypted before use, reducing the risk of private key exposure.

• High Availability of Rollup Nodes

The cloud server adopts a compute-storage separation architecture, where computing resources and storage resources are deployed on different physical machines. Currently, the cloud platform has implemented high availability capabilities for both computing and storage. The storage resources are designed with multiple redundancies, ensuring high availability. In the event of a physical machine failure, the computing resources can automatically migrate to other physical machines and quickly restart. The rollup service on the cloud server is managed by systemd during RedPine deployment and will automatically recover when new computing resources are started.

• Login Cookie

The login cookie is a method employed by the RedPine platform to verify the user's identity. When the user does not have a login cookie locally, logging into the console requires the user to sign a message using a wallet such as MetaMask. After receiving the signature, RedPine can parse the user's address and allocate a cookie for that address, which is then returned to the console. The console stores this cookie locally, and it is sent along with subsequent visits to the platform. The platform can use this cookie to identify the corresponding address.