CuvexACADEMY

M09 · Edition 0.1

Creating invitations and contributing keys

Free · no registration

Objective

Build a policy with verified participants without sharing seeds.

Understanding the topic

The creator chooses the name, network, M, N, contacts, their own public information and operational invitation conditions. The reviewed schema accepts mainnet and regtest, 2 to 15 participants before applying device limits and an operational expiry of 1 to 720 hours. Those limits never authorize skipping a capacity check.

Each participant reviews and accepts or rejects the invitation, then supplies their extended public key with the fingerprint and BIP48 path through the compatible workflow. They do not supply a seed, private key, isolated address or another wallet’s entire descriptor. A key with incorrect context can produce a different policy even if it looks like a valid xpub.

The creator coordinates. Each signer remains responsible for validation. Before receiving funds, everyone should be able to reconstruct and verify the same parameters and a verification address. Accepting a contact in chat does not automatically approve every policy the contact sends.

An invitation expiry is an application coordination rule. It does not change an already funded script, delete signatures others retained or serve as a consensus timelock. Canceling a proposal and withdrawing funds from an existing policy are distinct actions.

Practice

  1. In a prepared regtest lab, create a 2-of-3 proposal with test contacts.
  2. Act out acceptance, rejection and a contribution on the wrong network. Verify that the last one is stopped.
  3. List what everyone must retain before funding: network, threshold, public keys, origins, script and verified address.

Show what you know

Identify an incomplete invitation and explain whose approval is missing without inferring approval from a chat connection.

Common question

Does an expiry date make later spending impossible? Not when it is merely an invitation field. A Bitcoin time restriction requires specific script or transaction conditions and actual support.

Pause point

Keep the training proposal ID and the outstanding approval.

1. What does the documented workflow request when you contribute your part of a multisignature wallet?

  1. Every participant’s seed.
  2. Any receiving address.
  3. Your extended public key with a compatible fingerprint and BIP48 origin.
Show answerYour extended public key with a compatible fingerprint and BIP48 origin.

The correct public material allows the policy to be built without disclosing private keys.

Download PDF ↗

You can keep reading without an account. To share progress with TutorAI, activate a code.