Bitcoin-powered trust engine for the web

In Softwar, Jason Lowery theorizes about “bitpower protocols” and “proof-of-power wall APIs” that raise the physical cost of sending unwanted control signals—forming what he calls an “electro-cyber dome” around a digital system.

Chronicle is the practical implementation of of this idea. By adding persistent identity and shared memory it enables the following dynamic: A server can require a client to prove control of a pubkey with sufficient cost or credibility at stake. Credible actors pass through with little friction whereas unknown or harmful actors face a higher barrier, or are denied access altogether.

If the pubkey abuses that access, the server can publish a counter-signal against it. Other servers can immediately factor that warning into their own policies, raising the barrier or refusing the pubkey altogether. Instead of every defender maintaining their own blacklist, one defender’s signal can inform every other on the network. A local attack can trigger a global response among participating clients. In that sense, Chronicle can become a global cyber-immune system for the internet.

Escrow exists because a stranger can take your money and disappear.

We rarely use escrow when buying from an established business. It has a public history, a stable identity, a reputation, and legal exposure. The value of an ordinary purchase is usually far less than what the business risks by cheating.

Chronicle can create a similar accountability structure for pseudonymous trade. A pubkey can accumulate a public history of costly signals, endorsements, and oppositions. Before trading, a buyer can see the credibility that the other party is putting at risk and judge whether they have more to lose from cheating than to gain.

This does not guarantee honest behavior, but it does provide buyers with a reasonable basis for choosing who to put confidence in. When the counterparty has substantially more to lose than to gain, cheating becomes irrational.

Email is cheap to send and expensive to receive.

Hashcash was built around this problem: require proof-of-work for each message and bulk spam becomes expensive. But with Hashcash every message begins from zero as the system carries no persistent identity and history from one interaction to the next.

Chronicle adds those missing dimensions. A sender can attach Bitcoin cost to a specific message or verify an email address with a pubkey that has an established public history. The recipient chooses the threshold: sufficient credibility, sufficient cost, or some combination of both.

Credible senders pass through this email filter with little friction. A new sender with no history can still get through by putting more at stake. If spam comes through, the recipient can oppose the message, address, or pubkey, creating a public warning that other email clients can use. In this way, bulk spam becomes expensive while the system remains usable for legitimate senders.

The same signals can also be used to rank the inbox by importance, not just arrival time.

Civility begins when actions have consequences.

Michael Saylor points out that people say thing online they would never say face-to-face; that when you look behind a hostile post, you often find an account created three days ago. The platform can remove the account, but a Python script can spin up hundreds of accounts more. The identity is disposable, so consequences have nowhere to land.

His orange check proposal is simple: post a small Bitcoin security deposit, then let users accept replies and messages only from accounts that have done the same. If an account turns malicious, the platform can seize its deposit. Trolls and bot armies would have something to lose.

Chronicle extends this idea beyond a platform-controlled badge. A social client can accept replies from pubkeys with sufficient cost or credibility behind them, without requiring a real name. If someone abuses that access, users can publish a counter-signal against the post or pubkey. Other clients using Chronicle can see the warning immediately and decide to ignore it. The troll can discard the pubkey, but it would lose the history that was costly to acquire.

A convincing scam website can be created in minutes in the age of LLMs, and there is no recourse when the money and credit card information is eventually stolen.

Chronicle lets an operator cryptographically link a domain to a pubkey and put its accumulated credibility behind the site. A browser can consult the public record: who stands behind the domain, how much cost and credibility they have committed, and whether credible actors have supported or opposed it.

A site backed by a new pubkey can be treated with greater caution than a domain backed by a key with an existing history. If a site defrauds someone, victims can oppose the domain or the pubkey behind it. That warning becomes available to every browser using Chronicle.

A scammer can keep registering domains, but rebuilding credible history is harder.

Today, evidence about mint operators is scattered across Nostr posts, community lists, and personal recommendations.

With Chronicle, a mint operator can verify the mint’s domain with their pubkey, and put their existing credibility behind it. Other credible actors can publish costly endorsements or oppositions based on their experience with the mint.

A wallet can combine this public record with the amount a user intends to deposit and their tolerance for risk when recommending a mint. Chronicle makes it possible to see who stands behind the mint and whether they have sufficient credibility at stake to warrant a deposit of certain size. A mint trusted with 20,000 sats doesn’t need to be trusted with 20 million sats. Mint credibility can be matched to the value at risk.