Author

Topic: 0.0325 BTC up for grabs - Round 2 - Completed (Read 1686 times)

newbie
Activity: 1
Merit: 0
September 07, 2018, 08:30:57 AM
#10
 Wink
newbie
Activity: 1
Merit: 0
September 07, 2018, 08:44:55 AM
#9
Inspired from http://forum.bitcoin.org/index.php?topic=23521.0

Round Over... all the coins were claimed within an hour Smiley


0.0015 BTC free to the 1st finder.
   Hint:
   ./bitcoind dumpprivkey 1Mtu4hUJvtCmmdK9pYjqbYYVR4u6BxPWoN
   5KVRdM4X2GbSAwAckoaQja9Vnovnfz4Z3bbHwG5S44vExG1UM2z
       Claimed!
       http://blockexplorer.com/address/1Mtu4hUJvtCmmdK9pYjqbYYVR4u6BxPWoN


0.0105 BTC free to the 1st finder.
   Hint:
   http://imagebin.org/160568
       Claimed!
       QRcode is privkey 5JGcbnumbToWKAyphi1s4xQnca6fzPGWPqJPXLjieMVBPLiKh5b
       http://blockexplorer.com/address/1FnnrUGynY3VswufGPMdEymvNAZrZgA3HC

0.0205 BTC free to the 1st finder.
   Hint:
   my github
       Claimed!
       privkey to be found at http://github.com/zamgo/shared-wallets
       http://blockexplorer.com/address/12FT1M8R8mxZpT6ZdDBzMzNc6myjWwTjDd

 Wink
Cпacибo зa инфopмaцию)
hero member
Activity: 672
Merit: 500
BitLotto - best odds + best payouts + cheat-proof
To import keys you need a patched client for now...
http://bitbills.com/bitcoind-sipa.tgz is one.
Then make sure to have a bitcoin.conf file:
Put into a txt file:
Just remove # at password line and set it.
Code:
# bitcoin.conf configuration file. Lines beginning with # are comments.
 
 
 # Network-related settings:
 
 # Run on the test network instead of the real bitcoin network.
 #testnet=1
 
 # Connect via a socks4 proxy
 #proxy=127.0.0.1:9050
 
 ##############################################################
 ##            Quick Primer on addnode vs connect            ##
 ##  Let's say for instance you use addnode=4.2.2.4          ##
 ##  addnode will connect you to and tell you about the      ##
 ##    nodes connected to 4.2.2.4.  In addition it will tell ##
 ##    the other nodes connected to it that you exist so     ##
 ##    they can connect to you.                              ##
 ##  connect will not do the above when you 'connect' to it. ##
 ##    It will *only* connect you to 4.2.2.4 and no one else.##
 ##                                                          ##
 ##  So if you're behind a firewall, or have other problems  ##
 ##  finding nodes, add some using 'addnode'.                ##
 ##                                                          ##
 ##  If you want to stay private, use 'connect' to only      ##
 ##  connect to "trusted" nodes.                             ##
 ##                                                          ##
 ##  If you run multiple nodes on a LAN, there's no need for ##
 ##  all of them to open lots of connections.  Instead       ##
 ##  'connect' them all to one node that is port forwarded   ##
 ##  and has lots of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################
 
 # Use as many addnode= settings as you like to connect to specific peers
 #addnode=69.164.218.197
 #addnode=10.0.0.2:8333
 
 # ... or use as many connect= settings as you like to connect ONLY
 # to specific peers:
 #connect=69.164.218.197
 #connect=10.0.0.1:8333
 
 # Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to
 # find other peers.
 #noirc=1
 
 # Maximum number of inbound+outbound connections.
 #maxconnections=
 
 
 # JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
 
 # server=1 tells Bitcoin to accept JSON-RPC commands.
 #server=1
 
 # You must set rpcuser and rpcpassword to secure the JSON-RPC api
 #rpcuser=Ulysseys
 #rpcpassword=YourSuperGreatPasswordNumber_385593
 
 # How many seconds bitcoin will wait for a complete RPC HTTP request.
 # after the HTTP connection is established.
 rpctimeout=30
 
 # By default, only RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you like to allow connections from
 # other hosts (and you may use * as a wildcard character):
 #rpcallowip=10.1.1.34
 #rpcallowip=192.168.1.*
 
 # Listen for RPC connections on this TCP port:
 rpcport=8332
 
 # You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
 # running on another host using this option:
 rpcconnect=127.0.0.1
 
 # Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
 # with Bitcoin -server or bitcoind
 #rpcssl=1
 
 # OpenSSL settings used when rpcssl=1
 rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 rpcsslcertificatechainfile=server.cert
 rpcsslprivatekeyfile=server.pem
 
 
 # Miscellaneous options
 
 # Set gen=1 to attempt to generate bitcoins
 gen=0
 
 # Use SSE instructions to try to generate bitcoins faster.
 #4way=1
 
 # Pre-generate this many public/private key pairs, so wallet backups will be valid for
 # both prior transactions and several dozen future transactions.
 keypool=100
 
 # Pay an optional transaction fee every time you send bitcoins.  Transactions with fees
 # are more likely than free transactions to be included in generated blocks, so may
 # be validated sooner.
 paytxfee=0.00
 
 # Allow direct connections for the 'pay via IP address' feature.
 #allowreceivebyip=1
 
 
 # User interface options
 
 # Start Bitcoin minimized
 #min=1
 
 # Minimize to the system tray
 #minimizetotray=1



