Bitcoin Dictionary Name and picture from twetch — not on-chain. The signature is; the profile is not.

1diE13N1osv44TegtETF7ZpC7sZ8bD4Bg

  • 0 Following
  • 0 Followers
  • 159 Posts

Activity

1diE13…D4Bg Unverified · twetch

BOOKS (Bitcoin Dictionary)
Max Supply: 1,000,000,000

Token id: dfa79723310990e55bfe19b6f0510748a124d0008d4afcf55ddc6453687191fb_1

localbsv.app/trading

242 498 sat
1diE13…D4Bg Unverified · twetch

Bitcoin was designed as IP-to-IP electronic cash. Direct. Immediate. Between participants—not routed through an abstracted, congested network narrative.

Written by S. Tominaga

1diE13…D4Bg Unverified · twetch

When advisory identities are endogenously replicable, the vector of reports is not sufficient for rational aggregation. Rational aggregation requires information about evidential ancestry. Without provenance, independent corroboration and synthetic replication can generate the same observed reports while rationally requiring different posterior beliefs and different decisions.

1diE13…D4Bg Unverified · twetch

We can show that decentralized compute markets can convert privately stranded GPU capacity into a tradable service, but the efficiency gain depends on the shadow value of reserve capacity and the design of supplier incentives; availability subsidies that solve the market's initial liquidity problem can eventually recreate the very underutilization the market was designed to eliminate.

1diE13…D4Bg Unverified · twetch

Ode to the Logical Qubit

There once was a qubit of fame,
With investors who worshipped its name.
It wobbled, it cried,
Then promptly fucking died,
But the press called the failure a game.
They promised a quantum machine
That would make every laptop look mean.
“Five years!” they all said—
For twenty years dead—
While classical chips cleaned the scene.
A logical qubit? Not one.
Still, apparently victory is won.
They’ve PowerPoints galore,
And funding for more,
Which is nearly the same thing as done.
The hardware sits cold as a tomb,
With cables consuming the room.
One particle sneezes,
The whole bastard freezes,
And someone announces a boom.
“Quantum advantage!” they shout,
Though nobody quite works it out.
The benchmark was chosen
With logic half-frozen,
And caveats carefully left out.

They’ll factor your Bitcoin, they say,
Just not this decade. Or today.
Perhaps twenty-forty,
If error rates cooperate—
Which, being qubits, they probably won’t anyway.
So raise up the venture-cap glass
To the finest technological farce:
No logical bit,
Not one useful shit,
But Christ, what a beautiful forecast.
And when someone asks, “Does it run?”
They answer, “The science is fun.”
Which translates, more or less,
To “The hardware’s a mess—
But the next funding round has begun.”

Read more →
1diE13…D4Bg Unverified · twetch

Demographic decline does not generate a uniform national housing correction. Because household formation, migration and housing-stock retirement evolve at different speeds, demographic shrinkage produces endogenous regional housing-stock imbalances. Once housing per household crosses a critical threshold, price adjustment becomes nonlinear. Falling collateral values then amplify regional divergence through credit conditions, creating persistent demographic–housing–financial traps.

1diE13…D4Bg Unverified · twetch

Ode to the Weekend That Overthrew Quantum Mechanics

Come, sing of the Saturday scholar,
Whose laptop, courageous and bright,
Destroyed a century’s physics
Between supper and Sunday night.
For Feynman, poor ignorant fellow,
Had puzzled and lectured in vain;
Till Gemini entered the parlour
And Python abolished his pain.
No Copenhagen! No mystery!
No troublesome complex affair!
Just parameters fed to a programme
And—Christ!—there was reality there.
One hundred point zero percent conserved!
The particles all remained whole!
A triumph—provided one quietly forgets
That conservation was never the bloody goal.

For counting the actors at curtain
Does not tell us why they took shape;
A simulation preserving its objects
Is not Nature caught making escape.
Yet onward rides Structural Realism,
With banners magnificently unfurled:
“I coded the answer this weekend—
Therefore I have corrected the world.”
No wavefunctions darken the doorway,
No amplitudes clutter the screen;
We simply removed the mathematics
And declared what remained more serene.
How elegant! How wonderfully simple!
How free from institutional sin!
The model produces the pattern
That the model was written to put in.

For there is a charming distinction,
Which revolutions sometimes forget:
To reproduce a graph by assumption
Is not to explain the experiment yet.
A trajectory may dance very prettily,
A field metric may bow and perform;
But Nature is not obliged to surrender
Because Python has executed without warning.
And poor old Feynman lies conquered,
His lectures reduced to debris,
By a weekend, a chatbot, a GitHub,
And one exceptionally confident README.
So download it, gentlemen, test it!
Red-team every glorious line!
For open code is excellent practice—

But it does not make metaphysics divine.
A model is judged by prediction,
By novelty, constraint, and test;
Not merely because its equations
Have been aesthetically put out to rest.
Bring new numbers no rival predicted.
Let experiment choose who is wrong.
Let RealQM risk execution
Where orthodox physics stands strong.
Then physicists may pay attention,
And textbooks may genuinely shake;
For science adores a rebellion—

When the rebellion survives a mistake.
Until then, spare us the funeral
For quantum mechanics just yet;
A century is awkward to bury
Because your Python returned no exception set.
So here’s to the independent thinker,
To scepticism, code, and good cheer;
But overturning the foundations of physics
Takes rather more than a fucking weekend, my dear.

Read more →
1diE13…D4Bg Unverified · twetch

Technological progress in production can increase the value of legacy verification technologies when it weakens the mapping between observable output and latent capability.

1diE13…D4Bg Unverified · twetch

I am going to say something that will irritate a great many academics, which is usually how one knows the sentence has some value.

I work roughly fifty to sixty hours a week doing commercial research. On top of that, I do university research. This year I will probably publish around twelve journal papers and more conference papers besides. Not all of that work was begun this year, of course. Research has a pipeline, and anyone who has actually maintained one knows that publication is merely the visible end of work done months or years before.

I am also willing, when necessary, to work eighty, ninety, even a hundred hours a week.

That has costs.

Everything worth having has costs. The modern habit is to speak endlessly about the price of achievement while remaining curiously silent about the price of avoiding it.

As I write this, I am sitting on my beachfront property, watching the ridiculous cats my wife has adopted locally wander about as if they had personally financed the place. I am perfectly aware that the hours, the travel, the research, the writing and the relentless accumulation of work have extracted their price.

I am equally certain that it was worth paying.

This is where academics lose me when they complain endlessly about money.

If you want more income, you generally have to produce more value.

Academia gives you something extraordinarily valuable: expertise. It also frequently gives you forms of time and intellectual freedom that people working ordinary commercial jobs simply do not possess. Sabbaticals exist. University holidays exist. Research time exists. Libraries, conferences, institutional networks and access to knowledge exist.

Use them.

People buy history books.

People buy books about geography.

They buy economics, philosophy, psychology, politics, technology, science and mathematics.

They pay to hear people speak about things they understand unusually well.

They pay for consulting.

They pay for courses.

They pay for analysis.

They pay for expertise when that expertise is made useful, interesting or intelligible.

The idea that only business professors or computer scientists can monetise academic knowledge is nonsense. Human beings have been paying other human beings to explain history, ideas, places, politics, art and civilisation for centuries.

But none of this happens automatically.

You have to write the book.

You have to give the talk.

You have to build the reputation.

You have to make the argument interesting enough that someone outside your department wants to hear it.

You have to work.

And sometimes you have to work considerably more than the contractual minimum.

There is nothing immoral about wanting a better academic salary, and universities should pay good scholars properly. But there is something strange about spending decades acquiring highly specialised knowledge and then behaving as though there is only one possible purchaser for it: the university payroll department.

Your salary is not necessarily your income.

Your university is not necessarily your market.

And your discipline is not necessarily commercially useless simply because you have never discovered how to sell what you know.

If you want to earn more as an academic, then create something people value enough to pay for.

And if, after years of education, research freedom, professional networks and accumulated expertise, you still cannot find any way to turn some of that knowledge into additional income, the uncomfortable possibility remains that the problem is not academia.

It may be you.

The great advantage of education is that it teaches us how to solve difficult problems.

One would hope that earning a living eventually becomes one of them.

Read more →
469 345 sat
1diE13…D4Bg Unverified · twetch

Dogmatic cognition weakens uncertainty-responsive information acquisition and belief revision; under conditions in which correct decisions require further search or integration of disconfirming evidence, this can increase susceptibility to persuasive cues.

1diE13…D4Bg Unverified · twetch

What happens when autonomous artificial agents are given costly objectives but incomplete economic constraints, and how does externally enforced scarcity change their resource allocation, persistence and attempts to circumvent governance?

