So, after discussions on IRC we have resulted in the creation of a new bitcoin wiki at https://en.bitcoin.it/Why, you are going to tell me, do we have a new wiki while there's already one on bitcoin.org ? Well, I'll give the three main reasons: - People do not want to add community-related subjects to the official bitcoin wiki. Probably because nobody said if it was OK or not, but since the wiki is labelled as "Documentation", only technical stuff have ended in there. I believe the community should have its own wiki too (it may contain technical stuff in the end, why not)
- Dokuwiki is ugly. This is not really a fact, but more like a shared opinion. If you like dokuwiki more, you are free to stay there
- The wiki on bitcoin.org cannot be mirrored easily. bitcoin.org went down once for a fairly long time, which is not reassuring. This new wiki can be mirrored easily by anyone since the mediawiki xml dump files are available for download. Extensive documentation on mediawiki mirroring is available on Internet.
So anyway, come and share your bitcoin experience on https://en.bitcoin.it/ (other languages available on request)
|
|
|
日本語喋ってもだれでもいないから意味がない〜
本当にBitcoinは日本人が作ったの?〜
|
|
|
Si vous cherchiez en *europe* et pas en France ? En France vu les régulations en vigueur, c'est clairement mort :p
|
|
|
Let me start with 100 BTC
|
|
|
[22:11:50] <gavinandresen> MT`AwAy: RE: curl and ssl: I bet you have: rpcssl=true in your bitcoin.conf [22:12:26] <gavinandresen> (correct syntax is rcpssl=1, I made the command/option file parsing consistent in 0.3.18)
Indeed, replacing rpcssl=true to rpcssl=1 fixed the issue.
|
|
|
Hi,
I'm having troubles with bitcoin 0.3.18. I have a PHP program connecting automatically to various bitcoin nodes via curl+ssl and checking node status with getinfo. When I upgraded some nodes to 0.3.18, I had timeouts on this system, and looking more into it, I found the system was stuck on those upgraded nodes.
I downgraded them back to 0.3.17 and everything worked again.
Running bitcoind to get informations about the node doesn't seem to have any advert effect on the node.
|
|
|
Hello, I'm looking for a web designer, hopefully for a long term relationship. The work: - Design simple websites (usually a few pages), for example http://smsz.net/
- Create HTML/JS code and make the whole thing interactive (I provide an API compatible with jQuery which makes calling AJAX functions easy, see http://gg.st/rpc_test.html)
- Maintain existing websites and add features
Websites are to be created via a specific interface using a home-made template syntax. I'll be here to explain the stuff and add features should anything be missing. The concept is easy, you get paid for the work you do (in bitcoins), and you get a share on the websites you are maintaining (depending on the kind of products). I'm mainly looking for simple and clear designs which looks good. Show me things you did in the past and I'll tell you if it matches.
|
|
|
the .bitcoin file could just contain the address in binary format, or could be formatted to also include informations about, for example, a transaction to be made
|
|
|
I agree, currently in case of down of bitcoin.org the only remaining official information source is IRC, I think alternative urls should be either known, or included (for example on an help page in the bitcoin client)
|
|
|
Well you can always try by first explaining what kind of people you are looking for... or contacting people on IRC might work too~
|
|
|
For those interested, I rewrote base58_encode/base58_decode in PHP, and added a "decode_btc" function (that will return an array containing "version" and "hash" for a given bitcoin address). This code requires the following php extensions: - gmp (for bignum values, we could use bc, or even the php-native implementation in pear, I'm just too lazy and I got gmp installed on all my servers anyway)
- hash (or mhash, someone could insert a php-native sha256 implementation to fallback to)
Here's the code, largely inspired from the code of the previous authors of this thread: <?php $btc = decode_btc('1Eym7pyJcaambv8FG4ZoU8A4xsiL9us2zz'); var_dump($btc); var_dump(encode_btc($btc)); $btc = decode_btc('1111111111111111111114oLvT2'); var_dump($btc); var_dump(encode_btc($btc));
function hash_sha256($string) { if (function_exists('hash')) return hash('sha256', $string, true); if (function_exists('mhash')) return mhash(MHASH_SHA256, $string); // insert native php implementation of sha256 here throw new Exception('Too lazy to fallback when the guy who configured php was lazy too'); }
function encode_btc($btc) { $btc = chr($btc['version']).pack('H*', $btc['hash']); if (strlen($btc) != 21) return false; $cksum = substr(hash_sha256(hash_sha256($btc)), 0, 4); return base58_encode($btc.$cksum); }
function decode_btc($btc) { $btc = base58_decode($btc); if (strlen($btc) != 25) return false; // invalid $version = ord($btc[0]); $cksum = substr($btc, -4); // checksum is double sha256 (take 4 first bytes of result) $good_cksum = substr(hash_sha256(hash_sha256(substr($btc, 0, -4))), 0, 4); if ($cksum != $good_cksum) return false; return array('version' => $version, 'hash' => bin2hex(substr($btc, 1, 20))); }
function base58_encode($string) { $table = '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz';
$long_value = gmp_init(bin2hex($string), 16);
$result = ''; while(gmp_cmp($long_value, 58) > 0) { list($long_value, $mod) = gmp_div_qr($long_value, 58); $result .= $table[gmp_intval($mod)]; } $result .= $table[gmp_intval($long_value)];
for($nPad = 0; $string[$nPad] == "\0"; ++$nPad);
return str_repeat($table[0], $nPad).strrev($result); }
function base58_decode($string) { $table = '123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz'; static $table_rev = null; if (is_null($table_rev)) { $table_rev = array(); for($i=0;$i<58;++$i) $table_rev[$table[$i]]=$i; }
$l = strlen($string); $long_value = gmp_init('0'); for($i=0;$i<$l;++$i) { $c=$string[$l-$i-1]; $long_value = gmp_add($long_value, gmp_mul($table_rev[$c], gmp_pow(58, $i))); }
// php is lacking binary output for gmp $res = pack('H*', gmp_strval($long_value, 16));
for($nPad = 0; $string[$nPad] == $table[0]; ++$nPad); return str_repeat("\0", $nPad).$res; }
This outputs: array(2) { ["version"]=> int(0) ["hash"]=> string(40) "9955c1b44fa66688d27aaa06ba4ad02c6dd91088" } string(34) "1Eym7pyJcaambv8FG4ZoU8A4xsiL9us2zz" array(2) { ["version"]=> int(0) ["hash"]=> string(40) "0000000000000000000000000000000000000000" } string(27) "1111111111111111111114oLvT2"
|
|
|
For information we are now accepting payments with 3 confirmations. This makes processing of the order faster and should be as safe.
|
|
|
Now the problem is to find merchants with QR code readers (or webcam able to focus on close objects + appropriate QR-decoding soft) ready to sell stuff for bitcoins
The merchants will be the ones with QR-codes listed on products; customers snap a picture with their mobile to add to a shopping cart, or initiate payment. Well then that's easy. I was thinking of doing something anyway... Didn't plan to put that in the SMS site however
|
|
|
This shouldn't be hard, however you would only be able to pay with bitcoins already in your wallet (if not, you'd have to transfer more bitcoins first, which would take one hour to clear). I could make a simple service to allow sending bitcoins from one wallet to another (or transform bitcoins into an encrypted QR code a merchant could then redeem instantly online, verifying it in the process). I could make this an android/iphone app by using PhoneGap Now the problem is to find merchants with QR code readers (or webcam able to focus on close objects + appropriate QR-decoding soft) ready to sell stuff for bitcoins
|
|
|
Good beginning, but I would like to see such feature like sending e-mail to sms. Is it possible?
It is possible, I'd have to find a "good" way to make sure the SMS is indeed from you. For example a special email (your login @smsz.net) with a special keyword in the subject followed by the destination phone number, and the SMS itself in the body of the mail. How does that sound?
|
|
|
i can't understand the international format you wish me to use, neither on this forum nor on the website. what kind of example is +1.0000000000?
The format is +<country_code>.<number> So if you live in France, it'd be: +33.612341234 or in US: +1.1231231234 or in Japan: +81.8012341234 I guess I could change the phone number input to use a dropdown box per country for the prefix, would probably help.
|
|
|
Now I can send a twitter message with bitcoin Mh, I think there are easier ways to do that with a computer
|
|
|
Hi, I'm testing a service I put together quickly: for 0.50 BTC you can send a SMS anywhere in the world. I implemented a small "wallet" where you can load & unload bitcoins easily (without any fee, of course) and a really limited interface (you'll soon see how bad I am at design). NB: Loading coins to the wallet will wait for 3 confirmations (~30 min). URL: http://smsz.net/Missing features:- View status of previously sent SMS, including transfer status
- Change password/email page
- Longer messages (will bill 0.5BTC * ceil(length_of_message / 160))
- Ability to send messages coming from your own phone number (you put your phone number, pay 0.5BTC, receive a code by SMS you then enter on the site and voila)
- Phone number book
- When entering the destination phone number, the input should be prefixed of country list with number prefix (need to find a database with country iso code -> country phone code list)
- Feature for payments (generate payment urls compatible with mobile phones?)
Anyway before spending more time on that, some feedback would be welcome. Remember to enter numbers in international format (+<country_code>.<phone_number>)!! Even if you make a mistake in the number, the SMS will be sent to the gateway and you'll be billed anyway. Oh and if you are interested in sending large amount of SMS I can put together an API too
|
|
|
Why not use startssl instead of CAcert? At least the certificate would be trusted by default, and is still free
|
|
|
Hosting is fine, however domain names are non-refundable (and usually hosting comes with a domain name) so such occurences would bring extra cost in the equation.
If things are working well we'll switch to less confirmations and we'll monitor cases of fraud to see if there are really people out there bothering with that. If not, we might even make the required confirmations count dependent on our fraud detection system (based on various informations obtained on order: proxy, address, ip, previous orders, etc) and provide people who look legit (ie. returning customers) a validation without payment confirmation (payment almost instant in this case if the bitcoin network is not overloaded).
|
|
|
|