ukstv on master
Publish - @machinomy/wraptso@… Remove dependency on chalk in w… Publish - @machinomy/wraptso@… (compare)
ukstv on wraptso@0.1.4
ukstv on wraptso@0.1.3
ukstv on master
Publish - @machinomy/wraptso@… Publish - @machinomy/wraptso@… Do not require console.table and 1 more (compare)
ukstv on wraptso@0.1.2
Publish - @machinomy/wraptso@… Publish - @machinomy/wraptso@… (compare)
ARyaskov on master
Up wraptso version. (compare)
ARyaskov on master
Fix wraptso for modern environm… (compare)
ukstv on master
Remove isGreaterThanPrevious va… Publish - @machinomy/cli@0.0.… (compare)
ARyaskov on master
Fix TravisCI. (compare)
ukstv on master
Publish - @machinomy/cli@0.0.… (compare)
ARyaskov on master
Introduce updateSettlingUntil m… Fix lint error. Fix SQL quotes. and 4 more (compare)
ARyaskov on updateSettlingUntil-in-DAO
Inflate channel's settlingUntil… Publish - @machinomy/cli@0.0.… Merge branch 'master' into tech… (compare)
ukstv on master
Publish - @machinomy/cli@0.0.… (compare)
ukstv on master
Inflate channel's settlingUntil… (compare)
ukstv on inflate-settling-until
Inflate channel's settlingUntil… (compare)
ARyaskov on updateSettlingUntil-in-DAO
Refactor BigNumber operation. (compare)
If I'm not mistaken, I believe Machinomy is the library Spankchain is actually using (https://medium.com/machinomy/explaining-vynos-91f73eeb133a).
I think @ukstv was planning to implement bidirectional channels but not sure if that's still on the roadmap (I'd argue that's an optimization that's only really useful if a) the network fees are super high and b) the use case actually involves balanced flows that can net out)
Since the channels are unidirectional, the receiver can always claim the funds they are owed (see https://github.com/machinomy/machinomy-contracts/blob/master/contracts/Unidirectional.sol#L118-L125). It's only the sender that has to wait before getting their money out of the channel
/Users/michiel/.machinomy/storage.db
)