Running the code for Sell and I get an error
const settings = machinomy.configuration.receiver();
^
TypeError: Cannot read property 'receiver' of undefined
at Object.<anonymous> (/Users/jinsukim/Workspace/abigail/server.js:9:41)
at Module._compile (module.js:570:32)
Will fix the issue as soon as I can reproduce it.
In PM
any idea?
We spent few hours today thinking it’s something with our code.
Depending on version yarn blows up or stucks.
@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
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
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 ;)
I have been told the general idea of state channels, but all the details are new to me
To link two chains one have to reveal proofs on both chains that the value transfer happened.
Would it need the nonces to be in sync too ?
Oh and I have infinite source of the tokens too.
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.
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