Bitcoin Forum
May 10, 2024, 08:59:08 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: Vanity address mining - How to pool work?  (Read 2855 times)
Kontakt
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 08, 2013, 05:43:56 PM
 #21

I'm still happy to collaborate. just tell me what you need.
1715331548
Hero Member
*
Offline Offline

Posts: 1715331548

View Profile Personal Message (Offline)

Ignore
1715331548
Reply with quote  #2

1715331548
Report to moderator
1715331548
Hero Member
*
Offline Offline

Posts: 1715331548

View Profile Personal Message (Offline)

Ignore
1715331548
Reply with quote  #2

1715331548
Report to moderator
1715331548
Hero Member
*
Offline Offline

Posts: 1715331548

View Profile Personal Message (Offline)

Ignore
1715331548
Reply with quote  #2

1715331548
Report to moderator
No Gods or Kings. Only Bitcoin
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
fizzisist (OP)
Hero Member
*****
Offline Offline

Activity: 720
Merit: 525



View Profile WWW
July 14, 2013, 03:21:50 PM
 #22

I'm still happy to collaborate. just tell me what you need.

Sorry, I don't seem to be getting notifications from the forum these days, so I didn't see your reply. What kind of stuff would you be interested in helping with? Design? Backend? DB? The site is Python/Flask/MongoDB. The biggest thing to figure out right now is how to restructure the DB for pooled work. I have a basic idea down for using user accounts for requestors (each account maintaining a balance to pay PPS rewards, spread over all outstanding requests from a given user). Miners don't need accounts, but I'd like to copy the Eligius model to let a miner view some stats for a given payout address. I'd also like to get a nice API up.

Structuring the DB will be a task we would need to do together, but either of the other two things could be tasks you could mostly take on yourself. Interested?

Thanks!

Kontakt
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
July 14, 2013, 09:30:29 PM
 #23

I don't know too much about database operations, but I can help design infrastructure for backend communications, whatever language you need. I'd really recommend that work requestors use the same elliptic pair, as all of their requests could be mined simultaneously, by the way.

But yeah, I can help with whatever, more once school starts back up in august.
jixin55
Newbie
*
Offline Offline

Activity: 39
Merit: 0


View Profile WWW
December 14, 2013, 12:23:48 PM
 #24



A client asks for an 8-character vanity address, knowing the cost is too high.  After one (or more) 7-character partial matches have been found, the client cancels their request.  Now what?

Maybe the client wanted a 7-character address in the first place.  Depending what information is public, the client may have their 7-character address for free, and neither you nor the miners get anything.

Maybe the client wanted a 7-character address in the first place.  Even if partial matches are secret, a miner who found a 7-character partial match may negotiate with the original client for the 7-character match.  Neither you nor the other miners get anything.

I would suggest that a refund should deduct *something* related to the value of work done so far.  The deduction to be paid to the miners for work already performed.

it's highly unlikely customers who pay for a vanity address would also be interested doing something so sophisticated for a relatively small gain
Kontakt
Sr. Member
****
Offline Offline

Activity: 266
Merit: 250



View Profile
December 15, 2013, 02:28:33 AM
 #25

Bit of a necro there.
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!