14:59:07 RRSAgent has joined #interledger 14:59:07 logging to http://www.w3.org/2016/05/04-interledger-irc 15:00:34 dimitri has joined #interledger 15:00:48 Present+ 15:01:41 Scribe: AdrianHB 15:02:44 these recent openssl ASN.1 parser issues worry me about the crypto-conditions encoding. But hopefully OER is less crazy to work with 15:03:28 Topic: Updated five-bells code for new crypto-conditions 15:04:30 https://bluejeans.com/795795755/ 15:04:34 If you are dialing in for the call it's just started 15:05:51 Stefan: quick update. 15:06:01 ... some major changes to reference implementations 15:06:17 ...lots of contributors to crypto-conditions spec now stable 15:06:26 ...time to update the code to match 15:07:03 ...we've also used crypto-conditions for signing the notifications 15:07:23 ...actually sped things up (uses some built in crypto libs) 15:07:32 ...internal feedback has been good 15:07:49 ...nicely abstracted so can use as drop in lib 15:07:56 ...esp for multi-sig 15:08:10 ...will be a lot of uses outside of just ILP 15:08:21 ...seen some inbound interest for others 15:08:34 ...still some issues about naming (some people aren't happy) 15:08:50 ...want to be careful that we don't make it confusing 15:09:18 ...lots of people now using them so don't want to change prefixes 15:09:38 ...cc are also more general than sigs so don't want to use sigs 15:10:24 topic: Routing 15:10:47 Stefan: working ona writeup on how we think it should work 15:11:14 ... considers some of the ideas on the mailing list (thanks contributors) 15:11:38 ... one of the biggest changes is an idea taken from how routing works in TCP/IP stack 15:11:45 ... routing not done by sender 15:12:22 ... most efficinet routing is to route for local environment 15:12:42 ... will have good knowledge and can cache routes 15:12:59 ... so proposal is to do incremental routing 15:13:31 ... reliability of routes can be determined by ledgers as they have some data on connectors they use 15:13:52 ... difference from Internet is trying to avoid an equivalent of IANA 15:14:07 ... proposal is to use Interledger to pay to advertise routes 15:14:37 ... there is a prototype which are in PRs on connector, ledger, and sender etc 15:14:47 "will have good knowledge and can cache routes" 15:14:49 ... early days though so consider unstable and please give input 15:14:53 I like where this is going. 15:15:04 would like to discuss later (tomorrow?) on this channel 15:15:19 same for this "reliability of routes can be determined by ledgers as they have some data on connectors they use" 15:15:37 justmoon: +1 15:16:31 stefan: correction - neighbouring connectors will maintain this data 15:16:42 ... intent is to keep functionality in connectors 15:16:52 jamesyoung has joined #interledger 15:17:17 "neighbouring connectors will maintain this data" good for me 15:17:49 dimitri: Woo, crypto-condition HYPE! :) 15:17:52 dimitri: is now using crypto-conditions as a base for all transactions and works perfectly 15:18:28 ... what would be a great demonstrator for us would be to run with another ledger and prove connectivity 15:18:39 ... what is the effort to get this up? 15:19:02 I'm looking forward to the write up. hafta go now but will be on this channel later/tomorrow 15:19:21 evan: in theory, in the connector code you just add a ledger plugin 15:19:23 xavier: Cool! Thanks for stopping by! 15:19:36 ... it's a bit old and so there are some hard-coded assumptions in other places 15:19:47 justmoon: sorry now is night time on my side of the planet 15:19:48 ... need to clean those up 15:20:13 dimitri: can I get some help as we try this 15:20:15 evan: yes 15:22:05 stefan: I got a lot of calls about why we weren't at Consensys. Thanks for those that were there who were talking about ILP 15:22:37 ... we know that we need to do better with outreach but are trying to balance adding noise to the group with some quick early progress 15:23:06 ... we think we have gotten to a a good level of maturity where we can be more proactive about getting more input 15:24:23 https://medium.com/the-bigchaindb-blog/w3c-interledger-protocol-workshop-what-happened-and-what-s-coming-next-f02e8c0e9a9e#.utglr6x4y 15:26:52 topic: cc test suite 15:27:20 stefan: working on design of test suite and trying to find the ways it could break and document those 15:27:47 ... also starting to write and implementation of that that will enable a data driven test suite 15:28:13 ... quote a few different language implementations being talked about so this is becoming a crucial req 15:28:52 ... lots of exploits caused by edge cases in crypto algos so need to test for standard behaviour 15:29:01 ... hope to share test plan soon 15:31:05 topic: Updates to Five Bells Demo 15:31:39 stefan: no updates for a while. Now uses latest package versions but also switched ledger notifications from webhooks to websockets 15:31:58 ... websockets are a little more lightweight 15:32:21 ... the change removes reliability of delivery 15:32:46 ... the realization was that ILP already accounts for lost notifications 15:33:02 ... this also made the demo much faster 15:33:28 ... next change will be to implement the new routing logic which should increase speed significantly esp for large test nets 15:34:34 as AdrianHB said, gotta run! thanks all!! 15:34:38 topic: OWPS 15:34:58 evan: we've been discussing the diff between the ledger and the wallet 15:35:22 ... ledger is lower level and wallet implements some "application layer" stuff on top 15:36:33 * Custom condition logic 15:36:33 * Custom memos (as objects) 15:36:33 * Websocket notifications 15:36:33 * Webfinger address resolution (just so users don’t have to type ledger account on login) 15:36:33 * Simple, unchanging API for sending payments (don’t want to include f-b-sender) 15:36:33 https://github.com/interledger/specs/blob/gh-pages/0001-interledger-architecture.md 15:36:35 * Simple API for pathfinding (needed for normalizing amounts in sender’s currency) 15:36:35 * All of these would ideally work with any ledger 15:37:10 evan: these are the functions of the application layer protocol that are needed 15:38:20 ... the idea is that developers can get a lib that implements this and building on ILP is easier 16:28:50 jamesyoung has joined #interledger 16:34:42 RRSAgent make minutes 16:34:49 RRSAgent, make minutes 16:34:49 I have made the request to generate http://www.w3.org/2016/05/04-interledger-minutes.html AdrianHB 16:35:54 rrsagent, set logs world-visible 17:16:33 Zakim has left #interledger