Distribution of code and binary files

[andyoknen]

I suggest discussing options for solving the problem of delivering installation packages to end users. The details are described in my explainer

[gked]

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

1. Developer builds release binary
2. Uploads to IPFS/Bastyon storage
3. Creates release record on Bastyon with:
   • Binary hash
   • IPFS location
   • Version info
   • Their signature
   • Build instructions/environment specs
4. Other developers:
   • Download source
   • Verify they can reproduce the binary
   • Review code changes
   • Add their signatures if approved
5. Once threshold of signatures reached, release becomes "official"
6. Release record updated with all signatures and proofs

Scenario 2: Recovery/Rollback Management

1. Network maintains:
   • Complete version history
   • All signatures for each version
   • Build verification proofs
   • Known issues/security alerts
2. Organizations can:
   • Roll back to any verified version
   • See who signed each version
   • Verify the integrity of old versions
   • Check security history
3. Emergency procedures:
   • Revocation of compromised signatures
   • Quick deployment of security fixes
   • Alert system for critical issues
   • Coordinated rollback procedures

End User Scenario 3: Standard User App Download

• User visits Bastyon web/desktop app

• App shows available versions with:

  • Version number
  • Release notes
  • List of developers who signed
  • Total number of signatures
  • Release date

• User downloads binary

• Bastyon app automatically:

  • Verifies hash matches what's recorded on network
  • Shows which developers signed this version
  • Confirms signatures are valid

• Installation proceeds only if verification passes

End User Scenario 4: Auto-Update Flow

• Installed app checks Bastyon network for updates
• Finds new version with required signatures
• Downloads binary from IPFS/Bastyon
• Verifies signatures and hash
• Prompts user with verification details
• Performs update if user approves

[andyoknen]

@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?