aboutsummaryrefslogtreecommitdiff
path: root/api/validators/ZblockValidator/index.js
diff options
context:
space:
mode:
authorkaotisk <kaotisk@arching-kaos.org>2023-03-30 01:09:30 +0300
committerkaotisk <kaotisk@arching-kaos.org>2023-03-30 01:09:30 +0300
commite2da6d2db20093ebd2a65aad35c9991ab1a02176 (patch)
treee5c77a8f4a6fd106b13b659e248cab5768d07cdc /api/validators/ZblockValidator/index.js
parenta4901ad47d2945e9a6c6616661840c97ebbf03e7 (diff)
downloadarching-kaos-tools-e2da6d2db20093ebd2a65aad35c9991ab1a02176.tar.gz
arching-kaos-tools-e2da6d2db20093ebd2a65aad35c9991ab1a02176.tar.bz2
arching-kaos-tools-e2da6d2db20093ebd2a65aad35c9991ab1a02176.zip
Introducing an HTTP JSON API
Diffstat (limited to 'api/validators/ZblockValidator/index.js')
-rw-r--r--api/validators/ZblockValidator/index.js29
1 files changed, 29 insertions, 0 deletions
diff --git a/api/validators/ZblockValidator/index.js b/api/validators/ZblockValidator/index.js
new file mode 100644
index 0000000..2cd2a7b
--- /dev/null
+++ b/api/validators/ZblockValidator/index.js
@@ -0,0 +1,29 @@
+/*
+ * To verify a block we simply put it on `enter`. `enter` will crawl
+ * the zchain that is connected to the zblock we got. If it fails for
+ * any reason we can check `logfollow` for that.
+ *
+ * We send the data tested and the exit code to continuethings()
+ *
+ */
+module.exports = (ch, res) => {
+ const command = spawn("ak-enter",[ch]);
+ response_string = "";
+ command.stdout.on("data", data => {
+ response_string = response_string + data;
+ console.log(`${data}`);
+ });
+
+ command.stderr.on("data", data => {
+ console.log(`stderr: ${data}`);
+ });
+
+ command.on('error', (error) => {
+ console.log(`error: ${error.message}`);
+ });
+
+ command.on("close", code => {
+ console.log(`child process exited with code ${code}`);
+ continuethings(code,ch,res);
+ });
+};