INFO - Processing 2 certificates under work path=/etc/cert-issuer/work
INFO - Processing 2 certificates under work path=/etc/cert-issuer/work
WARNING - address mmsyB5TbdphHD2gGAfRq3osLbdSmceERYs has a balance of 0
WARNING - address mmsyB5TbdphHD2gGAfRq3osLbdSmceERYs has a balance of 0
INFO - Total cost will be 133500 satoshis
INFO - Total cost will be 133500 satoshis
ERROR - Please add 133500 satoshis to the address mmsyB5TbdphHD2gGAfRq3osLbdSmceERYs
ERROR - Please add 133500 satoshis to the address mmsyB5TbdphHD2gGAfRq3osLbdSmceERYs
Traceback (most recent call last):
File â/usr/bin/cert-issuerâ, line 11, in
load_entry_point(âcert-issuer==2.0.9â, âconsole_scriptsâ, âcert-issuerâ)()
File â/usr/lib/python3.5/site-packages/cert_issuer/main.pyâ, line 17, in cert_issuer_main
issue_certificates.main(parsed_config)
File â/usr/lib/python3.5/site-packages/cert_issuer/issue_certificates.pyâ, line 68, in main
return issue(app_config, certificate_batch_handler, transaction_handler)
File â/usr/lib/python3.5/site-packages/cert_issuer/issue_certificates.pyâ, line 35, in issue
transaction_handler.ensure_balance()
File â/usr/lib/python3.5/site-packages/cert_issuer/transaction_handler.pyâ, line 94, in ensure_balance
raise InsufficientFundsError(error_message)
cert_issuer.errors.InsufficientFundsError: Please add 133500 satoshis to the address mmsyB5TbdphHD2gGAfRq3osLbdSmceERYs
I have balance in testnet for the address : mmsyB5TbdphHD2gGAfRq3osLbdSmceERYs
But still I am getting zero balance issue.
Based on below statement I am assuming that docker will not be looking at the local node.
By default, cert-issuer does not assume you have a bitcoin/ethereum node running locally, and it uses APIs to look up and broadcast transactions. There is API support for both testnet and mainnet chains.
Iâm wondering if there is a regression with one of the endpoints we are using. I will debug into this. I should have an answer/fix by tomorrow morning (PST)
I placed below hard coded statement in
bitcoind = False
in connectors.py => get_providers_for_chain function
and the issue get resolved.
This mean that it is for sure related to configuration, btw before applying this temporary fix I tried
removing bitcoind and also tried setting bitcoind=False in configration and both of them didnt worked for me.
So, for time being I will be using this hardcoded fix.
I tried removing "bitcoind " from configuration and still it is not working. so I guess there is some problem.
I have a workaround but looks like this is an issue.
HI Hussain! And Kim!
Im getting better at this, and still crashing but against new walls. I have as you did @d.hussain, and completed my conf.ini file with bitcoind=false, but I do not understand what you mean by this
Can you elaborate a little bit further??
Thanks in advanced
Thanks for your response @d.hussain!
Im a beginer/amateur programer, so everything requires a lot of hard work. I managed to ââpublishââ on the regtest version of the cert-issuer ussing the docker version.
Im trying to do this workaround also but im having a hard time to implement. I tried to see your âconnectors.pyâ but I get an error and can not acces, is it a downloadable version?
I also tried to modify the Code, but I think I did not do it right, from the connectors.py from github lines 144 through 147:
âdef spendables_for_address(self, bitcoin_address):
for m in service_provider_methods(âspendables_for_addressâ,
get_providers_for_chain(self.bitcoin_chain, self.bitcoind)):â
what I did was replace self.bitcoind for a bitcoind=False as I understood you did but the error persists. Will you show me exactly how you did that workaround to get it to publish? For a non progamer
I will try to find a permanent solution later, once i get to issue my first certificate.
Thanks in advance for all the help
Julian