{"id":18204646,"url":"https://github.com/shesek/bcash-instadump","last_synced_at":"2026-04-01T17:17:38.822Z","repository":{"id":65997552,"uuid":"99266554","full_name":"shesek/bcash-instadump","owner":"shesek","description":"CLI tools for insta-dumping bcash in exchange for bitcoins (via ShapeShift), creating bcash-compatible transactions, and more","archived":false,"fork":false,"pushed_at":"2017-12-01T23:06:26.000Z","size":598,"stargazers_count":28,"open_issues_count":0,"forks_count":16,"subscribers_count":1,"default_branch":"master","last_synced_at":"2026-03-28T01:30:16.555Z","etag":null,"topics":["bcash","bcc","bch","bitcoin","dump","hodl","instadump"],"latest_commit_sha":null,"homepage":"","language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/shesek.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2017-08-03T19:11:06.000Z","updated_at":"2020-10-15T07:44:59.000Z","dependencies_parsed_at":"2023-03-30T05:48:03.639Z","dependency_job_id":null,"html_url":"https://github.com/shesek/bcash-instadump","commit_stats":{"total_commits":96,"total_committers":1,"mean_commits":96.0,"dds":0.0,"last_synced_commit":"e73ef58416956cc9cb0d502d921bcaf9ed1cc117"},"previous_names":[],"tags_count":7,"template":false,"template_full_name":null,"purl":"pkg:github/shesek/bcash-instadump","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/shesek%2Fbcash-instadump","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/shesek%2Fbcash-instadump/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/shesek%2Fbcash-instadump/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/shesek%2Fbcash-instadump/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/shesek","download_url":"https://codeload.github.com/shesek/bcash-instadump/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/shesek%2Fbcash-instadump/sbom","scorecard":{"id":817961,"data":{"date":"2025-08-11","repo":{"name":"github.com/shesek/bcash-instadump","commit":"e73ef58416956cc9cb0d502d921bcaf9ed1cc117"},"scorecard":{"version":"v5.2.1-40-gf6ed084d","commit":"f6ed084d17c9236477efd66e5b258b9d4cc7b389"},"score":3,"checks":[{"name":"Code-Review","score":0,"reason":"Found 0/30 approved changesets -- score normalized to 0","details":null,"documentation":{"short":"Determines if the project requires human code review before pull requests (aka merge requests) are merged.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#code-review"}},{"name":"Token-Permissions","score":-1,"reason":"No tokens found","details":null,"documentation":{"short":"Determines if the project's workflows follow the principle of least privilege.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#token-permissions"}},{"name":"Packaging","score":-1,"reason":"packaging workflow not detected","details":["Warn: no GitHub/GitLab publishing workflow detected."],"documentation":{"short":"Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#packaging"}},{"name":"Binary-Artifacts","score":10,"reason":"no binaries found in the repo","details":null,"documentation":{"short":"Determines if the project has generated executable (binary) artifacts in the source repository.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#binary-artifacts"}},{"name":"SAST","score":0,"reason":"no SAST tool detected","details":["Warn: no pull requests merged into dev branch"],"documentation":{"short":"Determines if the project uses static code analysis.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#sast"}},{"name":"Maintained","score":0,"reason":"0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0","details":null,"documentation":{"short":"Determines if the project is \"actively maintained\".","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#maintained"}},{"name":"Dangerous-Workflow","score":-1,"reason":"no workflows found","details":null,"documentation":{"short":"Determines if the project's GitHub Action workflows avoid dangerous patterns.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#dangerous-workflow"}},{"name":"Pinned-Dependencies","score":-1,"reason":"no dependencies found","details":null,"documentation":{"short":"Determines if the project has declared and pinned the dependencies of its build process.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#pinned-dependencies"}},{"name":"CII-Best-Practices","score":0,"reason":"no effort to earn an OpenSSF best practices badge detected","details":null,"documentation":{"short":"Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#cii-best-practices"}},{"name":"Vulnerabilities","score":10,"reason":"0 existing vulnerabilities detected","details":null,"documentation":{"short":"Determines if the project has open, known unfixed vulnerabilities.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#vulnerabilities"}},{"name":"Fuzzing","score":0,"reason":"project is not fuzzed","details":["Warn: no fuzzer integrations found"],"documentation":{"short":"Determines if the project uses fuzzing.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#fuzzing"}},{"name":"License","score":10,"reason":"license file detected","details":["Info: project has a license file: LICENSE:0","Info: FSF or OSI recognized license: GNU General Public License v3.0: LICENSE:0"],"documentation":{"short":"Determines if the project has defined a license.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#license"}},{"name":"Signed-Releases","score":-1,"reason":"no releases found","details":null,"documentation":{"short":"Determines if the project cryptographically signs release artifacts.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#signed-releases"}},{"name":"Branch-Protection","score":0,"reason":"branch protection not enabled on development/release branches","details":["Warn: branch protection not enabled for branch 'master'"],"documentation":{"short":"Determines if the default and release branches are protected with GitHub's branch protection settings.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#branch-protection"}},{"name":"Security-Policy","score":0,"reason":"security policy file not detected","details":["Warn: no security policy file detected","Warn: no security file to analyze","Warn: no security file to analyze","Warn: no security file to analyze"],"documentation":{"short":"Determines if the project has published a security policy.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#security-policy"}}]},"last_synced_at":"2025-08-23T14:39:41.117Z","repository_id":65997552,"created_at":"2025-08-23T14:39:41.117Z","updated_at":"2025-08-23T14:39:41.117Z"},"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":31290537,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-04-01T13:12:26.723Z","status":"ssl_error","status_checked_at":"2026-04-01T13:12:25.102Z","response_time":53,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["bcash","bcc","bch","bitcoin","dump","hodl","instadump"],"created_at":"2024-11-03T11:05:02.679Z","updated_at":"2026-04-01T17:17:38.803Z","avatar_url":"https://github.com/shesek.png","language":"JavaScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# bcash-instadump\n\nCLI tools for insta-dumping bcash in exchange for bitcoins (`bcash-instadump`),\ncreating bcash-compatible transactions (`bcash-tx`),\nlisting unspent bcash outputs (`bcash-utxo`)\nand broadcasting raw bcash transactions (`bcash-broadcast`).\n\nNo bcash wallet or exchange account necessary.\n\nDeveloped by [Nadav Ivgi](https://www.bitrated.com/nadav) ([@shesek](https://twitter.com/shesek))\nof [Bitrated](https://www.bitrated.com/).\n*1HNDUy34hrqoTEChCZZjb6vWAU9APAKG78*\n\n**TL;DR**\n\n    $ bcash-instadump --tor --key LmyBcashKeyWIF --payout 1myBtcAddr\n    # confirm the details and press Y to sell your bcash and get your bitcoins\n\n(yes, that's it! but do read the whole thing to fully understand the risks involved.)\n\n**Warning! This software could put your bitcoins, bcash and privacy at risk.**\n\nThese tools are meant for technically advanced users.\nUsing them incorrectly (or even correctly!) could result in loss of funds and privacy.\nIf you don't consider yourself a technical user, please seek advice from someone who is.\n\nMake sure to read *all* the instructions *carefully* before doing anything.\nYou can use these tools in a way that doesn't risk your bitcoins,\nby moving them out first. There are also instructions for signing offline.\nSee \"*Instructions*\" below.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND. USE AT YOUR OWK RISK.\n\n## Install\n\n*Requires nodejs 6.0.0 or newer.*\n\nThe quick, less safe way:\n\n    $ npm install -g bcash-instadump\n\nThe safer way: find a Git commit reference published by a third-party security auditor that you trust, then:\n\n    $ npm install -g git://github.com/shesek/bcash-instadump#[GIT-COMMIT-SHA256-HERE]\n\nThere are currently no security audits that I'm aware of,\nbut the code is \u003c 500 SLOC if you want to review it yourself.\nIf you do, you should publicly announce the hash for the Git commit you reviewed\n(and [tell me!](https://github.com/shesek/bcash-instadump/issues/new)).\n\n## CLI tools\n\n### `bcash-instadump` - dump bcash on ShapeShift\n\n    $ bcash-instadump --key LmyBcashKeyWIF --payout 1myBtcAddr\n\nInsta-dump the bcash held in the provided `--key` (in base58 WIF)\non [ShapeShift](https://shapeshift.io/)\nand send the purchased BTC to the bitcoin address provided in `--payout`.\nShows details and asks for a confirmation before actually dumping.\n\nUsing `--key \u003ckey\u003e` will load all of the unspent outputs belonging to `\u003ckey\u003e`.\nTo add specific inputs instead, you can use `--input txid,vout,amount,key`.\nLoading unspent outputs is done using the\n[Electrum bcash servers](https://github.com/shesek/bcash-instadump/blob/master/electrum-servers.json)\n(see \"*Privacy considerations*\" below).\n\nYou can specify both `--key` and `--input` multiple times,\nor specify a file with `--keys keys.txt` and `--inputs utxos.csv`.\nAll the inputs will be joined together in a single transaction (see \"*Privacy considerations*\" below).\nOnly `p2pkh` scripts are currently supported.\n\nYou can set your bcash refund address with `--refund \u003caddress\u003e`\n(used by ShapeShift in case anything goes wrong with the exchange).\nDefaults to the address associated with the first key provided.\n\nSpecify `--feerate` to control the transaction fee (in `satoshis/byte`).\nDefaults to `rand(50,100)`.\n\nUse `--whateverjustdump` to skip all confirmations (for exchange rates, miner fees, etc) and just dump.\nThis is probably a terrible idea.\n\nShapeShift is used with a referrer code that tips the author of this tool.\nThis can be disabled with `--noreferral`.\n\nThe `--(no)proxy`, `--tor` and `--electrum` options are the same as for `bcash-tx` (below).\n\nSee `bcash-instadump --help` for the full list of options.\n\n**The author of this tool is not affiliated with ShapeShift.**\nThere are reports of orders failing with ShapeShift\ndespite the funds being sent. Reaching out to ShapeShift's\ncustomer support should usually resolve that.\n\n----\n\nScreenshot of `bcash-instadump` in action (dummy details, of course):\n\n![Screenshot](https://raw.githubusercontent.com/shesek/bcash-instadump/master/screenshot.png?z)\n\n----\n\n### `bcash-tx`- make bcash-compatible transactions\n\n    $ bcash-tx --input txid:vout:amount:key --output 1BcashAddr:ALL --feerate 250\n\nCreate and sign a bcash-compatible transaction with the provided inputs and outputs.\nThe transaction will be invalid on the Bitcoin network.\n\n`--output addr:amount` can be used multiple times.\nUse `ALL` as the `amount` to send the maximum available amount minus tx fees, or specify the amount in whole bitcoins.\n`--feerate` is only relevant if `ALL` is used.\n\nSpecify `--inspect` to print the decoded transaction instead of its raw hex representation.\n\nUse `--broadcast` to broadcast the transaction via an Electrum bcash server\n(also see `bcash-broadcast` if you already have a raw transaction ready).\n\nUse `--proxy [socks4a|socks5h]://user:pass@host:port` or `--tor` to connect to the Electrum server over a proxy,\nor `--noproxy` to connect without one (see \"*Privacy considerations*\" below).\n\nYou can configure a custom Electrum bcash server using `--electrum [tls|tcp]://host:port`.\nIf not provided, one is chosen at random (from `electrum-servers.json`).\n\nSee `bcash-tx --help` for the full list of options.\n\n----\n\n### `bcash-utxo` - list unspent bcash outputs\n\n    $ bcash-utxo 1myFirstAddr 1myOtherAddr ...\n\nGet the unspent bcash outputs for the provided address(es) from the Electrum bcash servers,\nand print them as CSV (`txid,vout,amount,address` format).\n\nYou may also provide keys instead of addresses.\nIn this case, the CSV format would be `txid,vout,amount,key`\n(same as the format expected by `bcash-instadump` and `bcash-tx`).\n\nSpecify `--file \u003cfile\u003e` to read the list of addresses/keys from `\u003cfile\u003e` (one per line) instead of from arguments.\n\nThis will leak information to the Electrum bcash servers (see \"*Privacy considerations*\" below).\n\nThe `--(no)proxy`, `--tor` and `--electrum` options are the same as for `bcash-tx`.\n\nSee `bcash-utxo --help` for the full list of options.\n\n----\n\n### `bcash-broadcast` - broadcast raw bcash transactions\n\n    $ bcash-broadcast \u003crawtx\u003e\n\nBroadcasts the provided `rawtx` (in hex) to the bcash network via an Electrum bcash server.\n\nThe `--(no)proxy`, `--tor` and `--electrum` options are the same as for `bcash-tx`.\n\nSee `bcash-broadcast --help` for the full list of options.\n\n----\n\n## Instructions \u0026 gotchas\n\n### Protect your BTC\n\n**Move your bitcoins first!** To avoid risking your BTC, keys with a BTC balance should never be exposed to this tool.\nMake sure the keys provided to this software are *entirely emptied of BTC* and hold BCH only.\n\n### Extracting unspent outputs and keys\n\n#### From Bitcoin Core:\n\n```bash\n$ bitcoin-cli listunspent | jq -c '.[] | [.txid,.vout,.amount,.address]' | tr -d '[]\"' \\\n   | awk -F, '{\"bitcoin-cli dumpprivkey \"$4 | getline key; print $1 FS $2 FS $3 FS key }' \\\n   \u003e utxos.csv\n```\n\n#### From Electrum:\n\n```bash\n$ electrum listunspent | jq -c '.[] | [.prevout_hash,.prevout_n,.value,.address]' | tr -d '[]\"' \\\n   | awk -F, '{\"electrum getprivatekeys \"$4\"|jq -r .[0]\" | getline key; print $1 FS $2 FS $3 FS key }' \\\n   \u003e utxos.csv\n\n# @TODO assumes p2pkh outputs, will break with multisig\n```\n\n#### From a list of keys:\n\nPrepare `keys.txt` with a list of base58 WIF keys (one per line), then:\n\n```bash\n$ bcash-utxo -f keys.txt \u003e utxos.csv\n```\n\nWARNING: looking up the unspent outputs associated with your addresses\nwill leak information to the Electrum bcash servers.\nSee \"*Privacy considerations*\" below for suggestions to improve privacy.\n\n#### Dumping from the UTXO CSV file\n\n```bash\n$ bcash-instadump --inputs utxos.csv --payout 1myBtcAddr\n```\n\n### Signing offline\n\nTo sign offline, you can use [browserify](http://browserify.org/) to create a portable version\nof `bcash-tx` with all of its dependencies bundled in a single `.js` file,\nand run that from the offline machine (requires nodejs \u003e=6.0.0).\n\n```bash\n# Online machine - prepare portable bundle\nsatoshi@hot:~$ npm install -g browserify\nsatoshi@hot:~$ git clone https://github.com/shesek/bcash-instadump#[COMMIT-SHA256] \u0026\u0026 cd bcash-instadump\nsatoshi@hot:~$ npm install\nsatoshi@hot:~$ browserify --bare cli/bcash-tx.js \u003e /media/usb/bcash-tx.js\n\n# Online machine - prepare list of outputs\nsatoshi@hot:~$ bcash-utxo --tor 1myFirstAddr 1myOtherAddr \u003e /media/usb/utxos.csv\n# WARNING: will leak information to the Electrum bcash servers, see \"Privacy considerations\"\n\n# Offline machine - sign bcash transaction\nsatoshi@cold:~$ edit utxos.csv # change 4th column from address to key\nsatoshi@cold:~$ node /media/usb/bcash-tx.js --inputs utxos.csv --output 1myBcashAddr:ALL --inspect\nsatoshi@cold:~$ node /media/usb/bcash-tx.js --inputs utxos.csv --output 1myBcashAddr:ALL \u003e /media/usb/signed.tx\n\n# Online machine - broadcast to the bcash network\nsatoshi@hot:~$ bcash-broadcast --tor `cat /media/usb/signed.tx`\n```\n\n### Splitting coins\n\nIf your coins are too big to be sold with one order (due to ShapeShift's limits),\nyou can split them up with `bcash-tx` and make several orders.\n\nFor example, to split a 10 BCH output into two 4.995 BCH orders\n(leaving some for mining fees),\nuse something like:\n\n```bash\n$ bcash-tx --tor --broadcast --key LmyBcashKeyWithLargeOutput \\\n    --output 1myBcashAddr1:4.995 --output 1myBcashAddr2:4.995\n# take note of the resulting \u003ctxid\u003e\n$ bcash-instadump --tor --input \u003ctxid\u003e,0,4.995,LkeyForAddr1 --payout 1myBtcAddr1\n$ bcash-instadump --tor --input \u003ctxid\u003e,1,4.995,LkeyForAddr2 --payout 1myBtcAddr2\n```\n\n### Dump specific UTXOs\n\n`bcash-instadump --key \u003ckey\u003e` will by default dump all of the\nunspent outputs available to `\u003ckey\u003e`.\nTo select specific ones, use:\n\n```bash\n$ bcash-utxo --tor LmyBcashKey \u003e utxos.csv\n$ edit utxos.csv # leave just the ones you want to dump\n$ bcash-instadump --tor --inputs utxos.csv --payout 1btcAddr\n```\n\n### Privacy considerations\n\n#### Leaking data to the public blockchain\n\nMerging your unspent outputs together (in a single multi-input transaction)\nwill reveal the link between them (and their associated addresses)\non the public bitcoin/bcash blockchains, *to the entire world*.\n\nIt is recommended to invoke `bcash-instadump` multiple times,\nonce for each unspent output being sold (creating a separate 1-in,1-out tx each time)\nand with a different `--payout` address. Ideally, this should also be spread out over time.\nThis could be accomplished using a bash script along the lines of:\n\n```bash\n$ cat utxos.csv | xargs -L 1 bash -c 'sleep $[ ( $RANDOM % 3600 ) ]s \u0026\u0026\n    bcash-instadump --input $0 --payout `bitcoin-cli getnewaddress` --whateverjustdump'\n```\n\n#### Leaking data to ShapeShift\n\nSelling all of your unspent outputs from the same IP address\nwill reveal the link between your outputs (and their associated addresses) to ShapeShift\nand to anyone gaining access to their systems (via hacking, a legal warrant, or otherwise).\n\nIt is recommended to sell one output at a time and use `--proxy` or `--tor` to connect over a proxy.\nPreferably, use a proxy with a different public IP address for each request\n(otherwise the transactions would not be linked to your real IP address, but still linked to each-other. see more on that below.)\n\n#### Leaking data to the Electrum bcash servers\n\nThe Electrum bcash servers are used for two purposes:\n*(1)* Broadcasting raw transactions to the bcash network\n(for `bcash-instadump` and `bcash-tx --broadcast`),\nand *(2)* Fetching the unspent bcash outputs associated with your addresses\n(for `bcash-utxo` and `bcash-instadump --key).\n\nThis gives the Electrum servers the ability to link your transactions/addresses/outputs\nto each-other and to your IP address.\n\nTo completely mitigate this leakage, you should ideally broadcast transactions and\nfetch unspent outputs using a bcash full node under your full control, connected over Tor.\n\nHowever, if running a full node is not possible or desirable,\nyou can also retain better privacy by using a proxy -\nwith the same caveat mentioned above regarding different public IP addresses.\nTo switch public IP addresses between address lookups,\nyou can use Tor, the [tor-newnym](https://raw.githubusercontent.com/shesek/bcash-instadump/master/utility/tor-newnym.sh)\nscript available in `utility/`, and something like:\n\n```bash\n$ cat addresses-or-keys.txt | xargs -L 1 bash -c '\n     ./tor-newnym.sh \u003ccontrol-port\u003e \u003cpassword\u003e \u0026\u0026 sleep $[ ( $RANDOM % 180) ]s \u0026\u0026\n     bcash-utxo --tor $0' \\\n  \u003e utxos.csv\n```\n\nUnder the default Tor configuration, the control port is 9151 and authentication is done using the cookie file.\nThis should work: ```./tor-newnym.sh 9151 \"`cat /path/to/tor/control_auth_cookie`\"```.\nSee the [Tor manual](https://www.torproject.org/docs/tor-manual.html.en#ControlPort) for\nmore information about control port configuration and authentication.\n\n(`tor-newnym` will hopefully soon be integrated into the tool itself. PRs welcome!)\n\nIn addition, it is also recommended that you use a random Electrum bcash server for each lookup.\nThis is the default behaviour if you don't provide a specific server via `--electrum`.\n\n## Contributing\n\nPull requests are welcome! Some interesting next steps are:\n\n- A tool to prepare the list of unspent outputs based on the HD master seed.\n\n- Creating a GUI frontend (packaged as a browser extension, an [Electron](https://electron.atom.io/) app, or something else?)\n\n- Optimize input-merging behavior to improve privacy.\n\n- Multi-signature support (currently only `p2pkh` scripts are supported)\n\n- Connect to the Tor control port to change circuits (`NEWNYM` signal) between\n  address lookups in `bcash-utxo`.\n\n- Tests (there aren't any! :scream::scream:)\n\n- Have any other cool ideas? [Let me know!](https://github.com/shesek/bcash-instadump/issues/new)\n\n## License\n\nThis software is released under the GPL v3 license.\nSee LICENSE for more details.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fshesek%2Fbcash-instadump","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fshesek%2Fbcash-instadump","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fshesek%2Fbcash-instadump/lists"}