-
Follow-up of https://github.com/ethereum/eth2.0-specs/pull/2147#discussion_r555010707:
@vbuterin:
I think the light client being capable of reorging is reasonable. Definitely an okay response es…
-
## Summary
As I am going through updating the SDK to the latest Tendermint version there have been countless changes. One, in particular, is the trust node feature. This feature allowed users to se…
-
What would be the most appropriate way to fetch the chain spec needed for the light-client with the new V2 APIs?
Although there's been some discussion about a standard format for this checkpoint
-…
lexnv updated
3 months ago
-
the main top-level type we use the chainspec in the ethereum light client is in the header (and all of it's internal types):
https://github.com/unionlabs/union/blob/main/lib/unionlabs/src/ibc/light…
-
My code
```
import time
import machine
import network
import ujson
from simple1 import MQTTClient
SSID = b'Exxxye'
PASS = b'8xxx766'
CLIENT_ID = b'ixxxxxxxxxxxx6eb63'
AWS_ENDPOINT = b…
-
-
The IBC spec discusses misbehavior [here](https://github.com/cosmos/ibc/tree/main/spec/core/ics-002-client-semantics#updatestateonmisbehaviour). This test is the same as #5, but for a light client tha…
-
# Design: Optimistic Sovereign Rollups
## Background
Currently, Sovereign only supports full nodes. Although we have support for zk-proof generation, our node implementation always re-executes a…
-
Using `light-client` with docusaurus triggers a number of errors. While it might be doable to tweak `webpack` configuration to overcome those, it looks worth looking at tackling those individually to …
-
Using Kasper's API library, integrate features that lack the full-node requirement and implement the desktop application as a light client by default.