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

Runtime code Security Audit #435

Closed
tomusdrw opened this issue Oct 23, 2020 · 2 comments
Closed

Runtime code Security Audit #435

tomusdrw opened this issue Oct 23, 2020 · 2 comments
Labels
A-feat New feature or request P-Runtime

Comments

@tomusdrw
Copy link
Contributor

We need an audit of all the runtime code, which includes:

@tomusdrw
Copy link
Contributor Author

tomusdrw commented Dec 1, 2020

ongoing

@tomusdrw
Copy link
Contributor Author

tomusdrw commented Nov 15, 2021

Second round completed.

During this round of review of the Bridge bridge implementation, we found a few low-severity issues. However, there are no open high-severity issues as of now and while some things can definitely be improved, there is no showstopper and it is sensible to go ahead with the bridge deployment between Polkadot and Kusama, especially since the bridge will initially be in a test state where only privileged entities (root or bridge owner) can send messages.

svyatonik pushed a commit that referenced this issue Jul 17, 2023
* Rename `rococo-collator` to `polkadot-collator`

Also contains some other small changes.

* Test fixes and some further search&replace
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-feat New feature or request P-Runtime
Projects
None yet
Development

No branches or pull requests

1 participant