NEM

← Back to document page

NEMTechnical ReferenceVersion 23, 2018ContentsPrefaceiii1 Introduction12 Accounts and Account state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NEM addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Converting a public key into an address . . . . . . . . . . . . . . . . . . . . Intentional address collision . . . . . . . . . . . . . . . . . . . . . . . . . .63 Private and public key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signing and verification of a signature . . . . . . . . . . . . . . . . . . . . . Encoding and decoding messages.

0 2 4 6 8 10 12 14 16 18 20 0 10,000 20,000 30,000 40,000 50,000 60,000 70,000 80,000 90,000 days part Figure 1: Vesting of 100,000 XEM All accounts in the nemesis block2 are fully vested. 2.2NEM addresses A NEM address is a base-323 encoded triplet consisting of: • network byte • 160-bit hash of the account’s public key