Open andyoknen opened 1 week ago
I think it's a step in the right direction because it enables Bastyon project participants to drop their dependency on centralized solutions.
What did you mean in your post about making it mandatory? Is this about making code publishing to IPFS only? How do you foresee of using Bastyon as part of the solution? Something along the lines below?
Scenario 1: Developer Publishing Flow
Scenario 2: Recovery/Rollback Management
End User Scenario 3: Standard User App Download
User visits Bastyon web/desktop app
App shows available versions with:
User downloads binary
Bastyon app automatically:
Installation proceeds only if verification passes
End User Scenario 4: Auto-Update Flow
@gked I think distribution via IPFS is not necessary, because the current IPFS network is not stable, and we do not have enough independent nodes to create a reliable network. Overall, I think github looks good in the short term. The main thing is the process of passing the baton between developers - how to solve the problem of parallel signature?
I suggest discussing options for solving the problem of delivering installation packages to end users. The details are described in my explainer