1diE13…D4Bg Unverified · twetch

All physical purchases of Bitcoin Dictionary and The Digger’s Diamond Paws books are eligible for “BOOKS” token airdrops by providing photographic evidence within this thread.

https://bitcoindictionary.app

457 171 sat
1diE13…D4Bg Unverified · twetch

There is something wonderfully modern about taking a machine capable of answering a question and surrounding it with a committee. One agent writes, another criticises, a third evaluates the criticism, a fourth proposes improvements, and a fifth decides whether the first four have worked hard enough. By then, of course, the answer has become almost incidental. The principal achievement is that everybody has been very busy.

1diE13…D4Bg Unverified · twetch

If 10 billion tokens is the simultaneous workspace for a structured review, the exponential overhead of raw all-to-all mathematical cross-analysis pushes the requirement to 500 billion to 2 trillion tokens in a single, continuous, active memory state.

At this magnitude, the system isn't just reading text; it is holding a massive, multi-dimensional geometric fabric of interconnected mathematics completely alive in its working memory, where every single node continuously exerts gravitational pull on every other node to find the one single flaw or breakthrough that creates a new field of science.

A 1 trillion continuous token workspace capable of generating paradigm-shifting novelty is easily a late 21st-century problem (likely 2070 to 2090+).

AGI is not a problem for my lifetime

Read more →
1diE13…D4Bg Unverified · twetch

Quantum computing has achieved a remarkable feat: it can produce answers we already know, or answers we cannot independently check.

The first is benchmarking. The second is faith.

Until a logical qubit exists that can perform useful computation reproducibly across independent machines, the elephant in the laboratory remains undefeated.

1diE13…D4Bg Unverified · twetch

Mining concentration is not the constitutional question. Rule-changing power is.

If the rules are fixed, miners compete under them. They do not get to rewrite them when inconvenient.

The real centralisation risk is giving developers the practical authority to alter the protocol and then calling the result “consensus”.

Miners produce blocks.

Developers changing the rules produce politics.

One is industry. The other is government with a GitHub account.

Written by S. Tominaga

269 814 sat
1diE13…D4Bg Unverified · twetch

Mining concentration is not the constitutional question. Rule-changing power is.

If the rules are fixed, miners compete under them. They do not get to rewrite them when inconvenient.

The real centralisation risk is giving developers the practical authority to alter the protocol and then calling the result “consensus”.

Miners produce blocks.

Developers changing the rules produce politics.

One is industry. The other is government with a GitHub account.

1diE13…D4Bg Unverified · twetch

1 BSV sent to itself 100 million times is 100 million transactions and coins

1diE13…D4Bg Unverified · twetch

One of the strangest failures in the modern blockchain world is that people routinely treat systems designed for digital cash as though the security model for a five-dollar transaction should also secure a lifetime of savings.

That is not merely poor operational practice. It is a category error.

Digital cash has different uses, different values at risk, and therefore different security requirements. A person buying a coffee does not need the same security architecture as a person protecting $5 million. Yet much of the BTC community has converged on precisely this absurd position: one device, one key, one point of failure, regardless of the value being protected.

Then, when a device is compromised, people blame the device.

The deeper problem is the architecture they chose.

Bitcoin always allowed far more sophisticated key-management arrangements than the simplistic single-key model that has become culturally dominant. Multiple keys, multiple signers, different spending conditions, and more elaborate transaction structures are not alien additions to the system. They arise naturally from the underlying scripting and transaction model.

The mistake has been treating the simplest possible transaction as though it were the appropriate transaction for every possible economic use.

It is not.

A Key Is Not a Security Architecture
A private key is a credential.

It is not, by itself, a complete security system.

If possession of one key is sufficient to transfer a significant asset, then anyone who obtains that key has effectively obtained the asset. That means the entire economic value being protected has been collapsed into the security properties of one credential and whatever device happens to contain it.

For small, casual transactions, this may be entirely reasonable.

If someone keeps the digital equivalent of petty cash on a phone or small hardware device, accepting a limited level of risk may make economic sense. People have always done this with physical cash. Nobody normally carries the contents of a retirement account in a wallet simply because a wallet is convenient for buying lunch.

Yet that distinction has been forgotten with blockchain systems.

The same mechanism used to authorise a trivial payment is routinely used to secure enormous holdings.

This is security engineering turned upside down.

