Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

testing GC with sweeptool

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
ios, rust
Domain
cli, documentation, mobile-dev, testing

Research direction

Install Gordian Cosigner on iOS 13 or later and use sweeptool-cli with a testnet account exported as a Bitcoin output descriptor. Follow the issue's create, fund, export, sweep, import, sign, and broadcast flow, noting any descriptor tail that must be appended. Document the exact steps and outcomes in a PR, including problems and any bonus scenarios tested.

Written by the indexing model from the issue text.

Description

internship

Abstract

For non-coders with some CLI knowledge. Also iOS 13 or higher needed.

We want to test if sweeptool-cli and Gordian Cosigner app are interoperable.

  • First, install Gordian Cosigner (GC) and familiarize with it (try to create/import cosigners, create an account map, a psbt etc.)
  • In Gordian Cosigner we can export an account (Bitcoin output descriptor) (*) and import it into sweeptool-cli to see if it works.
  • For example, working with GC in testnet mode, you can first try to create an account with 2 cosigners created from seed or bip39 words. Then try to send some testnet coins to that account (google for a testnet faucet). Export that account into sweeptool-cli and sweep those funds to any address of your liking. The sweeptool-cli will create a PSBT for you which you can import back into GC and sign it with your cosigners. Can the transaction actually be signed and broadcast? Show and document the steps you've taken and PR a document. Report if you run into problems.

/* the app may export a descriptor without a tail (1/* and 0/*) which should be appended manually, make notes

Bonus work: come up with more test scenarios

Dominant language
Rust
Stars
3
Forks
1
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BlockchainCommons/sweeptool-cli

All issues in BlockchainCommons/sweeptool-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.