Reducing End to End latencies on the Internet Computer

General
41

Could it be because not all subnets have V3?

42

The boundary nodes don’t support v3 yet. That’s why you see the 404. We are coordinating with the networking team on when to enable it.

3 Likes
43

Thank you. Do you have an estimate for when it’ll be available? Days vs weeks?

45

Update:

V3 Call endpoint

  • The V3 call endpoint is now available, with all subnets and boundary nodes accepting traffic to the /v3/<<effective_canister_id>>/call endpoint.
  • @kpeacock Will publish a new version of agent-js today that targets the V3 endpoint for update calls.
  • One small detail; Only one subnet, snjp, currently responds synchronously with a certificate. All other subnets will accept update calls on the v3 endpoint, but they do not respond with a certificate. The response is asynchronous similar to the V2 endpoint. DFINITY will propose to enable the synchronous response on all other subnets in next week’s proposed release.

Increasing the Block Rate of subnets.

NNS proposals to increase the finalization rate of the subnets below were adopted a few hours ago:

  • 4zbus → 2.61 Blocks/s
  • 2fqc7 → 1.32 Blocks/s
  • qdvhd → 2.24 Blocks/s
  • fuqsr → 2.49 Blocks/s
  • pae4o → 2.31 Blocks/s
  • qxesv → 2.51 Blocks/s
  • w4rem (Bitcoin System Subnet) → 1.8 Blocks/s
  • w4asl → 2.53 Blocks/s
  • brlsh → 2.38 Blocks/s
9 Likes
46
6 Likes
47

Great News! @neeboo lets do V3. Let me know how can we help

2 Likes
48

That’s awesome. Much quicker than I anticipated :clap:t5:

1 Like
49

no not blackbox AI , BUT opensource , audited AI

50

I can see that you really want an answer :wink: What do you mean by audited AI, and how would that solve the problem?

51

Are you usijg the V3 endpoints for rubaru

1 Like
52

Hi! Not yet. There are some additional dependencies that need to be upgraded before we can implement V3. We plan to include it in upcoming releases.