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 }}
Repository navigation
"This library may go unmaintained in the near future" #192
We plan to maintain a derivative (Not a fork! Simplexum#17 (comment)) of this library: python3-only, with all bitcoin network-related code stripped from it (bitcoin/bloom.py, bitcoin/messages.py, bitcoin/net.py), so we changed the name to python-bitcointx (and module name to 'bitcointx'), to avoid conflicts.
We do all signing and verifying with libsecp256k1, support HD keys and bech32-encoded addresses.
EDIT: update about python module rename, update about libsecp256k1 signing/verifying, HD keys
EDIT: in the next versions, python-bitcointx will likely deviate more from python-bitcoinlib, will be less compatible, to better meet the goals of our project, and improve composability (see Simplexum#20)
Activity
dgpv commentedon Oct 18, 2018
We plan to maintain a derivative (Not a fork! Simplexum#17 (comment)) of this library: python3-only, with all bitcoin network-related code stripped from it (bitcoin/bloom.py, bitcoin/messages.py, bitcoin/net.py), so we changed the name to python-bitcointx (and module name to 'bitcointx'), to avoid conflicts.
https://github.com/Simplexum/python-bitcointx
We do all signing and verifying with libsecp256k1, support HD keys and bech32-encoded addresses.
EDIT: update about python module rename, update about libsecp256k1 signing/verifying, HD keys
EDIT: in the next versions, python-bitcointx will likely deviate more from python-bitcoinlib, will be less compatible, to better meet the goals of our project, and improve composability (see Simplexum#20)
dbolser commentedon Dec 11, 2018
So did this happen? Can you patch the readme?
Why not hand over the keys of this library rather than forking and moving on?
Thanks,
kanzure commentedon Jun 12, 2019
I am also interested in a status update.
petertodd commentedon Jun 22, 2019
Been busy with other (paying) stuff right now; no-one is paying me to work on this right now.
I'm dubious about just handing it over to someone else, as I think it's better that people make a conscious decision to change who they trust.
dgpv commentedon Aug 21, 2019
So the library in fact did not go 'unmaintained'. This issue can be closed now, I suppose.
petertodd commentedon Aug 21, 2019
Well, it's somewhat maintained at least. :)
dbolser commentedon Aug 21, 2019
Thanks for maintaining Peter!
petertodd commentedon Aug 21, 2019
Thanks for everyone else submitting pull-reqs - they're doing the real work. :)