Quote from: MoparMiningLLC on Today at 01:30:12 AM

Quote from: WhyFhy on January 22, 2023, 11:05:09 PM

Quote from: MoparMiningLLC on January 22, 2023, 10:46:56 PM

But your process also requires the creators and buyers to also trust your process and to trust you do t keep the partials - right?

right, but even if your creators a bad actor, keeps everything and seeks out the mints theyve done
they couldn't pull the rug on everything. just whatever they've physically intercepted.
for example your vanity coin from willi, you trusted him with this process.
now add in a factor thats more in your hands (split key generation) and you have more doubt?
lets assume he did splitkey on the vanity coin.
he might could take your funds if you sent your coin to him with your partial on a coa style ticket.
question a why would willi want it back? it was custom made to you when you ordered it.
personally, I think your coin would be fine with willi,
as it stands right now. willi could wipe you out with or without the partials.
this process(splitkey generation) requires more trust in yourself than others.
it does add a layer of security but isn't foolproof. It's a hell of a lot better than what I see going on now.
I'm sure any creator that knows how to make keys wouldn't struggle with this concept.

vanitypool used this concept for vanity wallet bounties. its tried and true.

My coin from willi came unbuilt - he put the engraving on for an address I provided - I applied the key and holo myself.

My question is does your system keep/store any data? Being closed source, there is no way to validate what it does - so thst requires us to trust you and trust the creator.

I have no reason to distrust you or willi - in the end, if any makers allow for it, I always buy DIY

Long story short yes but this is notated here in tos https://1splitkey.com/#tos

"Even if we get hacked all the hackers will have is Public Key,SPLiTKEY provided partialpriv and your email address."
"If this case scenario happens, we are not responsible for random collisions via 3rd party bruteforcing, or email phishing attempts." - I have a typo on site here.

there is also a hall of fame, this could be modified to creator's advantage. a chain of command so to speak.
there's a lot of endpoints with the data (for example finished work is on rig, server and via output email)
BUT! we also have a browser hash system that's not fully implemented yet that this can be done and at least eliminates the need for email.
Currently my product isnt designed for a circulating system. its designed for one person and one person only. the endpoint user.

We can purge what we have but as long as the source code remains closed its irrelevant as stated in the tos
Even with all this data out in the open, if you do your due diligence, you should be fine unless your social engineered.
Keep in mind my service wasn't exactly designed with creators in mind, these where going to be offline batch jobs in the initial proposal.
"We are offering a maker vouch of batch splitkey wallets up to 7 digits(or less) & 100 wallets(or less)
this vouch is contingent an endorsement of our service and an agreement of difficulty/prefix.
We highly recommend maker submit 1 pub-key per wallet in this vouch offer."
a casual user has no reason for concern, but I understand the viewpoints a creator would have.
however, our tos states what our service really is a handler for vanitysearch and a modified bitaddress.org
anyone can do this without using my service. As stated though with input we can make it happen.

this won't prevent bad acting by any means.
but it will prevent full rug sweeps at a much better success rate.
if some creators utilize this on top of their already stellar reputation it shouldnt matter even if they got 20 of their original coins back in hand.
the originator having something they issued and seeing the key isn't a bad thing if they've destroyed the keys all along.
But should be viewed from the same current viewpoint as they possibly have the keys anyways.
keep in mind, my product isnt designed for a circulating system. its designed for one person and one person only. the endpoint user.
air gapping custom jobs solves data concerns on distributed coin models.