Screen shot above...Ledger account came up, I confirmed account and then sent but did not realise it was via Rinkby...but how did this account 0x9fdba...show up if it is not in my Ledger Nano S?
I was doing this as part of the set-up for Melonport @melonproject
If you look this account upon etherescan it has a balance, so why is Frame showing zero balance?
@BCAssetFund_twitter Hello! Here's what's happening, Frame uses a different derivation path (set of accounts) for testnets than it does for the mainnet. This was originally setup to help user limit the likelihood of accidentally interacting with a mainnet address without meaning to. I see it's done kind of the opposite here and I'm sorry for the confusion.
Frame is showing you the account's balance on Rinkeby, not on the Mainnet.
I'm looking into the best way for you to access this account while still on mainnet.
@BCAssetsFund_twitter I think the easiest way currently to access this account is to use https://mycrypto.com and select the Ledger option
When you get to selecting an address choose custom
and then enter m/44'/1'/0'
and be sure your connection is set to mainnet
I'm trying to get Frame working on Ubuntu, it's installed and running, and each browser I'm using (Firefox, Chromium, Brave) are all saying that Frame is connected, but it's stuck spinning on "Connected to Frame!
Waiting for account..."
Waiting for account..."
What to do?
Hi Jordan, my name is Philipp and I'm working for the EF. I'm currently doing some research about signers to be used in a project called "ethereum signed packages". The idea is to do code signing using ethereum key pairs. Guess my question is: How could frame be used as an external signer and where can I find documentation about the API / endpoints?
ws://127.0.0.1:1248 or http://127.0.0.1:1248 (More detailed documentation about integrating with Frame is on the way) Another lib I created called
eth-provider may also be helpful here: https://github.com/floating/eth-provider
so the signer should be able to sign a string containing base64Url encoded data either in Ethereum's personal message format or "pure" ECDSA
I will run some tests on the endpoint and see if I forgot something or if something is missing and let you know
Hi Jordan. I'd like to detect frame in my dapp and also suggest it as a supported desktop wallet/signer. Do you have any documentation? It looks like I can use eth-provider to manage detection. Are there any gotchas I should be aware of? I currently just check for the existence of window.ethereum or window.web3 and go from there but it looks like eth-provider can replace this
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
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'
