Three roles to keep separate
CoinHearted’s intended role is to help a group follow an agreement and contribution record. The wallet is where a member would review and approve a payment. The Bitcoin network is separate from the coordination interface. The current landing page does not connect a wallet or run that planned payment flow.
This distinction matters because “bring your own wallet” can otherwise sound like every provider works the same way. The provider icons on the landing page are links for exploration, not confirmed integrations or a claim of universal compatibility.
The circle
Agrees on contributions, timing and receiving order.
The wallet
Provides the member’s payment and custody experience.
CoinHearted
Plans to coordinate the agreement and its shared record.
An address and a private key do different jobs
A receiving address identifies a payment destination. Private keys are used to authorize spending. Knowing an address is not the same as possessing the ability to spend from the associated funds. Wallet software manages these functions for its user. Bitcoin developer guide: wallets ↗
CoinHearted will never ask for your seed phrase or private keys. Its planned coordination role does not require taking possession of them. Any future address-control check would need its own clear explanation and implementation; there is no such onboarding flow on this site today.
Who holds the keys?
With self-custody, the user controls the private keys and takes responsibility for protecting them. With a custodial service, a third party controls the keys and the user relies on that provider for access to funds. Those are different trust and recovery arrangements. Bitcoin.org: key control and custodians ↗
CoinHearted’s intended non-custodial role does not turn a custodial provider into a self-custody wallet. When exploring a provider, ask who holds the keys, what approvals are required and how its recovery process works. Check the provider’s current documentation; a familiar logo is not an answer to those questions.
Recovery belongs in the conversation
Wallet backups need to match the wallet’s design. A recovery phrase or other backup may be essential to restoring access, and protecting it is a separate task from keeping a payment schedule. Bitcoin.org explains why complete backups and secure storage matter. Read its wallet-security guidance ↗
A shared contribution record is not a backup of spending keys. CoinHearted cannot recover a lost seed phrase or restore access merely because an address or past contribution appears in a record. No recovery feature is being offered by the current site.
Approval should be explicit
In the planned circle flow, a reminder would help a member prepare. It would not authorize a payment for them. Before approving a real payment, the member would need to review the destination, amount and any fee shown by their wallet.
Bitcoin has no central authority that can simply undo a mistaken payment. Unconfirmed transactions also need to be distinguished from confirmed ones; a timer or a screenshot is not proof of settlement. Bitcoin.org: payments and confirmations ↗
The future interface would need to make these states understandable. The interactive circle example uses fictional records; it does not demonstrate production verification or a finalized confirmation policy.
Questions worth asking
- Who holds the keys for the provider I am considering?
- What would I be asked to approve for each contribution?
- How would I protect and recover access to my wallet?
- Which details would the circle share, and which should remain private?
- Can I distinguish a planned contribution from a verified payment?
Use these questions alongside the provider’s current guidance. Then return to the circle explainer or review what CoinHearted offers today. Choosing whether to participate is a separate decision from learning how the idea works.