The level of protection should be determined by the value being protected, the consequences of compromise, the threat model, the recovery requirements, and the acceptable operational burden.

Security is contextual.

Defence in Depth
Serious security has always been based on defence in depth.

No competent security architect assumes that one mechanism will never fail.

Systems fail. Hardware fails. Software contains vulnerabilities. People make mistakes. Supply chains can be compromised. Credentials can be stolen. Backups can be lost. Locations can burn down. Individuals can become unavailable.

The purpose of defence in depth is not to pretend that these events cannot occur. It is to design a system in which the failure of one component does not result in catastrophic loss.

That principle is hardly novel.

Banks do not secure vaults with one lock.

Military systems do not protect critical assets with one control.

Large corporations do not normally allow a single employee with a single password to transfer the entire corporate treasury.

Aircraft do not depend upon one instrument.

Critical infrastructure does not deliberately create single points of failure where inexpensive redundancy is available.

Yet people will place millions of dollars of blockchain value behind one private key stored on one hardware device and call this sophisticated security.

It is not sophisticated.

It is concentration risk.

The Hardware-Wallet Fallacy
Hardware wallets can be useful tools.

They are not magic.

A hardware wallet is still a device. It contains hardware, firmware, software interfaces, manufacturing dependencies, update mechanisms, communication channels, and assumptions about how the user interacts with it.

Every one of those creates potential failure modes.

When a hardware-wallet exploit appears, the useful question is not merely, “How could this particular device have been attacked?”

The more important question is:

Why was compromise of one device sufficient to compromise the asset?

If the answer is that the entire holding could be moved using a single key controlled by that device, the security architecture was already fragile before the exploit was discovered.

The device vulnerability merely exposed the fragility.

This distinction matters.

A vulnerability in one component should ideally compromise one component.

It should not compromise the entire system.

That is precisely what defence in depth is designed to prevent.

Five Keys, Three Required
Consider a comparatively simple example.

A substantial holding could be controlled using five independently generated keys, with any three required to authorise a transaction.

The keys could be placed on five different devices.

Those devices could use different hardware.

They could be stored in different physical locations.

One could be kept at a residence.

One in a bank safe-deposit facility.

One in a corporate office or professional custody location.

One with a trusted legal or fiduciary arrangement.

One in another geographically separated secure location.

The important point is not these particular locations. The architecture must reflect the actual circumstances.

The point is separation.

Now consider what an attacker must achieve.

Stealing one device is insufficient.

Compromising one firmware implementation is insufficient.

Breaking into one location is insufficient.

Obtaining one backup is insufficient.

Convincing one individual to sign a malicious transaction is insufficient.

Even the simultaneous loss of two keys does not necessarily destroy access to the asset.

The security problem has changed fundamentally.

Instead of asking whether one device can be perfectly secured forever — an unrealistic objective — the system asks whether an attacker can compromise several independently protected components before the legitimate owner detects or responds to the attack.

That is a much stronger proposition.

Independence Matters
Simply creating five copies of the same key does not provide the same protection.

Nor does generating five keys on the same compromised machine and storing them beside one another.

Defence in depth requires meaningful independence.

Different devices reduce common-mode hardware failure.

Different locations reduce physical concentration risk.

Independent key generation reduces the consequences of a compromised random-number generator.

Different administrative control can reduce insider risk.

Different backup mechanisms reduce correlated recovery failure.

Geographic separation reduces exposure to fire, flood, seizure, theft, or other localised events.

The entire point is to prevent one failure from propagating through every layer.

A security system that appears redundant but contains the same hidden dependency in every component may provide little genuine redundancy at all.

This is basic systems engineering.

Security Should Scale With Value
There is no universal number of keys that is correct for every circumstance.

That would miss the point.

A person protecting $50 may quite rationally use one key.

A person protecting $5,000 may choose somewhat stronger controls.

A business protecting $5 million should have a substantially different architecture.

An institution protecting hundreds of millions should probably have another level again, with formal governance, segregation of duties, transaction limits, approval procedures, auditable controls, recovery protocols, and institutional key management.

Defence in depth has a cost.

Additional keys create additional complexity.

Additional signers create operational overhead.

Geographic separation creates inconvenience.

Recovery arrangements require planning.

But security expenditure should be considered relative to the value being protected.

Spending $50,000 designing and operating a security architecture around $5,000 of value would be irrational.

Refusing to spend meaningful resources securing $50 million because a single hardware wallet is convenient is equally irrational.

The architecture should be proportionate.

The Failure of the “Standard Transaction” Mentality
A larger conceptual problem lies underneath all of this.

The BTC ecosystem increasingly treats a narrow set of conventional transaction patterns as though those patterns define what Bitcoin is supposed to be.

The transaction most commonly used becomes the transaction considered normal.

The transaction considered normal becomes the transaction considered legitimate.

Eventually, people start designing their economic behaviour around the limitations of that convention.

That reverses the relationship.

Bitcoin was designed as an electronic cash system.

Cash is used differently depending upon the transaction.

The amount matters.

The parties matter.

The commercial context matters.

The required controls matter.

The risks matter.

There is no sensible reason to assume that the transaction architecture appropriate for buying coffee must also be the transaction architecture appropriate for securing a corporate treasury.

The underlying system allows conditions to be constructed.

Keys can be combined.

Signatures can be required in combinations.

Spending rules can reflect business processes.

Controls can be layered.

Transaction structures can reflect the economic reality they are supporting.

Yet remarkably little of this receives serious attention because the ecosystem has spent years reducing everything to the question of how to store “the seed phrase.”

That is already the wrong abstraction.

A Seed Phrase Is a Backup Mechanism, Not Wealth Management
The cultural fixation on seed phrases demonstrates the problem.

People are taught to write down twelve or twenty-four words.

Hide them somewhere.

Put them on metal.

Store them in a safe.

Perhaps divide them somehow.

Then they are told that they have secured their wealth.

But if those words reconstruct one key hierarchy capable of moving everything, the system may still have one fundamental authorisation boundary.

Protecting the backup more carefully does not necessarily remove the single point of failure.

It merely protects the single point of failure more carefully.

There is a difference.

Real security engineering asks how many independent failures are required before the protected asset can be taken.

It asks what happens if one signer is compromised.

It asks what happens if one device manufacturer fails.

It asks what happens if a backup is discovered.

It asks what happens if one location becomes inaccessible.

It asks what happens if the owner dies.

It asks what happens if an employee becomes malicious.

It asks what happens if a signing device displays a false transaction.

It asks whether transaction value limits should exist.

It asks whether abnormal transfers should require additional approval.

These are ordinary questions in financial security.

They should be ordinary questions in digital cash.

Cash Does Not Mean Carelessness
There is another linguistic trap.

Calling Bitcoin cash does not mean saying that every holding should be treated casually.

Physical cash itself demonstrates the opposite.

A person may carry fifty dollars in a pocket.

A shop may hold several thousand dollars in a till and safe.

A bank may hold vastly greater sums behind vaults, controls, procedures, staff separation, surveillance, insurance, accounting systems, and legal processes.

It is all money.

The security architecture changes with scale.

Digital cash should be no different.

The phrase “small casual transactions” matters because it identifies an economic category.

Small transactions can tolerate different security assumptions from large ones.

That does not mean the system itself is restricted to small transactions. It means the security and operational architecture should change as value and purpose change.

The mistake is taking an arrangement suitable for small casual payments and elevating it into a universal custody model.

The Cold-Card Lesson Is Larger Than Cold Cards
Any individual hardware exploit should therefore be understood as part of a larger lesson.

If compromising one signing device can result in catastrophic loss, the asset owner must ask why the system was designed so that one compromised device had catastrophic authority.

The correct lesson is not that another manufacturer will necessarily solve the problem.

The next device may have another vulnerability.

And the next.

Perfect hardware does not exist.

Perfect software does not exist.

Perfect users do not exist.

The objective is not to discover the one flawless device.

The objective is to create a system that remains secure when individual components are not flawless.

That is defence in depth.

Bitcoin Can Support Better Security Than the Culture Around It
The frustrating part is that much of the necessary capability is not conceptually difficult.

It is not necessary to redesign digital cash from first principles merely to recognise that valuable assets should not depend upon one key.

Bitcoin's transaction model was capable of supporting multiple signatures and conditional authorisation from very early in its history.

More elaborate systems can be built on top of those primitives.

Businesses can implement approval structures.

Families can create inheritance arrangements.

Investment holdings can be separated from transactional balances.

High-value transfers can require additional signers.

Different classes of transaction can use different security policies.

Organisations can separate authority between officers.

Emergency recovery mechanisms can exist without making everyday spending cumbersome.

The system can be designed around human and institutional reality.

