404 Erreur lors de l'appel de certains ancêtres de bloc

Question

404 Erreur lors de l'appel de certains ancêtres de bloc

- 3
- 160 2019-12-26
|
Je suisen train d'observer différents comportementspour certains appels RPC

Curl -V http://mainnet.tzos.cryptium.ch:8732/chains/main/blocks/bkrq16vch5v3eeEE1HHSMLH54VBIKKMQYLDV4J7HANX6ZYLDV4J7HANX6ZYLDV4J7HANX6ZYLDV4J7HANX6ZYLDV4J7HANX6ZYLDV4J7HANX6ZE3RMB~72755

ne me donne aucune donnée (erreur 404)

Cependant,quandje fais

curl -v https://mainnet.smartpy.io/chains/main/blocks/bkrq16vch5v3eeE1HHSMENLH54VBIKKMQYLDV4J7HANX6ZYLDV4J7HANX6ZE3RMB~72755

I Obtenir lesinformations sur Bloc BLEAP7XQDW7W7YDU7G38GS82XJE6WNZMFM61CARUPASFBZJ6Q5R . Pourquoiest-ce?

Notez que sije demande un décalageplus récenttel que ~ 1 les deux données de retourpourbloc bln3bh4zcpbtade3va3sqgkyzkdl6tbq7fmd6f6

Edit: une question connexe concernant lanature de lamanière dont lesnœuds completset archives diffèrentpour cet appel RPCest disponible ici
I am observing different behavior for some rpc call

curl -v http://mainnet.tezos.cryptium.ch:8732/chains/main/blocks/BKrq16vch5v3iEE1hHSMENLh54vBikkmqYLDv4j7hANx6ZE3Rmb~72755

gives me no data (error 404)

however when i do

curl -v https://mainnet.smartpy.io/chains/main/blocks/BKrq16vch5v3iEE1hHSMENLh54vBikkmqYLDv4j7hANx6ZE3Rmb~72755

I get the information about block BLeam7Xqdw7w7ydU7g38gs82XJE6wNZMfm61cArUPaSFBzJ6q5r. Why is that ?

Note that if i request a more recent offset like ~1 both return data for block BLN3bh4ZCpBtade3VGbGbFWz2Nhvah3SqGKYZkdL6tbQ7FMD6f6

EDIT: a related question regarding the nature of how full and archive nodes differ for this RPC call is available here
node rpc error

1 réponses

votes

FFF · Accepted Answer · 2019-12-26

3

2019-12-26

Vouspouvez appeler lepoint de contrôle RPC:

  http://mainnet.tezos.cryptium.ch:8732/chains/main/Checkpoint

qui retourne

  {"Block":
  {"niveau": 729089,
   "proto": 5,
   "Prédécesseur": "BMF3ELAHUSKSVSFCT9QVFWX3PF6AV2SLPKRGWKWTEPPMO3TNJEG",
   "TimeStamp": "2019-12-09T21: 56: 50Z","validation_pass": 4,
   "Operations_Hash": "LLOB8AA16CFYHG1RCRMQ2NRLDTTCDEGMNQLXMRWLFD86KMYEFBWBI",
   "Fitness": ["01","0000000000012001"],
   "Contexte": "cowpc7uaehydxj3pepp6cykb11k9xgx4n87cjpamufzbyaerrhsd",
   "Protocol_data": "0000756e6b6f8a3562bc00f131365318490b14b69329500a1f6e2000f0f767edf777ec9c6f33c6ff149eee289f642b2bdcbfdd8d54013da72eeedea56c1b828ba11c8adbd67f63f5e93578"},
 "sauvegarde": 729089,
 "Caboose": 0,
 "Histoire_mode": "complet"
}

History_modepour cenœudest "complet"et desnœuds complets Tatus depruneaux autres que lesen-têteset les opérations debloc àpartir deblocs avant lepoint de contrôle actuel.

Querifier uniquement l'en-tête dublocen mode completfonctionne àn'importe quelniveau,parexemple: boucle -v http://mainnet.tezos.cryptium.ch:8732/chains/main/blocks/BKrq16vch5v3iEE1hHSMENLh54vBikkmqYLDv4j7hANx6ZE3Rmb~72755/header fonctionne. Malheureusement,lenoeudfinal RPCpour les opérations deblocen mode completest actuellementbrisé - Voir leproblème "NODE COMPLÈTEMENT INCOM Données defonctionnement de la requête desblocs avant le dernierpoint de contrôle récent ":

Cecin'est actuellementpas affichépourmainnet.smartpy.io (quiest unnœud d'archive).

