#Examples

#Initialization

1using ArkEcosystem.Crypto;

#Transactions

A transaction is an object specifying the transfer of funds from the sender’s wallet to the recipient’s. Each transaction must be signed by the sender’s private key to prove authenticity and origin. After broadcasting through the client SDK , a transaction is permanently incorporated in the blockchain by a Delegate Node.

#Sign

The crypto SDK can sign a transaction using your private key or passphrase (from which the private key is generated). Ensure you are familiar with digital signatures before using the crypto SDKs.

1var transaction = Crypto.Builder.Transfer.Create(
2  "validAddress",
3  1000,
4  "This is a transaction from .NET",
5  "This is a top secret passphrase"
6);
7 
8>>> Transaction

#Serialize (AIP11)

Serialization of a transaction object ensures it is compact and properly formatted to be incorporated in the ARK blockchain. If you are using the crypto SDK in combination with the public API SDK, you should not need to serialize manually.

1var transaction = new Serializer(transactionObject).Serialize();
2 
3>>> byte[]

#Deserialize (AIP11)

A serialized transaction may be deserialized for inspection purposes. The public API does not return serialized transactions, so you should only need to deserialize in exceptional circumstances.

1var transaction = new Deserializer(serializedTransaction).Deserialize();
2 
3>>> Transaction

#Message

The crypto SDK not only supports transactions but can also work with other arbitrary data (expressed as strings).

#Sign

Signing a string works much like signing a transaction: in most implementations, the message is hashed, and the resulting hash is signed using the private key or passphrase.

1var message = Message.Sign("Hello World", "passphrase");
2 
3>>> Message

#Verify

A message’s signature can easily be verified by hash, without the private key that signed the message, by using the verify method.

1var message = Message.Sign("Hello World", "passphrase");
2Console.WriteLine(message.Verify());
3 
4>>> bool

#Identities

The identities class allows for the creation and inspection of keyPairs from passphrases. Here you find vital functions when creating transactions and managing wallets.

#Derive the Address from a Passphrase

1Identities.Address.FromPassphrase('this is a top secret passphrase');
2 
3>>> string

#Derive the Address from a Public Key

1Identities.Address.FromPublicKey('validPublicKey');
2 
3>>> string

#Derive the Address from a Private Key

1Identities.Address.FromPrivateKey('validPrivateKey');
2 
3>>> string

#Validate an Address

1Identities.Address.Validate('validAddress');
2 
3>>> bool

#Private Key

As the name implies, private keys and passphrases are to remain private. Never store these unencrypted and minimize access to these secrets

#Derive the Private Key from a Passphrase

1Identities.PrivateKey.FromPassphrase('this is a top secret passphrase');
2 
3>>> Key

#Derive the Private Key Instance Object from a Hexadecimal Encoded String

1Identities.PrivateKey.FromHex('validHexString');
2 
3>>> Key

#Derive the Private Key from a WIF

1This function has not been implemented in this client library.

#Public Key

Public Keys may be freely shared, and are included in transaction objects to validate the authenticity.

#Derive the Public Key from a Passphrase

1Identities.PublicKey.FromPassphrase('this is a top secret passphrase');
2 
3>>> PubKey

#Derive the Public Key Instance Object from a Hexadecimal Encoded String

1Identities.PublicKey.FromHex('validHexString');
2 
3>>> PubKey

#Validate a Public Key

1This function has not been implemented in this client library.

#WIF

The WIF should remain secret, just like your passphrase and private key.

#Derive the WIF from a Passphrase

1Identities.WIF.FromPassphrase('this is a top secret passphrase')
2 
3>>> string