Skip to content

Issues: paritytech/parity-bitcoin

New issue

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

Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort

Issues list

Too many open files issue
#587 opened Aug 28, 2020 by alun
Build failure
#585 opened Aug 22, 2020 by zenkuro
Is sendrawtransaction JSON-RPC work?
#583 opened Jul 23, 2020 by zeroFruit
Run as a thin client?
#571 opened Dec 19, 2019 by taylorjdawson
Publish to crates io?
#570 opened Nov 5, 2019 by ndelvalle
Bitcoin SV compliance F8-enhancement An additional feature request. P9-somedaymaybe Issue might be worth doing eventually.
#552 opened Apr 11, 2019 by gWOLF3
Hardfork/upgrade trigger F3-annoyance The client behaves within expectations, however this “expected behaviour” itself is at issue. P5-sometimesoon Issue is worth doing soon.
#527 opened Oct 16, 2018 by svyatonik
Too many features have not been done M4-core Core client code / Rust. Z1-question Issue is a question. Closer should answer.
#522 opened Oct 4, 2018 by gguoss 0.9
Support Bitcoin Cash Nov 2018 HF F0-consensus Issue can lead to a consensus failure. M4-core Core client code / Rust.
#519 opened Aug 21, 2018 by svyatonik
5 of 6 tasks
Update outdated dependencies F3-annoyance The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core Core client code / Rust.
#482 opened Feb 9, 2018 by korczis 0.9
Merge Network and ConsensusParams F6-refactor Code needs refactoring. M4-core Core client code / Rust.
#478 opened Jan 9, 2018 by debris 0.9
Support pruning of transactions F8-enhancement An additional feature request. M4-core Core client code / Rust. P7-nicetohave Issue is worth doing eventually.
#472 opened Nov 13, 2017 by folsen 1.0
Support Bitcoin Gold / Bitcoin Platinum F8-enhancement An additional feature request. M4-core Core client code / Rust. P9-somedaymaybe Issue might be worth doing eventually.
#471 opened Nov 11, 2017 by ghost 1.1 & ...
Implement XThin F8-enhancement An additional feature request. M4-core Core client code / Rust.
#470 opened Nov 10, 2017 by lvella
Wallet functionality F8-enhancement An additional feature request. Q7-involved Can be fixed by a team of developers and probably takes some time.
#456 opened Sep 28, 2017 by jasondavies
Feature overview for Coin.Dance M3-docs Documentation. Z1-question Issue is a question. Closer should answer.
#455 opened Sep 12, 2017 by 5chdn
2 of 38 tasks
The sync verification thread paniced. F1-panic The client panics and exits without proper error handling. M4-core Core client code / Rust.
#446 opened Aug 24, 2017 by 5chdn
Proper fix for verification::Deployments panic F6-refactor Code needs refactoring. M4-core Core client code / Rust.
#443 opened Aug 22, 2017 by svyatonik
Additional support for libbitcoin-consensus at compile-time. F8-enhancement An additional feature request. M4-core Core client code / Rust. P9-somedaymaybe Issue might be worth doing eventually.
#404 opened Apr 27, 2017 by TheBlueMatt
Move seednode logic from AddrProtocol to SeednodeProtocol F6-refactor Code needs refactoring. M4-core Core client code / Rust.
#398 opened Apr 14, 2017 by svyatonik
pre-index transaction outputs F8-enhancement An additional feature request. M4-core Core client code / Rust.
#389 opened Apr 5, 2017 by debris
Verification of in-block transaction with many inputs takes too long F3-annoyance The client behaves within expectations, however this “expected behaviour” itself is at issue. F7-footprint An enhancement to provide a smaller (system load, memory, network or disk) footprint. M4-core Core client code / Rust.
#356 opened Dec 27, 2016 by svyatonik
chainwork should be fixed 64-digit U256 value in JSON RPC F3-annoyance The client behaves within expectations, however this “expected behaviour” itself is at issue. M6-rpcapi RPC API.
#355 opened Dec 26, 2016 by NikVolf 0.9
ProTip! Add no:assignee to see everything that’s not assigned.