by

Where communities thrive


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

    t-bast on anchor-output-force-close

    (compare)

  • 13:30

    t-bast on master

    Anchor output: handle unilatera… (compare)

  • 13:03

    t-bast on channel-ws-events

    Add some channel events to webs… (compare)

  • 10:10

    t-bast on channel-version-tlv

    fixup! [OpenChannel] Use TLV fo… (compare)

  • 08:45

    t-bast on split-integration-spec

    Refactor some integration tests… (compare)

  • Sep 21 16:29

    t-bast on split-integration-spec

    Split IntegrationSpec in two T… (compare)

  • Sep 21 15:12

    t-bast on split-integration-spec

    WIP (compare)

  • Sep 21 12:55

    t-bast on route-not-found-db

    Add DB entry for payment router… (compare)

  • Sep 21 12:34

    t-bast on anchor-output-force-close

    Rename transaction types (compare)

  • Sep 21 09:39

    t-bast on channel-version-tlv

    [OpenChannel] Use TLV for chann… (compare)

  • Sep 21 08:50

    dpad85 on android-phoenix

    Fix issue with Phoenix reestabl… Release v0.3.11-android-phoenix Merge branch 'hotfix/v0.3.11-an… (compare)

  • Sep 21 08:19

    pm47 on watcher-logs

    (compare)

  • Sep 21 08:19

    pm47 on master

    Minor improvements to the watch… (compare)

  • Sep 18 13:39

    pm47 on unhandled-cmd

    update tests (compare)

  • Sep 18 13:27

    pm47 on scala-2.3.3

    (compare)

  • Sep 18 13:27

    pm47 on master

    Update to scala 2.13.3 and akka… (compare)

  • Sep 18 12:52

    pm47 on scala-2.3.3

    added missing dependency Need … (compare)

  • Sep 18 10:12

    pm47 on watcher-logs

    fixup: typo Co-authored-by: Ba… (compare)

  • Sep 18 10:04

    pm47 on unhandled-cmd

    handle the `NoReplyTo` also in … (compare)

  • Sep 18 09:44

    pm47 on scala-2.3.3

    update scala and akka libraries (compare)

fiatjaf
@fiatjaf
what does localParams and remoteParams mean? localParams references my node's current view of state or the other node's view I received from them?
Bastien Teinturier
@t-bast
IIRC localParams are the parameters your node sets (which contains constraints for the other node, such as the to_self_delay)
fiatjaf
@fiatjaf
right, thank you!
ShahanaFarooqui
@ShahanaFarooqui
@t-bast Requesting for a new field in list invoices. ACINQ/eclair#1511
fiatjaf
@fiatjaf
isn't there a way to list all sent payments?
only using audit? is there a recommendation against using audit for that purpose?
fiatjaf
@fiatjaf
I don't know if this is a bug, but I sent a payment from the API, got an id for that payment. tried to query it with getsentinfo but that returned an empty list. the logs showed the payment had failed to find routes. it's not possible to know what happens in these cases from the API? perhaps by listening on the webhook endpoint?
Bastien Teinturier
@t-bast

isn't there a way to list all sent payments?

Right, there's only the audit API for now. It could make sense to have a dedicated API (listsent), that could optionally filter by nodeId

I don't know if this is a bug, but I sent a payment from the API, got an id for that payment. tried to query it with getsentinfo but that returned an empty list. the logs showed the payment had failed to find routes.

There are some edge cases where what you describe can happen, but it's only when no HTLC has been sent (which happens when we immediately can't find a route).
This is for technical reasons because of how we interact with the DB for outgoing payments, but I agree it's a tricky (bad?) UX.
I'll create an issue to get that fixed.

