hants will learn very quickly what the costs of accepting bitcoin
payments are, and the lower they are, the greater bitcoin merchant adoption
will be.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Sat, Jun 20, 2015 at 5:54 PM, Eric Lombrozo wrote:
> One more thing I would like to add t
fer than, for instance, credit card payments that can be charged back. As
long as it's reasonably good in practice, that's fine.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Fri, Jun 19, 2015 at 6:09 PM, Mark Friedenbach
wrote:
> What retail needs is escrowed microchannel
<
justusranv...@riseup.net> wrote:
> On 2015-06-16 07:55, Aaron Voisine wrote:
>
>> Suppose a billion mobile phones wanted to run SPV wallets tomorrow. Who
>>> would provide the nodes they would need connect to?
>>>
>>
>> The SPV wallet author would if
With their money, if they were to take advantage of optional additional
financial services, like, as one example, comsumer protection insurance.
Aaron
On Tuesday, June 16, 2015, wrote:
> On 2015-06-16 07:55, Aaron Voisine wrote:
>
>> Suppose a billion mobile phones wanted to run
> Suppose a billion mobile phones wanted to run SPV wallets tomorrow. Who
> would provide the nodes they would need connect to?
The SPV wallet author would if they wanted their wallet to function.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Mon, Jun 15, 2015 at 10:28 PM, wrote:
ative
impact on the network.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Mon, Jun 15, 2015 at 8:49 PM, Kevin Greene wrote:
>
>
> On Mon, Jun 15, 2015 at 8:41 PM, Luke Dashjr wrote:
>
>> On Tuesday, June 16, 2015 3:30:44 AM Kevin Greene wrote:
>> > Would SPV walle
;ve advocated for the blocksize increase, followed
by tx selection and propagation rule changes to create fee pressure.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Mon, Jun 15, 2015 at 6:17 PM, Alex Morcos wrote:
> Aaron,
>
> My understanding is that Gavin and Mike are proceedi
ork out on their own.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Mon, Jun 15, 2015 at 3:56 PM, Brian Hoffman
wrote:
> Who is actually planning to move to Bitcoin-XT if this happens?
>
> Just Gavin and Mike?
>
> [image: image1.JPG]
>
> On Jun 15, 2015, at 6:17 PM,
robably the
> wrong space for you.
>
If consensus must be reached to make any changes, that just means that
changes of anything more than trivial consequence simply can't be made.
Extreme bias toward the status-quo will only work if external factors
affecting the network also remain stati
e dropped
>> > lowest fee/KB first, a completely predictable way.
>>
>> Quite agreed.
>
>
> No, Aaron is correct. It's unpredictable from the perspective of the user
> sending the transaction, and as they are the ones picking the fees, that is
> what matt
d
however get the average fee-per-kb paid by all transactions in a block by
looking at the coinbase transaction, subtracting the block reward, and
dividing by the size of block minus the header.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Thu, Jun 11, 2015 at 11:30 AM, Nathan Wilcox
wro
you just have to hope that someone who wants that space more than you do
doesn't show up after you disconnect.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Wed, Jun 10, 2015 at 1:26 PM, Mike Hearn wrote:
> I described an alternative way for SPV wallets to learn about fees som
tly,
I actually just added it the other day after getting blockcypher to include
it in their api. The current release is still using a hard coded fee rate.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Wed, Jun 10, 2015 at 1:00 PM, Nathan Wilcox
wrote:
> On Wed, Jun 10, 2015 at 1:19 PM
then putting a hard coded range around it to
protect against the service being compromised. This is also the kind of
thing being done for exchange rate data which is probably the bigger
security risk until bitcoin becomes the standard unit of account for the
planet.
Aaron Voisine
co-founder and CEO
the cost of DOSing the network.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Fri, May 29, 2015 at 10:53 AM, Admin Istrator wrote:
> What about trying the dynamic scaling method within the 20MB range + 1
> year with a 40% increase of that cap? Until a way to dynamically scale i
network. There are plenty of avenues to create
fee pressure without resorting to such a drastic change in how the network
works today.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Thu, May 28, 2015 at 8:53 AM, Gavin Andresen
wrote:
> On Fri, May 8, 2015 at 3:20 AM, Matt Whitlock
> wro
See the "first-seen-safe replace-by-fee" thread
Aaron Voisine
co-founder and CEO
breadwallet.com
On Tue, May 26, 2015 at 11:22 AM, Danny Thorpe
wrote:
> What prevents RBF from being used for fraudulent payment reversals?
>
> Pay 1BTC to Alice for hard goods, then after yo
On Sat, May 16, 2015 at 1:35 PM, Owen Gunden wrote:
>
> This strikes me as a leap. There are alternatives that still use bitcoin
> as the unit of value, such as sidechains, offchain, etc. To say that
> these are "not bitcoin" is misleading.
>
The only options available today and in the near futu
lag date turns out to be poorly chosen
and a large number of non-mining nodes haven't upgraded yet. Would be a
nice safety fallback.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Wed, May 13, 2015 at 6:31 PM, Aaron Voisine wrote:
> > by people and businesses deciding to no
option, which is the least relevant.
I concede the point. Perhaps a flag date based on previous observation of
network upgrade rates with a conservative additional margin in addition to
supermajority of mining power.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Wed, May 13, 2015 at 6
large supermajority of the pervious 1000 blocks indicate they have
upgraded, as a safer alternative to a simple flag date, but I'm sure I
wouldn't have to point out that option to people here.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Wed, May 13, 2015 at 5:58 PM, Pieter Wuille
w
e the block size. Miners already have an
incentive to find ways to encourage higher fees and we can help them with
standard recommended propagation rules and hybrid priority/fee transaction
selection for blocks that increases confirmation delays for low fee
transactions.
Aaron Voisine
co-founder
actions after a prolonged delay.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Fri, May 8, 2015 at 3:45 PM, Mark Friedenbach
wrote:
> On Fri, May 8, 2015 at 3:43 PM, Aaron Voisine wrote:
>
>> This is a clever way to tie block size to fees.
>>
>> I would just
seeing degraded, long confirmation times followed by
eventual success.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Fri, May 8, 2015 at 1:33 PM, Mark Friedenbach
wrote:
> It is my professional opinion that raising the block size by merely
> adjusting a constant without any sort of fe
involve hybrid priority/fee selection so low fee
transactions see degraded performance instead of failure. This would be the
conservative low risk approach.
Aaron Voisine
co-founder and CEO
breadwallet.com
--
One dashboard
nodes were
doing was intended to be malicious with respect to network disruption. It's
our job to better handle non-standard or even malicious behavior from
random p2p nodes.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Mon, Mar 16, 2015 at 1:44 AM, Jan Møller wrote:
> What we were
to work on
current generation low power embedded devices when the next generation will
be more than capable. But I understand the motivation for the compromise.
Aaron Voisine
co-founder and CEO
breadwallet.com
--
Dive into t
flaws.
Their security level is reduced to the lowest common denominator. I see the
need for a "fire exit", certainly, but we must also remember that fire
exits are potential entrances for intruders.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Wed, Mar 11, 2015 at 12:46 PM, Gregory
ould take
the same stance with bitcoin as they did against e-gold. It wasn't clear at
all that bitcoin didn't violate legal tender laws or who knows what. When
Apple allowed wallets back in, it was just weeks before Apple pay launched.
It's seems clear that bitcoin is too
x27;s very large
bitcoin holders will find themselves uniquely positioned to engage in
as bitcoin grows into a major global currency.
Aaron Voisine
breadwallet.com
On Tue, Jan 20, 2015 at 10:07 PM, 21E14 <21x...@gmail.com> wrote:
> This is a response to a wonderfully insightful recent
This is great Pieter. I was able to sync the entire blockchain from
scratch in a little over 4 hours on a laptop over cable modem. :) No
issues to report. Even my family photos are intact! This makes it
practical to run a full node, part time on a laptop again.
Aaron Voisine
breadwallet.com
On
Of course you wouldn't want nodes to propagate alerts without
independently verifying them, otherwise anyone could just issue alerts
for every new transaction.
Aaron Voisine
breadwallet.com
On Thu, Sep 25, 2014 at 7:16 PM, Matt Whitlock wrote:
> Probably the first double-spend atte
Something like that would be a great help for SPV clients that can't
detect double spends on their own. (still limited of course to sybil
attack concerns)
Aaron Voisine
breadwallet.com
On Thu, Sep 25, 2014 at 7:07 PM, Matt Whitlock wrote:
> What's to stop an attacker from broadcas
monitoring propagation,
however it does still increase the cost of performing a 0 confirmation
double spend attack on an SPV client above just relaying double-spends
without indicating if a node believes the transaction to be valid.
Aaron Voisine
breadwallet.com
t signed payment requests be from the same
domain, and also require https?
Aaron
Aaron Voisine
breadwallet.com
On Fri, Sep 12, 2014 at 9:31 AM, Mike Hearn wrote:
> Putting aside the question of necessity for a moment, a more efficient
> approach to this would be;
>
> Add another m
physical theft, and the app
pin is just for when you lend your phone to a friend for a few
minutes.
Aaron Voisine
breadwallet.com
On Fri, Jul 25, 2014 at 9:22 AM, Natanael wrote:
> Probably because the network isn't designed for interactive proofs. Most
> interactive algoritms AF
g backwards, refuse
> to allow more attempts until it's advanced past the previous attempt.
>
>
> On Fri, Jul 25, 2014 at 7:56 AM, Aaron Voisine > wrote:
>
>> It's based on the block height, not the block's timestamp. If you have
>> access to the device a
crypted to a combination of pin+uuid. This was just an
easy way to prevent multiple pin guesses by changing system time in
settings, so that isn't the weakest part of the security model.
Aaron Voisine
breadwallet.com
On Thu, Jul 24, 2014 at 8:21 PM, William Yager wrote:
> On Thu, Jul 24
st and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it no
Aaron Voisine
breadwallet.com
On Fri, Jul 18, 2014 at 11:56 PM, Gregory Maxwell wrote:
> On Fri, Jul 18, 2014 at 9:38 PM, Aaron Voisine wrote:
>> Well, you could always create a transaction with a different signature
>> hash, say, by changing something trivial like nLockTime, or chan
Ah, good point. For some reason I was thinking the k value was
generated only from the hash being signed, but it's derived from both
the private key and the hash, so as you say there's no way for the
verifier to tell if the scheme is being followed.
Aaron Voisine
breadwallet.com
O
ath in the signature itself?
Aaron Voisine
breadwallet.com
On Fri, Jul 18, 2014 at 6:28 PM, Gregory Maxwell wrote:
> On Fri, Jul 18, 2014 at 3:03 PM, Aaron Voisine wrote:
>>> 9. New signatures by the sender
>>
>> I'm not suggesting it be required, but it would
> 9. New signatures by the sender
I'm not suggesting it be required, but it would be possible to
mitigate this one by requiring that all signatures deterministically
generate k per RFC6979. I'm using this in breadwallet.
Aaron Voisine
breadwallet.com
On Fri, Jul 18, 2014 at 1:56
t why Andreas's passphrase was
different than what I got.
Aaron Voisine
breadwallet.com
On Wed, Jul 16, 2014 at 4:04 AM, Andreas Schildbach
wrote:
> Damn, I just realized that I implement only the decoding side of BIP38.
> So I cannot propose a complete test vector. Here is what I have:
>
support, but it sounds like it might just be a JVM
string library bug that could hopefully be reported and fixed. I get
the same result as in the test case using apple's
CFStringNormalize(passphrase, kCFStringNormalizationFormC);
Aaron Voisine
breadwallet.com
On Tue, Jul 15, 2014 at 11:20 A
I believe tx have to be ordered sequentially within a block. Also
since a tx is referenced by it's hash, it's practically impossible to
make a self referential tx.
Aaron Voisine
breadwallet.com
On Sun, Jul 13, 2014 at 4:32 PM, Richard Moore wrote:
> Hey all,
>
> I
I wrote down a really short description in code comments for
breadwallet, based on what I figured out:
https://github.com/voisine/breadwallet/blob/master/BreadWallet/BRPeer.m#L318
Aaron Voisine
breadwallet.com
On Tue, Jul 8, 2014 at 1:04 PM, Matt Whitlock wrote:
> Is anyone working o
Agreed. If the POW is most efficient on general purpose CPUs, that
means Intel, AMD and maybe IBM would be the only entities capable of
producing competitive mining equipment.
Aaron
Aaron Voisine
breadwallet.com
On Fri, Jul 4, 2014 at 11:39 AM, Ron Elliott wrote:
> I feel everyone should
I'll implement it in breadwallet (oss SPV wallet, hopefully about to
be in the app store) if other wallet authors are planning to.
Aaron
https://github.com/voisine/breadwallet
There's no trick to being a humorist when you have the whole
government working for you -- Will Rodgers
On Fri, Jun 6,
Bit by bit, it's become clear that it's a bit much to worry even a
little bit that overloading the word "bit" would be every bit as bad
as a two bit horse with the bit between it's teeth that bit the hand
that feeds it, or a drill bit broken to bits after just a bit of use.
Aaron
There's no trick
> word at <http://zibcoin.org>.
>
> 'Zib' also lends itself to an expressive unicode symbol, 'Ƶ'
> (Z-with-stroke), that remains distinctive even if it loses its stroke or
> gets case-reversed. (Comparatively, all 'b'-derived symbols for
> data
It will also be important to chose the currency symbol for "bits" at the
same time. Lowercase stroke "b" I think is the obvious choice.
Unicode U+0180
Aaron
On Friday, May 2, 2014, Alan Reiner wrote:
> I've been a strong supporter of the 1e-6 unit switch since the beginning
> and ready to do w
At the moment BIP70 specifically requires that a request be rejected
if validation fails, so that should be fixed that sooner rather than
later:
"The recipient must verify the certificate chain according to
[RFC5280] and reject the PaymentRequest if any validation failure
occurs."
Aaron
There's
I'm also a big fan of standardizing on microBTC as the standard unit.
I didn't like the name "bits" at first, but the more I think about it,
the more I like it. The main thing going for it is the fact that it's
part of the name bitcoin. If Bitcoin is the protocol and network, bits
are an obvious ch
On github I commented on the BIP43 pull request about adding a
"purpose" of 0' which would correspond to the BIP32 recommended tree
structure for a single account wallet. (m/0'/chain) This will allow
for backwards compatibility and interoperability at least for existing
single account BIP32 impleme
55 matches
Mail list logo