eth_filter config docs

This commit is contained in:
Maksim Fomenkov
2022-10-27 13:44:36 +03:00
parent 0826e647c4
commit fc1b9b9b07

View File

@@ -51,6 +51,7 @@ cluster:
min-peers: 2 min-peers: 2
upstreams: upstreams:
- id: us-nodes - id: us-nodes
node-id: 1
chain: auto chain: auto
connection: connection:
grpc: grpc:
@@ -61,6 +62,7 @@ cluster:
certificate: client.crt certificate: client.crt
key: client.p8.key key: client.p8.key
- id: infura-eth - id: infura-eth
node-id: 2
chain: ethereum chain: ethereum
role: fallback role: fallback
labels: labels:
@@ -80,6 +82,7 @@ cluster:
username: ${INFURA_USER} username: ${INFURA_USER}
password: ${INFURA_PASSWD} password: ${INFURA_PASSWD}
- id: ethereum-pos - id: ethereum-pos
node-id: 3
chain: ropsten chain: ropsten
connection: connection:
ethereum-pos: ethereum-pos:
@@ -110,6 +113,12 @@ In the example above we have:
** label `[provider: infura]` is set for that particular upstream, which can be selected during a request.For example for some requests you may want to use nodes with that label only, i.e. _"send that tx to infura nodes only"_, or _"read only from archive node, with label [archive: true]"_ ** label `[provider: infura]` is set for that particular upstream, which can be selected during a request.For example for some requests you may want to use nodes with that label only, i.e. _"send that tx to infura nodes only"_, or _"read only from archive node, with label [archive: true]"_
** upstream validation (peers, sync status, etc) is disabled for that particular upstream ** upstream validation (peers, sync status, etc) is disabled for that particular upstream
=== Nodes
`[node-id: 1]` is numeric node identifier defined in a range [1..255] and used to forward
`eth_getFilterChanges` request to the node where one of `eth_newFilter`, `eth_newBlockFilter` or `eth_newPendingTransactionFilter` methods was executed (because filter is s stateful method).
*It's kindly recommended* to strictly associate _node-id_ parameter with a physical node and keep it during any configuration changes
=== Roles and Fallback upstream === Roles and Fallback upstream
By default, the Dshackle connects to each upstream in a Round-Robin basis, i.e. sequentially one by one. By default, the Dshackle connects to each upstream in a Round-Robin basis, i.e. sequentially one by one.
@@ -206,6 +215,10 @@ Dshackle currently supports
- `eth_getUncleByBlockNumberAndIndex` - `eth_getUncleByBlockNumberAndIndex`
- `eth_feeHistory` - `eth_feeHistory`
- `eth_getLogs` - `eth_getLogs`
- `eth_getFilterChanges`
- `eth_newFilter`
- `eth_newBlockFilter`
- `eth_newPendingTransactionFilter`
.Plus following methods are answered directly by Dshackle .Plus following methods are answered directly by Dshackle
- `net_version` - `net_version`