Comment 16 for bug 1803914

There's been no conversation on this bug for a month , is there still work to do here? I note that most of the snaps mentioned in the description no longer appear to be published, but only the bitcoin snap itself remains.

As I understand it, core bitcoin team are unhappy a third party has claimed the bitcoin name in the snap store.
We (Snap Store) do indeed prefer that core upstream teams are the publishers for snaps in the store. Sometimes that isn't possible, or desireable upstream, so an enthusiastic community contributor, or third party may indeed upload a build of the software in question.

For bitcoin, we understand this may be problematic. The way I see it there are a few ways forward.

1) The bitcoin snap is removed from the store, and the name set aside such that we only allow a bitcoin core developer to publish to it.
2) The bitcoin snap is transferred to the bitcoin core team, who can choose to make it private, continue to update it at their discretion.
3) The snap is left as-is, with Gal Buki publishing updates.

I believe bitcoin core team prefer 1 or 2, I would prefer 2, but 1 is fine, if that's the desire from upstream. The Snap Store admin team are able to process the steps necessary for 1 and 2.

One additional feature [1] not currently in use, which may be desireable, for options 2 and 3 is to enable manifests in the snap. Essentially setting SNAPCRAFT_BUILD_INFO=1 on the build system will cause snapcraft to add a snap/manifest.yaml inserted into the snap. This file details what components were used to build the snap, and links to the build log. This may be appreciated for auditing and transparency purposes. If the snap is built in launchpad or on build.snapcraft.io, I believe this is enabled by default. This option has not been used for the current build of the bitcoin snap, but could be, to give users confidence in the origin of the code in the snap.

[1] https://snapcraft.io/blog/introducing-developer-notifications-for-snap-security-updates