BitShares Forum
Other => Graveyard => KeyID => Topic started by: toast on October 03, 2014, 04:10:33 pm
-
I want a delegate node which runs a keyID registration faucet with completely transparent accounting. Demonstrate that you are signing up new unique users and you campaign to get some commission. Become a valuable asset for later marketing efforts.
A good place to start is with a 1% delegate running this:
https://github.com/keyid/keyid-faucet
-
I just setup a delegate bitcube with a faucet at the following URL:
http://bit.cubeconnex.com:5555
I am creating a new twitter, google and facebook accounts to facilitate this faucet. The layout and design will be enhanced later.
Edit: The authentication using twitter and google can work now. I suppose I need DNS 'coins' to enable the faucet to register KeyIDs, right? Where can I get some DNS to start the operation?
ps: I missed the snapshot phase.
-
I just setup a delegate bitcube with a faucet at the following URL:
http://bit.cubeconnex.com:5555
I am creating a new twitter, google and facebook accounts to facilitate this faucet. The layout and design will be enhanced later.
I clicked on the Twitter link and got this:
Error: Failed to validate oauth signature and token
at Strategy.parseErrorResponse (/root/keyid-faucet/node_modules/passport-twitter/lib/strategy.js:178:10)
at Strategy.OAuthStrategy._createOAuthError (/root/keyid-faucet/node_modules/passport-twitter/node_modules/passport-oauth1/lib/strategy.js:349:16)
at /root/keyid-faucet/node_modules/passport-twitter/node_modules/passport-oauth1/lib/strategy.js:218:41
at /root/keyid-faucet/node_modules/passport-twitter/node_modules/passport-oauth1/node_modules/oauth/lib/oauth.js:543:17
at passBackControl (/root/keyid-faucet/node_modules/passport-twitter/node_modules/passport-oauth1/node_modules/oauth/lib/oauth.js:397:13)
at IncomingMessage.<anonymous> (/root/keyid-faucet/node_modules/passport-twitter/node_modules/passport-oauth1/node_modules/oauth/lib/oauth.js:409:9)
at IncomingMessage.EventEmitter.emit (events.js:117:20)
at _stream_readable.js:920:16
at process._tickCallback (node.js:415:13)
-
I just setup a delegate bitcube with a faucet at the following URL:
http://bit.cubeconnex.com:5555
I am creating a new twitter, google and facebook accounts to facilitate this faucet. The layout and design will be enhanced later.
I clicked on the Twitter link and got this:
Error: Failed to validate oauth signature and token
at Strategy.parseErrorResponse (/root/keyid-faucet/node_modules/passport-twitter/lib/strategy.js:178:10)
at Strategy.OAuthStrategy._createOAuthError (/root/keyid-faucet/node_modules/passport-twitter/node_modules/passport-oauth1/lib/strategy.js:349:16)
at /root/keyid-faucet/node_modules/passport-twitter/node_modules/passport-oauth1/lib/strategy.js:218:41
at /root/keyid-faucet/node_modules/passport-twitter/node_modules/passport-oauth1/node_modules/oauth/lib/oauth.js:543:17
at passBackControl (/root/keyid-faucet/node_modules/passport-twitter/node_modules/passport-oauth1/node_modules/oauth/lib/oauth.js:397:13)
at IncomingMessage.<anonymous> (/root/keyid-faucet/node_modules/passport-twitter/node_modules/passport-oauth1/node_modules/oauth/lib/oauth.js:409:9)
at IncomingMessage.EventEmitter.emit (events.js:117:20)
at _stream_readable.js:920:16
at process._tickCallback (node.js:415:13)
This error occurred because I did not have a google or twitter account then. I have registered both twitter and google accounts. The authentication is working now.
-
I have posted in the marketplace seeking to buy DNS - https://bitsharestalk.org/index.php?topic=9661.0 and top up the coffer.
I just realise delegate bitcube has started producing blocks which means a stream of DNS will be coming in soon. I am very much encouraged! Many thanks for your kind votes and support!
With your crucial support and votes, delegate bitcube will be able to fulfill its mission - to promote Bitshare DNS and attract new users. Looking forward to a bountiful of new happy users. :)
-
@toast
I have setup the site http://bit.cubeconnex.com:5555 for Get Free KeyID. Could you please check if it is working as you have intended? Thanks in advance!
-
@toast
I have setup the site http://bit.cubeconnex.com:5555 for Get Free KeyID. Could you please check if it is working as you have intended? Thanks in advance!
Worked for me to register my KeyID.
Edit: I got a response from the service saying it worked ("Done! Your KeyID account is now registered."), but my registration didn't stick on the blockchain. So I redact my previous statement. Thanks for running the faucet anyways. ;)
-
@toast
I have setup the site http://bit.cubeconnex.com:5555 for Get Free KeyID. Could you please check if it is working as you have intended? Thanks in advance!
Worked for me to register my KeyID.
Edit: I got a response from the service saying it worked ("Done! Your KeyID account is now registered."), but my registration didn't stick on the blockchain. So I redact my previous statement. Thanks for running the faucet anyways. ;)
Thanks for the feedback. I tried and have the same result too. I am not sure how the faucet app suppose to do after the 'Done!' message. I hope toast could give me some guidance here.
Edit:
@toast
The log from the console shows a successful HTTP POST. However the registration is not showing in the blockchain.
GET /user 200 36.292 ms - 110
POST /register-account 200 76.044 ms - 16
-
I am pleased to let you know that the site http://bit.cubeconnex.com:5555 is working.
And if you wish to contribute fund to the Free KeyID faucet, please send your DNS to KeyID: bitcube.
Cheers! :)
-
"Oh no! The faucet has run dry!"
are there any other such registration faucets running?
thanks! :)
-
"Oh no! The faucet has run dry!"
are there any other such registration faucets running?
thanks! :)
try freekeyid.com
-
The faucet has run out of fund faster than I thought. I will send some fund in once the new 0.04 GUI wallet is available.
The new account registration fee has increased 5 times to 500DNS. The Get Free KeyID faucet will need more support and fund. Please kindly send your DNS to account ID bitcube to support this cause. Thank you! :)
-
@cube @toast, I just tried to setup a faucet, but don't know how to config below settings
"
export BACKEND_URL=http://url-of-backend-app:4444
export BACKEND_SECRET=random-string-shared-with-backend
"
Does this mean I need to run a client with "--httpport 4444" on "url-of-backend-app" ip address?
and what does BACKEND_SECRET suppose to be
thanks
-
I could not get the 0.0.4 windows wallet to work after an upgrade. I finally solved the problem by creating a new wallet (painful!). I have sent some fund to the faucet. The registration fee for a new account has increased 5 times. So please do not abuse the use of the faucet. Let the new users benefit from it.
Enjoy! :)
-
@cube @toast, I just tried to setup a faucet, but don't know how to config below settings
"
export BACKEND_URL=http://url-of-backend-app:4444
export BACKEND_SECRET=random-string-shared-with-backend
"
Does this mean I need to run a client with "--httpport 4444" on "url-of-backend-app" ip address?
and what does BACKEND_SECRET suppose to be
thanks
I have ever asked toast similar question but no answer. I believe the brief information in the readme serves a purpose. You may like to read through the codes and be familiarised with them (*hint*). ;)