Skip to content
.Net Standard 2.0 library for working with Tezos
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
Netezos.Forge.Tests First version of Local Forging test. Dec 25, 2019
Netezos.Keys Fix prefixes parsing Jan 7, 2020
Netezos.Ledger Fix prefixes parsing Jan 7, 2020
Netezos.Rpc Forging for origination, reveal, transaction, delegation, activation,… Dec 25, 2019
.gitignore Reveal and activation local forging added. Dec 25, 2019
LICENSE Initial commit May 16, 2019
Netezos.sln Move ledger things to Netezos.Ledger Dec 25, 2019 Update Dec 25, 2019


Made With License: MIT

.Net Standard 2.0 libraries pack for working with Tezos.

Package Nuget Description
Netezos.Rpc NuGet Tezos RPC wrapper
Netezos.Forge NuGet Forge operations locally or via RPC
Netezos.Keys NuGet Generate or parse keys, sign data, verify signature
Netezos.Ledger NuGet Interact with Tezos Ledger App


Netezos.Rpc provides an access to the Tezos node via RPC API. There is the main class TezosRpc which you need to build queries, supported by the Tezos RPC API.

Basic usage

Let's create an instance of the TezosRpc class, build a simple query and execute it by calling GetAsync() method.

using (var rpc = new TezosRpc(""))
    // get the head block
    var head = await rpc.Blocks.Head.GetAsync();
    // get only the hash of the head block
    var hash = await rpc.Blocks.Head.Hash.GetAsync();

Note that the real HTTP request is sent only when you call GetAsync(). Until then, you work with just the query object, which can also be used to get subqueries.

Accessing blocks

You can access any block in two ways: by forward or backward indexing.

// gets the block with level = 1
var firstBlock = rpc.Blocks[1]; // forward indexing

// gets the last block (e.g. with level = 400000)
var lastBlock = rpc.Blocks.Head;

// gets the block with level = 400000 - 10 = 399990
var tenthFromLast = rpc.Blocks[-10]; // backward indexing

RpcList and RpcDictionary

The results of many RPC API methods can be interpreted as arrays or dictionaries that allow you to get many objects or only one by specifying a key or an index.

var operations = rpc.Blocks.Head.Operations;
var firstEndorsement = rpc.Blocks.Head.Operations[0][0];

var contracts = rpc.Blocks.Head.Context.Contracts;
var myContract = rpc.Blocks.Head.Context.Contracts["KT1..."];

Query parameters

If some RPC API method has query parameters, the corresponding query object have the overridden GetAsync() methods.

var activeDelegates = await rpc.Blocks.Head.Context.Delegates.GetAsync(DelegateStatus.Active);

var bakingRights = await rpc.Blocks.Head.Helpers.BakingRights.GetAsync(maxPriority: 1, all: true);

POST methods

There are several ways to pass the data to the server.

Some of the RPC queries contain overridden methods which take required and optional parameters. This is enough for the most cases.

var protoData = await rpc.Blocks.Head.Helpers.Forge.ProtocolData
    .PostAsync(0, "nceUHEeriV43iAfcxsCFf2Ygqn2cQZnuGKump9JEmhaVXt79CvXdY", "0000000349a42671");

If the overridden method does not meet your needs, you can simply pass the object with required fields and it will be automatically serialized to JSON before being sent.

var protoData = await rpc.Blocks.Head.Helpers.Forge.ProtocolData
        priority = 0,
        nonce_hash = "nceUHEeriV43iAfcxsCFf2Ygqn2cQZnuGKump9JEmhaVXt79CvXdY",
        proof_of_work_nonce = "0000000349a42671"

In addition, you can simply pass a valid JSON string.

var protoData = await rpc.Blocks.Head.Helpers.Forge.ProtocolData
    .PostAsync(@"{""priority"": 0, ""nonce_hash"": ""nceUHEe..."", ""proof_of_work_nonce"":  ""00000...""}");
You can’t perform that action at this time.