-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to local velas network connect metamask? #429
Comments
Hi, Sorry for delay. Maybe your browser disallow you to process http requests from extensions? Check network inspector for your metamask extension. You also can check bridge logs, for example you can start bridge with environment variable To easy check https vs http you can use ngrok to create tunnel from your server to https subdomain. |
@mikewang68 How did you get the transfer to EVM to work? I keep getting this issue:
|
set rpc: http://192.168.1.167:8545 in metamask , then velas evm-transfer |
@mikewang68 could I pay you to assist me with this I am having the same error:
Have tried everything. |
@mikewang68 did you figure out the connection issue to metamask? |
Problem
I setup a local velas network , step follow
./setup.sh
./faucet.sh
./bootstrap-validator --allow-private-address
then run:
evm-bridge ~/my-wallet/my-keypair.json http://192.168.1.167:8899 192.168.1.167:8545 57005
metamask config:
network: local
new rpc: http://192.168.1.167:8545
chainID: 57005
when i run:
velas evm transfer-to-evm 0x245656B176b487524AA5639164f2322f29131C50 1 (0x2456.... is my metamask address)
output:
Transaction signature = mhyP3fxoeezVWALs7Nd49X5a6aRCmTUwkvePiLsvENuhttu1Fs7u8KM1G4F4vR7Dg7raMiNx1oHjni5Loy9mea2
Ok
that means transcation is successful
so run:
curl --data '{"method":"eth_getBalance","params":["0x245656B176b487524AA5639164f2322f29131C50"],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST 192.168.1.167:8545
output:
{"jsonrpc":"2.0","result":"0xae56f730e6d840000","id":1}
but metamask account 0x2456.... is nothing , value is 0 .
i want to know why ? how to resolve ?
Is there something wrong between evm-bridge and metamask ?
Thank you
Proposed Solution
The text was updated successfully, but these errors were encountered: