I see your channel (0x7d5D909dB425a6E302140C67062077833A07bE3e)
hmm "ValueError: {'code': -32010, 'message': 'Transaction nonce is too low. Try incrementing the nonce.'}" (from dappnode logs)
Is this WEI from you?
I'm running dappnode on a cloud server and stupidly allowed all connections. Could the problem with martin be due to NAT/firewall config?
I'd just like to know the minimal config
@jo-tud Hi, no ports need to be open. Raiden uses Matrix as it's transport protocol which is based on HTTP (which is one of the major reasons we chose it). As long as you can open outgoing HTTPS connections to the matrix servers (which normally should work through even the most convoluted router / NAT / firewall setups) you don't need to do anything else. You can see which server is used in the Raiden log (not sure how you'd get at that in dappnode though).
Hi everyone. I am running the Wizard and added some test eth to my account. And I'm trying to figure out how to use it with the light client SDK.
I am also running the light client dapp and I don't see how to get the goerli address from the Wizard into Metamask for the dapp. How does that work?
I am also running the light client dapp and I don't see how to get the goerli address from the Wizard into Metamask for the dapp. How does that work?
Hi, @hughlang . Sorry, I don't get your question. the Wizard is for the main Raiden Client (python), the full-node reference implementation. The light-client is a JS/TS lib/sdk/web-dApp implementation of a subset of the protocol, which connects to a full-node transparently as another Raiden Client for the protocol and perform payments "independently" on the Raiden Network by simply forwarding these payments to this connected full-node (called hub), as a full-node would do with one of its neighbors if it didn't have a direct channel with the payment target
So, one thing is to follow the wizard and get a full-node set up and running. A completely independent thing is using the light dApp to connect another account to the Raiden Network, which may happen to be with this full-node you also set up, but could be with any client in the network. This second part isn't related to the wizard at all
why ithaca milestone had changed to Alderaan
Or can I change the target to a local Goerli node?
@hughlang yes, you should be able to enter a local Goerli node as a target by pasting in the the URL that your local Görli node uses where you would usually put the Infura Project ID. We haven't tested this much, hence we're not officially listing it as an option, but it should theoretically work.
Hi. I have a question. When making a payment on the payment network, let L be the length of the hop, X be the payment amount, and T be the time at which the transaction is registered on the blockchain. If so, is the worst "in unit of money × time" equal to "LX x (L+T)"? It looks similar to the Sprites protocol because the receiver puts the secret on the contract.
@xiaofo09 In Raiden, not every payment has to be registered onchain. If peers cooperate and send transfers in both directions, they never need to go onchain (until the total transfers reach 2^256). In those cases,
T doesn't appear in the equation. Also, the amount of time and the amount of payments are not related. The number of hops matter though.
was looking at this lnd routing improvement lightningnetwork/lnd#3143
could something similar be used to benefit raiden multi-hop latency?
could something similar be used to benefit raiden multi-hop latency?
@xiaofo09 Raiden uses the same approach introduced by sprites, you can find the secret registry here
@pirapira was talking about the on-chain collateral, if you are interested on the collateral off-chain, then the time portion of the formula is just the lock timeout, currently defined as
2 * reveal_timeout
There is an error with the pathfinding service with address https://pfs-goerli-with-fee.services-dev.raiden.network. Raiden will shut down.
How to fix the above error?
@susilmohanty11_twitter I restarted the PFS, so it should work again for now. I'm also working on a fix for the problem you run into. It's tracked at raiden-network/raiden-services#520