New answers tagged

0

So when you are generating your transaction, it is filling it with a reference block in the transaction JSON. The problem is that the reference block should be a short time in the past, and in your case that isn't true. Are you generating the transaction on your local testnet, and then trying to sign and push it to a different chain? That would be a typical ...


1

I identified the problem - later in the function I'm trying to create a new extended asset by adding two extended assets together, and they don't have the same extended symbol. I'm really not sure why the print statements between that line and the line in my question weren't being printed, though - that left me with the impression that the above line was ...


0

You can access it from the command line using: cleos get transaction TRANSACTION_ID | jq '.block_num'


0

Here is the json that worked for me. Thanks to dfuse.io team for assistance. command: cleos -u http://localnetwork.com:8888 push action eosio setprods "testnetprods.json" -p eosio@active testnetprods.json: { "schedule": [ { "producer_name": "eosio", "authority": [ "block_signing_authority_v0", ...


0

This documentation should have the latest steps on setup producer. https://developers.eos.io/welcome/latest/tutorials/bios-boot-sequence/#2-transition-from-single-genesis-producer-to-multiple-producers Setting up the eosio network requires multiple steps. Any step skipped could result in an error. Probably it is better to follow that guide step by step


Top 50 recent answers are included