FAQ

The eMark network cannot be manipulated because all transactions are stored in the blockchain and thus simultaneously on thousands of different computers worldwide. All newly added transactions are also first checked several times by the eMark network, confirmed and only then integrated into the blockchain.

eMark cannot be stolen from the network by attacks on the eMark system. However, attacks on the user himself can lead to the loss of his own eMark. Once an attacker gets hold of a private key to an eMark address, he also has access to the eMark credit associated with it.

An attacker can gain this access, for example, through malware or viruses that can spy on or copy the "wallet.dat" file. Likewise, by accessing the computer itself (e.g. via WLAN), by "hacking" online storage devices such as Dropbox or iCloud (if private keys are stored there), or even by using fake wallets (fakes) that are modeled on the original.

Each user is therefore responsible for protecting his or her private keys, e.g. by encrypting the "Wallet.dat" file with a secure password that protects it from unauthorized access.

Yes, you can also lose your eMark permanently. For example, if you lose access to your private keys and thus also to the eMark directly. This could be due to a hard drive crash, other data loss, fire, water or theft. If you store your eMark in paper wallets, you will also no longer have access to your eMark if such a paper wallet is irretrievably lost or irreparably destroyed.

The greatest danger when using a wallet installed on one's own computer is the loss of the password with which the file "wallet.dat" was encrypted. The file is then still available, but NOBODY in the world can ever decrypt this file again without the valid password.

The Blockchain is the ledger to track transactions.

The Protocol contains all the rules of eMark, stake height, how many transactions fit in a block (block size), etc.

This Protocol is always queried and compared by all nodes, miners and users connected to the network when connecting to other eMark applications.

A Hardfork can occur when basic things in the source code (protocol) are changed.

Example: The Stake % value should be increased to 4.2% per year, all users must agree to this change, i.e. update their wallet (eMarkd/-qt) to this version. If the majority of users update, it will continue with the new version.

If there is a Hardfork, a time is set in the new application protocol (usually a certain block) where then older versions are no longer accepted to connect. Receiving the eMark would still work with the old version, but sending or generating it would no longer work.