Bastien Teinturier
@t-bast
fiatjaf
@fiatjaf
thank you!
but maybe you don't have to change your API and store unnecessary payment attempts if they were never made
I was very confused, but confusion can be fixed by documentation, maybe
I don't know
ChuckNorrison
@ChuckNorrison
Hey, in the lightning explorer, the node IP is not updated.
My node is running a DynDNS and LetsEncrypt Setup. Where does the acinq explorer reads the public ip from? The RTL is already showing the new IP after seconds
ChuckNorrison
@ChuckNorrison
hi
Pierre-Marie Padiou
@pm47
@ChuckNorrison Hi, I'm not even sure updating the ip is implemented, need to look into it
viaj3ro
@viaj3ro
I'm trying to get hold of the node operator of this node: 03baa70886d9200af0ffbd3f9e18d96008331c858456b16e3a9b41e735c6208fef (LIGHTNING)
if anyone is able to forward my telegram or email, please send me a private message
ChuckNorrison
@ChuckNorrison
@pm47 thank you, i would love to see a DNS over IP implementation but iam working on a VPN gateway to get a safe route without TOR
what is your experience with TOR in performance and ease of use with lnbits for daus?
is eclair supporting TOR yet?
btw. eclair is the best lightning node wallet, love it
iam hosting my lightning node with the RaspiBlitz 1.6 and iam very happy but i dont have the luck of a static IP where my pi lives
ChuckNorrison
@ChuckNorrison
i setup a static IP, can you update my node in your explorer?
check out LukeLightningWalker, feel free to open some channels :)
ChuckNorrison
@ChuckNorrison
@pm47 can you help here? :)
PaladinBF
@PaladinBF
Hello. why the error occurs: 2020-08-23 20:13:37,199 ERROR fr.acinq.eclair.Setup - bicoind did not respond after 30 seconds
PaladinBF
@PaladinBF
and erorr: 2020-08-23 20:21:39,822 ERROR f.a.e.gui.FxPreloader - fr.acinq.eclair.blockchain.bitcoind.rpc.JsonRPCError: No such mempool transaction. Blockchain transactions are still in the process of being indexed. Use gettransaction for wallet transactions. (code: -5)
bitcoin core v0.20
fesade
@fesade
hi, there how much time do i need .bat start , waiting command prompt like 5 minutes
Bastien Teinturier
@t-bast
@PaladinBF as the error message indicates, your bitcoin node is still indexing the blockchain so it's not available yet. You need to wait until your bitcoin node has finished indexing before you can connect a lightning node to it.
@fesade you must only run it once. By default it won't print anything to the console, you must find your eclair.log file to see what's happening to your node.
Or if you want your node to print directly to the console, see https://github.com/ACINQ/eclair/wiki/Logging
ILJA TKACHUK
@IljaTkachuk_twitter
Hello! Is there easy way to add one more required signature into funding transaction? The case where A and B have a payment channel, but they can create new state only if C agrees with it? And there is no plan for some "plugin" system to modify commitment TX format and state upgrade procedure? Might be useful thing in some cases
Bastien Teinturier
@t-bast
@IljaTkachuk_twitter modifying the commit tx structure is a lot more involved than you'd think; just look at how long it took to get anchor outputs merged (lightningnetwork/lightning-rfc#688). I don't think it will ever be possible to do via just a plugin, this is the kind of change that needs very precise tweaks to guarantee security so it really needs to be in the core codebase
However for the usecase you mention (adding a third partner, C) you don't need any change to the commit tx structure
What you need is a multisignature scheme where the two participants of your channel would be (A + C) and (B + C)
Once Bitcoin supports Schnorr signatures, there's MuSig that would enable this; meanwhile you can do stuff with ECDSA, but it's more involved and less efficient (and there are no good libraries that I can recommend to do it)
ILJA TKACHUK
@IljaTkachuk_twitter
Cool suggestion, @t-bast thanks for reply! Anyway, if we even have Schnorr signatures (I guess, it will not happen soon, can take a lot of time similar to segwit adoption, probably even more) - still this multisig makes creation of new state more interactive and A and B need to communicate with C to create new states (this is basically what I want). Is there any possibility to squeeze this additional interactivity to Eclair through plugin system? It sounds like pretty complex change
Bastien Teinturier
@t-bast
I think it would be doable. We are currently doing some work on the signature interface to make it asynchronous, which is a first step towards enabling what you suggest. Once that's done, a plugin could replace the signature component by one that makes a request to C to get his part of the signature. We would "simply" need to add a plugin hook inside the signature methods to allow plugins to add pre/post signing steps, so I don't think it would be impossible :)
ILJA TKACHUK
@IljaTkachuk_twitter
Very inspiring thread, Bastien! There are real-world applications for this, in some use cases (mostly custodial of course) we do need channel balances audit/observability. But of course Schnorr/Taproot/Eltoo proposals have much wider scope, I wish they will be adopted at some point!
Michael Weber
@MichiFreebird_twitter

I am now running the install script https://github.com/ACINQ/eclair/releases/tag/v0.4.1 on my remote microsoft server 2008 for about 20 min. Does it take so long or do i have something confirgured wrong?

Config:

