Hot answers tagged

6

curl https://florencenet.smartpy.io/version Output: {"version":{"major":9,"minor":1,"additional_info":"release"},"network_version":{"chain_name":"TEZOS_FLORENCENOBANET_2021-03-04T20:00:00Z","distributed_db_version":1,"p2p_version":1},"commit_info":{...


5

Every transaction in current and past Tezos protocols must reference a recent block (the "branch"). This acts as an informal checkpointing mechanism a replay protection mechanism an effective time-to-live limit on transactions edit: As to why it is required for parsing, it is because the node uses the branch to determine which protocol it should ...


4

If everything goes as expected, the network should switch to proto 7 in ~18 days (Thu, 12 Nov 2020 10:47:01 GMT). Sun Oct 25 22:41:40 UTC 2020 $ tezos-client show voting period Current period: "promotion_vote" Blocks remaining until end of period: 25207 Current proposal: PsDELPH1Kxsxt8f9eWbxQeRxkjfbxoqM52jvs5Y5fBxWWh4ifpo Ballots: { "yay&...


4

The Tezos protocol is defined by its OCaml implementation. When amendment to the protocol are proposed, the delegates vote on hashes of amended implementations. That being said, some parts of the protocol have been formalized. Most notably, the semantics of the Michelson smart-contract language has been formalized in several semantic frameworks: Coq, Ott, K, ...


3

You could use Flextesa In a docker-compose file, it should look like the following: version: '3.6' services: sandbox: image: tqtezos/flextesa:20210316 command: edobox start -P 8732 container_name: sandbox environment: block_time: 1 TEZOS_CLIENT_UNSAFE_DISABLE_DISCLAIMER: Y ports: - "8732:8732" It will bake ...


3

No, there are no events currently in Tezos. It has been discussed, but AFAIK there are no fixed plans to add it. This might change in the future though.


2

Giganode is indeed a public node, among many out there. However, not all RPC endpoints are exposed for performance and privacy reasons. For instance, https://mainnet-tezos.giganode.io/network/points returns 403 Forbidden because they don't allow it. If you are looking for a list of tezos nodes, you can use this popular script to get more nodes from TzKt.io ...


2

You can reveal seed nonce at any level in the following cycle. Example: level 3590 of 4096. You see most revelations within the first blocks because the native baking software simply tries to push the revelation operation ASAP. However, it would be much better to inject revelation in your own block in order to earn extra rewards. As for the proto.006-...


2

Here is an example with the correct syntax, I hope this helps. Contract Link The first issue you are having is with the way you call the entrypoint. It should be c1._verifySigPersonalSign(req = req, sig = AliceSignature) instead of c1._verifySigPersonalSign(req,AliceSignature) The second issue is because you are trying to create a record from a type ...


2

To generate docker images from scratch locally, the full recipe is (a lot of patience and disk space) $ wget https://gitlab.com/tezos/opam-repository/-/archive/v8.2/opam-repository-v8.2.tar.bz2 $ tar xf opam-repository-v8.2.tar.bz2 $ cd opam-repository-v8.2/ $ scripts/create_docker_image.sh tezos_build_deps v8.2 $ cd .. $ wget https://gitlab.com/tezos/tezos/-...


2

If you upgrade your node to version 7.4 or 8.0~rc1 you won't need to download the new protocol from your peers so the activation will be simpler and this also lets you check before the activation that the protocol compiles.


2

Courtesy of Pierre: https://gitlab.com/tezos/tezos/-/issues/1370#note_575210288 To recover "quickly", you need to start over from a fresh snapshot. (you could even probably generate a snapshot from your datadir as long as you take as --block something older than the problematic block but the simplest may be to download one from somewhere) To track ...


2

It may be that the whole network is lagging behind, because the timestamp of a block is not necessarily the time at which the block is produced, but instead the minimal time at which the block could be produced. For the latency, one should note that each node first validates a block before propagating it further, so the network diameter also plays a role. ...


2

To get listed on Baking Bad and TzKT as a public baker, just contact our support on twitter, telegram, discord or email us hello@baking-bad.org and we'll walk you through


2

The database powering tezos is extremely susceptible to crashes and corruption. Trash your datadir and import a fresh snapshot.


2

The docker implementation with tezos is bad. https://gitlab.com/tezos/tezos/-/issues/548 It does not allow for many configuration parameters to be customized, and hard-codes many parameters too. For your specific case, this can be solved by using an external mountpoint as the storage for the node like this: -v /opt/tezos/node_data:/var/run/node/data Start ...


1

You can try out the experimental tezos-node storage integrity-check (see tezos-node storage --help): $ ./tezos-node storage integrity-check -d /tmp/tezos-node.jqKo0RB7/ Running the integrity_check. 2k contents / 8k nodes / 0k commits Ok where -d <datadir> is used to give the storage directory of your node. It seems that node can't be running when ...


1

Neither proposals nor ballot operations affect account balance.


1

I answer myself : Contrary to what error message says about RPC port, the problem comes from node listening port. I updated my config.json to set 9733 instead of default 9732, and it's now ok.


1

You need to be sure you're running PtEdo2Zk tezos-baker and tezos-endorser instead of PtEdoTez. Your tezos-baker should at least provide low priority baking rights.


1

The release notes for 7.5+ contain instructions for getting rust built and the Zcash stuff. Make sure to check them out on the Gitlab. Here’s the rust info http://tezos.gitlab.io/introduction/howtoget.html#setup-rust


1

Both transactions sent from your address have the same fee 0.01 tez that is not enough, taking into account the gas limit 50000. Try to set the fee 0.015 tez. If this doesn't help, it also can be a problem with the node you use, so try to use another one, like Tezos Giga Node. And yes, operations stay in the mempool for only an hour, however TzKT explorer ...


1

I found that this answer was the solution. Basically I run the node on machine A using --rpc-addr 0.0.0.0 instead of localhost or 127.0.0.1.


1

Verify the RPC is running by doing this on machine A curl http://192.168.1.200:8732/chains/main/blocks/head/protocols If that does not return, then you don't have the RPC setup correctly. If that does return, next step is to verify B -> A. Can you ping A from B? If not, network issue. If you can, disable iptables completely on A and try to use the client ...


1

The issue is the branch of tezos of which I did a build. Branch mainnet isn't on delphi, apparently. Switching to the latest-release branch and rebuilding solves the issue.


1

There are no URL's involved in running a tezos node. You can run a node anywhere and it will connect to the P2P network. You can put your node in private mode, which means that other nodes will not include your node in their broadcast lists. Some bakers run a setup where they have several "public" nodes, and 1 "private" node which only ...


1

Yes. Tell your tezos-client to use a public RPC node that accepts injections (not all do). tezos-client -A https://publicrpc.node.com/ transfer 50 from tz1.. to tz1... You'll need to find a public RPC that allows injections. I think https://mainnet-tezos.giganode.io/ does


1

At the time I'm writing this is a known issue in Tezos' codebase. Developers are working to fix this issue. It is fine setting export OPAMSOLVERTIMEOUT=300 as a temporary workaround, but beware it may not suffice; I'm regularly using OPAMSOLVERTIMEOUT=6000. For a more robust workaround, apply the following patch (taken from this commit that isn't on master): ...


1

You can use SmartPy Nodes curl https://carthagenet.smartpy.io/version should work fine


1

It means 2 things: 1/ For some reason I cannot really guess like that, the economic protocol disagreed with your block and returned an error message. 2/ There were a bug in the JSON encoding of error messages from the economic protocol (fixed in the dev version but maybe not in v7 indeed) that made it crash with this unhelpful cryptic message. So, the faulty ...


Only top voted, non community-wiki answers of a minimum length are eligible