Optional cookies require your permission.Privacy & cookies

One Bitcoin treasury funds several citizenship applications.

Several family members may draw on the same treasury. An identical balance in their files would say little about which person is entitled to commit which amount or consent to its use.

Adam Juchniewicz, CEO, Bitcoin Lawyer9 min read
Sources cited in this essay (1)
Color-coded file folders with index tabs fill a filing cabinet.
In this essay11 sections
  1. The fifth application needs a system.
  2. Map people and roles before collecting everything.
  3. Build one source history with individual funding explanations.
  4. Work through a five-file example before moving coins.
  5. Schedule dependencies, not just desired completion dates.
  6. Give shared facts an owner and a version.
  7. Privacy improves when each recipient receives a purposeful file.
  8. Review each file alone, then review them together.
  9. Resolve a shared discrepancy once, then track every affected file.
  10. Budget shared preparation and separate obligations honestly.
  11. The Bitcoin Lawyer take

The fifth application needs a system.

The first citizenship file can be organized in a folder. By the fifth, the same business sale, company accounts, or Bitcoin acquisition history may appear in several packages. Each applicant also has a separate identity, family relationship, and explanation of the assets they intend to use. The risk is not simply a missing attachment. It is that the files tell different versions of the same event.

One application calls a transfer a gift. Another describes the same funds as a loan. A company chart uses the ownership position before a share sale, while the narrative describes the position afterward. The transaction values differ because one file records the gross amount and another the net amount without saying so. These contradictions can arise from ordinary document handling, without anyone deliberately inventing a story.

Calling the organization a family office does not answer who qualifies for a citizenship route or who owns the proposed funds. Treat coordination as an administrative discipline: common evidence where the facts are common, individual explanations where they are not, and an identifiable person responsible for resolving discrepancies.

Map people and roles before collecting everything.

Start with the people who are actually involved. Identify the applicants, dependents, proposed funders, authorized company representatives, and professionals whose advice may be needed. Record the relationship relevant to the file and the document supporting it. A family nickname, job title, or wallet label is not the same as a legal identity or authority to act.

Separate the questions. Who is applying? Who acquired the wealth? Who currently holds the assets? Who is permitted to authorize the proposed transfer? Who will be the sender visible to the recipient? The answers may be different, and the file needs to explain the differences instead of making every role appear to belong to the principal applicant.

Do this privately and proportionately. The coordination record is not a reason to collect every adult family member’s complete financial history. Establish which facts are relevant to each application and who needs to see them. Agree who can give instructions for a minor, an entity, or another person rather than assuming the household’s usual organizer has every necessary authority.

Build one source history with individual funding explanations.

A well-supported common history can be reused. For example, the evidence of a business sale can explain how a family’s wealth arose across several files. But the sale documents do not necessarily explain how a particular adult child or employee became entitled to the amount intended for their own application.

Maintain a master set of the shared records, then create a deliberate application-specific selection. Connect the shared event to the applicant through the relevant distribution, gift, remuneration, loan, or other actual arrangement. Use the label supported by the arrangement, and obtain the appropriate professional advice before treating it as settled.

Keep the two layers readable. The shared source history should explain the economic origin of the wealth. The individual explanation should follow the selected funds to the proposed payment and identify the person whose resources are being used. Neither a large balance nor a family relationship removes the need to make that connection.

Work through a five-file example before moving coins.

Consider a fictional founder coordinating applications for five people: the founder, a spouse, two adult children, and a senior executive. The proposed funds are held in a company-controlled Bitcoin wallet. Everyone knows the founder built the business. That shared understanding is not a complete account of each person’s funding.

The founder’s file needs to explain the intended payment and the relevant authority. The spouse’s and children’s files need their own relationship and funding explanations. The executive’s arrangement may be different again. The purpose of the exercise is not to select a convenient label. It is to establish the actual ownership, authority, and intended character of each transfer with the relevant corporate and tax professionals.

Do not broadcast a single transaction first and ask advisors to make the paperwork fit afterward. Before a transfer, resolve who authorizes it, what amount is approved, which valuation and date are being used, who bears fees and what evidence the recipient expects. Retain the transaction record alongside those instructions when the authorized transfer is made.

A transaction ID can demonstrate a movement on the network. It does not, by itself, decide whether the transfer was a gift, compensation, a distribution, or a loan. Preserve that distinction throughout the file. The practical benefit is a funding explanation that can be followed without guessing what the sender intended.

Schedule dependencies, not just desired completion dates.

Several applications can share preparation work while reaching different stages at different times. One person may need a replacement civil record. Another may need a translation, a consent decision, a correction to a name, or confirmation about a document’s remaining acceptance period. Identify the dependency and its owner before setting an internal target.

