Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Jordan Muir
    @floating
    There isn’t any official documentation yet other than the eth-provider readme that touches on some of this stuff. Frame has a ws (ws://127.0.0.1:1248) and http (http://127.0.0.1:1248) JSON-RPC endpoints that you can connect to manually using your own provider clients.
    Frame provides both ws and http for compatibility across browsers in https apps. Some browsers don’t consider connecting to localhost via websocket a secure origin (yet).
    eth-provider solves this issue by using both and falling back to http when needed. If you connect manually to these endpoints without eth-provider this compatibility is the main gotcha you’ll run into.
    Also, by default eth-provider will return the injected provider when one is available instead of trying to connect to Frame. The injected provider could be Frame's extension or another extension/browser injecting the provider.
    The most reliable way to know if it’s a Frame user is to call web3_clientVersion which will return "Frame/" and the version... currently Frame/v0.1.2
    Daniel Viau
    @DJViau
    Hey, I've got a super boring support question. Is this the best place for it?
    Jordan Muir
    @floating
    @DJViau Yep, ask away! :)
    Daniel Viau
    @DJViau
    Is the older generation of Trezor supported? After entering my pin in the Frame sidebar, the Trezor flashes past the "enter your passphrase" prompt screen. Frame hangs in the loading state and the Trezor screen shows the Trezor logo and the name I assigned it.
    I feel like the expected behavior would be Frame asking for my passphrase, but I never get the prompt
    website shows 'Connected to frame! / Waiting for account...', sidebar top left shows 'MAINNET'
    Jordan Muir
    @floating
    @DJViau You mean Trezor One devices? Yes they should be fully supported
    Screen Shot 2019-04-04 at 5.43.48 PM.png
    You should see this when plugging in the device
    Daniel Viau
    @DJViau
    roger, works smoothly through that phase
    Jordan Muir
    @floating
    Ok, then input pin and submit? Is that working?
    Screen Shot 2019-04-04 at 5.45.07 PM.png
    Daniel Viau
    @DJViau
    Screen Shot 2019-04-04 at 5.46.28 PM.png
    BTW, Trezor one is the model I own, confirmed. I input the pin, press submit, Frame transitions to the picture above, and that's the end of the line for me
    Jordan Muir
    @floating
    Oh, you're taking about using a "passphrase" as in https://wiki.trezor.io/Passphrase
    ?
    Daniel Viau
    @DJViau
    correct
    Jordan Muir
    @floating
    Ok, yes, that is likely the issue. I don't believe that is supported yet
    Daniel Viau
    @DJViau
    ok, gotcha. thanks! I'll play around and report back tomorrow. I appreciate the help :)
    Jordan Muir
    @floating
    Sorry about that! I will make a note that we should handle that case.
    Daniel Viau
    @DJViau
    @floating, disabling the Trezor passphrase got me through the impasse. thanks!
    unfortunately, I'm hung up again
    Daniel Viau
    @DJViau
    Is there an action I need to take to verify the connection between the Trezor and Frame?
    Jordan Muir
    @floating
    @DJViau The only thing I know that would cause that auto-close is... when Frame opens an account it checks the device with the current derivation path and index to make sure that the address displayed matches the address returned by the device. Which is a safety check that should basically never fail, so I'm not quite sure what's going on. I'm wondering if it's related to passphrase stuff but I haven't seen this before so I will need to try to recreate.
    No, it should just work, that's the whole point. Sorry you're hitting these issues.
    Daniel Viau
    @DJViau
    Screen Shot 2019-04-04 at 11.25.42 PM.png
    gotcha. I'll wipe and try again. console log if useful
    Jordan Muir
    @floating
    Everything looks normal there, error when no account is selected and error when an account open that hasn't giving permission to the frame website to connect (which is all new accounts)
    Daniel Viau
    @DJViau
    I've done a bunch of iterations of wiping, creating new addresses, restoring from my seed phrase, using no pin, using no passphrase, removing and reinstalling the software, still no success. I'm on the generation of macbook with four thunderbolt 3 ports, running OSX 10.14.1, connecting to the Trezor through an Amazon Basics USB C converter. I'll keep tinkering and let you know if I learn anything
    Jordan Muir
    @floating
    @DJViau Are you able to run from source? I could create a branch that adds a bunch of logs around the Trezor connect steps and see if we can uncover anything
    Daniel Viau
    @DJViau
    If it's really as easy as it looks here https://github.com/floating/frame#run-source, I should be able to. But I've got a Ledger in the mail that I'm optimistic about, so I'd say don't put a ton of effort into it if the goal is just customer service. If the goal is debugging, I'd be psyched to play a part :)
    Jordan Muir
    @floating
    Yes that's all it would take to run. I'd definitely like to know what's going on here. Before anything else lets check the error logs, I should have some in there that cover this case. You can find the logs at ~/Library/Logs/Frame/log.log
    If it's possible to email me that file jordan@frame.sh I can see if there's anything there to help us know what's going on.
    Daniel Viau
    @DJViau
    I'll email you the full file shortly, but here's a quick preview. I see a lot of [2019-04-04 23:12:01.705] [error] Error: Missing at least one required field for Message .EthereumAddress: address
    Jordan Muir
    @floating
    I have not seen this error before but it seems to be related to: trezor/trezor-wallet#377
    Jordan Muir
    @floating
    What is the firmware version of your trezor?
    Daniel Viau
    @DJViau
    1.8.0
    Jordan Muir
    @floating
    Ok, thanks so much for your help! I need some time to dig into this but it's a good start. Frame uses trezor.js and Trezor recently deprecated trezor.js with little notice or support for an upgrading. This could be a symptom of not yet making that transition off trezor.js as it looks like this issue was fixed in trezor-connect.
    Daniel Viau
    @DJViau
    I see. At least they're iterating, I suppose. I think I'll probably put the Trezor on mothballs for the weekend and pick up on Monday with Ledger, but if I can provide any more info or run a diagnosis branch, please let me know. Happy to help in any way
    Jordan Muir
    @floating
    Cool, yeah, I'll work on reproducing and start moving things over the trezor-connect. I'll let you know if I need anything else. Thanks again for all the help debugging!
    Gabi
    @0xGabi
    Hey @floating I'm having this weird behavior when using a ledger. Most of the time it recognize my device but when I start the Ethereum app on the device frame remove my ledger and is not recognized again.
    Jordan Muir
    @floating
    @0xGabi Hmm, how often is this happening?
    Chris Hobcroft
    @chrishobcroft

    Hi guys - excited to see this project progress, particularly as regards integration with Agent.

    But I have a quick question - why is it that the Ethereum address for my Trezor with Frame is different from the Ethereum address for my Trezor with MetaMask or MyCrypto?

    Gabi
    @0xGabi
    @floating most of the time. I also tried building from source and with previous versions and experienced the same behaviour. Note that I have used frame previously with the same ledger device without problem
    Luke Duncan
    @lkngtn
    Possibly related to the issue above, but I had to disable the start on login feature because it stopped detecting my ledger and was having to quit and restart frame each time I connected.