[DRAFT] Make Portal RPC Endpoints Great Again

[Olshansk]

Going to be using this GitHub issue as a thread of thoughts/plans / ideas rather than a pre-prepared issue.

[Olshansk]

Rough and mostly uncensored notes from conversation with @okdas and @fredteumer

Open Questions:
1. [Olshansky] Our v1 versus their v1
2. [Dima] Can we fix TLS configs to pass in service ID via header
3. [Fred] Update portal to show copy-pasta with app-id in portal only
4. [Olshansky] create ticket to track and decomission app-id in PATH in the future
5. [Fred/Olshansky] Annoucnements of decomissioning

The only thing that needs to be fixed today



1. Olshansky fixes 

Works:
curl -X GET https://pocket.rpc.grove.city/v1/status \
  -H "Authorization: REDACTED" \
  -H "Content-Type: application/json" \
  -H "Portal-Application-Id: REDACTED"


Does not work:
curl -X GET https://pocket.rpc.grove.city/v1/REDACTED/v1/status \
  -H "Authorization: REDACTED" \
  -H "Content-Type: application/json"

Olshansky takes what does not work and make it work in the same way as the thing that works

Dima DOES NOT have to do anything crazy with subdomains, TLS, certificates UNTIL we migrate to new infra.

Fred updates the poral such that the default copy-pasta is what CURRENTLY works above so that we can EVENTUALLY decomission the thing that olshansky is going to make work.

Dima is concerneda about Arash and Pascal telling Olshansky he should have done something in guard instead of path.
- Olshansky will use claude code to investigate a guard based solution AND a PATH based solution before committing to one
- 








Expected behaviour:
- Append path to endpoint copy-pasted from portal
- GROVE endpoints DO NOT have a v1: `curl https://rpc.grove.city/ -H …`
- GROVE endpoints for endpoints that do use v1 would loolk like: `curl https://rpc.grove.city/v1/… -H …`

Action items:
- Backwards compatible w/ app-id in PATH
- Portal is updated to shows copy-pasta with app-id in header

Question:
- Should “copy-pasta” from portal:
    - Contain app-id in PATH
    - Contain app-id in header
- 


What are we doing:
- Expe

## [Works] Pocket with subdomain

curl -X GET https://pocket.rpc.grove.city/v1/status \
  -H "Authorization: REDACTED" \
  -H "Content-Type: application/json" \
  -H "Portal-Application-Id: REDACTED"

## [Doesn’t work] Pocket with service header (no subomdina)

** Dima will (do his best to) make this work and let Fred/Olshansky know a status by EOD. **

curl -X GET https://rpc.grove.city/v1/status \
  -H "Authorization: REDACTED" \
  -H "Content-Type: application/json" \
  -H "Portal-Application-Id: REDACTED" \
  -H "Target-Service-Id: pocket" --insecure

- Dima was hoping to do this after infra migration
- Touch appofapps and MCG
- Timebox if there’s a solution in PATH/guard that:
    - Converts header to subdomain
- Wildcard has a certificate
- Non-wildcard does not

## [Works]  XRPL  with subdomain and portal-app-id in PATH

curl https://xrpl-evm-testnet.rpc.grove.city/v1/0caa84c4 \
  -X POST \
  -H 'Content-Type: application/json' \
  -d '{ "method": "eth_blockNumber", "params": [], "id": 1, "jsonrpc": "2.0" }'

## [Works]  XRPL with subdomain and portal-app-id in header

curl https://xrpl-evm-testnet.rpc.grove.city/v1 \
  -X POST \
  -H 'Content-Type: application/json' \
  -H "Portal-Application-Id: REDACTED" \
  -d '{ "method": "eth_blockNumber", "params": [], "id": 1, "jsonrpc": "2.0" }'

## [Doesn’t work]  XRPL with subdomain and portal-app-id in header

curl https://rpc.grove.city \
  -X POST \
  -H 'Content-Type: application/json' \
  -H "Portal-Application-Id: REDACTED" \
  -H "Target-Service-Id: xrpl-evm-testnet" --insecure
  -d '{ "method": "eth_blockNumber", "params": [], "id": 1, "jsonrpc": "2.0" }'


CERT: *.rpc.grove.city
NO CERT: rpc.grove.city


# Not discussing:
- gRPC
- Websockets


For Tendermint chains:
- How to access Tendermint RPC endpoints (CometBFT proxy)
- How to access appchain RPC endpoints (app specific)

Not using the words:
- REST
- Websocket
- gRPC

[Olshansk]

From @ArtSabintsev

[Olshansk]

I looked at a few other platforms to compare how they do JSON-RPC vs non JSON-RPC

Alchemy

Olshanky's Account

Alchemy - JSON-RPC (eth)

curl -X POST https://eth-mainnet.g.alchemy.com/v2/REDACTED \
-H "Content-Type: application/json" \
-d '{
  "jsonrpc": "2.0",
  "method": "eth_getBlockByNumber",
  "params": ["latest", false],
  "id": 1
}'

Alchemy - non JSON-RPC (starknet)

curl https://starknet-mainnet.g.alchemy.com/starknet/version/rpc/v0_8/REDACTED \
   -X POST \
   -H "Content-Type: application/json" \
   -d '{"jsonrpc": "2.0", "method": "starknet_blockNumber", "id": 0}'

Infura

Infura - JSON-RPC (eth)

curl https://mainnet.infura.io/v3/<YOUR-API-KEY> \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc": "2.0", "method": "eth_blockNumber", "params": [], "id": 1}'

Infura - non JSON-RPC (IPFS)

> curl -X POST -u "<YOUR-API-KEY>:<YOUR-API-KEY-SECRET>" "https://ipfs.infura.io:5001/api/v0/object/get?arg=QmaaqrHyAQm7gALkRW8DcfGX3u8q9rWKnxEMmf7m9z515w&encoding=json"
{
  "Links": [
    {
      "Name": "index.html",
      "Hash": "QmYftndCvcEiuSZRX7njywX2AGSeHY2ASa7VryCq1mKwEw",
      "Size": 1700
    },
    {
      "Name": "static",
      "Hash": "QmdtWFiasJeh2ymW3TD2cLHYxn1ryTuWoNpwieFyJriGTS",
      "Size": 2428803
    }
  ],
  "Data": "CAE="
}

Lava

Couldn't get it to work.

[fredteumer]

per your research (and mine which i won't post as you already have done it) we are in alignment with industry expectations and should continue to follow the existing pattern in the Portal for the foreseeable future.

As we onboard other services, this may start to get in the way where we can offer both the traditional endpoints at rpc.grove.city and then our own custom API on api.grove.city. This is something we discussed 2 years ago or more and is still worth exploring but at time of writing, is not a priority.

[fredteumer]

Related: pokt-network/poktroll#1579