Separate work that can proceed in parallel from work that depends on an answer. Collecting an available bank statement may not depend on a later appointment. A final funding narrative may depend on resolving an ownership question. Putting both tasks on the same urgent list hides the sequence that actually controls progress.

Vanuatu’s published application-process page distinguishes document review from the Commission’s decision and warns that missing valid information can lead to deferral or rejection. The page also contains older program descriptions, so it should not be used as a current timetable for every investment route. The relevant lesson here is limited: a coordinated submission is still subject to the applicable individual review and decision.

Give shared facts an owner and a version.

Choose a controlled version of each shared factual record. A company ownership chart should say the date it represents. A transaction schedule should identify its source files and distinguish gross amounts, fees, and net receipts. A translation should be tied to the document and version translated. Preserve the originals separately from the working explanation.

Appoint someone to check consistency across the files. That role does not turn the coordinator into a lawyer, certified public accountant (CPA), translator, or issuing authority. It means they know which professional or record owner must answer a discrepancy and make sure the corrected answer reaches every affected package.

For example, if the sale consideration was revised after completion, identify which valuation, bank record, and narrative need updating. Do not change one paragraph and leave the earlier figure in four other applications. Record the reason for the revision and retain the earlier version so the history of the correction remains understandable.

Privacy improves when each recipient receives a purposeful file.

A central archive can support careful disclosure. It can also become a folder shared with everyone who touches the project. The first approach is useful; the second creates unnecessary exposure. Decide which documents a translator, corporate advisor, tax professional, or application recipient actually needs.

An adult child should not have to circulate a sibling’s police record merely because both files refer to the same business sale. A translator working on a birth certificate does not need the family’s wallet history. Conversely, withholding a relevant fact from the professional assessing it can make the advice incomplete. The aim is a purposeful disclosure, not indiscriminate sharing or selective concealment.

Never place recovery words, private keys, or unrestricted signing access in the application archive. If a counterparty asks for wallet evidence, identify the proposition they need to test and agree on a proportionate method. Keep authority to spend separate from authority to help prepare a file.

Review each file alone, then review them together.

Before submission, ask whether an independent reader can follow each applicant’s identity, relationships, wealth explanation, and intended funding without access to the household’s internal conversations. Then compare the shared facts across the group. The two reviews find different problems.

Keep a record of exactly what was submitted, by whom and when. A package marked final in a shared folder is not proof that the recipient received that version. Save the acknowledgment and any subsequent request against the relevant application. A request concerning one person should not silently become a change to everyone else’s file.

If a shared fact changes after submission, identify every affected file and ask the responsible recipient how to correct it. Preserve the previous submission and the correction. Quietly replacing a document in the internal folder does not correct the version already outside it.

This discipline continues after a decision. Later passport, banking, and residence work may refer back to the same history. A coherent archive makes that later work more efficient without implying that one institution’s acceptance binds another or establishes a tax result.

Resolve a shared discrepancy once, then track every affected file.

Imagine that a closing statement shows $4.8 million received after a business sale, while a family presentation describes a $5 million sale. Both figures may be understandable if the difference represents documented costs or a holdback. The problem arises when applications use them as if they describe the same amount. Reconcile the figures in a shared factual note and link the underlying closing records.

Then identify which files use the event. One applicant may own the sold shares; another may have received a later gift; a third may have no entitlement to the sale proceeds at all. Correcting the shared sale figure does not complete the individual funding explanations. The coordinator needs to track both the common correction and each applicant’s separate connection to it.

If a file has already been submitted, preserve what the authority actually received and use the appropriate correction channel. Do not overwrite the internal final copy and assume that the external record changed with it. A controlled revision records the reason, the affected statements, the person authorized to approve it, and the evidence that the correction was delivered.

Budget shared preparation and separate obligations honestly.

Evidence reuse can reduce duplicated preparation, but it does not merge official applications or make one payment cover every principal. Ask the quotation to identify each applicant, the category assumed, and any genuinely shared professional work. An internal allocation of family money should remain distinguishable from the amounts due for each case.

The same applies to delays. If one applicant’s civil document is missing, consider whether independent preparation can continue for the others. If the missing issue concerns the shared ownership of the treasury, it may affect every proposed payment. The difference matters: coordinated work should reduce unnecessary waiting while respecting the dependencies that actually need to be resolved.

The whole picture

The Bitcoin Lawyer take

Keep a single source history for the shared funds and an individual explanation for each applicant. When one person’s authority changes, revise only the applications whose payments or permissions depend on it.

The test is whether each application stands on its own without telling a different version of the family’s facts. When ownership, authority, and amounts are settled before transfers occur, the common archive becomes useful evidence rather than a source of multiplied confusion.

Cite this essay

Adam Juchniewicz, CEO, Bitcoin Lawyer. “One Bitcoin treasury funds several citizenship applications.” https://www.bitcoinlawyer.com/journal/one-treasury-several-citizenship-files