Update DAL baker tutorial #423
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
timothymcmackin
force-pushed
the
update-dal-baker-tutorial
branch
from
97af4d1
to
5833d8a
Compare
timothymcmackin
force-pushed
the
update-dal-baker-tutorial
branch
from
b36b42c
to
0f4c008
Compare
|
I think tutorial.mdx also needs to be updated to weeklynet/ghostnet/nothing: |
| In this tutorial you have gone through all the steps needed to participate as a baker and DAL node. | ||
| The steps for participating on any other network, including Tezos Mainnet, are similar, but the attestation delay is much longer on other networks. | ||
|
|
||
| You could further improve the setup by defining system services so that the daemons are automatically launched when the machine starts. |
There was a problem hiding this comment.
FYI: In the next release, we are going to provide Debian packages that could do something like that. But this is not with docker, but systemd.
|
|
||
| You could further improve the setup by defining system services so that the daemons are automatically launched when the machine starts. | ||
| You could also plug a monitoring solution such as the Prometheus + Grafana combo; a Grafana dashboard template for DAL nodes is available in Grafazos. | ||
| The interactions between your baker and the chain can be observed on the Explorus block explorer which is aware of the DAL and can in particular display which DAL slots are being used at each level. |
There was a problem hiding this comment.
The Explorus check is rather easy to do, maybe it could be interesting to put it in the tutorial?
There was a problem hiding this comment.
I don't see any way in Explorus to show that a baker is doing DAL attestations. The DAL page shows if slots are attested but not what bakers are active with the DAL. So looking the baker up in Explorus doesn't seem to provide any info that confirms the baker's DAL activity.
There was a problem hiding this comment.
The trick is to look: https://explorus.io/consensus_ops , you'll see some bakers have a 0 in the bitset field for DAL. Most of them do not have it yet.
There was a problem hiding this comment.
Sorry, I should have hunted around more. How's this? I was unable to get a screenshot with anything other than 0 and X:
There was a problem hiding this comment.
Updated now that we've got better nodes running on Ghostnet:
| sudo apk add curl | ||
| ``` | ||
|
|
||
| 1. In the same terminal window, run this command: |
There was a problem hiding this comment.
I would put this in a dedicated section like: Check the DAL node is well configured that says:
- When the bakers starts, it registers to the DAL node with the profile (we could give it earlier actually) that will tell which topics to track.
- Check your DAL node still have some connections
I will try to ensure there is a producer but it is not the case at the moment, so we cannot guarantee there is some connections in each topics, but what is important is that the node is still connected to the bootstrap nodes.
There was a problem hiding this comment.
There are three types of profiles:
- Operator (if you are a rollup operator)
- Observer (if you are a rollup observer)
- Attester (if you are an attester)
When nothing is mentioned on the CLI, it is none of the three above, so there is no topics.
When the baker starts and a DAL node is provided, it patches the DAL node profile (via an RPC) to take into account the profile associated to the baker.
There was a problem hiding this comment.
Working on clarifying the modes/profiles here: https://gitlab.com/tezos/tezos/-/merge_requests/14591
|
I hope I have provided some elements regarding your two TODOs questions. |
Co-authored-by: fthire <[email protected]>
Co-authored-by: fthire <[email protected]>
|
LGTM. |
|
LGTM. |
Preview: https://docs-staging-git-update-dal-baker-tutorial-trili-tech.vercel.app/tutorials/join-dal-baker
TODOs:
/p2p/gossipsub/connectionsand what does it tell you?