Why buy energy when you can get it for free (from untapped renewable energy resources).
because the equipment to harvest said untapped renewable energy resources is decidedly non-free. True but you would amortize the cost over xyz years and deduct the cost. Yeah, and payback usually takes 20-40 years for backyard solar or wind equipment. Which probably means, you'll never make your money back (since the equipment is likely to break down and/or need servicing in that time, which pushes back the payback period further, etc). |
|
|
|
|
I mean, really all a roulette table is, in code, is a random number generator with a bunch of checks on the number to see which betting positions the end result potentially matches. IIRC, the default odds are in favor of the house at about 52%, which is close enough that any decent roulette operation would need to have a good-sized backing of money, to account for variance.
If someone wants to put up the funds for the variance, I'll code it. Eventually, anyway. Have a fairly large project in the pipe already, but after that's done, I'll do it if no one else has.
EDIT: I take that back - I believe it would be illegal for me to start up a gambling website in the US. Someone correct me if I am wrong.
|
|
|
|
Of course, the buyer couldn't trust that you didn't save the private key either, so at the point that you scan and enter the private key, the coins would have to be sent SOMEWHERE - either back to the buyer, or to you if the amount is acceptable for the sale.
The only way would be for the seller to attempt to send to themselves at a different address. They would still have to wait for a confirmation to guarantee they'll get the money. Well that's exactly what I mean. Once you enter the private key on the receiver's computer, they need to be sent to a new private key, regardless of which party ends up with the coins. If the buyer and seller mutually agree to not do the sale, the holder of the coins can simple send them to a new address from the already-loaded webpage. And since the transaction processing is done through the website, it could only allow one transaction per private key, to avoid the other person trying to send the coins to his own wallet and possibly getting priority on the transaction. The only way the non-owner could potentially scam is if they quickly imported the private key into their own wallet, did a -rescan, then sent a transaction, but my bet is on the website transaction going through first. |
|
|
|
I'll vouch for this card as being an excellent sound card. Have had one for a couple years now, and love every audible signal it produces.  |
|
|
|
I have an observation to make about this.
The parts of the address after the leading "1" would appear to be computed from a pseudorandom integer ranging 0 .. (256^24)-1.
The largest possible value is 33 base-58 digits long, approximately:
23.33798 x 58^32
If the address value is chosen randomly between 0 and the value above, then:
95.715% will be equal or greater than 58^32, and that group will produce an address with 33 characters following the "1", where the first letter is in the set "23456789ABCDEFGHJKLMNPQR".
3.894% will be less than 58^32 and greater than or equal to 256^23. These will produce an address with 32 characters following the "1", with any base-58 character except "1" as the first letter.
0.391% will be less than 256^23, i.e. the most significant byte is 0. The base-58 encoder will prefix these with at least two 1s instead of one.
So, the easier vanity addresses start with "23456789ABCDEFGHJKLMNPQR". If you want a vanity address starting with any letter from "STUVWXYZabcdefghijkmnopqrstuvwxyz", you're going to have to spend a lot more cycles to find it.
Interesting... I have noticed a lot fewer lower case letters in addresses than upper case, and wondered why that was.... |
|
|
|
I'm still waiting for bitcoin price increases to be started.  |
|
|
|
|
Would be extraordinarily easy to program too. Aside from making the graphics all fancy.
|
|
|
|
1. package this in sccm or $package_management_tool and deploy across a bank or other FI. 2. have the bank's computers mining bitcoins. 3.  4. Profit! 5. Go to jail. Hahaha, this. Reminds me of the ABC guy who added the miner to their website.  |
|
|
|
|
Excellent idea... I've been trying to think of a good way to do this, and I think you hit the nail on the head.
Also, it'd be helpful if the website could also confirm the number of bitcoins at the address of the private key before sending. Say someone wanted to buy something from you with bitcoins, but didn't bring along their computer/wallet to transfer them. Instead, they brought along a private key associated with an address that is loaded with 5 BTC. You couldn't just check the address, because you would have no way of knowing whether the private key he had was associated with that address, or even whether the private key is valid.
Of course, the buyer couldn't trust that you didn't save the private key either, so at the point that you scan and enter the private key, the coins would have to be sent SOMEWHERE - either back to the buyer, or to you if the amount is acceptable for the sale.
Even better - integrate firstbits into said website. Then, you don't have to type in the full address you want to forward the coins along to. Especially helpful for doing it on a mobile, which is the likely platform that would be used to scan and process a QR code anyway.
Perhaps the final piece of the puzzle is an easier way to load up a private key with coins. I think a local script or executable would be best for that though - make sure that the private key isn't being transferred over the internet.
|
|
|
|
|
I wish people would stop complaining about mtgox.... use a different exchange, perhaps? Tradehill has plenty of volume for buying or selling anything less than 100 coins, so unless you're a daytrader or playing the market, I don't see what the big concern is.
|
|
|
|
|
Where on earth are you going to find solar power in any decent amount for $100/month? It'd be at least $10k for a 2000w setup. If you're only paying $100/month for it, it'd take 9-10 years to pay off. And it would only be generating the full 2000w during the peak of the day at the peak of the season - you still have nighttime and winter to deal with.
|
|
|
|
but then couldn't get it to render a wallet file at width=100.
You uploaded your wallet!  If you have coins in them I'd put them in a different wallet now! I did indeed... unconvert it if you like. Lot's o coins in there! |
|
|
|
|
Feel free to convert it if you like.
|
|
|
|
bitplane, nice tool! Though a wallet file ends up being terrible unexciting....  bitlotto, I got your tool to work once or twice, but then couldn't get it to render a wallet file at width=100. It only seemed to like the tall vertical strips, or would randomly output nothing at all. |
|
|
|
|
I haven't had the opportunity to try it yet - in the middle of some operations. But I'll let you know if it does!
|
|
|
|
Sorry - I was excited to have working code, and promptly forgot to send you coins after posting that message. Just sent them now. |
|
|
|
Clarification: Is that for two cards (one with private key and one with bitcoin address) or just one?
This is a special release. you get 1 card witha n address alreay on your wallet engraved, or whatever else really on a gold metal credit card shaped usb drive with 1 gb capacity DEFINITELY count me in for one then! Thanks! |
|
|
|
Anyway to generate a vanity address in windows with the current bitcoin client? My friend wants one.
someone posted a working patch for the latest bitcoin source, it compiled fine for me in linux. I verified it worked by having it "search" for a 1-byte vanity address 'a' and it gave me one. I let it run for a few minutes trying to find one with 'BitVapes' but I'm sure it would take over 9,000 years. I did notice it only tied to one cpu core so I kicked off multiple instances to max out my cpus before shutting it down for fear of melting my box on this basically futile but fun effort. Just curious - does the patch say how many addresses it generates and looks through per second? |
|
|
|
Codler, your first example worked perfectly, thank you! Well, I haven't yet confirmed the receipt of the coins, but it gave me a transaction ID in return, so I am assuming it worked. The integration with bitcoin-php failed though - below are the errors. I'll go ahead and send you your half of the reward since the first solution works, but I would love to have it working and integrated with the existing bitcoin-php package, since that's what my site is built around. So, if you don't mind, take a look at the errors and let me know what you see. If jav replies in a reasonable amount of time with a quick how-to on using his script, he'll get the other half of the bounty. Otherwise, I'll pass that half along to you as well. ( ! ) Notice: Undefined offset: 0 in C:\wamp\www\includes\jsonrpc.php on line 1498
Call Stack
# Time Memory Function Location
1 0.0033 368824 {main}( ) ..\sendmany.php:0
2 0.0708 2095928 BitcoinClient->sendmany( ) ..\sendmany.php:19
3 0.0709 2096048 BitcoinClient->query( ) ..\bitcoin.php:750
4 0.0710 2098736 xmlrpc_client->send( ) ..\bitcoin.php:378
5 0.0710 2098768 xmlrpc_client->sendPayloadHTTP10( ) ..\xmlrpc.php:1223
6 0.0710 2098768 jsonrpcmsg->createPayload( ) ..\xmlrpc.php:1244
7 0.0712 2099040 serialize_jsonrpcval( ) ..\jsonrpc.php:953
( ! ) Warning: reset() expects parameter 1 to be array, null given in C:\wamp\www\includes\jsonrpc.php on line 1443
Call Stack
# Time Memory Function Location
1 0.0033 368824 {main}( ) ..\sendmany.php:0
2 0.0708 2095928 BitcoinClient->sendmany( ) ..\sendmany.php:19
3 0.0709 2096048 BitcoinClient->query( ) ..\bitcoin.php:750
4 0.0710 2098736 xmlrpc_client->send( ) ..\bitcoin.php:378
5 0.0710 2098768 xmlrpc_client->sendPayloadHTTP10( ) ..\xmlrpc.php:1223
6 0.0710 2098768 jsonrpcmsg->createPayload( ) ..\xmlrpc.php:1244
7 0.0712 2099040 serialize_jsonrpcval( ) ..\jsonrpc.php:953
8 0.0717 2099712 serialize_jsonrpcval( ) ..\jsonrpc.php:1498
9 0.0717 2100056 reset ( ) ..\jsonrpc.php:1443
( ! ) Warning: Variable passed to each() is not an array or object in C:\wamp\www\includes\jsonrpc.php on line 1444
Call Stack
# Time Memory Function Location
1 0.0033 368824 {main}( ) ..\sendmany.php:0
2 0.0708 2095928 BitcoinClient->sendmany( ) ..\sendmany.php:19
3 0.0709 2096048 BitcoinClient->query( ) ..\bitcoin.php:750
4 0.0710 2098736 xmlrpc_client->send( ) ..\bitcoin.php:378
5 0.0710 2098768 xmlrpc_client->sendPayloadHTTP10( ) ..\xmlrpc.php:1223
6 0.0710 2098768 jsonrpcmsg->createPayload( ) ..\xmlrpc.php:1244
7 0.0712 2099040 serialize_jsonrpcval( ) ..\jsonrpc.php:953
8 0.0717 2099712 serialize_jsonrpcval( ) ..\jsonrpc.php:1498
9 0.0719 2100056 each ( ) ..\jsonrpc.php:1444
( ! ) Notice: Undefined offset: 1 in C:\wamp\www\includes\jsonrpc.php on line 1498
Call Stack
# Time Memory Function Location
1 0.0033 368824 {main}( ) ..\sendmany.php:0
2 0.0708 2095928 BitcoinClient->sendmany( ) ..\sendmany.php:19
3 0.0709 2096048 BitcoinClient->query( ) ..\bitcoin.php:750
4 0.0710 2098736 xmlrpc_client->send( ) ..\bitcoin.php:378
5 0.0710 2098768 xmlrpc_client->sendPayloadHTTP10( ) ..\xmlrpc.php:1223
6 0.0710 2098768 jsonrpcmsg->createPayload( ) ..\xmlrpc.php:1244
7 0.0712 2099040 serialize_jsonrpcval( ) ..\jsonrpc.php:953
( ! ) Warning: reset() expects parameter 1 to be array, null given in C:\wamp\www\includes\jsonrpc.php on line 1443
Call Stack
# Time Memory Function Location
1 0.0033 368824 {main}( ) ..\sendmany.php:0
2 0.0708 2095928 BitcoinClient->sendmany( ) ..\sendmany.php:19
3 0.0709 2096048 BitcoinClient->query( ) ..\bitcoin.php:750
4 0.0710 2098736 xmlrpc_client->send( ) ..\bitcoin.php:378
5 0.0710 2098768 xmlrpc_client->sendPayloadHTTP10( ) ..\xmlrpc.php:1223
6 0.0710 2098768 jsonrpcmsg->createPayload( ) ..\xmlrpc.php:1244
7 0.0712 2099040 serialize_jsonrpcval( ) ..\jsonrpc.php:953
8 0.0721 2099888 serialize_jsonrpcval( ) ..\jsonrpc.php:1498
9 0.0722 2100144 reset ( ) ..\jsonrpc.php:1443
( ! ) Warning: Variable passed to each() is not an array or object in C:\wamp\www\includes\jsonrpc.php on line 1444
Call Stack
# Time Memory Function Location
1 0.0033 368824 {main}( ) ..\sendmany.php:0
2 0.0708 2095928 BitcoinClient->sendmany( ) ..\sendmany.php:19
3 0.0709 2096048 BitcoinClient->query( ) ..\bitcoin.php:750
4 0.0710 2098736 xmlrpc_client->send( ) ..\bitcoin.php:378
5 0.0710 2098768 xmlrpc_client->sendPayloadHTTP10( ) ..\xmlrpc.php:1223
6 0.0710 2098768 jsonrpcmsg->createPayload( ) ..\xmlrpc.php:1244
7 0.0712 2099040 serialize_jsonrpcval( ) ..\jsonrpc.php:953
8 0.0721 2099888 serialize_jsonrpcval( ) ..\jsonrpc.php:1498
9 0.0723 2100144 each ( ) ..\jsonrpc.php:1444
Caught exception: Didn't receive 200 OK from remote server. (HTTP/1.1 500 Internal Server Error) |
|
|
|
Here is a solution in Python: I usually use the excellent Bitcoin Python Library "authproxy.py" by Jeff Garzik. Here is a version with a few improvements I added: http://pastebin.com/RZNMCGRe . Save this as authproxy.py . Then you can use this code to use sendmany: from authproxy import AuthServiceProxy, JSONRPCException
RPC_URL = "http://rpcuser:rpcpassword@127.0.0.1:8332"
bitcoind = AuthServiceProxy(RPC_URL)
try:
recipients = { '14Z1mazY4HfysZyMaKudFr63EwHqQT2njz': 50.0
, '147dRpRoYQxpf5WGnz7dipCcavtANRRfjt': 50.0
}
bitcoind.sendmany("", recipients)
except JSONRPCException as e:
print "Error: %s" % e.error['message']
You can try out the above code on an empty wallet. You should get an "account has insufficient funds" error. If this code is to your satisfaction, I humbly request the bounty to go to this address: 1fYHRKUXnFfj7ZhjwMMNqddjcnkGtq4wA . :-) Ok, you'll have to forgive me, because I know very little about python except for how to open one from the command line. What do I do with the library file? |
|
|
|
|
Show Posts
