The end points where mining rigs. (The endpoints can be anything running windows)
Payments where processed with opennode.
but it enabled a simpler payment system. (It requires server owner to kyc) That's what it was about, simplicity for the endpoint user.
It's a compartmentalized system with argument breaks wrote in mostly c#.
It's a trustless design as far as Bitcoin security goes.
Software wise it's like mining software. Servers the pool, endpoints are workers. It's just clever workarounds to look like a pool
We where going to pull device IDs and cross reference mks for live key count estimations
Endpoint workers are teslaagents that report to server.
(They are pretty invasive we recommend keeping them on mining rigs and treating it like so)
Endpoint workers check work and only submit correct work.
Correct work got sent via email (jellyfish)
The endpoints run whatever software you want, but when a request comes in it closes that software and prioritizes the workers task untill finished.
You'd need a domain , email, opennode account
I'd request a few things if I just hand this over.
, if its repurposed for cracking it retains intended features as well to the public.
If you release SC , you have a checksum of some sort to verify it's the real deal.
Point the tip jar to the 1SPLiTKEY wallet.
Credit the 1SPLiTKEY Team. I had a partner in this but they wished to remain anon, I'll respect their wishes but still inadvertently credit them this way.