eclair.chain=mainnet
eclair.node-alias=ohyeah
eclair.bitcoind.rpcport=8332
eclair.bitcoind.rpcuser=username
eclair.bitcoind.rpcpassword=password
eclair.bitcoind.zmq="tcp://127.0.0.1:29000"
eclair.node-color="ffffff"

LOG:
2020-09-21 07:37:34,155 INFO o.b.Secp256k1Context - secp256k1 library successfully loaded
2020-09-21 07:37:34,348 INFO fr.acinq.eclair.Plugin$ - loading 0 plugins
2020-09-21 07:37:34,716 INFO a.e.slf4j.Slf4jLogger - Slf4jLogger started
2020-09-21 07:37:35,093 INFO fr.acinq.eclair.Setup - hello!
2020-09-21 07:37:35,096 INFO fr.acinq.eclair.Setup - version=0.4.1 commit=e5fb281
2020-09-21 07:37:35,098 INFO fr.acinq.eclair.Setup - datadir=C:\Users\xxxxxxxxxxx.eclair
2020-09-21 07:37:35,098 INFO fr.acinq.eclair.Setup - initializing secure random generator
2020-09-21 07:37:35,141 INFO fr.acinq.eclair.Setup - instanceid=32858d22-c1b2-430d-84b1-a98a4eeba5d3
2020-09-21 07:37:35,261 INFO f.a.eclair.db.Databases$ - successful lock on eclair.sqlite
2020-09-21 07:37:35,778 INFO fr.acinq.eclair.Setup - nodeid=03698f45ce29cb8c0ff31863c1a606e17311815c7cd0717b7aca22b01c86b78d78 alias=ohyeah
2020-09-21 07:37:35,781 INFO fr.acinq.eclair.Setup - using chain=mainnet chainHash=6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000
2020-09-21 07:37:36,531 INFO fr.acinq.eclair.Setup - current feeratesPerKB=FeeratesPerKB(21090,21090,3000,3000,3000,3000,1012) feeratesPerKw=FeeratesPerKw(5272,5272,750,750,750,750,253)
2020-09-21 07:37:36,578 INFO f.a.eclair.router.Router - loading network announcements from db...
2020-09-21 07:37:36,583 INFO f.a.eclair.router.Router - loaded from db: channels=0 nodes=0
2020-09-21 07:37:36,618 INFO f.a.eclair.router.Router - computing network stats...
2020-09-21 07:37:36,618 INFO f.a.eclair.router.Router - initialization completed, ready to process messages
2020-09-21 07:37:36,681 INFO f.a.e.b.b.zmq.ZMQActor - connected to tcp://127.0.0.1:29000
2020-09-21 07:37:36,683 INFO f.a.e.b.b.zmq.ZMQActor - connected to tcp://127.0.0.1:29000
2020-09-21 07:37:36,691 INFO f.a.e.p.r.PostRestartHtlcCleaner - htlcsIn=0 notRelayed=0 relayedOut=0
2020-09-21 07:37:36,691 INFO f.a.e.p.r.PostRestartHtlcCleaner - notRelayed=Queue()
2020-09-21 07:37:36,693 INFO f.a.e.p.r.PostRestartHtlcCleaner - relayedOut=Map()

