There has never been a project that I’m aware of that you can associate their project with just wallet address identification. Are you talking about projects that have multiple wallets and uses the same 3-4 characters to begin each? This creates a vulnerability for impersonation imo especially with nfd as an option already.
Maybe show a side-by-side comparison (time lapse) between algovanity and your generator?
Can you edit your post to include all the proposal info here? The idea of this forum is helping people who are not familiar with github to evaluate your proposal.
This tool was created and shared with the community as an open-source repository over a year ago (as shown in the Discord screenshots below). Why is it closed-source now?
Why should the xGov grants program reward a developer who takes a public repository, makes it private, and then asks for funding to re-open it?
It’s basically this - the funds are for reopening the repository and its maintenance. The reason for it being closed source is I’m not publishing it for free anymore.
Do you have any benchmarks across various GPUs? I wrote Algomania [1] a couple yrs ago which still remains the fastest benchmarked vanity address cracker for Algorand that anyone has currently open-sourced at ~1.1M keys/sec, and that was for CPU. Given your current #s up there Algomania is still faster.
Back when I was chasing this game the next logical step was to write a GPU cracker but I had no issues finding 8/9-char vanity tags using Algomania within a couple days. The next step was to port either lisk/nano-vanity [2][3] to Algorand since those are written in Rust + are pre-existing ed25519 vanity gens that already had a decent user base.
Further, I had all sorts of thoughts on creating some cloud vanity cracking service which would involve users generating client-side encryption keys and the service returning them their encrypted mnemonic. But never figured that’d pay off much. I love your idea though (I think I actually recall your Discord launch and wanting to try it but not finding the time). Would love to see how fast this runs on some of the crazier cloud GPU hardware these days.
What, if any benefits does your generator have compared to the other vanity address generators that are available? (examples below). Why are those benefits worth the amount requested?
Hi, all the generators mentioned are CPU-based and the one I’m proposing here is GPU-based. I’ve got some of the benchmarks already here in this topic, see xGov-100 - GPU-based vanity address generator for Algorand - #13 by DragMZ and the proposal itself. So far it’s 10 - 1000x faster than CPU generators, depends on the hardware of course.
As an xgov, It’s up to you to evaluate if the amount requested is worth it and decide. It would be definitely lower if funded directly because of the extra work required to go through the xgov process.
Thanks. Have you contemplated a way to integrate this into a web interface, similar to AlgoVanity? Or would that not be practical? I ask because I’m curious whether you could make this monetizable even if the proposal does not pass. For example, would there be a way for people set parameters on a web interface, pay upfront based on the difficulty of the vanity search, and then (and only then) have the search begin.
