-
Notifications
You must be signed in to change notification settings - Fork 505
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Support for Testnet #771
Comments
Hi at @lzhuor thank you so much for using the wallet and contributing an issue! The v4 wallet does not yet support testnet, we've looked into it a little bit but have not had sufficient time to fully implement it. I believe the crux of the issue is here: https://github.com/blockchain/blockchain-wallet-v4-frontend/blame/development/packages/blockchain-wallet-v4/src/types/Wrapper.js#L157. Where the wallet is created but the network is not passed in. We have some more work to do around network configurations, but this is definitely on the todo list! In the meantime, if its a testnet wallet you need you can use https://testnet.blockchain.info/wallet/#/login. Actually, you may be able to create a testnet wallet there and then use it with the v4 config you have, since it may just be the creation of the wallet that is incorrect. Best |
Thank you @plondon! The workaround works for me. I will take a look at the code snippet to understand the root cause. Btw, this react + redux (and saga) front-end project is awesome. I learned quite a few good points such as using monorepo, using ramda, using lense etc. Lesson learned. |
Hi folks, I tried to fix the above problem in #803. After the fix, in debug mode, I can see The error was thrown from const fetchKVStore = kv => {
let setKvFromResponse = curry((currentKv, res) => {
if (res === null) return set(KV.value, null, currentKv)
let setFromResponse = compose(
set(KV.magicHash, prop('compute_new_magic_hash', res)),
set(KV.value, KV.extractResponse(kv.encKeyBuffer, res))
)
return setFromResponse(currentKv)
})
return request('GET', kv.address)
.map(KV.verifyResponse(kv.address))
.chain(eitherToTask)
.map(setKvFromResponse(kv))
.rejectedMap(e => {
console.error(
`Failed to fetch metadata entry ${kv.typeId} at ${kv.address}:`,
e
)
return new Error('METADATA_FETCH_FAILED')
})
} Do you have an idea about the cause? Thank you for your time! 鉂わ笍 |
@lzhuor first of all, thank you so so much for your contribution. I or someone on the team will surely find time this week to make a more comprehensive review. For now to ensure you're not stuck I noticed that https://api-testnet.blockchain.info/metadata/**1CH6gsibWwGqTTZYZ6cEuMKMTwJL1Wvfsq** is not a testnet address. metadata will check this and fail because of that most likely. |
Compare the response to |
Thank you @plondon ! I will continue from above hint. |
Bitcoin testnet wallet available here: #874 |
馃悰 Bug Report 馃悰
Description
Hi team, I'm trying to connect to testnet from localhost:8080. However, I am getting below error during login:
The
development.js
config is :Could you please advise what can I do to connect to testnet via local environment? Do you mind providing a guide on how could developers start using testnet for development in local?
Thank you and greatly appreciate it!
Expected Behavior
I should be able to login
Reproduction Steps
yarn start:dev
with abovedevelopment.js
Screenshots/Logs
Additional Information
NIL
The text was updated successfully, but these errors were encountered: