You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2024. It is now read-only.
Counterblock is slowly slipping into obsolescence tbqh. I don't know if this call is used by counterwallet, but it would probably be better if any new wallets developed for the project try to rely as little as possible on counterblock in the future.
@jdogresorg I see. I'll create PR to remove get_insight_block_info() soon.
@chiguireitor I agree that Clounterblock (and Counterwallet) should be going to be obsolete.
And at least just now, it's required to follow up with current code by current users, IMO.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
counterblock/counterblock/lib/processor/api.py
Lines 58 to 61 in a564eeb
I couldn't
blockchain.getBlockInfo()
in the develop branch. Should we remove this API or fix to work again?Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: