Aleš Katona

Not officially no. If Erigon supports all required ETH APIs then it'd work, but I suspect they might not have `personal` which is deprecated, but still required by Etherwall. I...

NOTE: if you're ok with running geth just as the account holder node (e.g. not blockchain data) and switch to Erigon for the node itself, it "should" work since that...

You mean not use external blockchain data? If so then yes, you will need to run your own ethereum node however and point to it.

This is not supported atm. but can be done. I don't have the cycles to do it anytime soon but would happily review a PR. The steps would be roughly:...

I'll check, this should be possible.

It seems `geth` has deprecated the `personal` API which Etherwall requires. I'm afraid I do not have the cycles anymore to do a rewrite as the replacement `clef` system is...

A workaround alternative is to use older geth locally (only for account management). If you download geth v1.13 or older (but not older than v1.11) it should work fine if...

Hmm I don't see anything particularly wrong in the code, but AFAICS you should be able to push roughly 60fps with 80Mhz SPI. Of course in practice that's going to...

> The `display-interface` crate and `embedded-hal` 1.0 add quite a bit of overhead, which slows down the display update rate. To work with the new `SpiDevice` trait `display-interface-spi` buffers the...

> > I'm also curious why 64 byte chunks are necessary? > > That seems to be [this bit of code](https://github.com/therealprof/display-interface/blob/8fca041b0288740678f16c1d05cce21bd3867ee5/spi/src/lib.rs#L81-L103). > > Looks like the intent is to read...