Getting Started

Medusa Custody™ separates the account that holds assets from the identities that approve operations. A workspace brings your team together; an organization groups accounts and defines their governance. In this walkthrough you will create an organization, request a Bitcoin account and follow its approval. Use a test environment and a Bitcoin test network enabled for your workspace.

Sign in with an existing account or accept your workspace invitation. Select the intended workspace and confirm that you can create organizations and Bitcoin accounts there. If those actions or the required network are unavailable, ask your workspace administrator. Reading this public guide does not enable them.

Have an eligible signing identity ready in the browser extension or on a registered device. Device registration is in Workspace Settings → Users and devices → Add device. Scan the pairing QR and confirm the matching three-word phrase. Registration enables device login confirmation; signing eligibility still comes from the organization's policy. Never enter a recovery phrase or private key into a documentation page.

Open Organizations and choose the action to create an organization. Enter a clear name, such as Bitcoin Test Operations, and review the founder identities and approval policy. A solo organization can use one eligible identity; a shared policy can require several. Configure the policy to match who should control this organization.

Review the organization request before submitting it. Submit stores an unsigned request for eligible signers; Sign & Submit adds the browser extension's signature first. Collect any remaining approvals and wait for the organization to become available before creating its account.

Open the organization and choose Add account. Select the managed on-chain account option, give it a recognizable name and select the enabled Bitcoin ledger and network. Check the network label carefully: a testnet account is for test coins. Review the account name, organization and selected assets in the request preview.

Choose Submit to leave the request in Pending Signatures. Eligible signers receive a notification; the review page also displays a QR code that opens the same request on a device. Open the notification or QR, read the payload and compare the provided hash with the hash calculated on the device. Approve adds your signature; Reject declines the request. Login number matching is a separate flow.

You can also use Sign & Submit with the browser extension. Using the same key in the extension and on a device still counts as one signing identity. A policy requiring two distinct approvals remains pending after one signature; the first approval does not bypass governance.

Once Medusa Custody™ reports that signature collection is complete, the browser opens the pending account. The organization and account sidebar remains available while governance and account creation finish. The device closes its review after successfully adding an online signature. Account details replace the pending view when the account is ready. If creation fails, review the change and its error before retrying.

Open the account's assets and addresses and confirm the selected Bitcoin network. If address creation is still pending, wait for its status before using it. For an evaluation, start with a small test-coin transfer and check the transaction and confirmation status. Creating a Bitcoin account does not automatically create an RGB asset or enable RGB operations.