Pretty please... a5215bbc497697873594d50528e4605a93be093ffa6537cf80e4eaefa0005320
Thanks man!

I wonder what the miners think about the blocksize proposal. I believe they can choose the size of the block to be anywhere between 0 to 1MB today. Should the 1MB limit be raised, the final decision will remain with the miners, right?

What I'd like to know is how Skyhook protects operators from volatility. Other ATMs purchase bitcoin at exchanges (Bitstamp, Kraken, etc) for you at the moment your customer uses the ATM. Skyhook never mentions this feature. Neither I see it in their code. 

I want to take Coinee to another level and I'm 100% busy developing new features. I need help: I'm looking for an editor = someone who will seek and list new ATM locations. I offer $2 (in bitcoin) for each ATM you add. At the moment, I estimate the database to be about 20 ATM locations short (and there are new ATMs emerging almost everyday). Also, you'll be emailing ATM owners and query for buy/sell prices.

Please, email me info@coinee.net.

I liked your idea, homepage has been updated.

Also I'd like to ask anyone who owns or lives near a bitcoin ATM to post more info about it, photos or comments welcome.

All right, thanks for the hint.

That's interesting, why do you think so? What would you like to see on the homepage?

Hi,
I'll be launching http://coinee.net/ in a few days. It's a bitcoin ATM map focused on sending cash around the world. It finds the best route for transferring money via bitcoin ATMs. It suffers from the lack of data though, but I believe it'll improve in the future. Check it out!

Solved. In case someone else finds it helpful, the code has actually been released here: https://github.com/gavinandresen/paymentrequest/tree/master/php. Cheers!

Hi fellow coders,
I'd like to ask for your help. Does anyone here have a working payment request generator sample code (in any language)? I've been struggling for almost a day to generate payment requests in node.js, stumbled over the certificate signing phase. Gavin runs a simple PHP generator, but didn't release the code.

One invite for me, please.

Yes, inspired by Mastercoin.

I'm afraid I'm not familiar with the proposal, could you please link me to it?

Anyhow, based on number of reviews I received, I plan to make some minor improvements to the cointrace protocol and finalize it. I'll also create a tutorial on how anyone can use it just today with no need for a dedicated client application (unlike CC or Mastercoin).

I had the same requirement with my last project. Bitpay didn't support it. Solved by sending one part of the payment via their direct deposit to a bank account and the second part as a bitcoin payment to the other party's bitcoin address. I added this "split payment" as a feature request though, you can send them a support request to urge that.

Such transaction is ignored by the protocol.

Correct. The funding part is only used for pre-calculating share distribution for the issuance part. Let's say there are two funding transactions: 2 BTC from A and 3 BTC from B. Issuer will than be presented with an option to issue 5 BTC worth of shares (2 to A, 3 to B), but it's not binding or enforced. Issuer can simply decide to issue only 2 BTC worth of shares, say 1 to A and 1 to B, keeping the remaining 3 BTC off the protocol.

Thank you for your comment. Is there anything I can do about it or am I doomed to be ignored? Maybe I should summarize what this is all about. Here's why I'm trying to propose a new smart property protocol:

Colored coins match the digital property ownership with individual inputs/outputs of bitcoin transactions so one can't spend these coins without losing the digital property ownership. Cointrace matches the ownership with a bitcoin address and it even allows the balance of the address to be zero and still retain the property ownership. Colored coins require dedicated client application to carefully handle the ins/outs while Cointrace can be used with existing clients.

Mastercoin is a protocol too complex for a simple digital property control and also requires a dedicated client application. Its exodus address is picked and controlled by its creators (and so is the Mastercoin itself), introducing a possible point of failure. Cointrace is much simpler and allows anyone to create and control their own "exodus address" (called the project address).

Hello everyone,
I'm a big fan of Colored coins and Mastercoin projects, there are some issues with both of them though. So I created another, super-simple smart property protocol and you can see it in action here: http://cointrace.net. I'd be grateful if you could look at it and provide some critique. Thank you!

Hello everyone,
do you need to parse the blockchain in PHP? I created a simple library to do just that. It connects to blockchain.info API or bitcoind via json-rpc. You can use it to retrieve information about addresses and transactions.

See https://github.com/bitcont/bitcoin.

Aaah, it's at the bottom of the API page, pardon my question then, feeling dumb. Thanks!

Hi, I have a question about your API (https://blockchain.info/api/blockchain_api). I often get the HTTP 429 Too many requests response. I use your API to parse the blockchain. I didn't find any API usage limits on your website but apparently I'm successful in hitting them. Could you please tell me how many requests I'm allowed to do per second or minute?

What version of Electrum is planned to support payment requests? Waiting for the ref client implementation first?