Open talissonbueno opened 3 years ago
Same problem here.
Me too. also getting error: function decryptWallet
requires a password when im using the correct password for a create account request method
Same problem here. It is very urgent. Could you fix it SASP?
No i could not, this is affecting my system heavily. Do you have any solutions?
Same problem here. It is very urgent. Could you fix it SASP?
Same issue here too!
Same issue too:(
Hi, I was using your program and I had no problem, but today it is show this error 1623495837825 - error: Wallet version 4 not supported. what is this?
Hello, does anyone know the solution to this problem?
I haven't found anything yet, I'm 14 days waiting for the support response. :/
I sent an email to support and they announced that I would raise this issue here but no one will respond here.
Same problem here! And funds are not showing up in the wallet on the generated receiving addresses. Common guys, this support sucks! This is not a reliable service if we depend on ... waiting... Anyone out there? Hello?
Newly created wallets using Web interface (Wallet version 4) will not be supported by blockchain-wallet-service. You should use the service itself to create new wallet.
You may want to enableHD after creating the wallet.
Then you can use all the API listed without any error.
thanks for your answer I came to the same conclusion because the wallets I made with the service were accessible. If I convert the wallet created with the service into an HD wallet, I will be able to access it through the service or I will have a problem.
On Tuesday, June 22, 2021, 8:21:33 AM GMT+4:30, donguyenthanhlan ***@***.***> wrote:
Newly created wallets using Web interface (Wallet version 4) will not be supported by blockchain-wallet-service. You should the service itself to create new wallet.
You may want to enableHD after creating the wallet.
Then you can use all the API listed without any error.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
Hello friends I emailed support and that was their response.
Newly created wallets using Web interface (Wallet version 4) will not be supported by blockchain-wallet-service. You should the service itself to create new wallet.
You may want to enableHD after creating the wallet.
Then you can use all the API listed without any error
@donguyenthanhlan Could you describe the step you enable HD? I tried enable HD via command https://github.com/blockchain/service-my-wallet-v3#enable-hd-functionality It is still show error "Wallet version 4 not supported". It means I can't enable HD
hi Unfortunately, there is still a problem with creating a wallet and sending bitcoins for about 1 hour, but then the problem occurs again. On Tuesday, June 22, 2021, 2:03:02 PM GMT+4:30, dinhbang @.***> wrote:
@donguyenthanhlan Could you describe the step you enable HD? I tried enable HD via command "https://github.com/blockchain/service-my-wallet-v3#enable-hd-functionality" It is still show error "Wallet version 4 not supported"
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
You may pass hd=true parameter on the API to create a wallet that is already HD and doesn't need to call enableHD api.
@donguyenthanhlan Could you describe the step you enable HD? I tried enable HD via command https://github.com/blockchain/service-my-wallet-v3#enable-hd-functionality It is still show error "Wallet version 4 not supported". It means I can't enable HD
This isnt a good solution because it isnt connected to the web wallet. If this is the case then we need a fix that updates this service to be compatible with wallet 4
@donguyenthanhlan I've created wallet as you said with hd=true parameter. It worked for some time, but again "Wallet version 4 not supported" appeared.
On our implementation, we no longer use the merchant API. We only need to generate address and that does not require the merchant.
@donguyenthanhlan I've created wallet as you said with hd=true parameter. It worked for some time, but again "Wallet version 4 not supported" appeared.
It is same my issue. I created with &hd=true, It return new wallet ID. But, when I use function "receivingAddress" with HD, It is still error "Wallet version 4 not supported" Who can fix this issue, please share!
Thank you so much!
It is same my issue. I created with &hd=true, It return new wallet ID. But, when I use function "receivingAddress" with HD, It is still error "Wallet version 4 not supported"
I got this error after logging into the blockchain to add security settings. I believe that the wallet can only be used in the API.
I created a new wallet and I'm using it only via API and it's working normally.
It is same my issue. I created with &hd=true, It return new wallet ID. But, when I use function "receivingAddress" with HD, It is still error "Wallet version 4 not supported"
I got this error after logging into the blockchain to add security settings. I believe that the wallet can only be used in the API.
I created a new wallet and I'm using it only via API and it's working normally.
Thank you so much! The api only create address. How can you send payment via api?
Muito obrigado! A api só cria endereço. Como você pode enviar o pagamento via API?
I'm using api-v1-client-java library and sendMany method to make payments.
See more here: https://github.com/blockchain/api-v1-client-java/blob/master/docs/wallet.md
Muito obrigado! A api só cria endereço. Como você pode enviar o pagamento via API?
I'm using api-v1-client-java library and sendMany method to make payments.
See more here: https://github.com/blockchain/api-v1-client-java/blob/master/docs/wallet.md
Thanks. But, It is still call to "http://localhost:3000/". The issue the http://localhost:3000/ is error with "Wallet version 4 not supported"
same my issue.
same here.
Basically, I'm using this flow in the API. I don't know if it's the best practice, but it's what's working for me after upgrading the wallet to v4.
Importantly, do not share your wallet data.
Request for create new wallet curl --request GET \ --url 'http://localhost:3000/api/v2/create?password=YOUR-PASSWORD&api_code=YOUR-API-CODE&label=YOUR-LABEL-OPTIONAL&hd=true'
The response is { "guid": GUID-WALLET, "address": XPUD-ADDRESS, "label": YOUR-LABEL }
Using your guid wallet create for request methods
The response is [ { "balance": 0, "label": LABEL, "index": 0, "archived": false, "extendedPublicKey": extendedPublicKey, "extendedPrivateKey": extendedPrivateKey, "receiveIndex": 0, "lastUsedReceiveIndex": null, "receiveAddress": receiveAddress } ]
For payments curl --request POST \ --url 'http://localhost:3000/merchant/GUID-WALLET/sendmany?password=YOUR-PASSWORD&recipients=RECIPIENT&from=FROM&fee=40000'
yes, but as soon as you log in to the website , your wallet will automatically migrate to v4.
yes, but as soon as you log in to the website , your wallet will automatically migrate to v4.
Yes, so I'm just using it via API. And it's working normally. Only solution so far is not to login to the website with the portfolio created through API
How i can set IP whitelist without login on the website blockchain.com. my VM wallet server run from googleserver.
- To verify your receiving address curl --request GET --url 'http://localhost:3000/merchant/GUID-WALLET/accounts?password=YOUR-PASSWORD'
Thank you for your help. But, It is error at step: `To verify your receiving address curl --request GET --url 'http://localhost:3000/merchant/GUID-WALLET/accounts?password=YOUR-PASSWORD'
`
Do you guys also have problems with segwit addresses ? bc1xxxxxx format? When I have one of these in the receipients I receive every time: 1626702454903 - error: Missing destination address Is this happening to you too ?
Muito obrigado! A api só cria endereço. Como você pode enviar o pagamento via API?
I'm using api-v1-client-java library and sendMany method to make payments.
See more here: https://github.com/blockchain/api-v1-client-java/blob/master/docs/wallet.md
Hi, the library still is available? where i can find it?
same issue , HD wallets also returns error: Wallet version 4 not supported.
once I created HD wallet I did log in into web interface, put email & whitelisted addresses. It was good maybe during 1 hr after problem repeated
On my side, as i necessarily needed API access, i created a new wallet (hd=false) with import of my private key from the old wallet. I will never access this wallet via the web (otherwise it will switch to v4).
The import of privkey not working with hd=true.
I didn't try yet the sendmany method but i hope it will work fine as before.
same here.
Do you got any solution?
Please has anyone been able to solve blockchain API issue, we are still having error with version 4
change API to TATUM.io. solve this problem,,
El dom, 26 sept 2021 a las 8:46, zenithincome @.***>) escribió:
Please has anyone been able to solve blockchain API issue, we are still having error with version 4
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/blockchain/service-my-wallet-v3/issues/513#issuecomment-927300663, or unsubscribe https://github.com/notifications/unsubscribe-auth/AILVGYW55ARFDDYHIEPXX3TUD4I2RANCNFSM46KOEBMA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Hey how do we do this?? Where can I change the API. Alot of money on the wallet version 4 and I cant access it
Please note, this API problem does not prevent you from accessing your wallet via the website.
This issue only affects those using the API, not a normal user using website access.
Using any other non-Blockchain API is at your own risk.
NEVER communicate your personal data (identifiant,password and recover phrase,etc) to people who, under the guise of helping you, will steal your bitcoins.
Stay careful!
Newly created wallets using Web interface (Wallet version 4) will not be supported by blockchain-wallet-service. You should use the service itself to create new wallet.
You may want to enableHD after creating the wallet.
Then you can use all the API listed without any error.
This fails either way since someone had the bright idea of using cloudflare. I mean why would bots use APIs?
Service v0.26.3, Node v12.18.3. After updating the wallet to version 4 I can no longer access it through the REST or RPC API.