Skip to content
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

Firo (FIRO) integration considerations #177

Closed
kayabaNerve opened this issue Dec 2, 2022 · 3 comments
Closed

Firo (FIRO) integration considerations #177

kayabaNerve opened this issue Dec 2, 2022 · 3 comments
Labels
discussion This requires discussion

Comments

@kayabaNerve
Copy link
Member

kayabaNerve commented Dec 2, 2022

This is solely a tracking issue for notes on the potential of integrating Firo.

Firo is outside the top 500 coins, yet has put forth a strong privacy protocol (Lelantus Spark) which will exceed Monero's (in theory, once Firo deploys theirs, until Monero evolves to Seraphis...). Accordingly, I'm personally interested from a tech perspective, even though it's hard to justify it practically.

We'd have to implement their privacy protocol in Rust, yet since they're a BTC fork, may be able to fork bitcoin-rs for the transaction side of things. The signature scheme, a modified Chaum-Pedersen proof, is decomposable to Schnorr and I've actually written an implementation (of the theory, not of whatever they're deploying). This is actually of independent interest to Serai as it's a single signature with multiple nonces, which our FROST library supports (yet currently doesn't test for, even though that branch arguably serves as a test).

@kayabaNerve kayabaNerve added the discussion This requires discussion label Dec 2, 2022
@monerobull
Copy link

I wouldn't bother with FIRO for quite some time, even if it is interesting.

@kayabaNerve
Copy link
Member Author

It should be noted Spark's modular design means all Serai may have to do is the Chaum-Pedersen proof, types, and RPC code. This assumes a sufficiently competent/flexible Spark light wallet RPC is available.

@kayabaNerve kayabaNerve changed the title Firo (FIRO) listing considerations Firo (FIRO) integration considerations Apr 14, 2023
@kayabaNerve
Copy link
Member Author

Deprecating this issue from lack of use over the past two years/having Discord channels for this topic.

@kayabaNerve kayabaNerve closed this as not planned Won't fix, can't repro, duplicate, stale Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion This requires discussion
Projects
None yet
Development

No branches or pull requests

2 participants