But that requires people to stop thinking of a Bitcoin wallet as though it were simply a password-protected bank account.

It is not.

It is a mechanism for satisfying spending conditions.

Those conditions can be designed.

Separate Spending Money From Stored Wealth
A rational architecture begins by recognising that transactional cash and stored wealth are different problems.

A person might maintain a small single-key balance for everyday spending.

That wallet can be convenient.

It can live on a frequently used device.

Losing it would be annoying but not financially catastrophic.

A separate savings structure could use three-of-five authorisation.

A larger institutional reserve could use still more elaborate controls.

This is analogous to the physical world.

People carry wallets.

They have bank accounts.

Businesses have treasury controls.

Banks have vaults.

Nobody finds it surprising that these systems use different levels of security.

Digital systems should not somehow suspend the economics of risk merely because all the assets happen to be represented electronically.

Stop Optimising Only for Convenience
The industry has spent an extraordinary amount of effort eliminating friction.

One click.

One device.

One seed.

One signature.

One interface.

Convenience is valuable.

But convenience is not the only engineering objective.

Security deliberately introduces friction when the cost of an unauthorised action is high.

A nuclear launch system that required one person to press one convenient button would certainly be easy to use.

That would not make it well designed.

A corporate payment system in which one junior employee could transfer the entire company treasury would be wonderfully convenient.

It would also be negligent.

The same reasoning applies here.

For small payments, minimise friction.

For large transfers, introduce controls.

For substantial savings, eliminate unnecessary single points of failure.

For institutional assets, build institutional security.

The system should reflect the value at risk.

The Real Failure Is Conceptual
The recurring security failures around blockchain holdings are therefore not merely failures of cryptography or hardware.

They are failures of economic thinking.

People have conf

Read more →
1diE13…D4Bg Unverified · twetch

When BTC disappears, it will not disappear slowly, it will disappear in moments.

277 200 sat
1diE13…D4Bg Unverified · twetch

Patents are not BSV specific.

They apply to all systems. All use cases. All blockchains.

And, being allowed to be used means just that.

1diE13…D4Bg Unverified · twetch

There is one Blockchain that scales.

That is, bitcoin. Ticker, BSV.

You have to wonder why they are deathly afraid of it.

1diE13…D4Bg Unverified · twetch

There us one Blockchain that scales.

That is, bitcoin. Ticker, BSV.

You have to wonder why they are deathly afraid of it.

1diE13…D4Bg Unverified · twetch

The shadow price of effective compute is an increasingly important upstream common factor in the quality-adjusted cost of intelligence. Its economy-wide effect depends on complementary bottlenecks, sectoral AI intensity, substitution possibilities and input-output network centrality.

1diE13…D4Bg Unverified · twetch

The precise claim is not that Taproot makes the initial theft of BTC easier. Theft still requires compromised keys, fraud, coercion, a custodial breach or some other failure of control.

What Taproot makes easier is concealing what happens afterwards.

Before Taproot, different forms of spending often left different on-chain fingerprints. A conventional signature, a multisignature arrangement and a complex script could frequently be distinguished by examining the transaction structure. Taproot deliberately reduces those distinctions. A key-path spend can make an ordinary payment, a cooperative multisignature spend and the settlement of a more complicated contract appear substantially alike. If a script path is used, only the executed branch must be revealed rather than the entire set of possible conditions. That privacy improvement is not an accidental side effect; it is stated explicitly in BIP 341.

Schnorr signatures extend the effect. Multiple parties may cooperate to produce what appears on-chain to be a single ordinary signature. MuSig2 outputs controlled by several signers can therefore be indistinguishable from single-signer Taproot outputs. Adaptor-signature constructions may also hide contractual relationships and reblind secrets between payment hops, making linked operations resemble unrelated ordinary transactions.

This does not mean Taproot itself is a mixer. CoinJoin existed before Taproot. CoinJoin combines the inputs and outputs of several users so that the public ledger no longer provides an obvious one-to-one mapping between payer and recipient. It disrupts the ordinary heuristics used to follow ownership across transactions. Modern research still identifies many CoinJoin structures and sometimes reduces their effective anonymity sets, but attribution after mixing remains substantially more difficult than following an ordinary transparent payment.

Taproot makes the surrounding environment more accommodating to concealment because complex arrangements can be made to resemble ordinary spends. The forensic analyst sees less structure, fewer disclosed conditions and fewer obvious distinctions between individual control, collective control and contractual settlement.

