baking-bad / netezos Goto Github PK

Should be upgraded to .net 6.0 as it is for LTS

Are there any plans to do so?

1. Write missing documentation for methods and parameters.
2. Rewrite existing documentation to make it more understandable.

For parameters mapping the dictionary should be alphabetically ordered

Hi, in 2.0.1 version, shouldn't BytesExtension class in Netezos.Utils.Extension be public ?
otherwise the usage example in README.md
bytes.Concat(signature)
or
Netezos.BytesExtension.Concat(bytes,signature)
does not seem to work.

I get the following message:
'BytesExtension' is inaccessible due to its protection level

When trying sample code i am getting error as mentioned in subject

Code is

var key = Key.FromBase58("edsk4ZkGeBwDyFVjZLL2neV5FUeWNN4NJntFNWmWyEBNbRwa2u3jh1");

		// use this address to receive some tez
		var address = key.PubKey.Address; // tz1SauKgPRsTSuQRWzJA262QR8cKdw1d9pyK

		using var rpc = new TezosRpc("https://mainnet-tezos.giganode.io/");

		// get a head block
		var head = await rpc.Blocks.Head.Hash.GetAsync<string>();

		// get account's counter
		var counter = await rpc.Blocks.Head.Context.Contracts[address].Counter.GetAsync<int>();

		var content = new ManagerOperationContent[]
		{
			new RevealContent
			{
				Source = address,
				Counter = ++counter,
				PublicKey = key.PubKey.GetBase58(),
				GasLimit = 1500,
				Fee = 1000 // 0.001 tez
			},
			new TransactionContent
			{
				Source = address,
				Counter = ++counter,
				Amount = 1000000, // 1 tez
				Destination = "tz1KhnTgwoRRALBX6vRHRnydDGSBFsWtcJxc",
				GasLimit = 1500,
				Fee = 1000 // 0.001 tez
			}
		};

		var bytes = await new LocalForge().ForgeOperationGroupAsync(head, content);

		byte[] signature = key.SignOperation(bytes);

		// inject the operation and get its id (operation hash)
		var result = await rpc.Inject.Operation.PostAsync(bytes.Concat(signature));

To write comprehensive tests of your Tezos application, your would need to mock responses from RPC calls. If the TezosRpc was implemented as an interface, it would be easily mockable, but I am not sure how to approach it in this case.

https://dotnetfiddle.net/8po214

I am getting this on my local system as well. any idea what's wrong?

Write tests to ensure that all rpc methods paths are correct and all query parameters work

It would be nice if this library could take a signed transaction in a hex format and parse it into a transaction object, so you could read the amount, the source, destination, fee etc. without having to talk to a node.

I was reading https://www.c-sharpcorner.com/article/getting-started-with-smart-contracts-in-c-sharp/ for jump into smart contract creation.
Is there any similar article targeting tezos?

Source could be a contract as follow

{
"protocol":
"Pt24m4xiPbLDhVgVfABUjirbmda3yohdN82Sp9FeuAXJ4eV9otd",
"chain_id":
"NetXdQprcVkpaWU",
"hash":
"onmzRXbyKvm6SRsTSsorqwtdeXMpA3r4YCG2GVpTx1pzsX3bsf9",
"branch":
"BMFGtKPqQ5spmxS1WwaWxkVadaEVemEVW2PCPDJ3Bgr2sNkronC",
"contents":
[
{
"kind":
"delegation",
"source":
"KT1JJemnt1aoGGRK1trx1Sh8hjV6w3n88WL9",
"fee":
"1420",
"counter":
"3",
"gas_limit":
"10000",
"storage_limit":
"0",
"delegate":
"tz1TDSmoZXwVevLTEvKCTHWpomG76oC9S2fJ"
}
]
"signature":
"sigt9zdrzJgFV9sWhaZ3B6r6S1dSaBVHKUjtBcfHjCJiEZtPY44GR5viGrLFhPDYo8nBUbJKoMnooH19qRojpxADesruhec8"
}

https://tzkt.io/onmzRXbyKvm6SRsTSsorqwtdeXMpA3r4YCG2GVpTx1pzsX3bsf9/3

Usage of forgeTzAddress seems incorrect.

my scenario is like i will provide the word from secret phrase and in return i will got password.
or things like password is correct for account e.t.c.
https://tezos.stackexchange.com/questions/29/what-are-my-remedies-if-i-forgot-the-password-i-created-during-the-fundraiser