I'm wondering about whether (don't laugh) moving signing into the kernel
and then using the MTRRs to disable caching entirely for a small scratch
region of memory would also work. You could then disable pre-emption and
prevent anything on the same core from interrupting or timing the signing
I just did my first contactless nfc payment with a MasterCard. It worked
very well and was quite delightful - definitely want to be doing more of
these in future. I think people will come to expect this kind of
no-friction payment experience and Bitcoin will need to match it, so here
are some
You've heard of TRESOR?
No, not Trezor.
https://en.wikipedia.org/wiki/TRESOR
Signing on the CPU, without touching RAM.
- Sent from my phone
Den 6 mar 2014 09:41 skrev Mike Hearn m...@plan99.net:
I'm wondering about whether (don't laugh) moving signing into the kernel
and then using the
I'm not sure if iso-dep is the way to go here. Afaik as soon as you pick
up the phone the connection breaks. It's ok if some people decide to let
the app do risk analysis, but you cannot force it onto users by picking
a protocol that cannot deal with manual verification. Users should
always have
I think stealth addresses combined with zk-snarks would obviate the need
for CoinJoin. zk-snarks could be used to hide the coin's value and
stealth addresses could be used to hide the recipient for payments and
even mined coins. More info on zero-knowledge snarks:
On Thu, Mar 6, 2014 at 12:26 PM, Andreas Schildbach
andr...@schildbach.dewrote:
I'm not sure if iso-dep is the way to go here. Afaik as soon as you pick
up the phone the connection breaks.
If the phone isn't willing to immediately authorise then it'd have to fall
back to HTTPS or Bluetooth as
On Mar 6, 2014 3:47 AM, Mike Hearn m...@plan99.net wrote:
I just did my first contactless nfc payment with a MasterCard. It worked
very well and was quite delightful - definitely want to be doing more of
these in future. I think people will come to expect this kind of
no-friction payment
Hi Mike
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.
For now this is just an NDEF URI message with Bitcoin URI inside, and then
transaction itself propagated to the network by the phone using it's own
Internet
On 03/06/2014 02:44 PM, Mike Hearn wrote:
I'm not sure if iso-dep is the way to go here. Afaik as soon as you pick
up the phone the connection breaks.
If the phone isn't willing to immediately authorise then it'd have to
fall back to HTTPS or Bluetooth as normal.
Ok, that would be
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.
Thanks for the video! It's always good to see these things in action so
you can start believing in it.
For now this is just an NDEF URI message with Bitcoin URI inside,
I wonder about the receipt step -- are you generating a PDF on device
and sending it via NFC? This is something that could be supported by the
BIP70 payment protocol. We should try to avoid the second tap, its not
intuitive.
Together, the signed PaymentRequest and the transactions in the
On 03/06/2014 03:51 PM, Andreas Schildbach wrote:
I'm not sure if iso-dep is the way to go here. Afaik as soon as you pick
up the phone the connection breaks.
If the phone isn't willing to immediately authorise then it'd have to
fall back to HTTPS or Bluetooth as normal.
Ok, that
I think maybe the way you do it is to have a NDEF tag that triggers the
app, and then that starts an IsoDep protocol once opened. I *think*.
On Thu, Mar 6, 2014 at 5:55 PM, Andreas Schildbach andr...@schildbach.dewrote:
On 03/06/2014 03:51 PM, Andreas Schildbach wrote:
I'm not sure if
Thanks Alex!
About the video - I'm curious how your device is better than just a regular
tablet. Could you give us the elevator pitch? :)
On Thu, Mar 6, 2014 at 3:39 PM, Alex Kotenko alexy...@gmail.com wrote:
I mean - if with Bitcoin v0.9 transaction fees will become really
floating, and it
if some sort of Stealth address or HD wallet root was the identity gaining
the reputation, then address re-use wouldn't have to be mandatory.
The identity would be the X.520 name in the signing cert that signed the
payment request. It doesn't have to be a difficult to obtain cert. It could
If there was a way for a Bitcoin user to provide feedback on a payment
(ECDSA signature from one of the addresses involved in the payment, signing
an identifier of the payment and a feedback score)
Well now you're getting into the area that I said rapidly got very
complicated.
Define
it's the responsibility of the individual members to maintain their own
good/bad user lists. Would you think that's a good thing or a bad thing to
give the individual players that level of control/responsibility?
If it's explicit, I think it's a non starter and nobody will bother with
it,
Yes please, pull req would be great! I also noticed that escaping doesn't
seem to be necessary, and the resultant de-escaped QRcodes are certainly
much nicer! Thanks!
--
Subversion Kills Productivity. Get off Subversion
Hello,
I am attempting to write a parser for bip-0021 URI's, including
support for the new bip-0072 payment parameters. My goal is absolute
correctness. Unfortunately, these BIP's have a few ambiguities and
mistakes which ought to be corrected.
First, I would like to point out that internet RFC
On Thu, Mar 6, 2014 at 2:59 PM, Mike Hearn m...@plan99.net wrote:
Yes please, pull req would be great! I also noticed that escaping doesn't
seem to be necessary, and the resultant de-escaped QRcodes are certainly
much nicer! Thanks!
All right, I have submitted the pull request. Hopefully, the
20 matches
Mail list logo