2020-09-21 07:37:36,718 INFO fr.acinq.eclair.Setup - initial wallet address=3LjkZ1ApZpfnWNnPoQuboUirgPbxyvro4s
2020-09-21 07:37:36,751 INFO f.acinq.eclair.io.Server CON - bound on /0:0:0:0:0:0:0:0:9735
2020-09-21 07:37:36,751 INFO fr.acinq.eclair.Boot$ - json API disabled
2020-09-21 07:47:36,530 INFO fr.acinq.eclair.Setup - current feeratesPerKB=FeeratesPerKB(21090,21090,3000,3000,3000,3000,1012) feeratesPerKw=FeeratesPerKw(5272,5272,750,750,750,750,253)
2020-09-21 07:47:36,537 INFO akka.actor.LocalActorRef - Message [fr.acinq.eclair.blockchain.CurrentFeerates] to Actor[akka://eclair-node/user/$c/watcher#-315690274] was unhandled. [1] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.

Bastien Teinturier
@t-bast
@MichiFreebird_twitter what's the issue? It looks like your node is running fine, isn't it?
Michael Weber
@MichiFreebird_twitter

@t-bast I cant find any GUI Interface at all.

The cmd.exe is still running and very 10 minutes I get the same error log. There is a GUI Interface right? Or do I have to download that seperately?

2020-09-21 07:57:36,539 INFO fr.acinq.eclair.Setup - current feeratesPerKB=FeeratesPerKB(23069,23069,3000,3000,3000,3000,1012) feeratesPerKw=FeeratesPerKw(5767,5767,750,750,750,750,253)
2020-09-21 07:57:36,539 INFO akka.actor.LocalActorRef - Message [fr.acinq.eclair.blockchain.CurrentFeerates] to Actor[akka://eclair-node/user/$c/watcher#-315690274] was unhandled. [2] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
2020-09-21 08:07:36,558 INFO fr.acinq.eclair.Setup - current feeratesPerKB=FeeratesPerKB(24057,24057,3000,3000,3000,3000,1012) feeratesPerKw=FeeratesPerKw(6014,6014,750,750,750,750,253)
2020-09-21 08:07:36,558 INFO akka.actor.LocalActorRef - Message [fr.acinq.eclair.blockchain.CurrentFeerates] to Actor[akka://eclair-node/user/$c/watcher#-315690274] was unhandled. [3] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
2020-09-21 08:17:36,560 INFO fr.acinq.eclair.Setup - current feeratesPerKB=FeeratesPerKB(24375,24375,3000,3000,3000,3000,1045) feeratesPerKw=FeeratesPerKw(6093,6093,750,750,750,750,261)
2020-09-21 08:17:36,560 INFO akka.actor.LocalActorRef - Message [fr.acinq.eclair.blockchain.CurrentFeerates] to Actor[akka://eclair-node/user/$c/watcher#-315690274] was unhandled. [4] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
2020-09-21 08:27:36,549 INFO fr.acinq.eclair.Setup - current feeratesPerKB=FeeratesPerKB(23827,23827,3177,3000,3000,3000,1080) feeratesPerKw=FeeratesPerKw(5956,5956,794,750,750,750,270)
2020-09-21 08:27:36,549 INFO akka.actor.LocalActorRef - Message [fr.acinq.eclair.blockchain.CurrentFeerates] to Actor[akka://eclair-node/user/$c/watcher#-315690274] was unhandled. [5] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
2020-09-21 08:37:36,561 INFO fr.acinq.eclair.Setup - current feeratesPerKB=FeeratesPerKB(23826,23826,5037,3000,3000,3000,1120) feeratesPerKw=FeeratesPerKw(5956,5956,1259,750,750,750,280)
2020-09-21 08:37:36,561 INFO akka.actor.LocalActorRef - Message [fr.acinq.eclair.blockchain.CurrentFeerates] to Actor[akka://eclair-node/user/$c/watcher#-315690274] was unhandled. [6] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
2020-09-21 08:47:36,573 INFO fr.acinq.eclair.Setup - current feeratesPerKB=FeeratesPerKB(23825,23825,6896,3000,3000,3000,1160) feeratesPerKw=FeeratesPerKw(5956,5956,1724,750,750,750,290)
2020-09-21 08:47:36,573 INFO akka.actor.LocalActorRef - Message [fr.acinq.eclair.blockchain.CurrentFeerates] to Actor[akka://eclair-node/user/$c/watcher#-315690274] was unhandled. [7] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
2020-09-21 08:57:36,572 INFO fr.acinq.eclair.Setup - current feeratesPerKB=FeeratesPerKB(23604,23604,8860,3000,3000,3000,1200) feeratesPerKw=FeeratesPerKw(5901,5901,2215,750,750,750,300)
2020-09-21 08:57:36,572 INFO akka.actor.LocalActorRef - Message [fr.acinq.eclair.blockchain.CurrentFeerates] to Actor[akka://eclair-node/user/$c/watcher#-315690274] was unhandled. [8] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.

Bastien Teinturier
@t-bast
That's expected, the GUI was deprecated in v0.4 (see https://github.com/ACINQ/eclair/releases/tag/v0.4).
It's always been only meant for demo purposes and was not suited for production use.
If you want a GUI, we recommend using https://github.com/Ride-The-Lightning/RTL which can plug seamlessly to eclair and provides a lot of very nice features!
What you currently have is a node running without any GUI (but your node is running fine, the message about the unhandled event is harmless and has been fixed on master)
Michael Weber
@MichiFreebird_twitter
@t-bast Thanks Bastien for your input. Will check out the GUI you have recommended. I am totally new in this.