--- Day changed Tue Mar 29 2016
00:04 -!- Don_John [~Don@247-223-114-134.nat.resnet.nau.edu] has quit [Read error: Connection reset by peer]
00:13 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
00:14 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
00:22 -!- abritoid [~abritoid@46.16.193.99] has joined #bitcoin-core-dev
00:27 -!- BCBot [~BCBot@pc-5305.ethz.ch] has joined #bitcoin-core-dev
00:29 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
00:30 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
00:33 < GitHub191> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/84370d58ffc6...26794d4645e4
00:33 < GitHub191> bitcoin/master fa3fafc MarcoFalke: [qa] wallet: Wait for reindex to catch up
00:33 < GitHub191> bitcoin/master 26794d4 Wladimir J. van der Laan: Merge #7757: [qa] wallet: Wait for reindex to catch up...
00:33 < GitHub5> [bitcoin] laanwj closed pull request #7757: [qa] wallet: Wait for reindex to catch up (master...Mf1603-qaWalletReindex) https://github.com/bitcoin/bitcoin/pull/7757
00:46 -!- xiangfu [~xiangfu@111.198.29.53] has quit [Remote host closed the connection]
01:03 < jonasschnelli> wumpus: awesome idea with the "bc-monitor"!
01:03 < jonasschnelli> Would it only require to connect over ZMQ or also over RPC?
01:03 < wumpus> thanks :)
01:03 < jonasschnelli> The later would probably require two stunnels?
01:03 < wumpus> it requires both, eventually I want to make zmq optional
01:04 < jonasschnelli> With RPC long poll? Or how would you update the stat?
01:04 < wumpus> but I'm most interested in the zmq stats myself so that's the priority for what I'm currently buildlng :)
01:04 < wumpus> just poll, updates will be slower and some things will be missing (like the actiity log)
01:04 < jonasschnelli> Hmm... the polling is kinda lame/hacky and also I don't like the JSON/http overhead...
01:04 < wumpus> so the eventual plan is: zmq is *nice*, rpc is required to get the base info
01:05 < jonasschnelli> I had similar ideas for a new GUI (monitor).
01:05 < wumpus> JSON and http overhead doesn't matter for things that never change (say the name and version of the node)
01:05 < jonasschnelli> right..
01:05 < wumpus> as well as the max size of the mempool
01:05 < wumpus> etc
01:06 < wumpus> also things can be updated asynchronously, you don't have to hang the GUI while an RPC request is underway
01:06 < jonasschnelli> I think we should definitively add a sequence number for each zmq notification.
01:07 < jonasschnelli> This is at tiny cost...
01:07 < wumpus> yes I'm not sure why that wasn't done in the first place
01:07 < jonasschnelli> Right. It would be an API break now.
01:07 < jonasschnelli> But we might risk that...
01:07 < wumpus> would need to be a sequence number per notifier, not a global one, you can't expect people to be listening for everything
01:07 < jonasschnelli> or optionally allow to enable it.
01:07 < wumpus> right.
01:07 < jonasschnelli> Right. It should be per message type.
01:08 < jonasschnelli> A uint64 per message type.
01:08 < wumpus> nah a uint64 is not necessary
01:08 < wumpus> you just need to check that next packet is prevpacket+1
01:08 < wumpus> even a byte woulddo :)
01:09 < jonasschnelli> Indeed. A "skip" > 256 would be extremely rare.
01:09 < wumpus> hm  you're right... well ok, 2 bytes then
01:09 < wumpus> if you miss 65k packets, well, I'd say you're screwed anyway...
01:10 < jonasschnelli> Hah. True.
01:10 < jonasschnelli> Let me know when you have your bc-monitor ready for testing..
01:10 < wumpus> sure!
01:10 -!- jannes [~jannes@178.132.211.90] has joined #bitcoin-core-dev
01:17 < wumpus> <jonasschnelli> Hmm... the polling is kinda lame/hacky and also I don't like the JSON/http overhead... <- what about encoding univalues as cbor (http://cbor.io/) instead  *ducks*
01:19 < wumpus> not actualy convinced how much it would help, but for huge structures like the output of e.g. getrawmempool true it may save a few bytes
01:19 < jonasschnelli> wumpus: hah! More hacky! But i like it. :)
01:19 < jonasschnelli> The polling is just not in-sync with thread synchro.
01:20 < jonasschnelli> The notification approach would scale better IMO
01:20 < wumpus> I do think json parsing can be made very fast too
01:20 < wumpus> (e.g. univalue is already plenty faster than the boost thing)
01:20 < jonasschnelli> I kinda like zmq and I have also though about a channel into the other direction,.. but I'm also aware of the risks.
01:21 < wumpus> sure, notification is good fo things that change, especially at high frequency
01:21 < wumpus> it's not a replacement for a command/response system
01:21 < jonasschnelli> What would speak against accepting requests over zmq (bitcoind listens) and process it async and response with some events (similar to p2p)? Bad design?
01:22 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: Leaving]
01:22 < jonasschnelli> With requests I mean: "give me some informations about connected peers",... just some basic stuff.
01:22 < jonasschnelli> Auth would be a problem.
01:22 < wumpus> why not use rest instead?
01:22 < wumpus> we already have an unauthenticated information interface
01:22 < jonasschnelli> I just don't like having multiple port connected for one purpose (a monitor)
01:23 < wumpus> (and rest doesn't need to be necessarily json)
01:23 < jonasschnelli> It would be very difficult to connect a "monitor" app to your remove node.
01:23 < jonasschnelli> *remote
01:24 < wumpus> I'd like zmq events for some P2P events though
01:24 < wumpus> like 'new node connected' 'node disconnected' etc
01:24 -!- PRab [~chatzilla@c-68-34-102-231.hsd1.mi.comcast.net] has quit [Read error: Connection reset by peer]
01:24 < wumpus> jonasschnelli: I'm mostly aiming at local usage right now, that's why I use ncurses in the first place
01:25 < wumpus> I could split it into two components, one that connects to a local RPC and ZMQ, the other that connects to the tool, and one TCP connection in between. But meh, that's not a priority :)
01:25 < jonasschnelli> wumpus: Yes. This makes sense. I though about a GUI tool that is also process separated.
01:25 -!- PRab [~chatzilla@c-68-34-102-231.hsd1.mi.comcast.net] has joined #bitcoin-core-dev
01:25 < jonasschnelli> And this would require RPC and ZMQ.
01:26 < wumpus> zmq is not very suitable for over-the-internet usage, if you're considering that
01:26 < jonasschnelli> Maybe someone could write a proxy-python script that sits behind apache/ngix and bundles the channels, do the SSL, etc.
01:26 < jonasschnelli> (bundles the channels = RPC & ZMQ)
01:26 < wumpus> something like websocket notification would work better for that. Wouldn't be too difficult to roll a zmq-to-websocket adapter.
01:26 < jonasschnelli> right.
01:27 < wumpus> initialliy I'd have preferred using a streaming http socket for notifications, but zmq is more 'standard'
01:27 < jonasschnelli> Yes.
01:28 < jonasschnelli> I think if one likes to connect over the inet with a monitor app, a CGI python script would be sufficient. You could use SSL and http digest from apache/httpd
01:29 < jonasschnelli> But lets first focus on the monitor locally connected!
01:29 < wumpus> if it's for over the internet a whole new world of authentication, security, etc opens up... scope creep etc :)
01:29 -!- ebfull [~sean@73.34.119.0] has quit [Ping timeout: 248 seconds]
01:30 < wumpus> I do agree it'd be nice though
01:31 < jonasschnelli> I really dream of re-usign an old computer as "monitor center" for a couple of nodes... mempool, peers, blocks
01:31 -!- ebfull [~sean@73.34.119.0] has joined #bitcoin-core-dev
01:32 < wumpus> what about snmp support? *sorry, troll mode today*
01:32 < jonasschnelli> Is that still alive.. :)
01:33 < jonasschnelli> But yes. Would allow to attach multiple tools.
01:33 < btcdrak> OMG wumpus. 
01:33 < wumpus> I dont't actually know, I played around with it >10 years ago when I did something with *gasp* servers
01:33 < jonasschnelli> haha... 
01:34 < btcdrak> mind you, it's probably not a bad idea...
01:34 < wumpus> the protocol is terrible and the implementations are even worse, brittle and old (think: openssl but worse)
01:34 < jonasschnelli> I still use it to create some stats from my servers though. I guess "munin" still uses snmp.
01:34 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
01:34 < wumpus> you could make a snmp-to-RPC adapter though, if you come up with enough OIDs and learn to speak ASN.1
01:35 < jonasschnelli> lol
01:36 < wumpus> jonasschnelli: sure, lots of enterprise equipment still uses it, and the big monitor tools support it. It's just not very internet-ready, unless you use it over a secure monitoring VPN or such.
01:36 < jonasschnelli> Agree.
01:39 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has joined #bitcoin-core-dev
01:47 -!- MarcoFalke [05c7b6cb@gateway/web/cgi-irc/kiwiirc.com/ip.5.199.182.203] has joined #bitcoin-core-dev
01:53 < GitHub151> [bitcoin] laanwj pushed 2 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/597494f5a90c...a0cea89456f8
01:53 < GitHub151> bitcoin/0.12 c0fe2c9 BtcDrak: Mark p2p alert system as deprecated....
01:53 < GitHub110> [bitcoin] laanwj closed pull request #7741: [0.12] Mark p2p alert system as deprecated (0.12...alert0) https://github.com/bitcoin/bitcoin/pull/7741
01:53 < GitHub151> bitcoin/0.12 a0cea89 Wladimir J. van der Laan: Merge #7741: [0.12] Mark p2p alert system as deprecated...
01:56 < sipa> wumpus: if we need to fix the serialization for gettxoutsetinfo... maybe we can replace it with a merkleized version?
01:57 < wumpus> sipa: you mean a 6-month masters project for someone? :) or isn't it that bad to do?
01:57 < sipa> wumpus: i don't mean UTXO commitments
01:57 < wumpus> ohh!
01:58 < wumpus> sure, would be good to have a better format
01:58 < wumpus> I'm everything but married to the current one, and apparently we already broke it once without anyone noticing, so (as long as we mention it in the release notes) I'm not against breaking it again
01:58 < sipa> but we can iterate over the utxo entries in order like now, but use an incremental merkle tree hasher (similar to the algorithm used by ComputeMerkleRoot and friends now)
01:58 < wumpus> cool
01:59 < sipa> the overhead would be the same, and you could make it answer queries for specific entries... and it could later just be converted to a commitment structure
01:59 < wumpus> yes, after  the memory improvement for the merkle tree hasher it doesn't have to store all the data in meory
02:03 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
02:06 -!- johnwhitton [~johnwhitt@c-71-202-223-50.hsd1.ca.comcast.net] has quit [Quit: johnwhitton]
02:06 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
02:08 < GitHub100> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/26794d4645e4...aa0d2b263186
02:08 < GitHub100> bitcoin/master f11c5a3 Wladimir J. van der Laan: devtools: make github-merge.py use py3...
02:08 < GitHub100> bitcoin/master aa0d2b2 Wladimir J. van der Laan: Merge #7737: devtools: make github-merge.py use py3...
02:08 < GitHub80> [bitcoin] laanwj closed pull request #7737: devtools: make github-merge.py use py3 (master...2016_03_python_3_github_merge) https://github.com/bitcoin/bitcoin/pull/7737
02:11 < GitHub88> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/aa0d2b263186...2676e12016db
02:11 < GitHub88> bitcoin/master cef8bdf Jonas Schnelli: [Wallet][RPC] add missing abandon status documentation
02:11 < GitHub88> bitcoin/master 2676e12 Wladimir J. van der Laan: Merge #7742: [Wallet][RPC] add missing abandon status documentation...
02:11 < GitHub177> [bitcoin] laanwj closed pull request #7742: [Wallet][RPC] add missing abandon status documentation (master...2016/03/ab_doc) https://github.com/bitcoin/bitcoin/pull/7742
02:15 < GitHub34> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/2676e12016db...b35a59179359
02:15 < GitHub34> bitcoin/master 7eb7029 instagibbs: Add importprunedfunds rpc call
02:15 < GitHub34> bitcoin/master f1bb13c instagibbs: Added companion removeprunedfunds call.
02:15 < GitHub34> bitcoin/master b35a591 Wladimir J. van der Laan: Merge #7558: [RPC] Add import/removeprunedfunds rpc call...
02:16 < GitHub96> [bitcoin] laanwj closed pull request #7558: [RPC] Add import/removeprunedfunds rpc call (master...prunedforport) https://github.com/bitcoin/bitcoin/pull/7558
02:25 < GitHub90> [bitcoin] jonasschnelli opened pull request #7761: [Qt] remove trailing output-index from transaction-id (master...2016/03/ui_txid) https://github.com/bitcoin/bitcoin/pull/7761
02:45 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)]
02:51 -!- rubensayshi [~ruben@c89225.upc-c.chello.nl] has joined #bitcoin-core-dev
03:25 -!- fengling [~fengling@111.198.29.53] has quit [Ping timeout: 240 seconds]
03:31 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev
03:32 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
03:39 -!- BCBot_ [~BCBot@pc-5305.ethz.ch] has joined #bitcoin-core-dev
03:43 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Quit: laurentmt]
03:54 -!- anttea [~anttea@a88-112-146-73.elisa-laajakaista.fi] has joined #bitcoin-core-dev
03:59 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has quit [Quit: Leaving.]
05:01 -!- dermoth_ [~thomas@dsl-66-36-146-182.mtl.aei.ca] has joined #bitcoin-core-dev
05:02 -!- dermoth [~thomas@dsl-216-221-63-79.mtl.aei.ca] has quit [Disconnected by services]
05:02 -!- dermoth_ is now known as dermoth
05:23 -!- jtimon [~quassel@227.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev
05:24 -!- fengling_ [~fengling@111.198.29.53] has joined #bitcoin-core-dev
05:28 -!- fengling_ [~fengling@111.198.29.53] has quit [Ping timeout: 240 seconds]
05:33 < jonasschnelli> wumpus: what about adding a github label "ZMQ"?
05:33 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev
05:33 < jonasschnelli> Maybe each IO should have its label
05:33 < wumpus> hmm maybe, I generally prefer to keep anything that is about communicating with applications under 'RPC'
05:34 < jonasschnelli> okay.
05:34 < wumpus> but I'm not against it, we have some more zmq specific issues now
05:34 < wumpus> there is a compromise somewhere between general enough labels for sorting, and specific enough
05:34 < MarcoFalke> what about adding a github label 'easy'?
05:35 < wumpus> not a bad idea
05:36 -!- abritoid [~abritoid@46.16.193.99] has left #bitcoin-core-dev ["O.o"]
05:39 < GitHub188> [bitcoin] jonasschnelli opened pull request #7762: [ZMQ] append a message sequence number to every ZMQ notification (master...2016/03/zmq_seq) https://github.com/bitcoin/bitcoin/pull/7762
05:39 < jonasschnelli> MarcoFalke: "Easy" would stand for "trivial"? "Easy" to review? 
05:43 < MarcoFalke> Easy just for issues
05:44 < MarcoFalke> So when someone want to "try out" patching something in bitcoin, they can jsut grab an easy issue
05:44 < MarcoFalke> But fixing an issue tagged with easy usually implies the review is easy as well.
05:48 < wumpus> easy to implement, not so much 'trivial'
05:48 < wumpus> trivial was used for comment and message changes
05:48 < wumpus> this can be somewhat more beefy, but not requires deep understanding of bitcoin core itself
05:49 < wumpus> and indeed for PRs it makes no sense :)
06:04 < jonasschnelli> maybe we could rename "RPC" to "RPC/ZMQ/REST"?
06:04 < jonasschnelli> and remove "REST"
06:05 < jonasschnelli> For "Easy" we could use "easy to implement" (so interpretation is more clean than)
06:05 < jonasschnelli> *clear
06:07 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
06:11 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has joined #bitcoin-core-dev
06:18 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
06:45 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Quit: laurentmt]
06:55 < wumpus> jonasschnelli: yes, let's do that
06:57 < wumpus> done
06:59 < jonasschnelli> Looks good!
07:27 -!- fengling_ [~fengling@111.198.29.53] has joined #bitcoin-core-dev
07:31 < morcos> wumpus: 7648 is actually relatively simple code wise, i believe it has gotten a lot of review.  i believe at least one of petertodd's comments were about testing of the consensus code in bip68 which is tested fairly heavily by the new rpc test.
07:32 -!- fengling_ [~fengling@111.198.29.53] has quit [Ping timeout: 240 seconds]
07:37 -!- p15 [~p15@25.91.145.64.client.static.strong-tk2.bringover.net] has quit [Ping timeout: 264 seconds]
07:48 < GitHub125> [bitcoin] sipa opened pull request #7763: Reformat version in UpdateTip and other messages (master...hexver) https://github.com/bitcoin/bitcoin/pull/7763
07:50 < GitHub140> [bitcoin] MarcoFalke opened pull request #7764: [qa] Don't run pruning.py twice (master...Mf1603-qaPruningTwice) https://github.com/bitcoin/bitcoin/pull/7764
07:57 -!- Amnez777 [~Amnez777@unaffiliated/amnez777] has quit [Ping timeout: 246 seconds]
08:07 < GitHub4> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/b35a59179359...a65b36ce354a
08:07 < GitHub4> bitcoin/master faa9f01 MarcoFalke: [qa] Don't run pruning.py twice
08:07 < GitHub4> bitcoin/master a65b36c Wladimir J. van der Laan: Merge #7764: [qa] Don't run pruning.py twice...
08:07 < GitHub58> [bitcoin] laanwj closed pull request #7764: [qa] Don't run pruning.py twice (master...Mf1603-qaPruningTwice) https://github.com/bitcoin/bitcoin/pull/7764
08:09 -!- Amnez777 [~Amnez777@37.157.216.147] has joined #bitcoin-core-dev
08:15 -!- Amnez777 [~Amnez777@37.157.216.147] has quit [Changing host]
08:15 -!- Amnez777 [~Amnez777@unaffiliated/amnez777] has joined #bitcoin-core-dev
08:16 < GitHub161> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/a65b36ce354a...d8e862a5a753
08:16 < GitHub161> bitcoin/master 018b60c Wladimir J. van der Laan: test_framework: detect failure of bitcoind startup...
08:16 < GitHub161> bitcoin/master d8e862a Wladimir J. van der Laan: Merge #7744: test_framework: detect failure of bitcoind startup...
08:17 < GitHub133> [bitcoin] laanwj closed pull request #7744: test_framework: detect failure of bitcoind startup (master...2016_03_detect_startup_failure) https://github.com/bitcoin/bitcoin/pull/7744
08:23 < GitHub11> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/d8e862a5a753...5131005e5b26
08:23 < GitHub11> bitcoin/master 18f05c7 Wladimir J. van der Laan: build: python 3 compatibility...
08:23 < GitHub11> bitcoin/master 5131005 Wladimir J. van der Laan: Merge #7723: build: python 3 compatibility...
08:23 < GitHub163> [bitcoin] laanwj closed pull request #7723: build: python 3 compatibility (master...2016_03_build_python_3) https://github.com/bitcoin/bitcoin/pull/7723
08:25 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Read error: Connection reset by peer]
08:26 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-core-dev
08:32 -!- Amnez777 [~Amnez777@unaffiliated/amnez777] has quit [Ping timeout: 252 seconds]
08:44 -!- Amnez777 [~Amnez777@37.157.216.147] has joined #bitcoin-core-dev
08:45 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Remote host closed the connection]
08:46 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
08:50 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Ping timeout: 276 seconds]
08:54 -!- Amnez777 [~Amnez777@37.157.216.147] has quit [Changing host]
08:54 -!- Amnez777 [~Amnez777@unaffiliated/amnez777] has joined #bitcoin-core-dev
08:54 -!- zooko [~user@2601:281:8001:26aa:759f:a191:9026:e4fa] has joined #bitcoin-core-dev
08:57 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev
08:57 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit]
09:21 -!- JeromeLegoupil [~textual@46-127-102-197.dynamic.hispeed.ch] has joined #bitcoin-core-dev
09:30 -!- fengling_ [~fengling@111.198.29.53] has joined #bitcoin-core-dev
09:35 -!- fengling_ [~fengling@111.198.29.53] has quit [Ping timeout: 240 seconds]
09:43 -!- droark [~droark@c-24-22-36-12.hsd1.or.comcast.net] has quit [Read error: Connection reset by peer]
09:46 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
09:48 -!- [_smitty] [~chatzilla@97-90-24-187.dhcp.mtpk.ca.charter.com] has joined #bitcoin-core-dev
09:49 -!- [_smitty] is now known as roidster
09:50 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev
09:51 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Ping timeout: 276 seconds]
10:02 -!- molly [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
10:04 -!- arowser_ [~quassel@106.120.101.38] has joined #bitcoin-core-dev
10:05 -!- arowser [~quassel@106.120.101.38] has quit [Ping timeout: 276 seconds]
10:06 -!- xabbix__ [~xabbix@bzq-79-176-85-172.red.bezeqint.net] has joined #bitcoin-core-dev
10:06 -!- sturles_ [~sturles@ulrik.uio.no] has joined #bitcoin-core-dev
10:06 -!- sturles_ [~sturles@ulrik.uio.no] has quit [Changing host]
10:06 -!- sturles_ [~sturles@unaffiliated/sturles] has joined #bitcoin-core-dev
10:07 -!- Eliel_ [~jojkaart@a91-154-164-164.elisa-laajakaista.fi] has joined #bitcoin-core-dev
10:07 -!- teward [teward@ubuntu/member/teward] has quit [Ping timeout: 268 seconds]
10:07 -!- binns [sid105317@21/bitcoin/binns] has quit [Ping timeout: 268 seconds]
10:07 -!- michagogo [uid14316@wikia/Michagogo] has quit [Ping timeout: 268 seconds]
10:07 -!- eragmus [sid136308@gateway/web/irccloud.com/x-eubwytnbhpjptphc] has quit [Ping timeout: 268 seconds]
10:07 -!- lightningbot [supybot@2400:8900::f03c:91ff:fedf:3a06] has quit [Ping timeout: 268 seconds]
10:07 -!- sipa [~pw@unaffiliated/sipa1024] has quit [Ping timeout: 268 seconds]
10:07 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 268 seconds]
10:07 -!- nsh [~lol@wikipedia/nsh] has quit [Ping timeout: 268 seconds]
10:07 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 268 seconds]
10:07 -!- Eliel [~jojkaart@a91-154-164-164.elisa-laajakaista.fi] has quit [Ping timeout: 268 seconds]
10:07 -!- gavinandresen [~gavin@unaffiliated/gavinandresen] has quit [Ping timeout: 268 seconds]
10:07 -!- amiller [~socrates1@unaffiliated/socrates1024] has quit [Ping timeout: 268 seconds]
10:07 -!- cfields [~quassel@unaffiliated/cfields] has quit [Ping timeout: 268 seconds]
10:07 -!- sturles [~sturles@unaffiliated/sturles] has quit [Ping timeout: 268 seconds]
10:07 -!- mturquette [sid66043@gateway/web/irccloud.com/x-xssakqkhptmhjqsi] has quit [Ping timeout: 268 seconds]
10:07 -!- Taek [~quassel@2001:41d0:1:472e::] has quit [Ping timeout: 268 seconds]
10:07 -!- gavinandresen [~gavin@66.172.11.36] has joined #bitcoin-core-dev
10:07 -!- Taek42 [~quassel@2001:41d0:1:472e::] has joined #bitcoin-core-dev
10:07 -!- xabbix_ [~xabbix@bzq-79-176-85-172.red.bezeqint.net] has quit [Ping timeout: 250 seconds]
10:07 -!- sipa_ [~pw@2a02:348:86:3011::1] has joined #bitcoin-core-dev
10:07 -!- lightningbot [supybot@2400:8900::f03c:91ff:fedf:3a06] has joined #bitcoin-core-dev
10:07 -!- teward [teward@ubuntu/member/teward] has joined #bitcoin-core-dev
10:07 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev
10:08 -!- gavinandresen is now known as Guest27562
10:08 -!- cfields [~quassel@unaffiliated/cfields] has joined #bitcoin-core-dev
10:08 -!- amiller [~socrates1@li175-104.members.linode.com] has joined #bitcoin-core-dev
10:08 -!- amiller is now known as Guest26461
10:09 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
10:10 -!- Guest26461 is now known as amiller
10:10 -!- amiller [~socrates1@li175-104.members.linode.com] has quit [Changing host]
10:10 -!- amiller [~socrates1@unaffiliated/socrates1024] has joined #bitcoin-core-dev
10:12 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
10:15 -!- nsh [~lol@wikipedia/nsh] has joined #bitcoin-core-dev
10:16 -!- sipa_ is now known as sipa
10:16 -!- sipa is now known as Guest47312
10:16 -!- zooko [~user@2601:281:8001:26aa:759f:a191:9026:e4fa] has quit [Ping timeout: 248 seconds]
10:17 -!- binns [sid105317@21/bitcoin/binns] has joined #bitcoin-core-dev
10:17 -!- Guest47312 is now known as sipax
10:18 -!- mturquette [sid66043@gateway/web/irccloud.com/x-nrrayrenypzgweig] has joined #bitcoin-core-dev
10:18 -!- michagogo [uid14316@wikia/Michagogo] has joined #bitcoin-core-dev
10:19 -!- eragmus [sid136308@gateway/web/irccloud.com/x-cmtwggarufikczxy] has joined #bitcoin-core-dev
10:21 -!- jannes [~jannes@178.132.211.90] has quit [Quit: Leaving]
10:47 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
10:52 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Ping timeout: 244 seconds]
11:05 < GitHub158> [bitcoin] laanwj opened pull request #7766: rpc: Register calls where they are defined (master...2016_03_separate_rpc_registration) https://github.com/bitcoin/bitcoin/pull/7766
11:12 -!- JeromeLegoupil [~textual@46-127-102-197.dynamic.hispeed.ch] has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
11:30 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev
11:33 -!- fengling_ [~fengling@111.198.29.53] has joined #bitcoin-core-dev
11:34 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit]
11:38 -!- fengling_ [~fengling@111.198.29.53] has quit [Ping timeout: 240 seconds]
11:48 -!- JeromeLegoupil [~textual@46-127-102-197.dynamic.hispeed.ch] has joined #bitcoin-core-dev
11:49 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
11:53 -!- achow101 [~achow101@pool-96-227-114-115.phlapa.fios.verizon.net] has joined #bitcoin-core-dev
11:54 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Ping timeout: 244 seconds]
12:02 < jonasschnelli> Right? importaddress leads to ISMINE_WATCH_UNSOLVABLE? and importpubkey to ISMINE_WATCH_SOLVABLE? (at least for P2PKH outputs)
12:03 < sipax> yes
12:03 < jonasschnelli> Is there no internal ripemd(hash()) cache that could map an P2PKH output to a given private key? 
12:03 < jonasschnelli> Or why is importing and address "UNSOLVABLE"?
12:05 < jonasschnelli> I guess privkey->pubke->hash->hash160->base58c, then compare against required scriptsig pkh and sign...
12:10 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
12:12 -!- molz [~molly@unaffiliated/molly] has quit [Ping timeout: 252 seconds]
12:14 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
12:15 -!- Taek42 is now known as Taek
12:16 < btcdrak> meeting recap for anyone that missed it https://bitcoincore.org/en/meetings/2016/03/24/
12:17 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 268 seconds]
12:18 < instagibbs> I was going to check for mediantimepast violations, but I don't have an unpruned node...
12:18  * instagibbs really should get a larger ssd
12:29 < jonasschnelli> instagibbs: use a spinning disk?!
12:29 < instagibbs> what am I, a cave man
12:29 < gmaxwell> 1tb SSDs can be had for $200-$300 now.
12:35 < jonasschnelli> instagibbs: lol!
12:36 < jonasschnelli> use 7200rpm. :)
12:37 < jonasschnelli> or try: http://www.extremetech.com/wp-content/uploads/2012/12/ibm-3390-hard-drive-teardown-640x353.jpg
12:42 < btcdrak> jonas 10k rpm or nuthin'
12:43 < sipax> jonasschnelli: it's unsolvable because it doesn't know what scriptPubKey to construct.
12:45 < jonasschnelli> sipax: but couldn't it look through all provided/available private keys and generate the pubkey in a temp. keystore and does a lookup?
12:45 < sipax> jonasschnelli: the point is that it shouldn't
12:46 < jonasschnelli> hah. ok.
12:46 < sipax> wallets should not try to guess how to spend coins
12:46 < sipax> that only leads to confused behaviour, as it makes you forget under what circumstances it works
12:46 < jonasschnelli> okay. This makes sense.
12:47 < gmaxwell> for example, say someone pays a 1 of 2, me and you... and you 'guess' correctly that you can spend it, show it in your wallet... then LOL 8 confirms in I claw the funds back.
12:47 -!- d_t [~textual@212.144.253.35] has joined #bitcoin-core-dev
12:47 < sipax> it's like saying "how do you mean, you didn't get my money? oh, i took your pubkey and added 21/7 times the generator to it! that's easy rightz your wallet should have guessed that that was possible and look for it!"
12:49 < sipax> if you import an address, you're telling the wallet "treat this address as mine, regardless of whether you know how to spend it or not"
12:49 < sipax> if you want it to be able to solve, you should tell it what it needs to be able to solve (by importing the keys and scripts)
12:50 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
12:55 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Ping timeout: 252 seconds]
12:55 < jonasschnelli> sipax: Agreed.
12:56 < jonasschnelli> I was just thinking about separating key from the wallet but still use the wallets coinselection, etc.
12:56 < jonasschnelli> You could do this by impoting the addresses/pubkey and use fundrawtransaction to create your transactions.
12:56 < sipax> yes, then you need to import the keys, not just the addresses
12:57 < jonasschnelli> Then sign it locally (in my case over the hardware wallet app), then send it back for broadcasting.
12:57 < jonasschnelli> Right... I see now the point with the keys instead of the addresses.
12:58 < jonasschnelli> First I though "addresses could include less risks to 'pass around'". But agree with your statement "wallets should not try to guess how to spend coins".
13:07 -!- Don_John [~Don@250-223-114-134.nat.resnet.nau.edu] has joined #bitcoin-core-dev
13:20 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-core-dev
13:33 -!- anchow101 [~achow101@pool-96-227-114-115.phlapa.fios.verizon.net] has joined #bitcoin-core-dev
13:35 -!- achow101 [~achow101@pool-96-227-114-115.phlapa.fios.verizon.net] has quit [Ping timeout: 244 seconds]
13:37 -!- zooko [~user@c-73-217-16-2.hsd1.co.comcast.net] has joined #bitcoin-core-dev
13:41 < sdaftuar> instagibbs: gmaxwell: i don't see any blocks mined from 12/1/15 to 3/13/16 that include transactions which fail MTP
13:41 < sdaftuar> however there are very few transactions that use time based locktimes, and only a small fraction of those appear to use times that are remotely relevant 
13:42 < sipax> maybe we should try creating some?
13:42 < sdaftuar> yeah i think that would be great
13:42 < gmaxwell> Indeed, for MTP thats the next thing to do.. conduct the test.
13:45 < gmaxwell> what we're trying to do is avoid a hot cut of MTP, causing block orphaning. (again, this doesn't block deployment; but if there are miners still mining these things they'll need to be actively nagged to stop mining them before the soft fork)
13:54 -!- anchow101 [~achow101@pool-96-227-114-115.phlapa.fios.verizon.net] has quit [Quit: Leaving]
13:54 -!- achow101 [~achow101@pool-96-227-114-115.phlapa.fios.verizon.net] has joined #bitcoin-core-dev
14:05 -!- zooko [~user@c-73-217-16-2.hsd1.co.comcast.net] has quit [Ping timeout: 244 seconds]
14:07 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has joined #bitcoin-core-dev
14:12 < cfields> anyone happen to know why bitcoind always uses ATYP DOMAINNAME when connecting to a proxy, even when using ipv4/ipv6 ?
14:15 -!- roidster [~chatzilla@97-90-24-187.dhcp.mtpk.ca.charter.com] has quit [Ping timeout: 240 seconds]
14:30 -!- d_t [~textual@212.144.253.35] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
14:33 -!- Don_John [~Don@250-223-114-134.nat.resnet.nau.edu] has quit [Ping timeout: 268 seconds]
14:46 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev
14:57 < MarcoFalke> passing getblock(., False) into deserialize of mininode should not fail?
15:00 -!- JeromeLegoupil [~textual@46-127-102-197.dynamic.hispeed.ch] has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
15:03 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)]
15:04 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Quit: .]
15:05 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
15:05 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Client Quit]
15:07 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
15:08 -!- gevs_ [~greg@ip-83-134-233-91.dsl.scarlet.be] has joined #bitcoin-core-dev
15:11 -!- gevs [~greg@unaffiliated/gevs] has quit [Ping timeout: 240 seconds]
15:15 < GitHub186> [bitcoin] MarcoFalke opened pull request #7767: [qa] add test: Deserialize getblock result (master...Mf1603-qaMininodeDeser) https://github.com/bitcoin/bitcoin/pull/7767
15:21 -!- sipax is now known as sipa
15:21 -!- sipa [~pw@2a02:348:86:3011::1] has quit [Changing host]
15:21 -!- sipa [~pw@unaffiliated/sipa1024] has joined #bitcoin-core-dev
15:22 -!- cryptapus is now known as cryptapus_afk
15:25 -!- Don_John [~Don@250-223-114-134.nat.resnet.nau.edu] has joined #bitcoin-core-dev
15:28 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev
15:29 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit]
15:39 -!- fengling_ [~fengling@111.198.29.53] has joined #bitcoin-core-dev
15:43 -!- fengling_ [~fengling@111.198.29.53] has quit [Ping timeout: 240 seconds]
15:54 < GitHub10> [bitcoin] MarcoFalke closed pull request #7767: [qa] add test: Deserialize getblock result (master...Mf1603-qaMininodeDeser) https://github.com/bitcoin/bitcoin/pull/7767
16:05 -!- Netsplit *.net <-> *.split quits: anttea
16:21 -!- MarcoFalke [05c7b6cb@gateway/web/cgi-irc/kiwiirc.com/ip.5.199.182.203] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
16:27 -!- roidster [~chatzilla@97-90-24-187.dhcp.mtpk.ca.charter.com] has joined #bitcoin-core-dev
16:52 -!- gijensen [~gijensen@gijensen.xyz] has quit [Ping timeout: 244 seconds]
16:54 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev
16:56 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit]
17:02 -!- harding [~harding@mail.dtrt.org] has quit [Remote host closed the connection]
17:12 -!- harding [~harding@mail.dtrt.org] has joined #bitcoin-core-dev
17:13 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has quit [Ping timeout: 250 seconds]
17:13 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-core-dev
17:14 -!- wangchun_ [~wangchun@li414-193.members.linode.com] has quit [Quit: leaving]
17:17 -!- wangchun [~wangchun@li414-193.members.linode.com] has joined #bitcoin-core-dev
17:20 -!- gijensen [~gijensen@gijensen.xyz] has joined #bitcoin-core-dev
17:27 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has quit [Read error: Connection reset by peer]
17:27 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has joined #bitcoin-core-dev
17:31 -!- roidster [~chatzilla@97-90-24-187.dhcp.mtpk.ca.charter.com] has quit [Quit: ChatZilla 0.9.92 [SeaMonkey 2.39/20151103191810]]
17:41 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-hwrzxinnhaozdpwb] has quit [Quit: Connection closed for inactivity]
17:42 -!- fengling_ [~fengling@111.198.29.53] has joined #bitcoin-core-dev
17:42 -!- molz [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer]
17:42 -!- molz [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
17:43 -!- arowser_ [~quassel@106.120.101.38] has quit [Ping timeout: 260 seconds]
17:45 -!- dermoth [~thomas@dsl-66-36-146-182.mtl.aei.ca] has quit [Quit: Ex-Chat]
17:45 -!- fengling_ is now known as fengling
17:58 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
17:58 -!- frankenmint [~frankenmi@174-25-22-102.ptld.qwest.net] has quit [Remote host closed the connection]
17:59 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
18:05 -!- p15 [~p15@45.91.145.64.client.static.strong-tk2.bringover.net] has joined #bitcoin-core-dev
18:19 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving]
18:20 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has quit [Read error: Connection reset by peer]
18:20 -!- davec [~davec@cpe-24-243-251-52.hot.res.rr.com] has joined #bitcoin-core-dev
18:27 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Ping timeout: 276 seconds]
19:15 -!- xiangfu [~xiangfu@111.198.29.53] has joined #bitcoin-core-dev
19:22 -!- fengling [~fengling@111.198.29.53] has quit [Ping timeout: 240 seconds]
19:24 -!- fengling [~fengling@111.198.29.53] has joined #bitcoin-core-dev
19:29 -!- Chris_Stewart_5 [~Chris_Ste@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 248 seconds]
19:29 -!- fengling [~fengling@111.198.29.53] has quit [Ping timeout: 240 seconds]
19:35 -!- xiangfu [~xiangfu@111.198.29.53] has quit [Ping timeout: 248 seconds]
19:37 -!- xiangfu [~xiangfu@111.198.29.53] has joined #bitcoin-core-dev
19:37 -!- fengling [~fengling@111.198.29.53] has joined #bitcoin-core-dev
19:43 -!- Chris_Stewart_5 [~Chris_Ste@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev
19:56 -!- Chris_Stewart_5 [~Chris_Ste@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 260 seconds]
19:57 -!- xiangfu [~xiangfu@111.198.29.53] has quit [Ping timeout: 240 seconds]
19:58 -!- xiangfu [~xiangfu@111.198.29.53] has joined #bitcoin-core-dev
20:03 < GitHub66> [bitcoin] RHavar opened pull request #7768: Clarify outdated text in comment (master...patch-1) https://github.com/bitcoin/bitcoin/pull/7768
20:08 -!- xiangfu [~xiangfu@111.198.29.53] has quit [Ping timeout: 244 seconds]
20:10 -!- xiangfu [~xiangfu@111.198.29.53] has joined #bitcoin-core-dev
20:15 -!- Giszmo [~leo@pc-122-14-46-190.cm.vtr.net] has quit [Quit: Leaving.]
20:22 -!- achow101 [~achow101@pool-96-227-114-115.phlapa.fios.verizon.net] has quit [Read error: Connection reset by peer]
20:23 -!- fengling [~fengling@111.198.29.53] has quit [Ping timeout: 240 seconds]
20:27 < GitHub15> [bitcoin] RHavar closed pull request #7768: Clarify outdated text in comment (master...patch-1) https://github.com/bitcoin/bitcoin/pull/7768
20:47 -!- cryptapus_afk is now known as cryptapus
20:49 -!- cryptapus is now known as cryptapus_afk
21:15 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
21:16 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
21:31 -!- d_t [~textual@212.144.253.35] has joined #bitcoin-core-dev
21:31 -!- d_t [~textual@212.144.253.35] has quit [Read error: Connection reset by peer]
21:32 -!- d_t [~textual@212.144.253.35] has joined #bitcoin-core-dev
22:04 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
22:05 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
22:06 -!- zooko [~user@c-73-229-199-227.hsd1.co.comcast.net] has joined #bitcoin-core-dev
22:19 -!- d_t [~textual@212.144.253.35] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
22:20 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
22:21 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
22:29 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has quit [Ping timeout: 250 seconds]
22:29 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-core-dev
22:59 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
23:00 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
23:14 -!- Don_John [~Don@250-223-114-134.nat.resnet.nau.edu] has quit [Read error: Connection reset by peer]
23:15 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has quit [Quit: Leaving.]
23:33 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has quit [Ping timeout: 244 seconds]
23:33 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-core-dev
23:44 -!- fengling [~fengling@111.198.29.53] has joined #bitcoin-core-dev
23:48 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
23:49 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
23:58 -!- abritoid [~abritoid@mail.abrites.com] has joined #bitcoin-core-dev