Anchor the ts-proto plugin version to v1.181.2

README.md

@@ -31,7 +31,7 @@ Collection of packages which allow you to build SEDA Data Requests:
 
 # Quick getting started
 
-The easiest way to get started it by using our [starter kit](https://github.com/sedaprotocol/seda-sdk-starter-template) this has all the tools installed that you need:
+The easiest way to get started it by using our [starter kit](https://github.com/sedaprotocol/seda-request-starter-kit) this has all the tools installed that you need:
 
 - AssemblyScript
 - JSON-AS
@@ -47,7 +47,7 @@ For API documentation check [the TypeDocs](https://sedaprotocol.github.io/seda-s
 Below is an example of an Oracle Program that retrieves the name of a planet in the SWAPI database.
 
 ```ts
-import { Process, httpFetch, OracleProgram, Bytes, JSON } from '@seda-protocol/as-sdk/assembly';
+import { Process, httpFetch, OracleProgram, Bytes, JSON } from "@seda-protocol/as-sdk/assembly";
 
 // The JSON schema of the response we're expecting, since in AssemblyScript we need to deserialize JSON into structured objects
 @json
@@ -69,7 +69,7 @@ class PlanetProgram extends OracleProgram {
       // Exits the program (with an exit code of 0) and sets the Data Request result to the planet name
       Process.success(Bytes.fromUtf8String(planet.name));
     } else {
-      Process.error(Bytes.fromUtf8String('Error while fetching'));
+      Process.error(Bytes.fromUtf8String("Error while fetching"));
     }
   }
 }
@@ -82,25 +82,25 @@ new PlanetProgram().run();
 In order to test this we can use a JS testing suite (we use Bun:test in this repository and the starter kits, but any runner should work). We use the `@seda-protocol/dev-tools` package for this, which runs the Oracle Program in a similar environment as it would on the SEDA network:
 
 ```ts
-import { executeDrWasm } from '@seda-protocol/dev-tools';
-import { readFile } from 'node:fs/promises';
+import { executeDrWasm } from "@seda-protocol/dev-tools";
+import { readFile } from "node:fs/promises";
 
-const WASM_PATH = 'build/debug.wasm';
+const WASM_PATH = "build/debug.wasm";
 
-describe('Oracle Program: execution', () => {
-  it('should be able to run', async () => {
+describe("Oracle Program: execution", () => {
+  it("should be able to run", async () => {
     const wasmBinary = await readFile(WASM_PATH);
 
     // Calls our SEDA VM
     const vmResult = await executeDrWasm(
       // The wasm file
       wasmBinary,
       // Inputs for the Oracle Program
-      Buffer.from('1'),
+      Buffer.from("1")
     );
 
     expect(vmResult.exitCode).toBe(0);
-    expect(vmResult.resultAsString).toBe('Tatooine');
+    expect(vmResult.resultAsString).toBe("Tatooine");
   });
 });
 ```

libs/dev-tools/README.md

@@ -6,7 +6,7 @@ The SEDA dev tools includes a CLI to interact with the SEDA chain as well as a c
 
 Command Line Interface (CLI) for the SEDA SDK. Allows you to upload list and show information about Data Request binaries.
 
-This guide assumes you have already a package.json in place and a wasm binary. If not you can use our [starter template](https://github.com/sedaprotocol/seda-sdk-starter-template), which already has all dependencies you need.
+This guide assumes you have already a package.json in place and a wasm binary. If not you can use our [starter template](https://github.com/sedaprotocol/seda-request-starter-kit), which already has all dependencies you need.
 
 First add the SEDA SDK dev tools to your `devDependencies`:
 

libs/dev-tools/package.json

@@ -13,11 +13,11 @@
 	},
 	"main": "build/index.js",
 	"dependencies": {
-		"@cosmjs/cosmwasm-stargate": "^0.32.3",
-		"@cosmjs/crypto": "^0.32.3",
-		"@cosmjs/proto-signing": "^0.32.3",
-		"@cosmjs/stargate": "^0.32.3",
-		"@cosmjs/tendermint-rpc": "^0.32.3",
+		"@cosmjs/cosmwasm-stargate": "^0.32.4",
+		"@cosmjs/crypto": "^0.32.4",
+		"@cosmjs/proto-signing": "^0.32.4",
+		"@cosmjs/stargate": "^0.32.4",
+		"@cosmjs/tendermint-rpc": "^0.32.4",
 		"@seda-protocol/proto-messages": "0.3.0-dev.0-1",
 		"@seda-protocol/vm": "^0.0.4",
 		"big.js": "^6.2.1",

libs/proto-messages/gen/amino/amino.ts

@@ -1,6 +1,6 @@
 // Code generated by protoc-gen-ts_proto. DO NOT EDIT.
 // versions:
-//   protoc-gen-ts_proto  v1.178.0
+//   protoc-gen-ts_proto  v1.181.2
 //   protoc               unknown
 // source: amino/amino.proto
 

libs/proto-messages/gen/cosmos/auth/v1beta1/auth.ts

@@ -1,6 +1,6 @@
 // Code generated by protoc-gen-ts_proto. DO NOT EDIT.
 // versions:
-//   protoc-gen-ts_proto  v1.178.0
+//   protoc-gen-ts_proto  v1.181.2
 //   protoc               unknown
 // source: cosmos/auth/v1beta1/auth.proto
 

libs/proto-messages/gen/cosmos/base/v1beta1/coin.ts

@@ -1,6 +1,6 @@
 // Code generated by protoc-gen-ts_proto. DO NOT EDIT.
 // versions:
-//   protoc-gen-ts_proto  v1.178.0
+//   protoc-gen-ts_proto  v1.181.2
 //   protoc               unknown
 // source: cosmos/base/v1beta1/coin.proto
 

libs/proto-messages/gen/cosmos/msg/v1/msg.ts

@@ -1,6 +1,6 @@
 // Code generated by protoc-gen-ts_proto. DO NOT EDIT.
 // versions:
-//   protoc-gen-ts_proto  v1.178.0
+//   protoc-gen-ts_proto  v1.181.2
 //   protoc               unknown
 // source: cosmos/msg/v1/msg.proto
 

libs/proto-messages/gen/cosmos/staking/v1beta1/staking.ts

@@ -1,6 +1,6 @@
 // Code generated by protoc-gen-ts_proto. DO NOT EDIT.
 // versions:
-//   protoc-gen-ts_proto  v1.178.0
+//   protoc-gen-ts_proto  v1.181.2
 //   protoc               unknown
 // source: cosmos/staking/v1beta1/staking.proto
 

libs/proto-messages/gen/cosmos/vesting/v1beta1/vesting.ts

@@ -1,6 +1,6 @@
 // Code generated by protoc-gen-ts_proto. DO NOT EDIT.
 // versions:
-//   protoc-gen-ts_proto  v1.178.0
+//   protoc-gen-ts_proto  v1.181.2
 //   protoc               unknown
 // source: cosmos/vesting/v1beta1/vesting.proto
 

libs/proto-messages/gen/cosmos_proto/cosmos.ts

@@ -1,6 +1,6 @@
 // Code generated by protoc-gen-ts_proto. DO NOT EDIT.
 // versions:
-//   protoc-gen-ts_proto  v1.178.0
+//   protoc-gen-ts_proto  v1.181.2
 //   protoc               unknown
 // source: cosmos_proto/cosmos.proto
 

libs/proto-messages/gen/gogoproto/gogo.ts

@@ -1,6 +1,6 @@
 // Code generated by protoc-gen-ts_proto. DO NOT EDIT.
 // versions:
-//   protoc-gen-ts_proto  v1.178.0
+//   protoc-gen-ts_proto  v1.181.2
 //   protoc               unknown
 // source: gogoproto/gogo.proto
 

libs/proto-messages/gen/google/api/annotations.ts

@@ -1,6 +1,6 @@
 // Code generated by protoc-gen-ts_proto. DO NOT EDIT.
 // versions:
-//   protoc-gen-ts_proto  v1.178.0
+//   protoc-gen-ts_proto  v1.181.2
 //   protoc               unknown
 // source: google/api/annotations.proto
 

libs/proto-messages/gen/google/api/http.ts

@@ -1,6 +1,6 @@
 // Code generated by protoc-gen-ts_proto. DO NOT EDIT.
 // versions:
-//   protoc-gen-ts_proto  v1.178.0
+//   protoc-gen-ts_proto  v1.181.2
 //   protoc               unknown
 // source: google/api/http.proto
 

libs/proto-messages/gen/google/protobuf/any.ts

@@ -1,6 +1,6 @@
 // Code generated by protoc-gen-ts_proto. DO NOT EDIT.
 // versions:
-//   protoc-gen-ts_proto  v1.178.0
+//   protoc-gen-ts_proto  v1.181.2
 //   protoc               unknown
 // source: google/protobuf/any.proto
 
@@ -37,7 +37,7 @@ import _m0 from "protobufjs/minimal";
  *       foo = any.unpack(Foo.getDefaultInstance());
  *     }
  *
- *  Example 3: Pack and unpack a message in Python.
+ * Example 3: Pack and unpack a message in Python.
  *
  *     foo = Foo(...)
  *     any = Any()
@@ -47,7 +47,7 @@ import _m0 from "protobufjs/minimal";
  *       any.Unpack(foo)
  *       ...
  *
- *  Example 4: Pack and unpack a message in Go
+ * Example 4: Pack and unpack a message in Go
  *
  *      foo := &pb.Foo{...}
  *      any, err := anypb.New(foo)
@@ -67,7 +67,7 @@ import _m0 from "protobufjs/minimal";
  * name "y.z".
  *
  * JSON
- * ====
+ *
  * The JSON representation of an `Any` value uses the regular
  * representation of the deserialized, embedded message, with an
  * additional field `@type` which contains the type URL. Example:
@@ -119,8 +119,7 @@ export interface Any {
    *
    * Note: this functionality is not currently available in the official
    * protobuf release, and it is not used for type URLs beginning with
-   * type.googleapis.com. As of May 2023, there are no widely used type server
-   * implementations and no plans to implement one.
+   * type.googleapis.com.
    *
    * Schemes other than `http`, `https` (or the empty scheme) might be
    * used with implementation specific semantics.