Skip to content
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.

upgrades: understand impact and gather requirements #171

Open
liamsi opened this issue May 31, 2021 · 1 comment
Open

upgrades: understand impact and gather requirements #171

liamsi opened this issue May 31, 2021 · 1 comment

Comments

@liamsi
Copy link
Member

liamsi commented May 31, 2021 •
edited
Loading

IMO, before jotting down an upgrade mechanism (#128), we should understand (and write down) the impact of upgrades in general. This is more relevant in the light of LL being the DA layer for potentially many rollups. These rollups must be included in considerations. Hence, I propose to gather clear requirements before proposing or writing down a solution. Let's discuss these first.

ref: #128
@liamsi liamsi mentioned this issue May 31, 2021
Open
@liamsi liamsi added this to To do in Testnet via automation May 31, 2021
@liamsi liamsi removed this from To do in Testnet May 31, 2021
@liamsi liamsi added this to To do in Devnet via automation May 31, 2021
@liamsi liamsi changed the title upgrade: understand impact and gather requriements upgrades: understand impact and gather requirements May 31, 2021
@liamsi liamsi mentioned this issue May 31, 2021
Closed
@liamsi liamsi removed this from To do in Devnet Dec 8, 2021
@liamsi
Copy link
Member Author

liamsi commented Dec 8, 2021

same: #128 (comment)

@liamsi liamsi mentioned this issue Jan 3, 2022
Closed
5 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
No open projects
Celestia Node
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@liamsi