pokt-network / pocket-core

Official implementation of the Pocket Network Protocol
http://www.pokt.network
MIT License
208 stars 101 forks source link

FAQ: What is new with session rollovers in RC 0.10.4? #1577

Open Olshansk opened 11 months ago

Olshansk commented 11 months ago

Objective

Follow up on the session rollover feature from RC 0.10.

Origin Document

Goals

Deliverable

Non-goals / Non-deliverables


Creator: @Olshansk Co-Owners: @RossiNYC

RossiNYC commented 11 months ago

@Olshansk - is there a way to proactively view this and other parameters/settings w/o having to survey node runners directly?

Send out a survey to all node runners to understand what value everyone has set _client_session_syncallowance to in their configurations

Olshansk commented 11 months ago

is there a way to proactively view this and other parameters/settings w/o having to survey node runners directly?

tl;dr No - not to my knowledge.


Extra Unecessary Details & Investigation

Governance Params

I was able to query governance params like so

export POCKET_ENDPOINT=https://mainnet.gateway.pokt.network/v1/lb/60a2ac11b1747c6552385c61
pocket query params --remoteCLIURL ${POCKET_ENDPOINT}

Which gives:

{
    "app_params": [
        {
            "param_key": "application/MaximumChains",
            "param_value": "15"
        },
        ...

But this does not give node configurations....

Tendermint Status / Configs

Since these are Tendermint level configurations, I tried to, I tried to query the status of the Tendermint notes on TesetNet provided by the NodeFleet team (cc @StevenMartinez94 @aqt01) like so:

curl -S "https://testnet:${NODE_FLEET_PASSWORD}@node1.tendermint.testnet.pokt.network/status"

But this does not show node-specific configurations:

{
  "jsonrpc": "2.0",
  "id": -1,
  "result": {
    "node_info": {
      "protocol_version": {
        "p2p": "7",
        "block": "10",
        "app": "0"
      },
      "id": "77e608d8ae4cd7b812f122dc82537e79dd3565cb",
      "listen_addr": "tcp://86.48.21.90:26662",
      "network": "testnet",
      "version": "0.33.8",
      "channels": "4020212223303800",
      "moniker": "testnet-12",
      "other": {
        "tx_index": "on",
        "rpc_address": "tcp://0.0.0.0:26657"
      }
    },
    "sync_info": {
      "latest_block_hash": "9501F2C0A01C80C99B678A9D4B085439D6AAA55D69BAC8FAD0F4E6E02C6502E4",
      "latest_app_hash": "29DAB7A057F099C0F813ACBFC0CAB7654298409F3C3C0241F7164F21F633E812",
      "latest_block_height": "113790"

Node Configs

I ended up asking ChatGPT if it is aware of a way to query node-specific configurations (i.e. the off-chain, non-governance, node specific configs) and it also told me there's no way:

Screenshot 2023-08-03 at 11 34 11 AM


In short, unless the whole network (and forks) adopts a software change that exposes a new endpoint to expose this, I'm personally not aware of a way to do this.

Olshansk commented 11 months ago

@RossiNYC I wanted to know:

  1. Was the context above sufficient?
  2. Any progress on this issue?
  3. Any blockers or support you need on this?
RossiNYC commented 11 months ago

@Olshansk - set up call with @fredteumer & @kutoft for tomorrow afternoon, there was some concern in the last PNF All Hands around over-surveying so I was going to bring this up tomorrow morning on the next call which is why I was asking if the data was available proactively - I'm sure we can get the info, will get feedback/greenlight from them tomorrow (unless I confused a few things here and this isn't the proper process?) Let me know if I am over thinking it!

Olshansk commented 11 months ago

@Olshansk - set up call with @fredteumer & @kutoft for tomorrow afternoon, there was some concern in the last PNF All Hands around over-surveying so I was going to bring this up tomorrow morning on the next call which is why I was asking if the data was available proactively - I'm sure we can get the info, will get feedback/greenlight from them tomorrow (unless I confused a few things here and this isn't the proper process?) Let me know if I am over thinking it!

Sounds like a great plan!