Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 15:05

    t-bast on invoice-payment-metadata

    Add support for sending payment… Include payment metadata in all… Show payment metadata in API re… (compare)

  • 14:32

    t-bast on invoice-payment-metadata

    Show payment metadata in API re… (compare)

  • 11:54

    t-bast on invoice-payment-metadata

    Filter init, node and invoice f… Add support for sending payment… Include payment metadata in all… (compare)

  • 10:43

    t-bast on invoice-payment-metadata

    Filter init, node and invoice f… Add support for sending payment… Include payment metadata in all… (compare)

  • Dec 06 11:17

    thomash-acinq on fee-update-error

    (compare)

  • Dec 06 11:16

    thomash-acinq on master

    No error when updating the rela… (compare)

  • Dec 06 10:56

    thomash-acinq on fee-update-error

    Comment why it's OK (compare)

  • Dec 06 10:17

    thomash-acinq on fee-update-error

    No error when updating the rela… (compare)

  • Dec 06 09:46

    thomash-acinq on fee-update-error

    No error when updating the rela… (compare)

  • Dec 05 18:48

    sstone on use-psbt-kmp

    Use psbt to fund transactions (compare)

  • Dec 03 09:58

    sstone on use-bitcoin-kmp-through-bitcoin-lib

    Use bitcoin-kmp through bitcoin… (compare)

  • Dec 02 17:22

    t-bast on channel-type-feature-bit

    (compare)

  • Dec 02 17:22

    t-bast on master

    Add channel type feature bit (#… (compare)

  • Dec 02 16:54

    t-bast on channel-type-feature-bit

    Ensure channel type feature is … Verify that remote sets channel… (compare)

  • Dec 02 16:34

    t-bast on channel-type-feature-bit

    Fix test after rebase (compare)

  • Dec 02 16:28

    t-bast on channel-type-feature-bit

    Add channel type feature bit W… Ensure channel type feature is … Verify that remote sets channel… (compare)

  • Dec 02 15:47

    t-bast on remote-claim-htlc-success-log

    (compare)

  • Dec 02 15:46

    t-bast on master

    Remove misleading claim-htlc-su… (compare)

  • Dec 02 15:22

    t-bast on send-to-route-private-chan

    (compare)

  • Dec 02 15:22

    t-bast on master

    Support private channels in Sen… (compare)

Sergei Tikhomirov
@serg_tikhomirov_twitter
@araspitzu I've relaunched everything, now one of my channels is OFFLINE, and the peer is DISCONNECTED. However, when I run eclair-cli connect, I get reconnection is progress (but nothing is seemingly happening). I tried to manually disconnect, but got Ask timed out on [Actor[akka://eclair-node/user/$k#-762188208]] after [30000 ms]. Sender[null] sent message of type "fr.acinq.eclair.io.Peer$Disconnect".. The peer seems to be stuck in a DISCONNECTED state, and I can neither connect nor disconnect. What could be the way out?
Sergei Tikhomirov
@serg_tikhomirov_twitter
UPD problem solved by connecting from the other end. The core reason still unknown.
karhata
@karhata
hello?
araspitzu
@araspitzu
@serg_tikhomirov_twitter I think the core reason is ACINQ/eclair#1242 this prevents the manual reconnection when a scheduled reconnection is in place.
@karhata please state your question we're here to help :)
karhata
@karhata
may I ask a question?
karhata
@karhata
I have some problems.
I can't close or force close all channels on eclair.
And some channels have closed status confirmation but some have 'ERR_INFORMATION_LEAK' status.
How can I close these channels?
캡zbrthrth.PNG
araspitzu
@araspitzu
@karhata do you have logs about the channels with ERR_INFORMATION_LEAK?
karhata
@karhata
no
araspitzu
@araspitzu
did you restore the database from a backup?
karhata
@karhata
no. The latest status data. However, November 20th backup data exists.
Some of the oldest data can be 'force close' but it can cause problems, so it is working with the latest data.
araspitzu
@araspitzu
@serg_tikhomirov_twitter i don't know if you followed the conversation on github.com/eclair but the reconnection behavior has been deemed a will not fix. So we cannot force the reconnection to the same address and it makes sense because the remote will reconnect to us if it's available.
@karhata without logs or any further information is hard to provide help, logs in particular would be very helpful.
@karhata what was the "story" behind the faulty channels? Do you remember when they were opened? When did ERR_INFORMATION_LEAK appear first?
karhata
@karhata
like this?"2019-12-10 07:50:14,947 INFO fr.acinq.eclair.io.Peer n:032cc4541b25e86e39a7d450a979c1a9adbe2878df3a93fcb59c96c700bfe26aa3 - reconnecting to /181.126.128.201:9736 (next reconnection in 3600 seconds)
2019-12-10 07:50:14,947 INFO f.acinq.eclair.io.Client n:032cc4541b25e86e39a7d450a979c1a9adbe2878df3a93fcb59c96c700bfe26aa3 - connecting to 181.126.128.201:9736
2019-12-10 07:50:19,457 INFO f.acinq.eclair.io.Client n:032cc4541b25e86e39a7d450a979c1a9adbe2878df3a93fcb59c96c700bfe26aa3 - connection failed to 181.126.128.201:9736"
The first confirmation date is not remembered exactly. It's in about a week.
STAWKEYE
@STAWKEYE
// override this with a script/exe that will be called everytime a new database backup has been created
backup-notify-script = "C:\Users....eclair\BACKUPPER.bat"
I made a batch file that copies the contents of .eclair\mainnet folder into a remote backup drive, and appends the date to the end of the folder name, so that you have historical backups. When you run the batch file directly, it works fine. Since putting the above line in the Eclair config, it never runs even on a different day, after restarting, and after creating channels. Am I misinterpreting what this is for?
STAWKEYE
@STAWKEYE
Here is the batch file is anyone wants to use it - https://pastebin.com/9JFGfcPC
But again it only works if you explicitly click on it. You could just make it a scheduled task as a fix but I was curious if there was a proper way I should be incorporating it into .config where it only creates the backup if something's actually changed.
Sergei Tikhomirov
@serg_tikhomirov_twitter
Is there a way to get the capacity of a remote channel from Eclair API? Channels only covers local channels, and AllChannels only shows the short channel ID and the two endpoints, I need more info...
Bastien Teinturier
@t-bast
@serg_tikhomirov_twitter not that I know of, we didn't have any scenario where that was needed yet. Don't hesitate to submit a PR to add that though! Otherwise we'll add that when we have some "free" time.
Bastien Teinturier
@t-bast
You can also see that directly from the network DB, that might be a simpler first step to unblock you
Sergei Tikhomirov
@serg_tikhomirov_twitter
@t-bast thanks! Working around it for now. Another question: I've set up a pair of nodes and opened channels to other random node on Bitcoin testnet. However, my nodes don't "see" each other and can't route to one another. The channels I've opened are set to be public but don't appear on 1ML. How to make my nodes see each other?
Bastien Teinturier
@t-bast
You have to wait for your node_announcements to propagate through the p2p network. It will need to reach a 1ML node before they include you on the website. How long have your channels been created?
Bastien Teinturier
@t-bast
Do you see a line in your logs saying sent announcements to ...? If it contains your node_announcement it's been sent out, it's unfortunately now other nodes' responsibility to forward them in a timely manner
Sergei Tikhomirov
@serg_tikhomirov_twitter
@t-bast I call my nodes internally M and N. M set up a channel ~3 hours ago, N did ~ 1 hour ago. I see sent announcements to in N's logs but not in M's logs. However, N is now routing to M, but not vice versa. I've also tried pushing fee updates from both M and N. Is there a way to push an update directly from M to N?
Bastien Teinturier
@t-bast
That means that M correctly pushed its node_announcement and it was successfully forwarded to N. Since N had sent his node_announcement before M joined the network, M needs to sync gossip that it has missed. This all depends on who your peer is (hopefully not an old software version) but if you disconnect/reconnect M to its peer they should re-sync missed gossip (and hopefully M's peer has N's node_announcement to forward).
It is a bit painful for new nodes to broadcast their existence to the network because we've aggressively tried to reduce redundant gossip (maybe too aggressively in some cases). There have been a few bugs in older versions of all implementations related to gossip, sync and rebroadcast so if you're unlucky with your peer (especially if you only have one) it may take time to receive accurate gossip.
Sergei Tikhomirov
@serg_tikhomirov_twitter
@t-bast thanks! Seems that my node received the announcement after all, I just didn't expect it to take hours :) Another question: is there a way to specify the exact channels my payment would go through? I'm trying out sendtoroute, but I don't see a way to choose the route in case some intermediate nodes have multiple channels between them.
araspitzu
@araspitzu
@serg_tikhomirov_twitter good point, the sendtoroute could use short_channel_id however there is no guarantee the forwarding node will use the channel you indicated in the packet construction, it's called non-strict forwarding.
currently the logic in sendtoroute is to pick the largest channel between the given nodes in the arguments passed
Sergei Tikhomirov
@serg_tikhomirov_twitter
@araspitzu "the logic is to pick the largest channel" - is this decision made by my (sending) node or by the forwarding node?
araspitzu
@araspitzu
by the sending node because it has to pick a short_channel_id when constructing the onion packed :) but if the forwarding node has mode than one channel with the next hop it can ignore that and choose its own
Beatrice⚡️sometimes gives away sats
@hellofrombea_twitter
Hey guys! I'd like to include Acinq/Eclair in RADAR's 2019 State of the Lightning Network report coming out next week, who's the best person to chat with?
Sergei Tikhomirov
@serg_tikhomirov_twitter
Yet another question: my testnet nodes had 2 channels each. In my experiments, I want payments to be routed via specific channels. I decided to close the unneeded channels, now at each of my nodes one channel is NORMAL and one is CLOSING. However, findroutetonode returns a route using channels in the CLOSING state. Is this normal behavior?
VPS-DATA
@vpsdata_twitter
hi all. i’m trying Eclair with Docker on a Synology… my Eclair runs fine and talk to my bitcoind but peers are empty after hours. Don’t know why. Any idea ? my network works fine, bitcoind is synced
Bastien Teinturier
@t-bast
However, findroutetonode returns a route using channels in the CLOSING state. Is this normal behavior?
Yes right now the path-finding algorithm doesn't look at channel states, only at nodes from the graph's point of view
We have big updates to the path-finding algorithms planned that will fix this
This isn't an issue in practice because the channel state will be noticed after the route is built, and the actual payment mechanism will use the "right" channel
@vpsdata_twitter did you open a channel to someone? Or did someone open one to you? You need to have a channel to maintain peer connections and receive the network gossip
Sergei Tikhomirov
@serg_tikhomirov_twitter

