-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
expand FFI functionality #919
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
CI problems discussed above were solved via #1172 hiding the discussion to avoid confusion the core goal of this issue remains: expand FFI functionality to all |
since opening this issue, I changed my mind on this topic as far as we know, FFIs are not being actively used for any project in the community the argument for firmware (e.g.: skot/ESP-Miner#168 + https://github.com/plebhash/cgminer-sv2) no longer seems like a meaningful motivation to me, given that in 2025 pure-Rust firmware is perfectly doable (e.g.: https://github.com/bitaxeorg/esp-miner-rs) expanding FFI functionality would consist of a substantial engineering effort, and we don't really seem to have any real motivation for this |
As discussed here, for historical reasons, the FFIs were started with the intention to be imported into Bitcoin Core (TP).
So FFI functionality is currently limited to:
protocols/v2/codec-sv2
protocols/v2/const-sv2
protocols/v2/binary-sv2
protocols/v2/subprotocols/common-messages
protocols/v2/subprotocols/template-distribution-sv2
In order to allow firmware integrations (e.g.: skot/ESP-Miner#168), this functionality needs to be expanded with:
protocols/v2/framing-sv2
protocols/v2/noise-sv2
protocols/v2/subprotocols/job-declaration
protocols/v2/subprotocols/mining
The text was updated successfully, but these errors were encountered: