new .wit adding binding-cacher interface

Author: dolled-possum

hyperware-wit/hypermap-cacher-sys-v1.wit

@@ -1,6 +1,6 @@
-interface hypermap-binding-cacher {
+interface binding-cacher {
     // Metadata associated with a batch of Ethereum logs.
-    record logs-metadata {
+    record binding-logs-metadata {
         chain-id: string,
         from-block: string,
         to-block: string,
@@ -10,47 +10,47 @@ interface hypermap-binding-cacher {
     }
 
     // Represents an item in the manifest, detailing a single log cache file.
-    record manifest-item {
-        metadata: logs-metadata,
+    record binding-manifest-item {
+        metadata: binding-logs-metadata,
         is-empty: bool,
         file-hash: string,
         file-name: string,
     }
 
     // The main manifest structure, listing all available log cache files.
     // WIT does not support direct map types, so a list of key-value tuples is used.
-    record manifest {
+    record binding-manifest {
         // The key is the filename of the log cache.
-        items: list<tuple<string, manifest-item>>,
+        items: list<tuple<string, binding-manifest-item>>,
         manifest-filename: string,
         chain-id: string,
         protocol-version: string,
     }
 
-    record get-logs-by-range-request {
+    record binding-get-logs-by-range-request {
         from-block: u64,
         to-block: option<u64>, // If None, signifies to the latest available/relevant cached block.
     }
 
-    variant get-logs-by-range-ok-response {
+    variant binding-get-logs-by-range-ok-response {
         logs(tuple<u64, string>),
         latest(u64),
     }
 
-    // Defines the types of requests that can be sent to the Hypermap Binding Cacher process.
-    variant cacher-request {
+    // Defines the types of requests that can be sent to the Hypermap Cacher process.
+    variant binding-cacher-request {
         get-manifest,
         get-log-cache-content(string),
         get-status,
-        get-logs-by-range(get-logs-by-range-request),
+        get-logs-by-range(binding-get-logs-by-range-request),
         reset(option<list<string>>),
         start-providing,
         stop-providing,
         set-nodes(list<string>),
     }
 
     // Represents the operational status of the cacher.
-    record cacher-status {
+    record binding-cacher-status {
         last-cached-block: u64,
         chain-id: string,
         protocol-version: string,
@@ -61,12 +61,12 @@ interface hypermap-binding-cacher {
         is-providing: bool,
     }
 
-    // Defines the types of responses the Hypermap Binding Cacher process can send.
-    variant cacher-response {
-        get-manifest(option<manifest>),
+    // Defines the types of responses the Hypermap Cacher process can send.
+    variant binding-cacher-response {
+        get-manifest(option<binding-manifest>),
         get-log-cache-content(result<option<string>, string>),
-        get-status(cacher-status),
-        get-logs-by-range(result<get-logs-by-range-ok-response, string>),
+        get-status(binding-cacher-status),
+        get-logs-by-range(result<binding-get-logs-by-range-ok-response, string>),
         start-providing(result<string, string>),
         stop-providing(result<string, string>),
         set-nodes(result<string, string>),
@@ -156,7 +156,7 @@ interface hypermap-cacher {
 
 world hypermap-cacher-sys-v1 {
     import sign;
-    import hypermap-binding-cacher;
+    import binding-cacher;
     import hypermap-cacher;
     include process-v1;
 }