3 post etichettati con "repliqate"

Nel corso di quest'anno abbiamo già parlato dei cambiamenti che abbiamo fatto per rendere i binding di Cwtch riproducibili.

In questo devlog parleremo di come l'interfaccia utente Cwtch è attualmente creata, le modifiche che vi abbiamo apportato per rendere verificabili le future distribuzioni, e i prossimi passi che faremo per rendere tutte le build di Cwtch riproducibili.

Ciò sarà utile a chiunque cerchi di riprodurre specificamente i build dell'interfaccia utente di Cwtch e a chiunque voglia iniziare ad implementare build riproducibili nel proprio progetto.

In this development log, we continue our previous work on reproducible Cwtch bindings, uncovering the final few sources of variation between our Repliqate scripts and our docker/drone builds, leading to fully reproducible builds for Cwtch Android bindings!

From the start of the Cwtch project, the source code for all components making up Cwtch has been freely available for anyone to inspect, use, and modify.

But open source code is only one defense against malicious actors who might seek to undermine your privacy and security. This is why, as part of our ongoing Cwtch Stable work, we are working towards making all parts of the Cwtch chain reproducible and verifiable.

The whole point of reproducible builds is that you no longer have to trust binaries provided by the Cwtch Team because you can independently verify that the binaries we release are built from the Cwtch source code.

In this devlog we will talk about how Cwtch bindings are currently built, the changes we have made to Cwtch bindings to make future distributions verifiable, and the next steps we will be taking to make all Cwtch builds reproducible. This will be useful to anyone who is looking to reproduce Cwtch bindings specifically, and to anyone who wants to start implementing reproducible builds in their own project.