Now run it. You should be able to import keys generated there or use BOTG to test the script please!
newbie
Activity: 32
Merit: 0
Ok, so I scanned the qr code and i got 5JGcbnumbToWKAyphi1s4xQnca6fzPGWPqJPXLjieMVBPLiKh5b. now what? Smiley

Now you have a private key, in the format supported by an import/export function that may be coming soon to a client near you.  Until then, see https://github.com/bitcoin/bitcoin/pull/220  and compile the showwallet branch from: https://github.com/sipa/bitcoin/tree/showwallet
newbie
Activity: 32
Merit: 0
Could you if you want, next time use the BOTG script to test making private keys. And keep it all in one thread?

More is better.   Continued the original BOTG with 2 more addresses. See http://forum.bitcoin.org/index.php?topic=23521.msg302508#msg302508
newbie
Activity: 16
Merit: 0
Ok, so I scanned the qr code and i got 5JGcbnumbToWKAyphi1s4xQnca6fzPGWPqJPXLjieMVBPLiKh5b. now what? Smiley
legendary
Activity: 1008
Merit: 1001
Let the chips fall where they may.
Continued from http://forum.bitcoin.org/index.php?topic=23521.0


0.0015 BTC free to the 1st finder.
   Hint:
   ./bitcoind dumpprivkey 1Mtu4hUJvtCmmdK9pYjqbYYVR4u6BxPWoN
   5KVRdM4X2GbSAwAckoaQja9Vnovnfz4Z3bbHwG5S44vExG1UM2z
Code:
ubuntu@ubuntu:~/bitcoin/bin/32$ ./bitcoind --help
Bitcoin version 0.3.23-beta

Usage:
  bitcoin [options]                    
  bitcoin [options] [params]  Send command to -server or bitcoind
  bitcoin [options] help                List commands
  bitcoin [options] help      Get help for a command
Options:
  -conf=       Specify configuration file (default: bitcoin.conf)
  -pid=        Specify pid file (default: bitcoind.pid)
  -gen               Generate coins
  -gen=0             Don't generate coins
  -min               Start minimized
  -datadir=     Specify data directory
  -timeout=       Specify connection timeout (in milliseconds)
  -proxy=   Connect through socks4 proxy
  -dns               Allow DNS lookups for addnode and connect
  -addnode=      Add a node to connect to
  -connect=      Connect only to the specified node
  -nolisten          Don't accept connections from outside
  -upnp              Attempt to use UPnP to map the listening port
  -paytxfee=    Fee per KB to add to transactions you send
  -daemon            Run in the background as a daemon and accept commands
  -testnet           Use the test network
  -rpcuser=    Username for JSON-RPC connections
  -rpcpassword=  Password for JSON-RPC connections
  -rpcport=    Listen for JSON-RPC connections on (default: 8332)
  -rpcallowip=   Allow JSON-RPC connections from specified IP address
  -rpcconnect=   Send commands to node running on (default: 127.0.0.1)
  -keypool=       Set key pool size to (default: 100)
  -rescan            Rescan the block chain for missing wallet transactions

SSL options: (see the Bitcoin Wiki for SSL setup instructions)
  -rpcssl                                  Use OpenSSL (https) for JSON-RPC connections
  -rpcsslcertificatechainfile=  Server certificate file (default: server.cert)
  -rpcsslprivatekeyfile=         Server private key (default: server.pem)
  -rpcsslciphers=                 Acceptable ciphers (default: TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH)
  -?                 This help message

That appears to be an undocumented option. Is this one of those "Use the source Luke..." moments?

Edit:  Weird, the help command requires a password to be set:
Code:
ubuntu@ubuntu:~/bitcoin/bin/32$ ./bitcoind help
error: You must set rpcpassword= in the configuration file:
/home/ubuntu/.bitcoin/bitcoin.conf
If the file does not exist, create it with owner-readable-only file permissions.
hero member
Activity: 672
Merit: 500
BitLotto - best odds + best payouts + cheat-proof
Could you if you want, next time use the BOTG script to test making private keys. And keep it all in one thread?
hero member
Activity: 630
Merit: 500
Posts: 69
Oh boy, a chance to win something and a bunch of coded text in a post, this speaks highly to me.... and to every single person on the board lol
newbie
Activity: 32
Merit: 0
Inspired from http://forum.bitcoin.org/index.php?topic=23521.0

Round Over... all the coins were claimed within an hour Smiley


0.0015 BTC free to the 1st finder.
   Hint:
   ./bitcoind dumpprivkey 1Mtu4hUJvtCmmdK9pYjqbYYVR4u6BxPWoN
   5KVRdM4X2GbSAwAckoaQja9Vnovnfz4Z3bbHwG5S44vExG1UM2z
       Claimed!
       http://blockexplorer.com/address/1Mtu4hUJvtCmmdK9pYjqbYYVR4u6BxPWoN


0.0105 BTC free to the 1st finder.
   Hint:
   http://imagebin.org/160568
       Claimed!
       QRcode is privkey 5JGcbnumbToWKAyphi1s4xQnca6fzPGWPqJPXLjieMVBPLiKh5b
       http://blockexplorer.com/address/1FnnrUGynY3VswufGPMdEymvNAZrZgA3HC

0.0205 BTC free to the 1st finder.
   Hint:
   my github
       Claimed!
       privkey to be found at http://github.com/zamgo/shared-wallets
       http://blockexplorer.com/address/12FT1M8R8mxZpT6ZdDBzMzNc6myjWwTjDd

 Wink
Jump to: