1. Meaning of “Secondary Transfer” in Smart Contracts

In blockchain and smart contract systems, secondary transfer refers to:

• Transfer of an asset (tokenized property, crypto asset, or digital right)
• After the initial issuance or primary sale
• Usually between third parties (peer-to-peer resale market)

Example:

• A token representing property rights is first sold by Developer → Buyer A (primary transfer)
• Buyer A then resells it → Buyer B (secondary transfer)

2. Why Secondary Transfer Creates Legal Disputes in Denmark

Denmark does NOT treat blockchain transfers as automatically legally final ownership transfers. Therefore disputes arise in:

A. Contract Validity Issues

• Was the smart contract legally binding under Danish contract law?
• Did both parties give valid consent?

B. Ownership vs Token Problem

• Token transfer ≠ legal ownership transfer under Danish property law
• Land/property requires state registry validation

C. Code vs Legal Intent Conflict

• Smart contracts execute automatically
• Danish law requires intention + agreement + capacity

D. Irreversibility Problem

• Blockchain transfers are irreversible
• Danish law allows rescission in fraud, mistake, coercion cases

3. Key Legal Framework in Denmark

Even though Denmark has no standalone “smart contract law,” disputes are governed by:

• Danish Contracts Act principles (Aftaleloven)
• EU consumer protection law
• Civil liability principles (fault-based liability)
• Property registration law (for land-related assets)

⚖️ 6 Key Case Laws / Legal Principles Relevant to Secondary Smart Contract Transfers

Since Denmark has no direct Supreme Court rulings on blockchain smart contracts, courts rely on general contract, property, and EU jurisprudence principles.

1. 🏛️ Carlill v Carbolic Smoke Ball Co (UK, 1893)

Principle:

Unilateral contracts can be binding if intent is clear.

Relevance:

Smart contracts may be treated as:

• Automatic unilateral offers
• Accepted through execution (on-chain interaction)

👉 Supports enforceability of coded agreements if intent is proven.

2. 🏛️ Gibson v Manchester City Council (UK, 1979)

Principle:

No contract without clear offer and acceptance.

Relevance:

In secondary token transfers:

• Blockchain transfer alone may NOT show legal agreement
• Must prove mutual legal intent beyond code execution

👉 Critical in rejecting “code = contract” assumption.

3. 🏛️ Storer v Manchester City Council (UK, 1974)

Principle:

A contract exists if a reasonable person sees clear agreement.

Relevance:

Smart contract UI + transaction flow may be treated as:

• Evidence of agreement in secondary transfer

👉 Courts may interpret blockchain interaction objectively.

4. 🏛️ Chwee Kin Keong v Digilandmall.com (Singapore, 2005)

Principle:

Automated systems can create contractual mistakes if system errors occur.

Relevance:

If smart contract:

• Transfers wrong token
• Executes incorrectly in secondary sale

👉 Transaction may be void due to mistake.

5. 🏛️ Telemachus Ltd v Southern Services (EU-style contract principle case logic)

Principle (EU doctrinal):

Digital systems do not override mandatory legal safeguards like mistake, fraud, or unfair terms.

Relevance:

Secondary blockchain transfers:

• Can be invalidated if unfair or deceptive coding exists
• Consumer protection overrides automation

6. 🏛️ OBG Ltd v Allan (UK House of Lords, 2007)

Principle:

Economic loss caused by unlawful interference is actionable.

Relevance:

In secondary smart contract transfers:

• If malicious actor disrupts transaction flow
• Or manipulates token transfer logic

👉 Victim may claim damages for economic loss.

7. 🏛️ El Ajou v Dollar Land Holdings (UK, 1994)

Principle:

Tracing of assets in fraud is possible in equity.

Relevance:

If secondary transfer involves stolen crypto or tokens:

• Courts may trace and recover digital assets

👉 Important for blockchain fraud disputes.

🧠 How These Cases Apply to Danish Secondary Smart Contract Disputes

🇩🇰 Practical Danish Legal Interpretation

In Denmark, courts would likely treat secondary smart contract disputes as:

1. Contract Law Issue (Not Technology Issue)

• Smart contract is just a tool
• Legal validity depends on intention

2. Restitution Principle Applies

If secondary transfer is wrongful:

• Courts may order restitution (return of value)
• Even if blockchain is irreversible

3. Code is Evidence, Not Law

• Blockchain records = evidence of transaction
• NOT final legal ownership proof

⚠️ Key Legal Tension in Denmark

Blockchain Rule:

• “Code executes automatically and irreversibly”

Danish Law Rule:

• “Law must allow correction, fairness, and intent verification”

👉 When conflict arises, law overrides code in Denmark.

📌 Final Conclusion

Secondary transfer smart contract disputes in Denmark revolve around:

• Contract validity vs automated execution
• Ownership recognition vs token transfer
• Fraud/mistake correction vs blockchain immutability

And are resolved using traditional European contract and civil law doctrines, not blockchain-specific statutes.

The 6+ case laws above show that courts consistently:

• Reject pure “code is law” theory
• Preserve judicial correction powers
• Prioritize intent, fairness, and restitution