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

BOB Full Relay #285

Closed
gregdhill opened this issue Jul 9, 2024 · 0 comments · Fixed by #273
Closed

BOB Full Relay #285

gregdhill opened this issue Jul 9, 2024 · 0 comments · Fixed by #273
Assignees
Labels
prio:high Important due to deadlines and/or clear customer needs/benefits.

Comments

@gregdhill
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Currently we have a LightRelay implementation copied from the tBTC-v2 repository. The problem with this relay is that it is not fully secure under SPV assumptions. I wrote a security analysis here but we recently discovered it is a lot cheaper to spoof a block within 2016 * 2 blocks. This isn't an issue for tBTC because they anyway have it controlled by the signer set and they also track specific UTXOs for the global wallet.

Describe the solution you'd like
We need to build a "Full Relay" based on our previous implementations:

See also the old tBTC full relay: https://github.com/summa-tx/relays/blob/30704ab2c443a8a24bdb1228da1e453347f62d3b/solidity/contracts/Relay.sol

Describe alternatives you've considered
We could also build some kind of ZK light client using RISC Zero.

Additional context
Note the following bugs:

@nud3l nud3l added this to Backlog Jul 9, 2024
@github-project-automation github-project-automation bot moved this to New 🆕 in Backlog Jul 9, 2024
@gregdhill gregdhill moved this from New 🆕 to Development 🏗️ in Backlog Jul 9, 2024
@gregdhill gregdhill added the prio:high Important due to deadlines and/or clear customer needs/benefits. label Jul 9, 2024
@github-project-automation github-project-automation bot moved this from Development 🏗️ to Done ✅ in Backlog Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prio:high Important due to deadlines and/or clear customer needs/benefits.
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants