You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 17, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/tutorials/build-files-archive-with-dal/publishing-on-the-dal.md
+27-5Lines changed: 27 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Part 4: Publishing on the DAL"
3
3
authors: Tezos core developers, Tim McMackin
4
4
last_update:
5
-
date: 27 January 2025
5
+
date: 4 February 2025
6
6
---
7
7
8
8
Now that you can get information about the DAL, the next step is to publish data to it and verify that the kernel can access it.
@@ -101,6 +101,20 @@ The slot that you published the message to turns blue, as in this picture:
101
101
102
102
You can verify your message by converting the bytes in the message back to the first 10 characters of the string "Hello, World!"
103
103
104
+
You can also access the data from the DAL node by running this command, where `<PUBLISHED_LEVEL>` is the level that you published the data in and `<SLOT_INDEX>` is the slot that you used:
105
+
106
+
```bash
107
+
curl localhost:10732/levels/<PUBLISHED_LEVEL>/slots/<SLOT_INDEX>/content | more
108
+
```
109
+
110
+
This RPC endpoint returns the full contents of the slot, padded with zeros to the standard size of DAL slots on that network.
111
+
You can copy the contents, omitting the zeros, and use a hexadecimal to string conversion tool to convert it back to a string.
112
+
Online tools can convert hex to string, or you can use the `xxd` program, as in this example, which returns `Hello, world!`:
113
+
114
+
```bash
115
+
echo -n '48656c6c6f2c20776f726c6421'| xxd -r -p
116
+
```
117
+
104
118
## Troubleshooting
105
119
106
120
If you don't see the message that the slot is attested and contains your data, try these things:
@@ -122,10 +136,18 @@ If you don't see the message that the slot is attested and contains your data, t
122
136
from my_wallet for slot 10 with proof "${proof}"
123
137
```
124
138
125
-
- If the slot turned red, it's possible that the attesters for the network are offline.
126
-
In this case, your Smart Rollup cannot use the data on the DAL, but the blue slot in Explorus verifies that you published it successfully.
127
-
Without active attesters, you cannot continue with this tutorial.
128
-
You can try running your own attester by getting tez from the faucet and running a baker as described in [Join the DAL as a baker, in 5 steps](/tutorials/join-dal-baker).
139
+
- If the slot turned red on Explorus, these things may have happened:
140
+
141
+
- The attesters could not download the data to attest it.
142
+
This can happen if your DAL node is misconfigured and did not share the data with other DAL nodes.
143
+
Verify that your DAL node is accessible from outside your local network and that it is running with the correct arguments.
144
+
For example, DAL nodes can fail to share the data if they are configured with an attester configuration but are not connected to a baker with attestation rights.
145
+
You can try deleting the DAL node configuration and restarting the node with the correct `--observer-profiles` argument.
146
+
147
+
- The attesters for the network are offline.
148
+
In this case, your Smart Rollup cannot use the data on the DAL, but the blue slot in Explorus verifies that you published it successfully.
149
+
Without active attesters, you cannot continue with this tutorial.
150
+
You can try running your own attester by getting tez from the faucet and running a baker as described in [Join the DAL as a baker, in 5 steps](/tutorials/join-dal-baker).
0 commit comments