Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 16 14:11

    araspitzu on pruned

    Address PR feedback Don't fail on missing bitcoind … (compare)

  • Oct 16 13:23

    araspitzu on pruned

    Enable txindex for electrum int… (compare)

  • Oct 16 12:40

    araspitzu on recovery_tool

    (compare)

  • Oct 16 12:39

    araspitzu on recovery_tool_deterministic

    Add test for triggering the rem… WIP Merge branch 'master' into reco… and 3 more (compare)

  • Oct 16 10:05

    pm47 on pruned

    made integration tests pass wit… (compare)

  • Oct 16 08:05

    araspitzu on the_holy_build

    Sphinx: accept invalid downstre… Update string to match on bitco… Payment lifecycle refactoring (… and 16 more (compare)

  • Oct 15 17:50

    dpad85 on list-payments-generic

    Payments list aggregates by par… (compare)

  • Oct 15 17:26

    sstone on release-0.3.2

    (compare)

  • Oct 15 17:26

    sstone on master

    Release 0.3.2 (#1177) Set vers… (compare)

  • Oct 15 16:11

    sstone on release-0.3.2

    Set version to 0.3.3-SNAPSHOT (compare)

  • Oct 15 16:08

    sstone on v0.3.2

    (compare)

  • Oct 15 16:08

    sstone on v0.3.2

    (compare)

  • Oct 15 16:07

    sstone on release-0.3.2

    Set version to 0.3.2 Set version to 0.3.3-SNAPSHOT (compare)

  • Oct 15 16:00

    t-bast on payment-origin-refactor

    Refactor Upstream/Origin (compare)

  • Oct 15 15:51

    sstone on v0.3.2

    (compare)

  • Oct 15 15:19

    t-bast on trampoline-routing

    Add trampoline onion support. T… Refactor: move channel relaying… WIP (NodeRelayer) (compare)

  • Oct 15 14:37

    sstone on check-config

    (compare)

  • Oct 15 14:37

    sstone on master

    Check configuration for obsolet… (compare)

  • Oct 15 14:15

    sstone on check-config

    Use an (old key -> new key) map… (compare)

  • Oct 15 13:44

    sstone on check-config

    Move configuration check inside… (compare)

afslutning
@afslutning_twitter
it may be an older wallet yes
Pierre-Marie Padiou
@pm47
as a consequence eclair mobile doesn't recognize the mutual close, and complains that an unknown transaction has spent the channel (which is what ERR_INFORMATION_LEAK is about)
so regarding the channel for which you sent the channel data: it is closed, and you got your 949214 sats back on april 24th
afslutning
@afslutning_twitter
im not sure where the funds went from there
Pierre-Marie Padiou
@pm47
Here is what happened:
1) you funded a 971027 sats channel with tx https://api.blockcypher.com/v1/btc/main/txs/336b8ecfd390d9c49f7a45315365f40054c7627141c71565447cb65a08df7088
2) you got 949214 sats back when you closed the channel with tx https://api.blockcypher.com/v1/btc/main/txs/336b8ecfd390d9c49f7a45315365f40054c7627141c71565447cb65a08df7088
3) you then opened a new channel of 1005521 sats with the remaining funds and some other funds in your wallet
actually not sure about 3)
it looks like it is a channel, but could be something else
afslutning
@afslutning_twitter
hm and i cant recover the funds in the new channel with the seed? requires state backup?
Pierre-Marie Padiou
@pm47
correct
Premek
@pvyhnal-generalbytes

Hello, would anyone be able to help us with why is our node's public IP and alias not being shown in explorers? IP is configured and people are able to use it and successfully opened channels with us.
https://1ml.com/node/03e35a27fa8bfad8675aeb9e96530e7b00e6fa03b571d235f6b4e68cfb4ef9097c

Our conf:

eclair.api.enabled=true
eclair.api.binding-ip=0.0.0.0

eclair.node-alias = "ln1.generalbytes.com"
eclair.node-color = "1f57a1"

