I’d like to open a name dispute for the litecoin-core snap (https://snapcraft.io/litecoin-core).
Current state of the snap
Publisher: Jared Rice Sr. (arisebank)
Last updated: 2017-09-11
Version: 0.52.2, available only on the latest/beta and latest/edge channels
The Snap Store itself already flags it: “This snap hasn’t been updated in a while. It might be unmaintained and have stability or security issues.”
Per its own description, the snap builds from a repository called “GitChains”, described as “powered by AriseBank” — not from the official litecoin-project/litecoin source.
Why I don’t think this should stay with the current publisher
The publisher, Jared Rice Sr., was the co-founder of AriseBank, which the SEC halted in 2018 for running a fraudulent ~$600M initial coin offering (unregistered securities, false claims of FDIC insurance). He subsequently pleaded guilty to felony theft and tampering with government records in a related case.
(As a new forum user I’m limited to two links per post, so these are in code format:)
Combined with the snap being unmaintained for nine years and pointing at a non-upstream source repo, I don’t think this is a reasonable state for a snap that handles users’ cryptocurrency wallets and private keys.
What I’m requesting
Transfer of the litecoin-core name so I can publish a properly maintained snap that:
Downloads the official, GPG-signed release binaries from download.litecoin.org (not a third-party source), verifying both the detached PGP signature and the SHA256 checksums before anything is installed.
Runs the upstream test suite (test_litecoin) as part of every build.
Tracks new upstream Litecoin Core releases going forward.
This seems like a reasonable case to move forward with. One clarification, you’ve filed a dispute but are asking for a transfer. You may be aware but there is a subtle distinction between the two.
I can revoke the name for the current owner and grant it to you; note, however, that because of how snaps work, this will create an entirely new snap ID (32-character identifier) with the same name (SNAP) but since most snap operations actually are keyed on the snap ID, this means it will be effectively a different snap; the implication here is that any current users of SNAP will be stuck with their current revision and not receive updates, unless they uninstall and then reinstall the snap (which is actually removing the old SNAP and installing the new SNAP).
The other thing I can do is a transfer, where I move the existing snap with its current name and ID over to you; this way, users stay “connected” to the snap and don’t need to do anything; they will receive updates and continue working as they did previously. If the old snap was set up for your organization and you just want to recover control of it, this might be the best option.
Thanks — and yes, that distinction matters here, so I appreciate you spelling it out.
I’d like to go with the transfer (same snap ID), for one reason above all: the existing users are the people this request is actually about. Anyone currently running litecoin-core is running a 2017 build, from a non-upstream source, that handles private keys and wallet files. A revoke-and-grant leaves exactly those users stranded on revision 7 indefinitely, and realistically most of them will never find out there was a reason to reinstall. The transfer is the only option that actually reaches them.
To be clear about what I’m claiming: this was never my organisation’s snap, so this isn’t a case of recovering control of something that was mine. It is genuinely a change of hands. I’m asking for the transfer purely because of the continuity for existing users and expanding on my hobbies
One question, if you don’t mind: after a revoke-and-grant, does the previous owner retain the ability to push new revisions to the old snap ID for its existing users, or are they frozen at revision 7? It doesn’t change my preference for the transfer, but I’d like to understand what the alternative would leave behind.
Thanks again for handling the transfer — that part went through fine.
I have run into a follow-up problem though, and since it may be related to the
transfer I wanted to flag it here as well. Every change to this snap’s text
metadata is rejected as a Store terms of service violation. It does not appear
to depend on what I write: changing the summary to “Peer-to-peer network node
and wallet” is refused just as fast as anything else, while screenshot changes
save without any complaint. Uploads are also being held, with the revision page
showing manual_review_policy: allow.
Since the name was transferred rather than revoked and regranted, the snap ID
was preserved — so I am wondering whether restrictions attached to it under the
previous publisher came along with it.
I have sent the details to help@snapcraft.io rather than repeating them here.
Posting mainly so it lands with someone who already has the context.
Apologies I forgot that we’re restricting crypto/finance snaps to verified publishers. In order to unblock you temporarily, I’ve manually approved the revision you upload. However, I would encourage you to have the litecoin-core team apply to be a verified publisher and that should unblock future edits and uploads.
Thank you — that explains everything. I had been trying different wordings for
the summary, which of course was never going to help if the restriction is on
the category rather than on the text. Good to know.
I will ask the Litecoin Core team about applying for verified publisher status.
To make sure I take the right route, two questions:
Verification applies to the publisher account rather than to an individual
snap, correct? I ask because I would rather not be the verified party here.
I am not a member of the Litecoin project (yet) and I do not want to give the
impression that I speak for it. What I do is packaging and administration:
the snap ships the official release binaries from download.litecoin.org
unmodified, verified against David Burkett’s signature at build time, and
compiles nothing of its own.
So my assumption is that the right end state is a verified Litecoin publisher
account owning the snap, with me kept on as a collaborator so I can continue
doing the packaging work. Would you agree that is the route to take, and
would another name transfer be the mechanism for it? The last transfer
preserved the snap ID, which is what matters for existing users.
In the meantime, could I ask for one more manual approval? I have an arm64
build ready. There has never been an arm64 build of this snap, so those users
currently have nothing at all. Both architectures pass review-tools locally
and both contain the official binaries, verified against the signed
SHA256SUMS from upstream:
I would also like to get revision 11 released. Revision 10, which is what is
on stable now, is missing the desktop entry for the GUI, so the graphical
wallet does not appear in users’ application menus. Revision 11 fixes that
and is otherwise identical.
Yes, that is right. I agree that ideally the Litecoin Core team is the party that applies to be a verified publisher, and you can be a collaborator to help them along here. Once they’ve applied and are verified we can initiate a transfer to them
Thanks Melvin — revision 11 is on stable and the listing is editable again,
so the amd64 side is fully in order now.
The arm64 build I mentioned is uploaded, as revision 12, and it is held. If
you could approve that one as well I would appreciate it: there has never
been an arm64 build of this snap, so those users have nothing at all today.
It is the same upstream release as revision 11, built for arm64 from the
same packaging, with the hash I posted above.
The hold comes back as manual_review_policy: allow again — the automated
checks pass and are then set aside. Am I right that this flag sits on the
snap rather than on the publisher account? If so it would survive both
verification and a transfer, and every future release would still need a
human. Worth knowing before we go through the trouble, and if it can be
lifted once the snap is owned by a verified publisher, that would be the
thing to aim for.
Meanwhile I have put the verified publisher request to the Litecoin Core
team. I will follow up here once they have an account and have applied.
Hi Melvin — just a friendly bump after 11 days. A few things still open:
The arm64 upload has since moved on (routine rebuilds from CI) — the currently pending revision is 20 (arm64), same upstream release/hash as rev 12 I mentioned before.
There’s now also an amd64 revision held for manual review: 21 (same release, rebuilt via CI). Could you approve both 20 and 21?
Still curious about the manual_review_policy: allow question above — does that flag live on the snap or the publisher account? Would help us know what to expect after verification/transfer.
No word yet from the Litecoin Core team on the verified-publisher application — still chasing that separately, will update here once there’s movement.
No rush if you’re just busy, just didn’t want this to fall through the cracks.
Hm - something amiss here. Will need to dig a bit as revision 20 seems to be stuck in ReviewInProgress state for a while…
Manual review can be a whole host of things. In this case, we’re getting tripped up because of the financial aspect of the snap, and transfer/verification would ensure that this snap wouldn’t need manual review
After a bit more digging, these revisions look like they’ll be stuck till we get to a verified publisher status. Since we had multiple revisions get flagged for the same reason, the app will auto-reject future revisions and not allow manual review.
Please let us know when the verification bit gets going.
Quick update: it’s stayed quiet on the GitHub side (https://github.com/litecoin-project/litecoin/issues/1098) — no further response from the Litecoin Core team on the verified-publisher request. I’m not expecting anything more to come from that.
Given the track record so far, would it be possible to lift manual_review_policy: allow on this snap ID (litecoin-core) without going through the verified-transfer route? I’d rather stay a plain community maintainer without verified status.
OK — in that case I’d like to request Star Developer status for this account.
Track record is short (one snap), but it covers: taking over litecoin-core via a name dispute against the previous, fraud-linked publisher (arisebank/Jared Rice Sr.), packaging that only ever repackages the officially signed upstream release (PGP + SHA256 + upstream test suite, GitHub - MichielBruijn/litecoin-core-snap: Community-maintained snapcraft.yaml for litecoin-core. · GitHub ), and a few months of active maintenance with prompt responses to every store request.
Hi Melvin, I filed a Star Developer request in policy-requests as you suggested: https://forum.snapcraft.io/t/star-developer-request-michiel-bruijn-litecoin-core (11 days ago, no replies yet). Is that normal turnaround for these, or is there something I should nudge/fix on my end? Meanwhile new revisions still sit in manual review, so I’d like to keep this moving if possible.
Following up here since this is where the verified/Star Developer requirement was originally raised.
I did file the Star Developer request as suggested (policy-requests, Aug 25). It’s been sitting there for over three weeks now with no response from anyone, including a direct question about whether that turnaround is normal.
In the meantime the practical effect is that every revision keeps getting stuck in review, and upstream has since shipped two more releases — including 0.21.5.7, which was a security fix distributed privately to mining pools before being folded into the public 0.21.5.8. Snap users have no way to get either one right now.
I’ve kept up my side of this: verified builds, prompt responses to every request, full disclosure in the Star Developer request itself. At this point I’d just like to know if this is going anywhere. I’m giving it one more week — if nothing moves by then, I’ll stop maintaining the snap and step back from it.