Support for a TPM is a rather tricky thing.
By itself the TPM is independent of any CPU. However, it's also not very
useful (though for Pond's use case, it works).
The TPM gets much more useful when it's integrated with features on the
motherboard, BIOS, CPU, northbridge, IOMMU etc. Then you
On Wed, Jul 31, 2013 at 6:45 PM, Roy Badami r...@gnomon.org.uk wrote:
Is it envisaged to be possible/sensible to have a URI that is *only* a
payment request? i.e. something like the following (although I'm not
sure this is a valid URI):
On 31 July 2013 13:33, Gavin Andresen gavinandre...@gmail.com wrote:
On Wed, Jul 31, 2013 at 6:45 PM, Roy Badami r...@gnomon.org.uk wrote:
Is it envisaged to be possible/sensible to have a URI that is *only* a
payment request? i.e. something like the following (although I'm not
sure
Since the payment request is available from a location defined in the URI,I think it would be appropriate to attach the PaymentACK once paymentaccepted by Merchant.This would make the request and receipt available for later review.Regards,Tamás BlummerFounder, CEOhttp://bitsofproof.com
Sorry, I just noticed that this thread was CCd to the announce list not the
development list (why is it open access?)
It's offtopic anyway. Let's continue this discussion in private if anyone
wants to.
On Wed, Jul 31, 2013 at 5:53 PM, Mike Hearn m...@plan99.net wrote:
The reason why TPM
right the original Topic was BitMail
here a Server running for the next few days to test BitMail.sf.net
178.83.35.133:4710
--
Get your SQL database under version control now!
Version control is standard for application
On Wed, Jul 31, 2013 at 06:11:10PM -0400, Peter Todd wrote:
https://s3.amazonaws.com/peter.todd/litecoin-v0.8.3.7-audit-report.tar.bz2
I thought this may be of interest to Bitcoin as well as an example.
By request,
Zip archive:
I think it's important to expect PaymentRequest-only bitcoin URIs in the
future. Some types of payments (exotic transactions) may not make sense to
have a single fallback address. Or, a page with a bitcoin URI link may be
relying on a separate service provider to assemble the transaction.
On
On Thu, Aug 1, 2013 at 9:30 AM, E willbefull ewillbef...@gmail.com wrote:
I think it's important to expect PaymentRequest-only bitcoin URIs in the
future. Some types of payments (exotic transactions) may not make sense to
have a single fallback address.
P2SH addresses already support all
P2SH addresses support exotic transaction outputs, but not all exotic
transactions. This payment protocol can allow for combining multiple
outputs. A PaymentRequest for sending money to multiple parties, for
example, could not fall back to a single address.
On Wed, Jul 31, 2013 at 5:38 PM, Gavin
10 matches
Mail list logo