I'm experimenting with regtest nodes and try to interact with them using this Python wrapper . I'm having problems with the sendtoroute command. In CLI, it behaves as expected (the payment fails because I provide an incorrect hash). If I call it with the same parameters from a Python script, the payment is stuck in pending state. The logs of the sending node say: ERROR f.a.e.SimpleSupervisor - supervisor caught error for child=router strategy=Resume scala.MatchError: List(03678a7f6c32166efabdb31353f1f64f68b6b1c7424978ac80461e7bcd44f95e1c) (of class scala.collection.immutable.$colon$colon). The payment doesn't reach the receiving node at all. What can be the problem here?

CLI command:

eclair-cli-m sendtoroute --amountMsat=1000 --route=03678a7f6c32166efabdb31353f1f64f68b6b1c7424978ac80461e7bcd44f95e1c,03b66cddd29beb92f9fbdce91924cde26904ba7f5c44ddf73c4d3e0379541b3987,02972230da364450cb963878ba60d86a9f8b51917608ea912499f425297b04bac9,037cbbde36bbe5f49b529734502a25843c1d3ab72e77add425059e0b44d2580ad0 --paymentHash=1111111111111111111111111111111111111111111111111111111111111111 --finalCltvExpiry=9

Python code:

M = EclairClient(host=SENDER_HOST, port=SENDER_PORT, password=SENDER_PASSWORD)
N = EclairClient(host=RECEIVER_HOST, port=RECEIVER_PORT, password=RECEIVER_PASSWORD)
route = M.findroutetonode(nodeId=N.getinfo()['nodeId'], amountMsat=1000)
payment_id = M.sendtoroute(
        route=route,
        amountMsat=int(1000),
        # 32 arbitrary bytes
        paymentHash=1111111111111111111111111111111111111111111111111111111111111111,
        finalCltvExpiry=9
        )
