We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I used the api/ColdStaking/setup-cold-staking to generate the hex for a coldstaking transaction
Here's the JSON passed into the API:
{ "coldWalletAddress": "xds????", "hotWalletAddress": "xds????", "walletName": "walletname", "walletPassword": "password", "walletAccount": "account 0", "amount": "50", "fees": "0.01", "segwitChangeAddress": true, "payToScript": true }
CURL
curl -X POST "http://localhost:48334/api/ColdStaking/setup-cold-staking" -H "accept: application/json" -H "Content-Type: application/json-patch+json" -d "{ \"coldWalletAddress\": \"xds????\", \"hotWalletAddress\": \"xds????\", \"walletName\": \"walletname\", \"walletPassword\": \"password\", \"walletAccount\": \"account 0\", \"amount\": \"50\", \"fees\": \"0.01\", \"segwitChangeAddress\": true, \"payToScript\": true}"
When I broadcast the resulting hex, I received the following error:
{ "errors": [ { "status": 400, "message": "dust", "description": "Transaction Exception" } ] }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I used the api/ColdStaking/setup-cold-staking to generate the hex for a coldstaking transaction
Here's the JSON passed into the API:
CURL
curl -X POST "http://localhost:48334/api/ColdStaking/setup-cold-staking" -H "accept: application/json" -H "Content-Type: application/json-patch+json" -d "{ \"coldWalletAddress\": \"xds????\", \"hotWalletAddress\": \"xds????\", \"walletName\": \"walletname\", \"walletPassword\": \"password\", \"walletAccount\": \"account 0\", \"amount\": \"50\", \"fees\": \"0.01\", \"segwitChangeAddress\": true, \"payToScript\": true}"
When I broadcast the resulting hex, I received the following error:
The text was updated successfully, but these errors were encountered: