Topic: 1SPLiTKEY.com The easy, secure and mostly free vanity wallet service closed/down (Read 590 times)

Due to lack of interest (both parties myself and customers), we will no longer be maintaining this, and we do not own the tld (1splitkey.com) anymore.
Thanks to all who gave it a shot and used it. I enjoyed this project, but these days I'm shifting away from this kind of work and focusing on different endeavors.

My guess: there's just not much demand for this. I've had my "Pretty Addy Giveaway" since 2016, and from all the people who requested an addy, only a few actually used it. And even less people used it frequently.

At least the domain name gives a very strong hint of what to expect

We won't be doing opensource.

Or releasing our customer client in general.

An in-depth analysis has determined that this would likely do more harm to the community than good.

Repurposing concerns are as follows.

APT(Advanced Persistent Threat)

RAT(Remote Access Trojan)

Cryptojacking malware

A new dilemma.

monetizing, we have had no suggestions.

It's not that we want money, it's that we want to see more utilization in a positive manner.

Scam sites still out SEO us as this project has less positive interaction than the negative interaction the other sites have.

Basically, people like to talk more about the bad than the good.

More utilization would generally at least cover the server cost through a tipjar. At least that was the hope.

It's not worth the time upkeep anymore since it lacks a paying userbase.

Its 50/50 between free wallet seeking customers, or hackers. Thats our customer base. Resulting in negative unity.

So, this has been good to sharpen the saw in some respects but a little bit of insanity at the same time.

Weigh in what we should do?

We are open to selling and let the community know we no longer own it, but we don't want it in the hands of a bad actor.

We have some updates coming.
Open the source code for our end point app.
We are going to relay as much data as we can kind of like a "pool" (workers,cards, threads,m/keyps est, current job, time estimates, pending jobs).
No charge for service (unrealistic jobs that will just waste resources wont be accepted) ex, trailing 1's , pivot wallet with no actual prefix's
However this may lead to some kind of undesired profit model such as all wallets go into hall of fame involuntarily unless gratuity is paid based on initial difficulty?
(we are open minded, workers that help solve problems would get tip share)
Browser session's that purge instead of email (we will still have the email system but it will be optional)
We will be launching the "Advanced" version here soon. All features we be elaborated on later on but 1SPLiTKEY will be more than vanity searching and focused more on communal efforts.
Feedback is always welcomed.

The website quotes you before submitting entry. Trailing 1's do cost though. 1234567=Free  1111111=$347

I came across this address on the blockchain...
https://www.blockchain.com/btc/address/11111112bNPrmptGiA7obGq5KHrNaKdX

Out of curiosity, what would be the cost estimate for generating such a prefix (11111112) ?   Seems expensive.

Edit: found another example! So perhaps they’re not that hard to find.

Bump/Update 1splitkey's key counts are down for the moment so results may not be as instantaneous as usual.
I had to shut down outdoor servers due to extreme heat for the time being.
For those that don't know I'm in Texas and run in my garage, it's been over 105°F outdoors for weeks, normally I'd cool the garage but mining profits arnt well enough to justify that.

With this being said I'm looking for bulk a2000's I can run indoors or any low power 75w cards that at least pay for the electric they use.

To clarify 1splitkey will always be up and strive to be the best at what we do , we just need to optimize.

Solved thank you for bringing this to my attention.

The SSL for the 1SPLiTKEY.com site expired last week. Check to make sure certbot is running. https://certbot.eff.org/
Don't know if it's that or something else causing generation issues. Or if my browser is just not happy with the expired SSL.

-Dave

I need benchmarks for those cards, The 3090's you mentioned to me earlier should average around 1800-1900mk/s each with splitkeys? 3700~ without. (Bitcraken based numbers) I have yet to discover what actually matters in key counting on VS , theres speculation that its something to do with key cuda cores but I personally dont see it.
a4500 7168 cc
a5000 8192 cc
v100's 5120 cc 8500
2080ti 4352 cc (these outperform my v100's in vanity search)
titan z 5760 cc <- pretty intimidating for a 8 year old card.
3080 8960 cc near par with 2080ti's on sp keycounts
3090 10496 cc
3090ti 10752 cc
a100 6912 cc
If anyone could contribute these keycounts I would greatly appreciate it.
Phil on 1957phiLip -case insensitive in a best case scenario with the gear we have 3-4 days , an absolute worst case scenario (and worst case does happen sometimes) 50 days~
the 957 and iLi are a 66% increase on verbatim digits so its definitely not a simple all caseable "9 digit wallet" amazingly enough I dont see any pivots even up to 1957philipma
1957philipma on my best rig quotes 645~ days for 1 output with splitkeys
without splitkeys 422~ days for the only output you'll need.


Edit - Added SHA256 checksums for GH and Direct download button.
You can verify the tool with SHA256 (5/7/22)

I did a van address a few years ago took 2 weeks with a threadripper.




https://bitcointalksearch.org/user/philipma1957-64507


Other contact info:   My alt is judypug1956 vanity addy: 1956jUdYP.....FwiBSzt9AECdWj3KE4WV7taiM




https://bitcointalksearch.org/user/judypug1956-166799


but it was 8 characters

1957philip would be 9

and 1957philipma would be 11 and take basically a real long time.

I have a 12 card rig running smos
it has 11 rtx a4500 cards  and 1 rtx a5000 card.  We may be able to benchtest it and see what it can do speed wise.

We will see what we can conjure up on this notion. Possibly a cookie based delivery system ,  Short wallets I don't see a problem presenting on page , its the longer work I worry about.
There's many wonderful privacy based services. We may want to push service updates via email but we wont share your data, I cant even really think of service updates other than "hey we can do 7 digits free now".


edit. @DaveF @LoyceV
Here's a method to prevent email collection.
When a request is added to the database, a hash is generated based on [email, prefix, wallet type, current time (second)].
We could make it so that visiting "1splitkey.com/[hash]" brings you to a "progress" page made for your keys.
And maybe add a "I've finalized my wallet. Please purge my keys". Which invalidates the webpage.

A URL to bookmark to check the results could work.

I have had many dealing with WhyFhy so I would have no issues trusting him with this.
Did a quick test and the key was delivered and it did work.

Would like to see a way for there to be NO email involved, it's just another point of having another service know something about you.
The KEYS would still be secure but it's a way to trace a BTC address to an email address.

-Dave

We are running mostly nvidia so we are using VanitySearch for faster results due to its EC modifications,
1abcdef still shows 478688907 difficulty on vanity search with case insensitive
1abcdef     shows 888446610539 difficulty non case insensitive
1abcdefgh shows 402577370400 case insensitive 8 digits we output
1abcdefghj shows 11674743741610 case insensitive 9 digits
your right these a phenomenally vast differences
but when you factor in split key variables such as 1 of 6+ may be correct and key counts get divided 40-60%+ with a pub key applied and rekey drops we have to take this into account.
again this relates to the time it actually takes to yield a proper result so we concluded the following difficulty division formula is fair to us and our end point users.
If all case-able = 50% discount if partially case-able 30% discount if none case-able 0% discount.
Keep in mind this service does need to profit sometimes

I had never heard of vanity addresses until WhyFhy introduced me to them. The process I went through to create the public/private key was a breeze thanks to his instructions. I have zero experience in coding and/or brute forcing, so this was a neat project to be a part of. At no point was I asked for the private key. In my experience, no compromise in security. Now i've got a Vanity Address to show off and share my experience.

Are you sure there isn't something wrong in your code? Try to search 1ABCDEFG case-insensitive and keep searching until one of the outputs is 1ABCDEFG case sensitive. I expect many results like 1abCdEfG before you get it case sensitive, and if you get that many case insensitive results, it can only mean it's much easier.
In my experience with vanitygen, case insensitive in general is really much easier.

I've numbered your concerns and will address them accordingly. Thank you for your feedback

1.
We understand that "True" difficulty says one thing but we've done a lot of back end testing and have concluded that time is the big enemy
even if calculated that its 97% easier the time it takes to generate is still probable based on our in house formula.
We would assume case insensitive 1ABCDEFG is very easy to generate based on difficulty  but the truth is it still takes the same amount of time\2 to generate
since time is $  and all case insensitive scenarios take about half as long or slightly more we felt it best to max deduce 50% if all prefixes are case-able.
if partially case-able we've chosen %30, whether its 1 letter or all but 1 letter.

2.
Your absolutely correct on this, But is an "if" scenario that can be addressed via MD5 Checksums.
We will promptly implement this to address this concern and put the checksum on the site & github and here and possibly something like steemit that cant be edited. Great point out! Much Thanks!
In a worst case scenario of everything being (gh/server ect) compromised the site is registered to valid CC with multifactor auth measures implemented and everything can be taken down and promptly addressed.  
edit- Added SHA256 Checksum
You can verify the tool with SHA256 (5/7/22)


3.
Thats great to know! I hope more feedback comes in like this, I value it and appreciate it more than you know.

 
 

Isn't the difficulty calculation still wrong?
1LoyceVa: $2.00 case sensitive.
1LoyceVa: $1.50 case insensitive.
The Y, C, E, V and A can all change case, that's 2⁵ more valid results. Shouldn't the case insensitive address be 97% cheaper instead of only 25%?
My vanitygen stopped working (and doesn't compile anymore) so I can't check it.

There's a flaw: you made your own merge tool, and if anyone would get access to your account, it could get compromised. A fake random for instance would put your funds at risk. I think it's much better to (recommend to) use the original Bitaddress. Even if you "just" forked it, checking it is a lot of work.

I tested the service, and got 1LoyceV in about a minute. I used online Bitaddress for this test, so it's totally compromised.

Absolutely , I would even let you see/use the proprietary software to chip in mk/s as I trust you wouldn't leak it given your my hardware escrow guy.