Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Sep 08 19:14
    quentinlesceller closed #3657
  • Sep 08 19:14
    quentinlesceller closed #3656
  • Sep 08 14:58
    953075867 opened #3657
  • Sep 08 14:57
    953075867 opened #3656
  • Sep 07 08:12
    CRY0NE3 commented #1135
  • Aug 19 08:53
    quentinlesceller opened #3655
  • Aug 19 08:53
    quentinlesceller labeled #3655
  • Aug 19 07:06

    quentinlesceller on master

    bump to 5.2.0-alpha.1 on master… (compare)

  • Aug 19 07:06
    quentinlesceller closed #3652
  • Aug 19 06:49
    quentinlesceller synchronize #3652
  • Aug 18 13:46

    quentinlesceller on v5.1.1

    (compare)

  • Aug 18 13:45

    quentinlesceller on master

    Change connection name for CI R… (compare)

  • Aug 18 13:45
    quentinlesceller closed #3653
  • Aug 18 13:41

    quentinlesceller on v5.1.1

    (compare)

  • Aug 18 12:53
    quentinlesceller edited #3653
  • Aug 18 12:53
    quentinlesceller opened #3653
  • Aug 17 20:49
    quentinlesceller opened #3652
  • Aug 17 20:45

    quentinlesceller on v5.1.1

    (compare)

  • Aug 17 18:57

    quentinlesceller on master

    Tagging v5.1.1 release (#3651) (compare)

  • Aug 17 18:57
    quentinlesceller closed #3651
invertedcrosss
@invertedcrosss_twitter
I know this is not dev talk, but it's a continuation of the comment made by @quentinlesceller about Poloniex and their wallet being down again.
energyburn
@energyburn
@invertedcrosss_twitter Your wallet must be online listening during the withdrawal process
aleqx
@aleqx
@invertedcrosss_twitter Polo tells you the commitment (one of the very few exchanges that do so, to their credit) ... this you can then verify on grinscan.net to see whether it was actually mined. If it exists then it means it was mined (grinscan will show Maturity) which means that the problem is with your own wallet not showing it correctly somehow (e.g. you're not sync'ed or you're not running v3)
invertedcrosss
@invertedcrosss_twitter
@energyburn Thank you, I was online the whole time but it's been 24 hours for the finalization. @aleqx Thanks! I will make sure to check it out (I am running v3, been doing transactions until this one staled). Once again, thank you both for the help! :)
aleqx
@aleqx
"failed to spawn worker thread: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }" what's the most likely cause of that? this is grin-wallet 3.0.0 on a machine with 16gb ram and 32gb swap ... this is what TradeOgre experiences and says they never had a problem with the 2.0 wallet (same machine). I've been trying to persuade him to come and ask for help on gitter but ...
i said it's mostl likely too many threads running and hit the PTHREAD_THREADS_MAX limit ... i also suspected ram was gobbled at the time.
but he says the wallet keeps crashing, i.e. this is a recurring problem
aleqx
@aleqx
hmm, not much action in here for a while it seems
David Burkett
@DavidBurkett
@aleqx Most devs have switched to keybase
lever
@1971192997
hi there ,does anybody know how to set timeout of grin-wallet for rpc?
Ghost
@ghost~5e5030d4d73408ce4fda58c7
Is there a dedicated list of peers i can use? my node is falling behind
Blade Doyle
@bladedoyle
@1971192997 I dont think the timeouts are configurable. Im guessing this is the code to adjust here: https://github.com/mimblewimble/grin/blob/ef853ae469f994241574e42b6fe77ef58e4e1de2/api/src/client.rs#L183
@cyrus19901_gitlab The grin server gets a list of peers from DNS initially, then maintains its own peers list here:
~/.grin/main/chain_data/peer
It may help to delete that peer directory and restart the server.
It may also help to open your p2p port for inbound connections (3414)
Ghost
@ghost~5e5030d4d73408ce4fda58c7
thanks @bladedoyle , gonna give that a try
invertedcrosss
@invertedcrosss_twitter
When I use the listen command in the grin-wallet cli mode, it doesn't work unlike the grin-wallet -e listen command. Anyone else having this issue? Maybe worth looking into for the devs. Thanks!
patrickinchrist
@patrickinchrist
hello anyone here?
how to install gui mwc wallet?
it can not creat wallet
energyburn
@energyburn
@patrickinchrist what is MWC wallet? The official wallet does not have a GUI. Some other 3rd party wallets do, however, such as Grin++ wallet
johndavies24
@johndavies24
@invertedcrosss_twitter do you have tor installed?
Ghost
@ghost~5e5030d4d73408ce4fda58c7
Another latest encounter with the GRIN node is that , it gets stuck sometimes and tries quitting but isnt actually exiting . The only way to kill the daemon is then to do a manual KILL . Has anyone else encountered that issue ?
Blade Doyle
@bladedoyle
@cyrus19901_gitlab Yes. Lots of bugs. Its still new code, grin was written from scratch and is less than a year old. Best thing to do is to create a bug report on github. For issues with the node, file it here: https://github.com/mimblewimble/grin/issues
Unfortunately fixing bugs isnt very glamerous so does not happen much.
Antioch Peverell
@antiochp

Unfortunately fixing bugs isnt very glamerous so does not happen much.

I'd agree with the first part of that. Not so sure about the second part. We do spend a good amount of time improving things and fixing bugs.

@cyrus19901_gitlab Please file a bug as @bladedoyle suggested. There is a known issue there where the node fails to shutdown, probably a deadlock between threads which then do not shutdown cleanly. Filing a bug is probably the best way to get eyes on this.
Ghost
@ghost~5e5030d4d73408ce4fda58c7
okay thanks for the update @antiochp . Will file a bug for that
invertedcrosss
@invertedcrosss_twitter
@johndavies24 Yes, I do!
@johndavies24 If I use use the command, my wallet is listening and I've sent transactions. It just doesn't listen when I use the commands from the CLI.
johndavies24
@johndavies24
@cyrus19901_gitlab Yes, I have that issue all the time and sometimes manually killing doesnt even work
@invertedcrosss_twitter This is confusing, what commands do you use that isnt in the CLI? All of them are, including listen, so i am a tad confused. If you are using debian 9 or some older version of linux (maybe happens elsewhere as well) your tor will not be up to date and will not work properly
Ghost
@ghost~5e5030d4d73408ce4fda58c7
Regarding the Grin-server.toml config what would be an ideal value of max peer count and min peer count as by default the values are 25 and 8. Today my node forked again and stopped getting blocks, so i am thinking of increasing the default values of the above parameters to see if that is helpful . Thoughts ? @johndavies24 @antiochp
invertedcrosss
@invertedcrosss_twitter
@johndavies24 HI John, sorry this is weird to explain. I am using a newer version of Linux. Basically, when I use the command grin-wallet -e listen, I can see my port 3415 being open. That being said, then I use the wallet in CLI mode and I use the command listen, it does not open my 3415 port.
johndavies24
@johndavies24
@cyrus19901_gitlab and @invertedcrosss_twitter most of these convos should be on keybase and to Rajveer, it seems as if antioch might have solved this today so it's possible the fix is around the corner
@cyrus19901_gitlab i dont think any of those things will work, the error seems to be with how peer connections (maybe in the disconnection part) is handled. Killing the server (also filled with bugs that are being worked on) and restarting it works
@invertedcrosss_twitter tor doesnt use that port, the tor listener is all onion addresses and no ports specified. Your IP:port will not work via tor
johndavies24
@johndavies24
well no ports you need to specify or worry about
when you listen on tor, the send command is to "onion address" rather than to IP:3415
but also, the last version of debian (debian 9 stretch) cannot support the necessary version of tor, not even if you configure your app repository to use buster backports (debain 10 = buster)
Blade Doyle
@bladedoyle
The approach I took for ubuntu 18 was to download the latest version of the "tor browser" (https://www.torproject.org/download/), uncompressed and untar that, and then copied the "tor" executable out of there into /usr/local/bin/
It would be much better if grin packaged a version that works
Ghost
@ghost~5e5030d4d73408ce4fda58c7
another recent issue which i found is that a deposit get stuck with 0 confirmations sometimes even though it seems to be confirmed . Is this a known issue and if so is there a way to finalize this transaction @johndavies24
Blade Doyle
@bladedoyle
@cyrus19901_gitlab Yes, I see the issue frequently. The transaction never gets "posted" and needs to be canceled and re-created. I believe its this issue here: mimblewimble/grin-wallet#153
Blade Doyle
@bladedoyle
Nice, it looks like @jaspervdm offered to take a look!
Ghost
@ghost~5e5030d4d73408ce4fda58c7
Thanks @bladedoyle , will keep an eye for that fix. It just gets confusing with when i encounter that prob .
Antioch Peverell
@antiochp
3.1.0 is released! https://forum.grin.mw/t/grin-node-grin-wallet-v3-1-0-released/7118
This is not a mandatory release but strongly recommend people do upgrade as this release includes several stability fixes that should help with p2p and keeping the node in sync.
Muhammad Adeel Danish
@bashforger
Hi everybody. I trying to make abandoned grin project working grin-pool. Having trouble with rust dependencies.. rings any bells?
Quentin Le Sceller
@quentinlesceller
@M-Adeel-Danish might want to ask in #grin-pool gitter. Btw this software was created by @bladedoyle
Muhammad Adeel Danish
@bashforger
I have tried that. He doesn't seem to care
But I haven't gave up. I will keep poking
Quentin Le Sceller
@quentinlesceller
Good luck :)
Muhammad Adeel Danish
@bashforger
:D