As part of my green address endeavor, I'm currently trying to extend the
'gettransaction' call to include an extra field inputaddresses which
should return a list of the Bitcoin addresses associated with the inputs
of the transaction.
I understand that this is not generally possible,
Am Mo, 24.10.2011, 16:55, schrieb Gavin Andresen:
So my first shot at this is to go through the inputs of a transaction and
see if the scriptSig field has only two opcodes. If that is the case, I
assume that it is of the structure sig pubKey and calculate the
Bitcoin address from pubKey.
On Thu, Mar 06, 2014 at 02:39:52PM +, Alex Kotenko wrote:
Not sure if you've seen it, but here is how we do NFC right now
http://www.youtube.com/watch?v=DGOMIG9JUY8 with XBTerminal.
Very interesting, thanks for sharing! Are the two devices on the same
wifi network in the demo? In my
On Sun, Feb 22, 2015 at 05:37:16PM -0500, Andy Schroder wrote:
It's maybe not a bad idea for the wallet to try all payment_url
mechanisms in parallel. Should we add this as a recommendation to
wallets in TBIP75?
It doesn't need to be a recommendation I think, but maybe it would be
On Mon, Feb 23, 2015 at 05:59:34PM +0100, Mike Hearn wrote:
At the moment I'm also modifying BitPay's memo field to contain 'ack', as
Andreas' wallet otherwise reports a failure if I transmit the original via
For HTTP it checks whether 'nack' is _not_ presented:
On Tue, Feb 24, 2015 at 01:14:43AM -0500, Andy Schroder wrote:
I've had similar issues where the NFC device has to be disconnected
and reconnected. I've got lots of error checking in my code on the
NFC device, which helps, but still has problems sometimes. I've
found if I limit how quickly a
I am working on a Bitcoin point of sale terminal based on a Raspberry Pi, which
displays QR codes, but also provides payment requests via NFC. It can optionally
receive the sender's transaction via Bluetooth, so if the sender wallet
supports it, the sender can be completely offline.
Mail list logo