Josh Klopfenstein

We already support submitting v0 transactions. We should be good here. I'll leave this open in the backlog for now and close it once Braavos confirms that Juno meets their...

Latest version is fine, if that makes things easier.

Feel free to work on it @shubham-sonthalia. cc @IronGauntlets @omerfirmak

Thank you! I am no longer actively working on Juno, but @kirugan, @IronGauntlets, or @rianhughes should be able to provide the review.

`starknet_protocolVersion` is not part of the current spec, but there will be a `starknet_version` field in block headers starting in the v0.5 spec, which is currently in [a PR](https://github.com/starkware-libs/starknet-specs/pull/131).

I see. There isn't an endpoint for querying the RPC spec version, which is distinct from the Starknet protocol version. > Running the same api method set Each method receives...

@odednaor Only `v0.5` providers are technically required to implement this method. After a few more spec releases this shouldn't be a problem, but while `v0.5` is new it could be...

@ufo5260987423 Are there plans to continue with this PR? It looks like some work with github actions has been done in the [scheme-langserver](https://github.com/ufo5260987423/scheme-langserver/blob/main/.github/workflows/build-release.yml) repo. I'd be happy to help if...

I'll try to review this sometime next week. May take a bit longer depending on prioritization.

> Spawning a socket for each connection is overkill I believe, one is enough. Understood, thanks. > The problem here is that socket creation can fail in either of those...