Sergei Tikhomirov
@serg_tikhomirov_twitter
Based on the getsentinfo output, it seems that the Python code is trying to route the payment to the sending node...
[{'id': '0faad19f-8927-4e34-8028-d1ee53267856', 'parentId': '0faad19f-8927-4e34-8028-d1ee53267856', 'paymentHash': '1111111111111111111111111111111111111111111111111111111111111111', 'amount': 1000, 'targetNodeId': '03678a7f6c32166efabdb31353f1f64f68b6b1c7424978ac80461e7bcd44f95e1c', 'createdAt': 1576496455812, 'status': {'type': 'pending'}}]
trigger67
@trigger67
Hi, I configured a bitcoin node, and an eclair node this week-end on a server.
I created a channel this morning and saw that my alias is not displayed on explorers. Also my ip adresse and other info are not available.
I then saw that there was a mistake on the eclair.conf file with the eclait.server.public-ips line.
So I fixed the mistake, and restarted the node.
But still on explorers (acinq and 1ml) nothing changed. How can I check if everything is well configured / my node is reachable ?
Pierre-Marie Padiou
@pm47
@trigger67 what's your node id ?
trigger67
@trigger67
@pm47 039d97ac9e82a77e1c191cf72e813f108ef9a57f3b602f4e673ac4b63727759e52