• Ethereum has no max supply as bitcoin





Fast, cheap, scalable token transfers for Ethereum

Wallets / Smart contracts runners

Important security notes

  • IMPORTANT You should make a backup of your keystore file in order to access your accounts.

Account recovery

Ethereum encryption types

Taken from “Learning Ethereum and Solidity” book

Symmetric Encryption

A process by which a snippet of plain
text, usually held in a document, is smashed together with
a shorter data string called a key to produce a ciphertext
output. This output can be reversed, or decrypted, by the
party that receives it, so long as they also have that same
key. Trying to decode the message without the key would
be, computationally speaking, immensely time-consuming
and expensive—so much so that some kinds of encryption
are considered practically unbreakable, even with huge
computing resources.

Asymmetric encryption

This way of encrypting information
requires the program to issue two keys simultaneously, one
that is public and one that you keep private. The public
key is public in the sense that you can list it on your web
site or social profile, such as an e-mail address. (When
communicating, parties can use one anothers’ public keys to
encrypt information, as described below.)

Video playlist explaining concepts

Secure Messaging

In our first example, Alice uses Bob’s public
key to encrypt a message. When he receives the ciphertext,
he can decrypt it using his matching private key, ensuring
that only Bob can read the message. This is called secure
messaging. But it leaves a dangerous possibility open: anyone
could send Bob a message claiming to be Alice. How does he
know that Alice is the real sender of the message?

Secure and Signed Messaging

If Alice wanted to assure Bob
that she is the true sender, she would do things differently.
First, she would take her plaintext message and encrypt it
using her private key. Then, she would encrypt it again using
Bob’s public key. When Bob receives the message, he decrypts
it first using his private key, but he’s still left with ciphertext.
He must decrypt it again using Alice’s public key. This second
layer of encryption assures him that Alice is indeed the
sender, because presumably, nobody has Alice’s private key
but Alice. This is known as “secure and signed” messaging.
If Alice were to only encrypt her plaintext using her own
private key, then anyone with her public key could decrypt it.
This is known as an “open message format” because, while
it proves the identity of the sender, it can be decrypted by

Digital signature

For maximum security, Alice would take
another step: she would hash the plaintext of her message,
and attach it along with the message. She would then encrypt
this bundle with her own private key, and again with Bob’s
public key. When Bob receives and decrypts the ciphertext he
can run Alice’s plaintext message through the same hashing
algorithm Alice used. If for some reason the fingerprint of
the message turns out differently, then it means the actual
message text was damaged or altered en route.

Interesting projects

  • cryptopunks
  • - Decentraland is a virtual reality platform powered by the Ethereum blockchain. Users can create, experience, and monetize content and applications
  • - A network of decentralized markets and communities. Create, operate, and govern. Powered by Ethereum, Aragon, and IPFS


  • DAppNode - Connect to the decentralized Internet