eclair.server.port=9736
eclair.server.public-ips=["67.207.92.63"]
eclair-cli getinfo
{
  "nodeId": "03e35a27fa8bfad8675aeb9e96530e7b00e6fa03b571d235f6b4e68cfb4ef9097c",
  "alias": "ln1.generalbytes.com",
  "chainHash": "6fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d6190000000000",
  "blockHeight": 598451,
  "publicAddresses": [
    "67.207.92.63:9736"
  ]
}
araspitzu
@araspitzu
@pvyhnal-generalbytes what's the output of eclair-cli allnodes | jq '.[] | select(.nodeId == "03e35a27fa8bfad8675aeb9e96530e7b00e6fa03b571d235f6b4e68cfb4ef9097c")'
Premek
@pvyhnal-generalbytes
allnodes | jq '.[] | select(.nodeId == "03e35a27fa8bfad8675aeb9e96530e7b00e6fa03b571d235f6b4e68cfb4ef9097c")'
{
  "signature": "341158e6d655b668e4693845603937fd3ecfdb3af3b4df54b9207e5c9898a6bc3943c696b42d3f97ead7758dcd33a36766322520c7f92c7c2b1bb596d15c3911",
  "features": "",
  "timestamp": 1570188641,
  "nodeId": "03e35a27fa8bfad8675aeb9e96530e7b00e6fa03b571d235f6b4e68cfb4ef9097c",
  "rgbColor": "#1f57a1",
  "alias": "ln1.generalbytes.com",
  "addresses": [
    "67.207.92.63:9736"
  ]
}
araspitzu
@araspitzu
Your node_announcement looks good, we should investigate if the explorer received the same, if yes it's a visualization problem on their side.
Premek
@pvyhnal-generalbytes
the info is missing in all the explorers I found
we were running the node for some time without the port opened on the firewall. Also we are not using the default port. Can that cause the problem?
araspitzu
@araspitzu
Usually explorers use the node_announcement message to provide info about a node, which is correct. However sometimes they might get other gossip messages before (i.e channel_announcements if you opened a channel) in which case i suspect they try to display a node page with incomplete information (note that on 1ml you alias is your nodeId and the "color" is #000000).
I'm not sure what's the logic on their side to sync the info on the node page with the latest node_announcements
Premek
@pvyhnal-generalbytes
ok, thank you. I tried to reach them but without any response. Thanks for letting me know our node_announcement looks good
Premek
@pvyhnal-generalbytes
Actually I have the same problem on https://explorer.acinq.co/n/03e35a27fa8bfad8675aeb9e96530e7b00e6fa03b571d235f6b4e68cfb4ef9097c would anyone here know how it works at explorer.acinq.co?
araspitzu
@araspitzu
@pvyhnal-generalbytes the ultimate check is to see from another node if they received your node_announcement and looks like ACINQ did not receive it yet. The node_announcement is broadcast by eclair after it validates its first local channel (must be a public channel) and at every restart.
Bastien Teinturier
@t-bast
Thanks Chris ;)
Premek
@pvyhnal-generalbytes
oops, I restarted the node and now its showing the alias and IP in the explorers correctly (but I promise I tried to restart it before :)
thanks for your help
Rodrigo Souza
@pinhopro_twitter
good afternoon .... I am working to integrate LN on the second largest bitcoin exchange in Brazil.
friend of mine recommended eclair sever. So, I setup a server on testnet enviroment

and when I try to create a channel, the server drops the connection with the following error message:

2019-10-11 20:27:24,733 ERROR f.a.e.channel.Channel n:029a748812183bbc8483051f05252df7ba475595aa3aea85b29c40271dc0382190 c:8b0d31195dea4b2a8d63b0aad25dfef06d806e852b4fc298b8f19f870ad8e79c - local/remote feerates are too different: remoteFeeratePerKw=25000 localFeeratePerKw=750 while processing msg=OpenChannel in state=WAIT_FOR_OPEN_CHANNEL

does anyone knows what configuration I should change in order to ignore this error?
in case anyone wants to try to connect to my node on testnet, here is the address
03ac0089102dd87246030ef4a2033c8e81ee776e4b93404dd8da6db64d54735f68@lntbtcw.blinktrade.com:9735
Rodrigo Souza
@pinhopro_twitter

@Sealr0x the feerate seen by the two eclair are too different (788 vs 8160), to get over this you can increase the tolerated mismatch using the config key max-feerate-mismatch

I found the response

molxyz
@molxyz
@pinhopro_twitter I just opened a channel to your node and sent a push amount
Max
@MaxSan
Hey
I have an issues
So..
Trying to open a channel with any channel I get a specific error.
Two errors, one is Unable to publish funding transaction
Other one does not seem to be appearing anymore but it was reply ='n/a' bin=01
Do you folks have an irc room too?
Max
@MaxSan
Oh sorry this is in Eclair btw
Max
@MaxSan
on mobile ^^
molxyz
@molxyz
@MaxSan Eclair mobile reports go to page https://gitter.im/ACINQ/eclair-mobile and pls try not to use the ENTER key as punctuations :)
n1bor
@n1bor
Any date for release 0.3.2 been mentioned? Just would like the new API changes, but there are a lot of DB update so was wanting to wait till an official release...
Bastien Teinturier
@t-bast
@MaxSan can you get the logs from the application, paste them on a place like pastebin.com and share the link (privately)? With your logs we should be able to investigate (and you might have more success in the eclair-mobile room as molxyz points out).
Rodrigo Souza
@pinhopro_twitter
just in case there any python developer, I just wrrote a very simple python api client
Fabrice Drouin
@sstone
@/all Hi everyone, we've just released eclair 0.3.2, and encourage users to upgrade (it is compatible will all previous versions of eclair, please check the release notes for more details). Some configuration keys have been renamed, so if you've overridden their default values you'll need to update your config file (eclair will check for this on startup and tell you)
Pierre-Marie Padiou
@pm47
@MaxSan @t-bast this looks like an error returned by lnd
maybe try open a channel to our node first?
I was referring to the "n/a bin=01" error