at (but didn't even mention it here!)
https://github.com/bitcoin/bitcoin/pull/5468
Wladimir
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Rep
> I don't care which tabbing style or column width you pick, but **pick one**,
> and enforce it across the entire codebase.
See https://github.com/bitcoin/bitcoin/pull/5387
Wladimir
--
Download BIRT iHub F
:
https://github.com/bitcoin/bitcoin/issues
Cheers,
Wladimir
--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all
itcoin/bitcoin.git bitcoin-0.10
cd bitcoin-0.10/src
./autogen.sh
./configure
make
make check
```
Wladimir
--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnershi
On Sat, Jan 10, 2015 at 12:18 PM, Ivan Jelincic wrote:
> Is openssl1.0.1j unaffected?
Yes. It concerns CVE-2014-8275.
Which in https://www.openssl.org/news/openssl-1.0.1-notes.html is under:
Major changes between OpenSSL 1.0.1j and OpenSSL 1.0.1k [8 Jan 2015]
Wladi
I've just tagged 0.10.0rc2 in git.
To fetch, build, and test (see also doc/build-*.md):
```
git clone -b v0.10.0rc2 https://github.com/bitcoin/bitcoin.git bitcoin-0.10
cd bitcoin-0.10
./autogen.sh
./configure
make
make check
```
Note: This includes the changes required for interoperability with
O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, Jan 12, 2015 at 3:28 PM, Wladimir wrote:
> On Mon, Jan 12, 2015 at 11:31 AM, Wladimir wrote:
>
> If you build from source, and have already built rc2, there is no
> reason to build rc3.
0.10.0rc3 executables have been uploa
I
> think you've addressed
Progress information for the list: there is now a pull request
implementing the strict DER verification behavior, as well as the
deployment specified in BIP66 for Bitcoin Core. It needs
your review and testing:
https://github.com/bitcoin/bitcoin/pull/5713
Wladimir
languages.
Though JSON parsers are much more diverse, which people using Bitcoin
Core's RPC have bumped into e.g. some have some problems
handling large numbers. Something you wouldn't expect using a
straightforward binary format. There&#x
scaling up the block size will get some leeway in the short term,
but I believe a future scalable payment system based on bitcoin will be
mostly based on off-blockchain transactions (in some form) or that there
will be a hierarchical or subdivided system (e.g. temporary or per-locale
is already of interest if applying size limit to a block, since
> transaction count is var_int but is not part of the hashed header or the
> merkle tree.
Are you sure that this is a current concern? Non-canonical CompactSizes
are forbidden - in serialize.h this is flagged in ReadCo
elease?
> Sounds dangerous to me.
Again, there hasn't been any 0.9.4 release, neither a release candidate or
anything else.
Testing and such should be focused on the 0.10 release candidates.
Wladimir
--
Dive in
andment to BIP32. Excluding small language errors and
clarifications in examples, BIPs are not changed after the fact.
Wladimir--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and
change that's obviously softforking. Is
> anyone opposed to doing so at this stage?
Not opposed, but is kind of late for 0.10, I had hoped to tag rc4 today.
Wladimir
--
Dive into the World of Parallel Progr
reEncoding()
- ed4206a fix crash: CoinControl "space" bug
- 58259ad qt: fix broken unicode chars on osx 10.10
- aaf55d2 186a517 Add a -rpckeepalive option to disable RPC use of
HTTP persistent connections.
Hopefully this will be the last release candidate before the 0.10 fina
On Thu, Feb 5, 2015 at 12:33 PM, Wladimir wrote:
> FYI, I've just tagged v0.10rc4, and pushed my signatures to the
> gitian.sigs repository.
>
> Please start your gitian builders!
Thanks to the extremely quick response (a whopping 9 gitian builders
already!), the executables an
amounts,
which still make sense, and he wrote about them here:
https://medium.com/@octskyward/merge-avoidance-7f95a386692f
Wladimir
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Inte
with a release announcement until there are >3
builders and the binaries have been uploaded.
Cheers,
Wladimir
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed i
Luke Dashjr
- Mark Friedenbach
- Mathy Vanvoorden
- Matt Corallo
- Matthew Bogosian
- Micha
- Michael Ford
- Mike Hearn
- mrbandrews
- mruddy
- ntrgn
- Otto Allmendinger
- paveljanik
- Pavel Vasin
- Peter Todd
- phantomcircuit
- Philip Kaufmann
- Pieter Wuille
- pryds
- randy-waterhouse
- R E Broadley
- Ro
that is so bad in practice, after all the % of blocks that
will have transactions for a given wallet will generally be low, so the
block size is amortized in a way. Of course, if the block size would be
increased t
we can easily
> do them in minor releases too.
Agree here - there is no need to time consensus changes with a major
release, as they need to be ported back to older releases anyhow.
(I don't really classify them as software features, but properties of
the underlying system that we
A reminder - feature freeze and string freeze is coming up this Friday the 15th.
Let me know if your pull request is ready to be merged before then,
Wladimir
On Tue, Apr 28, 2015 at 7:44 AM, Wladimir J. van der Laan
wrote:
> Hello all,
>
> The release window for 0.11 is nearing, I&
The subject should obviously be "Bitcoin Core 0.10.2 release candidate
1 available", not the other way around,
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring s
one who directly contributed to this release:
- Cory Fields
- Gregory Maxwell
- Jonas Schnelli
- Wladimir J. van der Laan
And all those who contributed additional code review and/or security research:
- dexX7
- Pieter Wuille
- vayvanne
As well as everyone that helped translating on
[Transifex](htt
w all I see submitted for this is support for
> multiple local IPs (#829) though.
>
>
IPv6 support would be nice, but I don't think a milestone of 0.7 is
realistic. Such a change to the network code will require extensive
testing. Who has access to IPv6 and can help testing?
Wladimi
r
> we could
> > do a "cleanup" to 10 first, and start incrementing from there.
>
>
> It would be nice to have 10 as the baseline, "frozen" protocol.
>
Yes, I think increasing with one is
like this is sign message stuff is dragging the kitchen sink
into Bitcoin. It's fine for logging into a website, what you use it for,
but anything that approaches signing email (such as S/MIME implementations
and handling different cha
ich this makes P2SH easier and less involved. How many steps can be
eliminated of the 14?
Wladimir
BTW: we also still need a BIP to define URL signing / authentication
itself.
--
Better than sec? Nothing is better than sec
f the requested block header. If
this is passed in the reply, and the caller can correlate the request and
reply without a special nonce administration.
Wladimir
--
For Developers, A Lot Can Happen In A Second.
Boundary
k still occur.
>
If you're behind such a slow internet connection, and concerned about every
bit of bandwidth, it is better to run a lightweight node. For example,
Electrum.
Even if you could reduce the wasted bandwidth a bit by puzzling around with
partial blocks, the download w
destination address, message is a freeform message
describing the transaction.
I don't think the message is currently stored in the Satoshi client. That
feature is somewhere on our way-too-long issue and todo list.
But I un
core, and I'd think it is
pretty important to keep it a first-class citizen.
Wladimir
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has
e is no need to make it this fine-grained.
Wladimir
On Sat, Jun 16, 2012 at 3:34 AM, Amir Taaki wrote:
> Introspection/command discovery is nice, but I would prefer it to be
> immediately done in the first version exchange so no assumptions as to how
> a network is operating need to be m
ritical data structures. Sure, there might
be some cases in which the locks are not necessary, or read/write locks
could be used instead to improve concurrency, but this has to be approached
really carefully.
Wladimir
--
Live
n the granularity should
be large, not command-level. The interaction between protocol versions and
capabilities needs to be defined as well. Does offering "getdata" at
protocol version 10 mean the same as offering it at protocol version 11"?
Probably not guarantee
d the only difference.
>
>
To prevent surprises in the future, in case OpenSSL decides to add more,
can we disable all other key formats in advance?
Wladimir
--
Live Security Virtual Conference
Exclusive live event w
sition in the alt
clients list is less important. That said, I'm not a big fan of randomized
order because it's confusing. Come back to the page and it's different.
Some other neutral ordering is probably possible.
Wladimir
On Tue, Jul 10, 2012 at 5:05 AM, Gregory Maxwell wrote:
albox don't play along well.
Wladimir
On Fri, Jul 13, 2012 at 10:41 PM, Mark Friedenbach wrote:
> I had some difficulty setting up and maintaining my own gitian build
> system. So in the time-honored tradition of scratching my own itch, I
> recorded the necessary steps into a makef
But is he the only one using the broken URLs? It was my impression that
they were widespread already.
Wladimir
On Mon, Jul 16, 2012 at 10:52 AM, Gary Rowe wrote:
> Is it worth having a few more people email Ben to ask him politely to fall
> into line with the BIP? No point encouraging
status with
certainty, so quite a large safety margin is used. To be precise the
warning is shown when the last received block was generated more than 90
minutes ago.
Wladimir
--
Live Security Virtual Conference
Exclusive li
for those messages will be broken again. There should be no more message
changes before the release unless there is a very good reason.
Wladimir
--
Live Security Virtual Conference
Exclusive live event will cover all the w
Fully agree with the changes, but I think there should be a small BIP, for
consistency, and to make it documented for other client developers.
Wladimir
--
Live Security Virtual Conference
Exclusive live event will cove
the custom format for the wallets is
introduces, various new configurations will be possible: Multiple wallets,
wallet in block chain in separate dirs, etc.
Wladimir
--
Got visibility?
Most devs has no idea what their productio
some deeply nested wiki page. Ie, something
like
https://www.mozilla.org/en-US/contribute/
http://www.ogre3d.org/developers
...
I'm willing to write this. But I know these kinds of proposals always
end in a big discussion about what should be and what should not be on
bitcoin.org, however we sho
gin etc...). But I'm probably
misunderstanding what you're trying to do.
Wladimir
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has c
ould go
> into a 0.7.1 release?
I think we should also pull #1859 "add LOCK() for proxy related
data-structures" Missing synchronization primitives are a sure way to
get reports about random crashes.
The rest can wait.
Wladimir
--
ty.
I've just pulled all the small stuff that was already ACKed for
post-0.7.1, so IMO the freeze can start.
Wladimir
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Re
On Thu, Oct 11, 2012 at 12:51 PM, Wladimir wrote:
> On Wed, Oct 10, 2012 at 8:40 PM, Jeff Garzik wrote:
>> Proposal: following 0.7.1 release, freeze the tree. Do not pull
>> anything, until ultraprune is pulled (or rejected, but I think the
>> latter is unlikely).
>
n, Sourceforge
> would block certain downloads (but not the project site). That said it
> was trivial to bypass the restrictions then.
I don't think it's related to these sanctions but to the Great
Firewall of China, but sourceforge downloads are also blocked i
s at some point, or change their
interpretation, and bitcoin will automatically change with it. As
bitcoin happily links against any OpenSSL version you provide it, in
worst case, this can result in forks and unexpected behavior
completely out of our
ultraprune + bloom filtering is the two major scalability improvements we
> have right now.
>
I'm not sure about a full feature freeze. I agree it could be wise not do
any more changes of the scale of ultraprune before 0.9, to give some
stability to fix the kinks in the current version
BTC
units? And it's gone after 21 blocks.
I wonder if there is a way for the whole process to be transparent to the
user. The wallet is 'defragmented' but without losing the swept up coins to
the miner.
Wladimir
On Mon, Dec 3, 2012 at 12:19 PM, Michael Gronager w
e was a straightforward solution for that, yeah pooling together
our development on one or two clients instead of a zillion different ones
could help, but everyone has more fun working on their own client that's
just how things go :)
Wladimir
On Wed, Dec 5, 2012 at 6:38 AM, Jim Nguyen wrot
Maybe now that bitcoin is growing out of the toy phase it's an idea to
start gpg signing commits, like the Linux kernel (
https://lwn.net/Articles/466468/).
But I suppose then we can't use github anymore to merge as-is and need
manual steps?
Wladimir
On Tue, Apr 2, 2013 at 12:
ments are censored in the console screen and command line history. At
least `importprivkey`, `walletpassphrase`, `walletpassphrasechange` should
likely be in that list.
Wladimir
--
Learn Graph Databases - Download FREE O'
oes not help in implementation
:-)
Wladimir
Multiple recipients/amounts. Any syntax you like. Thanks!
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance
.bitcoin.it/wiki/Hardfork_Wishlist.
Wladimir
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analyt
Chris,
Using zmq is a great fit for high-speed notifications such as this. Have
you seen the pull request to integrate zmq directly into bitcoind, so that
you don't even need -blocknotify?
https://github.com/bitcoin/bitcoin/pull/2415
If not: we could use some testing there!
Wladimir
O
oded" thus are not fully opaque. But
it's a long shot, as a hashed value is still very opaque.
> I also here that there is a LIKELY change from the base58 encoding ...
> when was this established?
>
No, there have been no changes to base58. The encoding is still exactly the
same
gitian-build with.
>
Fully agreed about payment protocol, autotools and Qt5 build.
I'm still not very excited about coin control (and last time I looked at
the code, it has an issue that it introduced statefulness into the wallet
model - a bane for concurrency. But th
longer
need to burden the core code
(see also the discussion here: https://github.com/bitcoin/bitcoin/pull/2917).
Wladimir
--
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance C
e number of users) and reviewing and testing takes
time so pull requests, proposals and such can linger for a while. Which can
indeed be frustrating.
Wladimir
--
October Webinars: Code for Performance
Free Intel webinars
alves
as the results is 64 bytes.
Regards,
Wladimir
On Fri, Oct 25, 2013 at 10:46 PM, Mike Caldwell wrote:
> Gregory,
>
> No problem, thanks for providing the IRC recap, and glad I've finally made
> "radio contact" with the list. Perhaps there can be some lo
ere for donations,
consider it an anonymous (wel, pseudonymous) gift jar.
Regards,
Wladimir
--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explo
mentions of monetary value are accompanied with a unit).
Maybe we should stealthily collect people's settings and switch over once a
majority switched *ducks*.
Or, more seriously, maybe add a popup when upgrading the first time to 0.9
with an explanation where people can reconsider their unit s
ng the dropdown box in the
amount widget), but I'm going to make the verification dialog show the
totals in all three units. This will make people learn about other units
without having to choose them consciously.
Wladimir
--
P can be
implemented, even if still in draft status; it gives something to refer to
when mentioning a certain improvement proposal (in commit messages and such
it could be called BIP xxx Draft).
I don't think we are at risk of running out of numbers to assign
On Tue, Nov 19, 2013 at 6:06 PM, Peter Todd wrote:
> On Tue, Nov 19, 2013 at 05:32:55PM +0100, Wladimir wrote:
> > On Mon, Oct 21, 2013 at 4:30 PM, Jeff Garzik wrote:
> >
> > > BIP drafts are stored in git://github.com/bitcoin/bips.git/drafts/ and
> > > are
ork is not assigned a number until it is
> complete.
>
Talking about complete, BIP 40 and 41 don't even have an associated
document:
https://github.com/bitcoin/bips
I agree that was over-eager number assigning.
Wladimir
I think the problem is with this loop:
https://github.com/bitcoin/bitcoin/blob/master/src/qt/sendcoinsdialog.cpp#L261
This deletes widgets, but Qt may still be referring to them internally, and
"Deleting a QObject while pending events are waiting to be delivered can
cause a crash."
wiki with links to the github documents, with a notice that changes
should be proposed on github or mailed to the BIP editor (gmaxwell).
Agreed?
Regards,
Wladimir
--
Sponsored by Intel(R) XDK
Develop, test and display
On Thu, Dec 5, 2013 at 3:27 PM, Luke-Jr wrote:
> On Thursday, December 05, 2013 1:37:10 PM Wladimir wrote:
>
> I think this would stifle active BIP draft editing. We're already having a
> hard time getting some developers to write BIPs for their proposals - I
> don&#x
g this number out of thin air)
>
This was considered (see https://github.com/bitcoin/bitcoin/pull/3305) but
deemed to risky for 0.8.6 at the last moment, see the linked pull request
for details.
It will go into 0.9, at least if the full floating fee implementation isn&#
Yes, i'm updating BIP 0001 right now, will send a pull when ready.
On Fri, Dec 6, 2013 at 12:16 AM, Gavin Andresen wrote:
> RE: replace BIPs on the wiki with links to github documents: agreed.
>
> Wladimir or Gregory: can one of you update BIP 0001 to describe the Proper
> Pro
ing taken seriously.
Wladimir
--
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631
re unnecessary coordination.
Don't make problems where they don't exist, we have enough actual issues.
Wladimir
--
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code
.0. Was that an official
> announcement?
>
Yes, it is.
Wladimir
--
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doublecl
bitcoin-announce list that I missed? If
> not, maybe there should be)
>
Yes could have been announced here too.
We announced the rc1 here but not the final release.
...maybe we should add a list of places to announce to the rel
ryptocurrency for
spending. Or just maybe fiat already works well enough there...
Wladimir
--
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
h
-development),
this can be done in a later separate change.
See pull request here:
https://github.com/bitcoin/bips/pull/1
Regards,
Wladimir
--
Rapidly troubleshoot problems before they affect your business. Most IT
organiz
f
> the sending amount. "the fee seems unusually high, are you really sure you
> want to pay X in fees?"
>
Bitcoin-qt (in master) always shows the fee and total amount that is going
to be paid in the confirmation dialog, so it is very hard t
27;t support importing private keys. Replace the importing of private
keys by a "sweep" function.
Wladimir
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't ha
ns to the options dialog (and improve the dialog in general),
https://github.com/bitcoin/bitcoin/pull/3347
It doesn't add the RPC settings though. As Mark says, it's dangerous to
make it too easy to shoot yourself in
it.
>
Deterministic builds are one part of the equation. Matt Corallo actually
did implement auto-updating using gitian updater:
https://github.com/bitcoin/bitcoin/pull/1453
It ran into lots of bike shedding and was eventually abandoned, but there
is no question whether it is possible wit
n of
the 'coins' so it may be considered realistic to allocate one or two ports
for it. Or not, in which case the altcoins can forget it too.
Regards,
Wladimir
--
Rapidly troubleshoot problems before they a
efore
release
https://github.com/bitcoin/bitcoin/issues?milestone=12&state=open
If there is something else that you're working on and needs to end up in
0.9, or know of some nasty bug in master that should absolutely be solved
first, please t
#x27;s non-trivial to translate to a local term.
Wladimir
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environmen
nable-frontends=).
The others appear to be more controversial as they affect mining/consensus.
I'd really like to see ACKs from more reviewers and testers there before
merging.
Wladimir
--
CenturyLink Cloud: The Leader
> Hope I made you laugh a bit
>
So it's more like a jester's hat then :)
How did I end up on the dogecoin-development list?!?
Wladimir
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why M
is anyone else working on this?
Wladimir
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Ev
On Sun, Jan 19, 2014 at 11:24 AM, Wladimir wrote:
> Consensus running through the comments in the pull is that it needs
> (auto)tests.
>
> Are you going to do this Luke? Or is anyone else working on this?
>
*crickets*
Anyone willing to give pull #1647 its final push by addressi
om the coinbase transaction can be spent as any other output.
Wladimir
--
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview
be able to do for a long time.
Wladimir
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gamp
n
any way. Are you just arguing for the sake of arguing?
Wladimir
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Wh
On Sat, Feb 22, 2014 at 2:09 AM, Dustin D. Trammell <
dtramm...@dustintrammell.com> wrote:
> On Fri, 2014-02-21 at 07:43 +0100, Wladimir wrote:
> > The most straightforward way would be to run the blockchain daemon as
> > a system service (with its own uid/gid and se
how as "164x"?
I just tried getpeerinfo locally and all my peers show as: ""services" :
"0001" as expected.
Wladimir
--
Managing the Performance of Cloud-Based Applications
Take advantag
On Sat, Feb 22, 2014 at 9:08 AM, Wladimir wrote:
> On Sat, Feb 22, 2014 at 3:56 AM, Ronald Hoffman > wrote:
>
>> I noticed that the 'services' field appears to be garbled in the latest
>> source code level from github. Bitcoind is connected to my Java node
of bitcoin, as that only offers 256-bit security (at most) in the
first place.
And if this is not abused, these kind of transactions become popular, and
more space is really needed, the limit can always be increased in a future
version.
Wladimir
--
eone has
compromised that server (or hijacked DNS) to serve fake and unsigned
payment requests, the client can block these.
Neither scenario will help in the case in which the server serving the
Bitcoin URIs is compromised.
Wladimir
very unlikely that bitcoind would connect to port 443, let alone
'attack' anything.
Anything in debug.log regarding that IP?
Wladimir
--
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor
101 - 200 of 294 matches
Mail list logo
