Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Christoph
    @chrisdotn
    @joshua-mir I see, thx for the explanation. Still quite confusing at first, but I understand why it developed that way.
    Christoph
    @chrisdotn
    Have you considered making that transparent in the UI? I checked on MyCrypto and they are actively discouraging using the parity phrases. If you're generating a new account with fether it might be more consistent with other wallets to use the standard BIP39 phrases. At least it might be useful to mention that to the user. Should I file an issue for that for further discussion?
    joshua-mir
    @joshua-mir
    @chrisdotn the reason MEW/MyCrypto started disallowing the parity phrase for restoration is because people were using it like a brainwallet (manually creating wallets with a phrase they came up with)
    Currently parity started giving warnings about using it in that way
    Christoph
    @chrisdotn
    Yeah, I understand the reasoning for MyCrypto/MEW. I'm mostly concerned with fether, because it shows a "Restore wallet" option, but doesn't mention that it can only be used with accounts that have been previously generated by parity/fether. It cannot be used with accounts that have been generated by any other tool. At least I fell for that trap because I was used to think that a mnemonic passphrase is universal between different clients. With fether it isn't. So it's just something to consider from the UX side of things
    joshua-mir
    @joshua-mir
    Sorry yeah it's reasonable to put in an issue for that 😅
    Forgot I was in the fether channel
    Christoph
    @chrisdotn
    Ok, will do: paritytech/fether#202
    Andrew Gallasch
    @bemusementpark
    Hey, I just built the app on Mac OS and the it was just white until I refreshed a number of times. Do you know what the cause might be?
    joshua-mir
    @joshua-mir
    @bemusementpark that's a known issue that you might see if the background parity process isn't running or fether doesn't connect to it properly - are you using your own node or the node provided by fether?
    Andrew Gallasch
    @bemusementpark
    I just ran yarn start
    so all defaults (:
    I actually ran yarn electron and then yarn start and it went straight to the disclaimer without a white screen.
    I’m not sure if that’s just superstion, yeah, it looks like. another white screen.
    joshua-mir
    @joshua-mir
    @bemusementpark yeah, running via yarn/in dev mode will be less stable than running the app after it's built, you've probably already seen the troubleshooting line in the Readme https://github.com/paritytech/fether#run-with-live-reload-for-development
    Thibaut Sardan
    @Tbaut
    @bemusementpark Sorry I just saw that now, yarn start has this problem indeed, If you do a yarn electron you won't have the problem (but you won't have instant update from the code).
    Arkadiusz Szaleniec
    @deepinit-arek
    wohoo, we have activity again :D
    joshua-mir
    @joshua-mir
    (fether is the noisiest in terms of github activity)
    Arkadiusz Szaleniec
    @deepinit-arek
    true, will probably try to change that in near future
    it hasa lot potential imho
    Thibaut Sardan
    @Tbaut
    Launching v0.2-beta today, looking forward for feedback :) @deepinit-arek
    Arkadiusz Szaleniec
    @deepinit-arek
    @Tbaut Thank You for the info, will look into once it is released :)
    Thibaut Sardan
    @Tbaut
    it's out, break it and let us know : https://github.com/paritytech/fether/releases/tag/v0.2.0-beta
    And also let us know if you can't break it!
    Arkadiusz Szaleniec
    @deepinit-arek
    @Tbaut it segfaults :(
    i can try to trace it
    @Tbaut im on linux btw
    Thibaut Sardan
    @Tbaut
    nice! you have parity on the machine already right?
    did you try the AppImage or the archive?
    Arkadiusz Szaleniec
    @deepinit-arek
    deb & AppImage
    Thibaut Sardan
    @Tbaut
    what version of Parity?
    Arkadiusz Szaleniec
    @deepinit-arek
    2.3
    Thibaut Sardan
    @Tbaut
    I had problem yesterday with the beta
    Is this this panic paritytech/parity-ethereum#10185
    Fether installs stable 2.2.7 if you have nothing, but would take 2.3 if it's there
    Arkadiusz Szaleniec
    @deepinit-arek
    i think it would be best to bundle Parity-Ethereum with app probably
    Or maybe do some setup wizz
    as for node it runs fine
    i have both tracing / light nodes
    though not running at same time
    Thibaut Sardan
    @Tbaut
    yup bundling is planned, just not done yet but it's getting higher in the prio list!
    Arkadiusz Szaleniec
    @deepinit-arek
    Also is it decided for use of any UI frameworks? I could probably do the migration
    Thibaut Sardan
    @Tbaut
    When you say segfault, what happens exactly, any error you can copy/paste?
    Arkadiusz Szaleniec
    @deepinit-arek
    --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0xa4fa30} --- +++ killed by SIGSEGV (core dumped) +++ Segmentation fault (core dumped)
    this is relevant part of strace output i think
    when run normally its just : Segmentation fault (core dumped)
    Thibaut Sardan
    @Tbaut
    you see that in the console when launching Fether?
    Arkadiusz Szaleniec
    @deepinit-arek
    yep
    Thibaut Sardan
    @Tbaut
    what distro is that?
    Arkadiusz Szaleniec
    @deepinit-arek
    Ubuntu 18.10