Wladimir,
what is missing is a decision to pull for the reference client.
Or did I missed that bit?
signature.asc
Description: Message signed with OpenPGP using GPGMail
--
"Accelerate Dev Cycles with Automated Cross-Bro
On Sun, May 4, 2014 at 8:15 AM, Aaron Voisine wrote:
> 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 br
+1(bit) for your bit on bits.
> On 4/05/2014, at 2:18 pm, "Aaron Voisine" wrote:
>
> 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
>
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
+1
On 4 May 2014 02:06, "Chris Pacia" wrote:
> Absent a concerted effort to move to something else other than 'bits', I
> would be willing to bet the nomenclature moves in that direction anyway.
> 'Bits' is just a shorten word for 'millibits' (or microbits, if you
> will). It's easier to say and
On Sat, May 3, 2014 at 2:04 PM, Flavien Charlon
wrote:
> Outputs are above dust, inputs are not spent. OP_RETURN is supposed to be
> standard in 0.9.1 and the data is well below 40 bytes, so why is this being
> rejected?
The carried data must all be contained within one pushdata.
--
Jeff Garzik
Unfortunately this could fork the network permanently, which is much
worse than a double spend. There's no magic way to have a consensus,
so it becomes trivial with a few tries to split the network into two
halves: (tx1 before tx2, tx2 before tx1). Some nodes in the middle
will accept either block,
losew...@gmail.com
losew...@gmail.com
--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from t
Absent a concerted effort to move to something else other than 'bits', I
would be willing to bet the nomenclature moves in that direction anyway.
'Bits' is just a shorten word for 'millibits' (or microbits, if you
will). It's easier to say and my guess is people would tend to use it
naturally own t
This idea was suggested by "Joe" on 2011-02-14
https://bitcointalk.org/index.php?topic=3441.msg48484#msg48484 . It
deserves another look.
Nodes today make a judgment regarding which of several conflicting
spends to accept, and which is a double-spend. But there is no
incorporation of these c
Is it more complex? The current implementation using template matching
seems more complex than `if script.vch[0] == OP_RETURN &&
script.vch.size() < 42`
On 05/03/2014 12:08 PM, Gregory Maxwell wrote:
> On Sat, May 3, 2014 at 11:55 AM, Mark Friedenbach wrote:
>> I don't think such a pull request w
On Sat, May 3, 2014 at 11:55 AM, Mark Friedenbach wrote:
> I don't think such a pull request would be accepted. The point was to
> minimize impact to the block chain. Each extras txout adds 9 bytes
> minimum, with zero benefit over serializing the data together in a
> single OP_RETURN.
In this ca
I don't think such a pull request would be accepted. The point was to
minimize impact to the block chain. Each extras txout adds 9 bytes
minimum, with zero benefit over serializing the data together in a
single OP_RETURN.
On 05/03/2014 11:39 AM, Peter Todd wrote:
> The standard format ended up bei
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03.05.2014 02:54, Ben Davenport wrote:
> No one quotes amounts as 63 k$ or 3 M$. The accepted standard at
> least in the US is , i.e. $63k
> or $3M.
As you said, that's in the US, and I strongly suspect the sole reason
is that in the US the curr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The standard format ended up being exactly:
OP_RETURN <0 to 40-byte PUSHDATA>
You've split the data across two PUSHDATA's. The standard should have let the
data be split up like that; pull requests accepted.
On 3 May 2014 13:04:52 GMT-05:00,
Can someone enlighten me on why the following transaction is being rejected
by Bitcoind 0.9.1 with error code -22 on Mainnet.
0100015594a8c1f84b926e84d70c3a3d5e517e0c12dc07cb1a774b587121fef08f91b86b48304502202f534407f6dee4d8932ec22491cbc15a2d31af2bade4e8d417e4b1955de57f5902210086e2f021
I agree with the sentiment that most people don't understand either computer
science or Bitcoin. The goal of getting people to understand enough about
Bitcoin to use it is achievable and a goal that is "in scope" of our efforts.
Getting them to understand computer science at large at the same t
bit has a lot of meanings to geeks, so what.
bit means for average people:
- something very small, that 100 satoshi is.
- part of the name Bitcoin
- easy to get conversion 1 coin = 1 million bits = 1 Bitcoin
Regards,
Tamas Blummer
Founder, CEO
http://bitsofproof.com
On 03.05.2014, at 18:02, sl
Excellent points Christophe!
Although moving to 1e-6 units is fine for me and I see advantages of doing
this, I don't get that people on this mailing list are fine with calling
such unit "bit". It's geeky as hell, ambiguous and confusing.
slush
On Sat, May 3, 2014 at 5:48 PM, Christophe Biocca
Context as a disambiguator works fine when the interlocutors
understand the topics they're talking about.
Not a day goes by without me seeing "neurotypical people" get horribly
confused between RAM and Hard Drive sizes, because they share the same
units (not that that can be helped, as the units ar
> the SI prefixes. People *do* use 63k USD, $63k, and $3M. I'll be the first
> one
As a counter argument, many sources (including the BBC) abbreviate
million to 'm' (and billion to 'bn'), e.g. $3m, $3bn.
I think any similarity with SI units here is coincidental.
roy
--
21 matches
Mail list logo