id | title |
---|---|
examples |
Examples |
{% hint style="danger" %} WARNING! This package is deprecated and is no longer maintained and supported. {% endhint %}
using ARKEcosystem.Crypto;
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.
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.
var transaction = Crypto.Builder.Transfer.Create(
"validAddress",
1000,
"This is a transaction from .NET",
"This is a top secret passphrase"
);
>>> Transaction
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.
var transaction = new Serializer(transactionObject).Serialize();
>>> byte[]
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.
var transaction = new Deserializer(serializedTransaction).Deserialize();
>>> Transaction
The crypto SDK not only supports transactions but can also work with other arbitrary data (expressed as strings).
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
orpassphrase
.
var message = Message.Sign("Hello World", "passphrase");
>>> Message
A message's signature can easily be verified by hash, without the private key that signed the message, by using the
verify
method.
var message = Message.Sign("Hello World", "passphrase");
Console.WriteLine(message.Verify());
>>> bool
The identities class allows for the creation and inspection of keypairs from
passphrases
. Here you find vital functions when creating transactions and managing wallets.
Identities.Address.FromPassphrase('this is a top secret passphrase');
>>> string
Identities.Address.FromPublicKey('validPublicKey');
>>> string
Identities.Address.FromPrivateKey('validPrivateKey');
>>> string
Identities.Address.Validate('validAddress');
>>> bool
As the name implies, private keys and passphrases are to remain private. Never store these unencrypted and minimize access to these secrets
Identities.PrivateKey.FromPassphrase('this is a top secret passphrase');
>>> Key
Identities.PrivateKey.FromHex('validHexString');
>>> Key
This function has not been implemented in this client library.
Public Keys may be freely shared, and are included in transaction objects to validate the authenticity.
Identities.PublicKey.FromPassphrase('this is a top secret passphrase');
>>> PubKey
Identities.PublicKey.FromHex('validHexString');
>>> PubKey
This function has not been implemented in this client library.
The WIF should remain secret, just like your
passphrase
andprivate key
.
Identities.WIF.FromPassphrase('this is a top secret passphrase')
>>> string