machinomy/machinomy

Micropayments in Ether over HTTP

Sergey Ukustov

@ukstv

Depending on version yarn blows up or stucks.

Michiel de Jong

@michielbdejong

@ukstv can you publish a new version of https://www.npmjs.com/package/machinomy? We need some fixes that we can now only get by including the dependency from github, and it's non-trivial because it requires (the right version of) yarn to be installed

i created a built branch on my fork as a temporary workaround, but would be nice if we can just depend on machinomy via npm

Sergey Ukustov

@ukstv

Ooh, for sure!!

Sergey Ukustov

@ukstv

@michielbdejong released a new version on npm. Does it solve the problem?

Michiel de Jong

@michielbdejong

great! will switch to that. thanks a lot!

Asmodat

@asmodat

Is this project using tendermint ?

Sergey Ukustov

@ukstv

No, it doesn’t, @asmodat, why do you think so?

Pekka Puusaha

@PekkaPuusaha_twitter

Hi guys,

Pekka Puusaha

@PekkaPuusaha_twitter

I'm doing a system for keeping up user's balances in ETH20 tokens. Real-time settling would be expensive in the main chain, so I'm thinking of opening up a payment channel between my private chain and the main chain and aggregating a number of balance updates in one commit. Just an idea, nothing more specific yet planned. Would this be a use case for Machinomy?

µRaiden or Raiden would be the more famous ones, but I want to explore the alternatives as well

Sergey Ukustov

@ukstv

Aww, sweet scenario. The present version of machinomy can not handle the case. As far as I know, Raiden and microRaiden do not fit either. That might me a good case for a generalised state channels though, or to https://witnet.io/#/

Hmm, it might be a cool idea to do a channelised witnet ;)

Pekka Puusaha

@PekkaPuusaha_twitter

What's the shortcoming with machinomy for not doing this?

I have been told the general idea of state channels, but all the details are new to me

Sergey Ukustov

@ukstv

It is not indended for cross-chain state channels.

To link two chains one have to reveal proofs on both chains that the value transfer happened.

Pekka Puusaha

@PekkaPuusaha_twitter

I can have same private keys on both chains

Would it need the nonces to be in sync too ?

Oh and I have infinite source of the tokens too.

Sergey Ukustov

@ukstv

One has to verify on one chain that the corresponding transaction on the other chain happened. http://docs.electrum.org/en/latest/spv.html

The same logic applies to Ethereum.

David Aktary

@aktary

hey @ukstv ... any news on bidi?

Pekka Puusaha

@PekkaPuusaha_twitter

Which might be difficult, as I'm having it as my private chain, heh

Sergey Ukustov

@ukstv

@aktary https://medium.com/machinomy/code-walkthrough-for-generalised-state-channels-f3cdd52d8172

David Aktary

@aktary

sweet... thanks

Justinas

@gulbinas

Sergey Ukustov

@ukstv

Hi there, Justinas!

Ben Sharafian

@sharafian

Hi @ukstv, we're running into some problems with our Ethereum integration for Interledger. We're getting an error that says:

2018-04-13T18:46:10.417Z ilp-plugin-mini-accounts debug btp packet not accepted Error: Invalid payment.
   at ChannelManagerImpl.<anonymous> (/home/michiel/amundsen/node_modules/machinomy/lib/channel_manager.ts:126:15)
   at step (/home/michiel/amundsen/node_modules/machinomy/dist/lib/channel_manager.js:42:23)
   at Object.next (/home/michiel/amundsen/node_modules/machinomy/dist/lib/channel_manager.js:23:53)
   at fulfilled (/home/michiel/amundsen/node_modules/machinomy/dist/lib/channel_manager.js:14:58)
   at <anonymous>

and it looks like it's because canClaim is returning false in https://github.com/machinomy/machinomy/blob/master/lib/payment_manager.ts#L40 . We're on version 1.6.1.

If you get a chance could you take a look and let me know if there's anything wrong with the payment we're creating here? https://github.com/interledgerjs/ilp-plugin-ethereum-asym-client/blob/bs-fix-various/index.js#L94

Sergey Ukustov

@ukstv

@sharafian We will dig into that the coming few days. Currently are deep into preparations for Hannover Messe and EventHorizon.

Michiel de Jong

@michielbdejong

cool, good luck there! in the meantime, i'll see if i can upgrade our code from 1.6.1 to 1.7.9 and see if that helps

Michiel de Jong

@michielbdejong

@ukstv has the latest contract been deployed to Rinkeby, or could it be that there's still a version there that would be incompatible with 1.7.9?

Sergey Ukustov

@ukstv

It’s the latest contract on Rinkeby.

Michiel de Jong

@michielbdejong

http://machinomy.com/test redirects to https://machinomy.com/test which is a 404. Is the documentation on https://machinomy.com/ outdated?

https://machinomy.com/documentation/getting-started/ mentions http://playground.machinomy.com/hello as a Buy url to test with, but that seems to be down?

Michiel de Jong

@michielbdejong

The 'Sell' snippet from https://machinomy.com/documentation/getting-started/ also seems to be outdated, it uses require('machinomy').configuration

Michiel de Jong

@michielbdejong

It’s the latest contract on Rinkeby.

Hm, I'm getting better results on Ropsten(revived) than on Rinkeby, so will stick to Ropsten(revived) from now on! :) Will let you know if I run into any more problems, or if I get it working :)

https://github.com/interledgerjs/ilp-plugin-ethereum-asym-client/pull/9#issuecomment-382768053

JezSan

@JezSan

hey folks

im doing some analysis on the various state and payment channel offerings. is there anywhere I can play with a working test of the machinery channels, to see what opening and closing channels looks like?

(machinomy, sorry, my spellchecker took over)

does anyone know how they compare to ethcale?

eyals

@aykesubir

Hey ya'll, this have probably came up dozens of times but, is there a page explaining the differences between Machimony vs microRaiden/Raiden techs?

eyals

@aykesubir

@JezSan Hey, im doing something similar for Sirin Labs. We should talk!

JezSan

@JezSan

@aykesubir Happy to. im on jez@funfair.io - or Skype: JezSan

Evan Schwartz

@emschwartz

@aykesubir Machinomy does unidirectional channels for Ether and ERC20 tokens. When I was looking around for Ethereum micropayment libraries I was comparing them and was disappointed to find that microRaiden uses its own token rather than letting you use any one you want (see https://github.com/raiden-network/microraiden#tokens-and-channel-manager-contract). Raiden uses a more complex multi-hop design, but as far as I know isn't released yet

eyals

@aykesubir

@emschwartz Thank you! So machimony only supports unidirectional channels? Other than the underlying token, is there any difference in the protocol?

eyals

@aykesubir

For example are the funds released immediately upon a cooperative close of channel? (unlike lightning for bitcoin, to the best of my knowledge). Furthermore, is Machimony an implementation of a general state channel specified for payments, or what I've seen that spankchain have developed (https://github.com/SpankChain/general-state-channels) is a generalization of your work?
Sorry for q bombing

Evan Schwartz

@emschwartz

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

(That's actually a nice part about unidirectional channels)

Where communities thrive

People

Repo info

Activity