Simulate rollback message ?

[caike]

Is there a way to simulate a rollback message ? Either manually via CLI or as a configuration via config/env.

[satran004]

@caike

There is no direct way to simulate a rollback with a single-node setup.

But, with some manual steps it should be possible and we may try to automate this in the next release. Btw, manual steps are error-prone.

1. Start the DevKit node using the create-node command.

2. At a certain point, go to the node folder and make a copy of the node’s db folder:

   cp -r db db-snapshot

3. Wait for a few blocks and perform the transactions that need to be rolled back.

4. Stop the node using the stop command. (in yaci-cli prompt)

5. In the node folder, remove db folder and copy db-snapshot to db folder.

6. Start the node using the start command in yaci-cli prompt (not create-node).

7. The node should continue from the point when the snapshot was taken. (pt. 2)

For the Yaci Store indexer, there are some additional steps required.. such as cleaning the Yaci Store db folder (yaci-store folder under node folder).
But for Ogmios and Kupo, a normal start should be enough. (I have not tested it yet)

Depending on the Yaci DevKit distribution, the node folder can be found at:

• Yaci CLI (zip distribution): ~/.yaci-cli/local-clusters/default/node
• Yaci DevKit (Docker distribution): /clusters/nodes/default/node (inside the DevKit container; use devkit ssh)

[caike]

Thanks for the prompt and detailed response. It appears the stop command stops all services, including the node as well as ogmios, kupo, etc.

devnet:default>stop
💡 Trying to stop the running cluster ...
[💡 Process] 16950
[💡 Process] 16952
💡 Stopping node process : Process[pid=16949, exitValue="not exited"]
✅ Killed : Process[pid=16949, exitValue=143]
[💡 Process] 16965
💡 Stopping node process : Process[pid=16963, exitValue="not exited"]
✅ Killed : Process[pid=16963, exitValue=143]
💡 Trying to stop ogmios/kupo ...

Is there a command to stop only the node and keep ogmios running ?

[satran004]

Currently, there is no command to only stop the node. You may need to directly kill the node process. We will plan to add this when we implement rollback support in devkit.