Author

Topic: Free Bitcoin Vanity Pool (Read 1082 times)

newbie
Activity: 28
Merit: 0
October 14, 2014, 10:09:42 PM
#4
The domain is a demonstration (Hence the reason deposits are not allowed)
of a framework that I have been working on since Jan.
Next month we are coming out with full access to the front-end sql user.
Incorporating also (in the new base) elliptical curve signatures so that client requests are signed and can't be
forged without having the private key.


The xbox codes are given out in the shop in exchange for Lua (Moon) which are earned by doing surveys.

The site doesn't have any form of income other than that. As I have said right now it exists primarily for
demonstration.


So this is for mining xbox codes?  Huh Huh







http://btclinks.webstarts.com/
Wink




As for the security of this vanity pool
We have no need for your private key so we don't even ask for it.
The private key and public key you must generate are generated on your browser at another site (not belonging to me)

The public key is used by the miners to generate a private key part which if added to your other private key which
you have kept hidden will be the main private key to control the address belonging to the public key of

Public Key 1 + Public Key 2



A nodejs method of verifying the submitted work (Without the private key) is:

Code:
var bitcoin = require('bitcoinjs-lib');
var BigInteger = require('bigi');
var ecurve = require('ecurve');
var curve = ecurve.getCurveByName('secp256k1');
var inpt = {};
var inte = -2;
process.argv.forEach(function (val, index, array) {
  inpt[inte] = val;
  inte = inte + 1;
});

var PrivKey1 = new bitcoin.ECKey(new BigInteger(inpt[0], 16));
var PubKey1 = PrivKey1.pub;
var point = bitcoin.ECPubKey.fromHex(inpt[1]);
process.stdout.write(new bitcoin.ECPubKey(point.Q.add(PubKey1.Q),false).getAddress().toString());


Whenever you sumbit a request for a vanity address you must submit a public address.
For that public address you will have the matching private key. WE DO NOT ASK FOR THAT
The private key is required by you to generate the full private key with the mined private
key part.
legendary
Activity: 1632
Merit: 1010
October 14, 2014, 03:10:27 PM
#3
So this is for mining xbox codes?  Huh Huh







http://btclinks.webstarts.com/
Wink
newbie
Activity: 53
Merit: 0
October 14, 2014, 03:07:00 PM
#2
SCAM ARTIST JUSTIN FROM OPENEX, ICEYSCRYPT AND BITBAY

USE AT YOUR OWN RISK. ACTUALLY JUST DONT USE IT

I also suspect he ran Mt.Gox
newbie
Activity: 28
Merit: 0
October 14, 2014, 04:10:36 AM
#1
LuaPod is allowing public use of it's demonstration website's Vanity Pool NO FEES AND WE DO NOT ASK FOR YOUR PRIVATE KEY.

http://xboxtrial.cf


You are able to set a reward
(It is up to you whether or not you send the user their funds)
We are not allowing deposits into this system since it is for demonstration purposes only.
If you are interested in how our currency is/will be protected whenever we step
from demonstration you may check our page
at http://xboxtrial.cf/info/info.lua



This is a secure vanity pool that was built using the software VanityGenMiner
It operates securely by calculating addresses in a two part step called
split key generation. In order to make a Bitcoin address you need a public key
The public keys used by Bitcoin (to my understanding) are ECDSA (Elliptical Curve)
Which is another method of saying A HUGE NUMBER that is graphed with points.

The public key and private keys are technically "huge" numbers.
We can actually do two steps to generate a single private/public key from two.
The logical laymans math is this:

Bitcoin Address = bitcoinshafunction(Pub Key 1 + Pub Key 2)

and the Private key for that address would be

Main Private Key = Priv Key Part 1 + Priv Key Part 2


Since we are capable of generating the Bitcoin address with just the
public keys we are able to keep the other Private key hidden
and even out of our servers hands. This is kept safely by the user.



(I did not develop the split address generation method)

Newer methods are being worked on and do exist for split address generation
such as multiplication however these two options provide the same amount of entropy regardless.
The chance of hitting the same key is 1 in an unthinkable number for me.




Jump to: