Roman Zeyde
Roman Zeyde
Maybe we can return a JSON RPC error when responding to [server.version](https://electrumx-spesmilo.readthedocs.io/en/latest/protocol-methods.html#server-version) request? We can define a new `RpcError::Unavailable` error code, and return the current sync status in the error...
Actually, we can support [blockchain.headers.subscribe](https://electrumx-spesmilo.readthedocs.io/en/latest/protocol-methods.html#blockchain-headers-subscribe) while in initial sync - so the client will need to subscribe and wait for "tip" blockhash notification.
Please take a look at https://github.com/romanz/electrs/commit/8ec9ee981f0b8dae23b17259cf4911999da040c7 - it should support `blockchain.headers.subscribe` notifications :)
Opened #543 - let's continue the discussion there.
Please try #628 - to be released soon :)
> * Rust installed from Debian repositories (cargo 1.46.0) This is a bit unexpected, because IIUC Debian 11 should have [Rust 1.48.0](https://packages.debian.org/bullseye/rustc), no?
Could you please share `rustc --version` output?
Thanks! I'll try to reproduce using an emulator ([link](https://linuxconfig.org/how-to-run-the-raspberry-pi-os-in-a-virtual-machine-with-qemu-and-kvm)).
https://github.com/romanz/electrs/runs/3933536627
https://www.reddit.com/r/rust/comments/qamgyh/is_the_chrono_crate_unmaintained