-
Notifications
You must be signed in to change notification settings - Fork 130
Issues: paritytech/parity-bridges-common
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Make compact proofs backwards compatible for relaying with non-compact proof
#3020
opened Jul 1, 2024 by
bkontur
Integration tests and setup multiple relayers for "free header" feature for
polkadot-fellows
#3017
opened Jun 30, 2024 by
bkontur
Include equivocation detection to the auto deployment on Rococo/Westend
#3005
opened May 30, 2024 by
bkontur
Rename our 'obsolete' extensions to something that actually reflects what they are doing
P-Runtime
#2971
opened Apr 24, 2024 by
svyatonik
Investigate and setup
AVERAGE_BLOCK_INTERVAL
correctly everywhere 6 vs 12
#2914
opened Apr 7, 2024 by
bkontur
Remove obsolete relayer CLI args: host, port, path, secure
P-Relay
#2909
opened Apr 1, 2024 by
svyatonik
Complete the "running relayer" documentation with configuration for the Polkadot<>Kusama bridge
#2851
opened Mar 1, 2024 by
PierreBesson
Upgrade deployed bridges to use the new submit_finality_proof_ex call
A-chores
Something that has to be done, as part of regular maintenance
Avoid extra checks in transaction refund extension
A-chores
Something that has to be done, as part of regular maintenance
Previous Next
ProTip!
Updated in the last three days: updated:>2024-11-13.