Edit: Le RPCestmaintenant ouvert sur Mainnet.smartpy.io (etmontre "Archive").

  {
  "bloquer": {
    "Niveau": 729089,
    "proto": 5,
    "Prédécesseur": "BMF3ELAHUSKSVSFCT9QVFWX3PF6AV2SLPKRGWKWTEPPMO3TNJEG",
    "TimeStamp": "2019-12-09T21: 56: 50Z",
    "validation_pass": 4,
    "Operations_Hash": "LLOB8AA16CFYHG1RCRMQ2NRLDTTCDEGMNQLXMRWLFD86KMYEFBWBI",
    "Fitness": [
      "01",
      "0000000000012001"
    ],
    "Contexte": "cowpc7uaehydxj3pepp6cykb11k9xgx4n87cjpamufzbyaerrhsd",
    "Protocol_data": "0000756e6b6f8a3562bc00f131365318490b14b69329500a1f6e2000f0f767edf777ec9c6f33c6ff149eee289f642b2bdcbfdd8d54013da72eeedea56c1b828ba11c8adbd67f63f5e93578"
  },
  "sauvegarde_point": 0,
  "Caboose": 0,
  "Histoire_mode": "Archive"
} `` `

You can call the checkpoint rpc:

http://mainnet.tezos.cryptium.ch:8732/chains/main/checkpoint

which returns

{"block":
  {"level":729089,
   "proto":5,
   "predecessor":"BMF3ELahUsKsvSfct9qVFWX3Pf6aV2sLpKRgWkwTePpmo3tNjEG",
   "timestamp":"2019-12-09T21:56:50Z", "validation_pass":4,
   "operations_hash":"LLob8aa16cFyHG1rCrMQ2NrLDtCDegMNQLXmRWCHFD86KmYefbwbi",
   "fitness":["01","0000000000012001"], 
   "context":"CoWPc7UaEHYdXJ3PEpp6CyKB11K9XgX4n87cJpAMuFzbyAerrHSD",
   "protocol_data":  "0000756e6b6f8a3562bc00f131365318490b14b69329500a1f6e2000f0f767edf777ec9c6f33c6ff149eee289f642b2bdcbfdd8d54013da72eeedea56c1b828ba11c8adbd67f63f5e93578"},
 "save_point":729089,
 "caboose":0,
 "history_mode":"full"
}

history_mode for this node is "full" and full nodes prune data other than block's headers and operations from blocks before the current checkpoint.

Querying only the block's header in full mode works at any level, e.g.: curl -v http://mainnet.tezos.cryptium.ch:8732/chains/main/blocks/BKrq16vch5v3iEE1hHSMENLh54vBikkmqYLDv4j7hANx6ZE3Rmb~72755/header works. Unfortunately, the RPC endpoint for block's operations in full mode is currently broken - see issue "Full node unable to query operation data from blocks prior to most recent checkpoint":

This is currently not shown for mainnet.smartpy.io (which is an archive node).

Edit: the rpc is now opened as well on mainnet.smartpy.io (and shows "archive").

{
  "block": {
    "level": 729089,
    "proto": 5,
    "predecessor": "BMF3ELahUsKsvSfct9qVFWX3Pf6aV2sLpKRgWkwTePpmo3tNjEG",
    "timestamp": "2019-12-09T21:56:50Z",
    "validation_pass": 4,
    "operations_hash": "LLob8aa16cFyHG1rCrMQ2NrLDtCDegMNQLXmRWCHFD86KmYefbwbi",
    "fitness": [
      "01",
      "0000000000012001"
    ],
    "context": "CoWPc7UaEHYdXJ3PEpp6CyKB11K9XgX4n87cJpAMuFzbyAerrHSD",
    "protocol_data": "0000756e6b6f8a3562bc00f131365318490b14b69329500a1f6e2000f0f767edf777ec9c6f33c6ff149eee289f642b2bdcbfdd8d54013da72eeedea56c1b828ba11c8adbd67f63f5e93578"
  },
  "save_point": 0,
  "caboose": 0,
  "history_mode": "archive"
}```

Point de contrôle denœud SmartPy: https://mainnet.smartpy.io/chains/main/checkpoint

SmartPy node checkpoint : https://mainnet.smartpy.io/chains/main/checkpoint
- 2
- 2019-12-26
- RoMarQ
@ROMARQ,j'ai éditéma réponsepourinclure la sortie du checkpoint RPC sur Mainnet.smartpy.io.

@RoMarQ, I edited my answer to include the output of the checkpoint rpc on mainnet.smartpy.io.
- 2
- 2019-12-26
- FFF
Merci!Selon https://blog.nomadic-labs.com/introducing-snapshots-and-history-modes-for-the-tezos-node.html L'ensemble complet d'opérationsestenregistréen pleinnœud.Cela signifie-t-il que le décalageest considéré commefaisantpartie du contexte?EDIT: Voir https://Tezos.stackexchange.com/questions/1422/Tezos-rpc-doesnt-respectival-with-Blocks-below-The-Current-Checkpointpourplus de détails

Thanks! According to https://blog.nomadic-labs.com/introducing-snapshots-and-history-modes-for-the-tezos-node.html the full set of operations are saved in full node. Does it mean offset is considered part of context ? EDIT: see https://tezos.stackexchange.com/questions/1422/tezos-rpc-doesnt-respond-with-blocks-below-the-current-checkpoint for more details
- 0
- 2019-12-26
- Ezy