Significant new features in this release! Most notably, @dfinity/agent version 0.20.0 now handles query signature verification. All queries will automatically check for signatures in the state tree signed by the node that replies. This enables the client to verify that there have been no man-in-the…

While this is undoubtedly a nice feature, I assume it might impact performance. Do you have any benchmarks to share? Additionally, how can a developer verify that the signature verification was successful?

As a quick follow-up, 0.20.1 is now released. It has new retry and cache pruning logic for the case where you have a cached set of subnet keys, but the actual node you have queried has recently been updated or replaced. [image] Release v0.20.1 · dfinity/agent-js What's Changed feat: re…

I don’t currently have performance benchmarks for the agent’s performance. The query certificates will be present regardless of whether we check them or not (they have already been on mainnet), so the main new overhead is in checking the subnet status to gather the valid public keys of nodes that ar…

Thanks for the feedback! [image] anon74414410: so the main new overhead is in checking the subnet status to gather the valid public keys of nodes that are allowed generate query responses. That is also cached for subsequent requests, and the request_status call is made in parallel to the query …

@Shuo would you be able to run some benchmarks with an old agent and replica and see what the real world impact is? Is this pattern supported by the caching strategy No, you don’t have any benefit from caching using this strategy. I intend to externalize the cache as an enhancement, but the cach…

[image] anon74414410: but the cache is local to the HttpAgent instance currently So, if I re-create an HttpAgent everytime I create an actor, I get zero caching at the moment and the certificate is fetched for every query? Just asking to be sure I get it right.

I mean, if every single query or update you make creates a new Actor and HttpAgent instance, than yes, you will have no caching benefits. I don’t know exactly why someone would build their app that way - one Actor instance per canister seems pretty reasonable to me, but yeah, that’d be really ineff…

[image] anon74414410: I don’t know exactly why someone would build their app that way Why not? It’s not documented anywhere that agent-js is not stateless and must require a persistent state. [image] anon74414410: that’d be really inefficient Thanks for the confirmation. It means it’s…

It’s not documented anywhere that agent-js is not stateless Fair point! My intuition as a dev is that classes generally hold some degree of state, but not everyone necessarily thinks that way! Would you be interested in a set of purely functional exports to use instead of the Actor and Agent mod…

[image] anon74414410: Would you be interested in a set of purely functional exports to use instead of the Actor and Agent model? I personally would definitely prefer pure functions. The most important thing, I believe, is to have one single approach that is well-documented and that the entire…

Agent-JS 0.20.0 is released! (replica signed query edition)

Developers JavaScript

peterparker January 23, 2024, 10:29am 14

Linking the duplicate question of @JJ_2100 → Invalid signature from replica - #7 by JJ_2100

Topic		Replies	Views
Invalid signature from replica Developers nns	12	974	June 19, 2024
Intermittent "Signature verification failed" errors from AgentJS Developers	6	458	May 9, 2024
Feature discussion: Replica-signed queries Command Line Tools Discussing	14	1555	December 5, 2023
AgentError: Invalid certificate: Signature verification failed with NodeJS Developers Discussing	8	2663	May 24, 2024
Invalid certificate: Invalid signature from replica signed query: no matching node key found Developers	12	2204	November 20, 2023

Agent-JS 0.20.0 is released! (replica signed query edition)

Related topics