9
votes
Accepted
How counter grows
The counter always increases by 1 for every operation - the difference is where the counter "starts".
When an implicit (tz*) account becomes active (goes from 0 balance to more than 0), it adopts the ...
7
votes
Accepted
Why a reveal operation?
Ethereum way of retrieving the public key only works with some signing algorithms, ECDSA with secp256k1 in its case. It is also used by Tezos for tz2 (and P-256 for tz3), but not for tz1 which uses ...
7
votes
Accepted
Stuck in "Waiting for the operation to be included..." Infinitely
This means that your node is not fully synchronized yet or the fee you specified/defaulted is too low for any baker to include the operation.
Verifying if node is Synchronized:
./tezos-client get ...
7
votes
What are all of the operation types supported in Tezos?
$ ./tezos-client rpc schema post /chains/main/blocks/head/helpers/forge/operations | jq '.input.definitions."operation.alpha.contents".oneOf | .[] | .properties.kind.enum | .[0]'
"endorsement"
"...
6
votes
Accepted
How to use rpc parse operations endpoint
The problem is that /parse/operations expects signed operations. You can just add 64 zero bytes to the end:
{
"operations": [
{
"data": "...
6
votes
Accepted
Where is the reward operation for athens?
This happened directly as part of the context "stitching". When a new protocol is activated, an initialization function is called which lets the new protocol performs some housekeeping on the context ...
6
votes
Accepted
Inject Signed Operation Fails With Unrevealed_Key Error
Before sending transactions from an account, a 'reveal' operation must be made for the account. It looks like this account may have been activated, but not yet revealed. To make this work we would ...
6
votes
Accepted
Manager operation results: Applied | Backtracked | Failed | Skipped
The idea is pretty simple:
failed - operations which failed with some particular error (not enough balance, gas limit, etc);
backtracked - operations which were successful but reverted due to one of ...
5
votes
Accepted
Ballot RPC message
Period is a 32-bit integer, the current period is 10 so you'd encode this as:
0000000a
Proposal is just the hext bytes of the unencoded proposal hash, so you would b58cdecode the proposal hash and ...
4
votes
Is it possible to have a transaction operation in any operation's "contents"?
From my understanding, yes and no. There are four groups of operations:
Baking - endorsements
Voting - proposals and ballots
Annonymous - seed_nonce_revelation, double_bake/endorse, activate_account
...
4
votes
Accepted
How does tezos-client compute a transaction fee?
The fee computation follows the formula.
The only subtle thing here is that the fee itself can affect the size of the operation in binary. This usually doesn't matter, but to handle the general case, ...
4
votes
Accepted
Fees for various operation
Docs in tezos.git
Docs by TezTech
To copy from the tezos.git docs:
fees >= (minimal_fees + minimal_nanotez_per_byte * size
+ minimal_nanotez_per_gas_unit * gas)
(size is ...
4
votes
Operation cost for invoking smart contract
There is no formula that will give you the full cost and gas usage of smart contract invocation. The best method is to simulate. Contract code size and storage directly affects costs through storage ...
4
votes
Accepted
What is an operation counter?
The counter is simply a number that is incremented with each operation.
I think the documentation refers to a replay attack. If operations where not tagged with a counter, that is signed along with ...
4
votes
Accepted
Listen for operations of a deployed contract
After working with @taquito/rpc for a little while and having success there I also discovered in the main @taquito/taquito package there's some useful things you can subscribe to on the stream. A ...
3
votes
Accepted
Operation bytes parsing
If we put the hex strings next to each other and find out where they match it becomes easy to see why they differ.
...
3
votes
Accepted
Decode a Tezos hexadecimal operation
You can use the tezos-codec binary from the latest mainnet-staging branch to parse these bytes. So, signing request are indeed prefixed by the tag 1 + <chain_id> for the block cases. The ...
3
votes
Stuck in "Waiting for the operation to be included..." Infinitely
In case your node isn't fully bootstrapped, you can run:
tezos-client bootstrapped
This command will let you know in case your node isn't fully synced.
3
votes
Does Tezos have any on-chain signature verification algorithms implemented?
It's called
CHECK_SIGNATURE
in Michelson.
3
votes
How to estimate Baker and Storage fee with @taquito for a contract?
You can call toTransferParams({amount: 5}) on the method you want to estimate, and pass that result to Tezos.estimate.transfer()
The results of which will look something like:
Estimate {
_gasLimit:...
3
votes
Rewards for Operations
Here is a short description of how operations can affect balance:
Transaction - transfer | fee
Revelation - fee
Origination - transfer | fee
Delegation - fee
Endorsement - reward
...
3
votes
Accepted
Why won't transaction propagate to other nodes?
I don't agree that the mempool behavior indicate that the fee is all good. On the contrary. Public nodes like Giganode generally don't reject operations based on fee in the prevalidation, while most ...
2
votes
Can inject operation but can't preapply operation, returns 400
The preapply/operations endpoint requires an array of operations to be submitted.
Just wrap your call around square brackets and it should work. This is how it's done in eztz.
2
votes
Accepted
Sotez Forge Method Returns "Type Error: Expected String"
The operation should look like:
const operation = {
branch: 'BLDnyGuzjz6TuDvxgBtHUZmvY2zZqJ7VShDjZsHsxXQtnzrCrPf', // current head hash
contents: [{
kind: 'transaction',
source: '...
2
votes
Accepted
Can I add metadata to a transfer operation?
In short, no you can't as your delegators would be using standard KT1 accounts to receive their funds which means you're limited with what you can do with it.
You can capture the operation hash when ...
2
votes
Local operations vs remote operation
In general, there would be some logic to prioritize local operations versus remote operations. Yet, that would only be needed when a baker has both a baking slot, and the need to emit new operations ...
2
votes
Accepted
Signed bytes and encodedSignature explanation?
The signature in hex is the last 64 bytes (128 hex characters). edsigtXomBKi5CTRf5cjATJWSyaRvhfYNHqSUGrn4SdbYRcGwQrUGjzEfQDTuqHhuA8b2d8NarZjz8TRf65WkpQmo423BtomS8Q is the signature of 64 zero bytes, ...
2
votes
Accepted
Why Operations have extra money transaction that are not included in balance calculation?
That 257000 µꜩ is "origination burn". Simply put, when creating(or transferring to) a new address, there is a cost and the current value is 257000 µꜩ. Since this is a "burn", it's actually a deflation ...
2
votes
Where is the protocol change proposal injected?
Unless I am reading it wrong, there was one operation injecting both proposals:
https://tzscan.io/onydFJLWdGhfKNBfbnSLmqDu93j9NRimkbQm9WqLWYG8eyZUyTF
in Block 332624: https://tzscan.io/...
2
votes
Operation injected to node, but not added to blockchain | Wallet counter error
TLDR: the first operation you injected in your node is valid but will be never be injected by other nodes/bakers because it has too low fees. It is then stuck in the mempool and make the the next ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
operation × 71transactions × 14
rpc × 11
taquito × 10
tezos-client × 6
inject × 6
node × 5
transfer × 5
fees × 5
protocol × 4
mempool × 4
hash × 4
error × 3
fee × 3
smart-contracts × 2
wallets × 2
api × 2
voting × 2
tezos-signer × 2
testing × 2
gas × 2
javascript × 2
eztz × 2
reveal × 2
counters × 2