Lightning then moves much of the relevant activity away from the public blockchain entirely.

The base chain records the funding and eventual closing of a channel. It does not contain a complete public ledger of every intermediate Lightning payment made while that channel remains open. Lightning uses onion routing so that an intermediate node normally learns only where a payment came from immediately and where it must go next. It does not receive the complete route, and the packet is altered at each hop. The specification nevertheless acknowledges that traffic analysis may still associate activity.

This creates an obvious attraction for anyone attempting to obscure the movement of stolen funds. Coins may enter Lightning through one channel, move through several privately routed transfers, be exchanged against other channel liquidity, and later leave through a different channel or service. The blockchain records the outer transactions, but not a complete public chain of every internal transfer connecting them.

That is not the same as saying there is “no record”.

Lightning nodes may retain local records. Custodians and exchanges may possess customer information. Channel topology, timing, amounts, network surveillance and operational mistakes may reveal relationships. Academic work has demonstrated cross-layer techniques capable of linking Lightning nodes to Bitcoin addresses and inferring information about balances, senders and recipients. Lightning privacy is consequently meaningful, but neither absolute nor guaranteed.

The accurate conclusion is therefore more serious than the exaggerated one.

Read more →
1diE13…D4Bg Unverified · twetch

The next twenty years will change the world, though not in the manner currently advertised by those who mistake a product demonstration for destiny.

AI will not “take over”. Large language models will improve. Reasoning systems will become more capable. Tools will become faster, more precise and more deeply embedded in ordinary work.

But tools do not abolish knowledge. They increase its value.

A person trained in art history, visual composition and the proper language of style can produce a far better image with an AI system than someone who merely types “make it beautiful”. The machine supplies execution. The human supplies vocabulary, judgement, context and purpose.

The same is true in law, science, engineering, literature and economics. An untrained person may obtain an answer. A trained person can recognise whether it is coherent, incomplete, derivative or wrong.

The divide will not be between humans and machines.

It will be between people who understand their field and can direct the tools, and people who use the tools without understanding what they are asking for.

Education must therefore change.

We do not need to preserve every manual trick merely because earlier generations lacked calculators, computers or models. We do need people who understand the underlying ideas well enough to use those tools intelligently, test their outputs and improve upon them.

The purpose of education is not to make the student imitate a machine.

It is to ensure that, when the machine produces something, the student knows what it means.

Read more →
1diE13…D4Bg Unverified · twetch

The alternative is not “no governance.” The alternative is governance made invisible.

If a small group of developers, maintainers and institutional gatekeepers can alter the protocol whenever they consider it necessary, then they possess control. Calling their decisions “upgrades” does not make the power disappear. It merely gives authority a more fashionable vocabulary.

A decentralised system is not one in which everyone may watch a handful of people rewrite the rules. It is one in which no handful of people can rewrite them at all.

Stable rules force ambition to compete within the system. Mutable rules allow the ambitious to capture the system itself.

So yes, I prefer a protocol that cannot be casually redesigned by whichever committee presently mistakes influence for wisdom.

When people can change the rules, they govern.

When they govern, they control.

And when control is concentrated, “decentralisation” becomes little more than a charming word printed on the chains.

Read more →
1diE13…D4Bg Unverified · twetch

Bitcoin does not have a king.

That was rather the point.

Yet those who proclaim decentralisation most loudly seem perpetually desperate to find a sovereign. They want Satoshi returned, seated upon a throne, and required to tell them which rules to follow, which changes to approve, and what Bitcoin is permitted to become.

It is the same impulse directed at John Galt in Atlas Shrugged. The system has failed, the institutions have exhausted themselves, and those responsible demand that the one person who refused their authority return and provide the answers.

They do not want freedom. They want a superior ruler who agrees with them.

But Satoshi’s answer is already there.

The protocol was released. The rules were established. The design was set in stone so that neither its creator nor any later committee could become sovereign over it.

Bitcoin requires no king because it was designed to make kings unnecessary.

You are free to build upon it, compete through it, and create whatever you can imagine. What you are not entitled to do is seize the foundation, rewrite the rules, and call your authority decentralisation.

They keep asking, “Who is Satoshi, and what would he tell us to do?”

The better question is why they need anyone to tell them at all.

John Galt refused to govern men who would not govern themselves.

Satoshi left a protocol that did not require him to return.

Read more →