{"push_id":1023842480,"size":1,"distinct_size":1,"ref":"refs/heads/flow","head":"9d8bea3b244c601a9becfa66f1690f256e3d6932","before":"a30b47645365294313a8dc8a64f3a84dff0b53a8","commits":[{"sha":"9d8bea3b244c601a9becfa66f1690f256e3d6932","author":{"email":"9b53dab2edb1fa3e4a37a9ff4ebc112e5291f5f6@yahoo.com","name":"seelabs"},"message":"V2 implementation of payments:\n\nThe key changes from the old code are:\n\n    * A new algorithm for finding the liquidity in a payment path. There\n      is still a reverse and forward pass, but the forward pass starts\n      at the limiting step rather than the payment source. This insures\n      the limiting step is completely consumed rather than potentially\n      leaving a 'dust' amount in the forward pass.\n\n    * Each step in a payment is either a book step, a direct\n      step (account to account step), or an xrp endpoint. Each step in\n      the existing implementation is a triple, where each element in the\n      triple is either an account of a book, for a total of eight step\n      types.\n\n    * Because we consider accounts in pairs, rather than triples,\n     transfer fees are handled differently. In the existing code, in the\n     payment path A -> gw ->B, if A redeems to gw, and gw issues to B, a\n     transfer fee is changed. In the new code, a transfer fee is changed\n     even if A issues to gw.","distinct":true,"url":"https://api.github.com/repos/seelabs/rippled/commits/9d8bea3b244c601a9becfa66f1690f256e3d6932"}]}