Skip to main content

FAQ - General

Accounts​

Should a customer see use the account-hex or the account-hash?
Exchange customers or end-users only need to see the account-hex. They do not need to know the account_hash. The account_hash is needed in the backend to verify transactions. Store the account-hash to query and monitor the account. Customers do not need to know this value, so to simplify their experience, we recommend storing both values and displaying only the account-hex value.
Is it possible to convert an account-hash back to an account-hex?

An account-hash is a one-way hashed value of the account-hex. We refer to the account-hex as public_key and the account-hash as the account_address.

The account-hex originates with JS-SDK naming conventions. We store it and convert it to an account-hash. Using account-address within the Rust client generates an account hash from a given public key.

Why is my account invalid when I can see it on the testnet?

You must deposit tokens to activate it. You can request tokens from CSPR Live.

Minimum CSPR Balance​

What is the minimum CSPR balance required to transfer?

An account cannot transfer less than 2.5 CSPR.

Ledger Support​

Does Casper offer Ledger support?

Yes. Follow this guide to install the Casper app on your Ledger device to manage CSPR.

Staking​

What are the important aspects to consider when delegating tokens to a validator?

Users should consider consistent uptime, prompt upgrades and commission rates when choosing a validator. Offline and out-of-date validators do not generate rewards.

Active engagement in the community is another important aspect.

How do I stake tokens via the command line?

Follow the delegation workflow to learn how to stake your tokens via the command line.

How do I stake tokens using cspr.live?
What is self-stake percentage?

Self-stake is the amount of CSPR a validator personally staked on the network from their validating node, expressed as a percentage of the total amount of CSPR staked to that validator. Most validators choose to delegate their own tokens to their validating node as a security practice, which will show as a low self-stake percentage.

What is slashing?

Slashing is a penalty for inappropriate or malicious behavior. Ordinarily, the official node software will not act maliciously unless intentionally altered. When this happens, the validator in question gets slashed (Note: The network treats validator and delegator tokens equally).

Slashing is not currently enabled on the Casper Mainnet. If a validator behaves poorly on the network, they face eviction from the network and loss of rewards. When slashing is enabled, poor behavior will result in token removal. In this case, you will lose any rewards accrued during the eviction period.