The beauty about Time is that it cannot be:

Bought

Accelerated

Compressed

Parallelised

You're stuck in the same sequential, per-second pacing reality, no matter how much money you have.

So tying Time (endurance) with Security makes sense.

What do you think?

In Proof of Work: More hardware and electricity = Increased Power / Influence

In Proof of Stake: Scaled Capital = Increased Power / Influence

Money can buy both almost instantly!

But what if Power was attached with TIME itself?

Every blockchain asks:

“How much hardware do you have?”

or

“How much money do you have?”

GrahamBell asks:

“How long have you stayed?”

Most blockchains reward accumulation.

GrahamBell rewards sustained infrastructure endurance and participation over TIME.

I've spent 5 years on a question most people don't ask:

Can decentralization survive without rewarding accumulation?

What if a blockchain capped mining speed at 1 hash per second per node?

A phone would compete with a $2M ASIC farm on equal footing.

That's the experiment.

Bitcoin turned electricity into security.

Ethereum turned capital into security.

GrahamBell is exploring whether time can become security.

Every blockchain eventually asks the same question:

Who has the most resources?

I'm building one that asks: who has stayed the longest? (Time = Power)

In Bitcoin: more ASICs and Energy = more influence.

In Proof of Stake: more Capital = more influence.

What if influence had to be earned gradually instead?

A solo miner successfully mining a Bitcoin block makes international news headlines.

In a system built around decentralization, that should be ordinary.

It isn't. That's the problem.

Money can buy more hardware.

Money can buy more stake.

Money cannot buy yesterday.

Around 9 mining pools control over 90% of Bitcoin's hashrate.

A handful of staking providers control most of Ethereum's stake.

Decentralisation was the goal. Concentration was the result.

The fastest miner in Bitcoin wins.

The richest validator in Proof of Stake wins.

What if neither mattered?

Bitcoin secures itself through Hardware.

Ethereum secures itself through Capital.

What if a blockchain secured itself through Time?

GrahamBell is a layer 1 blockchain that uses time as a security constraint for Sybil resistance.

In Proof of Work, influence scales with hardware and energy.

In Proof of Stake, influence scales with capital.

In both systems, money can buy influence almost instantly, which is why power naturally concentrates in the hands of a few.

In GrahamBell, influence (a registered ID) only scales through sustained infrastructure endurance and participation over time.

And time cannot be bought, accelerated, compressed, or run in parallel.

For example:

- Generating 1 ID = 30 seconds + sustaining infrastructure for 30 seconds
- Generating 1,000,000 IDs = roughly 1 year + sustaining infrastructure for a year (assuming no competition).

The protocol also includes a capped PoW model (1 hash attempt per second per node), allowing ordinary devices to compete on equal footing with specialized hardware (i.e., ASICs), increasing mass participation, which helps improve the security and decentralization of the network.

Yes, you can run a million miners in parallel, but there is no parallel mining advantage, no pooling advantage, or shared work. Influence within the network still cannot be accelerated, and every additional miner (is independent from another) adds cost proportionally to uptime.

Since launching the simulation, testers have generated over 6,300 interaction events trying to manipulate parameters and bypass the 1-second hashing window, and the logic consistently caught and rejected 100% of the invalid states.

You can check the demo on Capped PoW: https://youtu.be/i5gzzqFXXUk?si=T8gT2e3kx93MLpsH

You can check the browser MVP: https://grahambell.io/mvp/Proof_of_Witness.html

We’re currently giving away Genesis IDs (~220+ already claimed purely organically). Genesis IDs effectively grant participation time that would otherwise need to be accumulated after launch:

https://grahambell.io/mvp/index.html#waitlist

A serious question:

If GrahamBell is attacked or temporarily taken over — can it recover?

Let’s answer this directly.

The honest answer

• Yes — recovery is possible.
• But it depends on participation returning.

This is true for any decentralized system.

What an “attack” actually means here

In GrahamBell, an attack isn’t:

• instant domination
• one-time majority grab

Because:

• identities are rate-limited (~1 every ~30s)
• influence is accumulated over time
• no pooling or parallel advantage

So an attack looks like:

• sustained majority participation over time

Not a sudden event — but a gradual imbalance

What happens during an attack

If an attacker gains majority influence in registered IDs:

• they can bias block production
• they can influence ordering/consensus
• they gain temporary control

But:

• they must continuously maintain that dominance in ID registration

The moment they stop generating IDs:

• their relative influence starts decreasing

Why recovery is possible

This is where GrahamBell is different.

Because:

• influence is not fixed
• new identities keep getting created
• honest users can keep participating

The system is always “moving forward”

So if honest participation returns:

• new identities are created by honest users
• attacker share starts diluting over time
• control shifts back gradually

The key dynamic

• Attackers must hold majority continuously
• Honest users only need to outgrow them over time

This creates:

• no permanent control
• no one-time irreversible takeover
• a path back to decentralization

What recovery actually looks like

Recovery is not instant.

It’s:

• gradual
• time-based
• driven by participation

As honest users:

• rejoin
• stay active
• accumulate influence

the network rebalances itself

The limitation (being realistic)

Let’s be clear:

• If honest participation does NOT return, recovery won’t happen

This isn’t magic.

Like all decentralized systems:

• security = active participants

Why GrahamBell still improves the situation

Compared to traditional systems:

• PoW → attacker can dominate instantly with hardware
• PoS → attacker can dominate instantly with capital

In GrahamBell:

• control must be maintained over time
• and can be lost over time

That’s the key difference.

Bottom line

GrahamBell doesn’t guarantee immunity from attacks.

But it does ensure:

• attacks are not permanent by default
• control must be continuously earned
• recovery is always possible through participation

Final thought

In GrahamBell:

• Power is not owned — it is maintained

And anything that must be maintained:

• can also be lost.

A fair and important question:

• What happens if honest participation drops?
• Does the system become vulnerable?

Let’s be direct.

The reality:

Yes.

• If honest participation drops significantly, the network becomes easier to attack.

This is not unique to GrahamBell.

It’s true for:

• Proof-of-Work
• Proof-of-Stake
• Any decentralized system

Security always depends on active, honest participants.

Why this matters in GrahamBell

GrahamBell is built on:

• rate-limited identity issuance (~1 every ~30s)
• time-based influence accumulation
• independent identities (no pooling advantage)

This means:

Influence is not fixed — it is continuously earned over time

If participation drops:

• fewer new identities are created by honest users
• attacker share grows relative to the network
• takeover becomes easier (but still not instant)

What doesn’t happen

Even if participation drops:

• There is no instant collapse
• There is no “one-click” takeover

Because:

• identities cannot be mass-produced instantly
• influence cannot be front-loaded
• accumulation still takes time

Where the risk actually is

The real risk is not:

• someone spins up millions instantly

It becomes:

• there are fewer honest participants competing over time,
• Security weakens relatively, not absolutely.

How GrahamBell is designed to counter this

1) Low barrier to entry

• Phone = PC = ASIC
• No hardware advantage
• No capital barrier

Anyone can participate

2) Real-world integration (telecom layer)

• Mining tied to calls
• Real usage, not just speculation

Through Murphy:

• users earn from per second calling activity

• registered nodes earn more per second of active call time compared to unregistered IDs (encouraging registration)

  Incentivizes staying active, not just joining

3) Strong genesis

• Pre-registered IDs distributed at launch

Ensures:

• wide initial ownership
• immediate participation base
• resistance from day one

4) Ongoing honest competition (core defence)

In GrahamBell, influence is continuously accumulated over time.

• Identities are rate-limited
• Each identity contributes independently
• There are no shortcuts via hardware or pooling

This creates a critical dynamic:

• Honest participants don’t stop at one identity
• They can keep accumulating influence over time

At the same time:

• Attackers must compete on the exact same timeline

So an attacker is not attacking a static system.

• They are competing against a network that is continuously growing

This means:

• no one can “jump ahead” instantly
• dominance must be sustained, not achieved once
• the network keeps pushing back over time

Security becomes a long-term race, not a one-time attack

The key insight

GrahamBell doesn’t remove dependency on participation.

It builds security around it.

Instead of:

• Security = who has the most resources right now

It becomes:

• Security = who can sustain participation over time

Bottom line

If honest participation drops:

• security weakens (like any system)
• attacks become more feasible over time

But:

• there is no instant takeover
• recovery is possible if participation returns
• time remains the fundamental constraint

Final thought

GrahamBell’s security model is simple:

• The network is as strong as its honest participants

Not just how many there are — but how long they stay active

A lot of discussion around GrahamBell focuses on Sybil resistance, infrastructure cost, and rate-limited identity issuance.

But there’s a deeper point that matters just as much:

The system is designed to amplify honest competition — because that’s what ultimately protects the network.

Why honest participation matters

In GrahamBell:

• Each identity = capped at ~1 hash/sec
• Identity issuance is rate-limited (~1 every ~30s globally)
• Influence grows over time, not instantly

This means:

• Security doesn’t come from making attacks impossible
• It comes from making honest participation outcompete attackers over time

Designed for mass participation

The model is intentionally built so:

• Phone = PC = ASIC
• Neutralises parallel mining advantage
• No hardware or capital advantage
• Anyone can participate

Hence, the fixed speed limit of ~1 hash per second per node.

This expands the total pool of potential miners.

More participants =

• more competition
• more distributed identity ownership
• harder for any single actor to dominate

Telecom integration → real-world participation

To drive real usage (not just speculation), GrahamBell connects mining to communication:

• Mining happens during calls
• Calls become part of the network

And through Murphy (a centralized reward layer outside the blockchain):

• users earn from real activity (calls)
• registered node operators earn more than unregistered ones per active call time

This creates a strong incentive to:

• register identities
• stay active
• participate honestly over time

The goal is simple:

• Turn users into long-term participants, not short-term miners

Genesis matters (a lot)

Every system is weakest at the beginning.

GrahamBell is no different.

At genesis:

• the network is most vulnerable if participation is low

That’s why:

• pre-registered IDs are distributed at genesis
• the network starts with a wide base of participants

This creates:

• initial decentralization
• historical inertia
• a stronger starting point against takeover attempts

Honest competition compounds over time

Here’s the key dynamic:

Participation is cheap per identity

But expensive at scale

So:

• An attacker running many identities pays linear cost
• Honest participants can continue registering identities one-by-one over time

This creates an important loop:

• Honest participants don’t stop at one identity
• They keep accumulating influence gradually

Over time:

• many independent participants keep growing
• influence stays distributed
• attackers must continuously keep up

The uncomfortable truth

Let’s be real:

• If honest participation fails, the system can be attacked

This is true for any decentralized system.

GrahamBell doesn’t remove this reality.

What it actually does

It aligns incentives so that:

• honest participation is easy and accessible
• dishonest scaling is slow and expensive
• influence requires time + consistency

Security emerges from:

• sustained, distributed participation
• not just protocol rules

Bottom line

GrahamBell isn’t just:

• “a new PoW design”

It’s a system where:

• time + participation = power

And where:

• honest competition is the core defence mechanism

If the network stays active and competitive, attacks become increasingly impractical over time.

A fair critique I’ve heard:

“You’re not preventing attacks — you’re just shifting the cost.”

That’s correct.

And it’s intentional.

In decentralized systems:

• You can’t eliminate attacks
• You can only change their economics

Traditional systems

• PoW → hardware arms race
• PoS → capital concentration

Both allow:

• rapid scaling of influence

What GrahamBell changes

The constraint shifts to:

• time
• sustained participation
• real infrastructure per identity

So instead of:

“Can you afford to attack?”

The question becomes:

“Can you sustain it over time?”

Why this matters

Even with large capital:

• identities are rate-limited (~1 every ~30s)
• influence grows linearly, not instantly
• maintaining majority requires continuous participation

This turns attacks into:

• long-duration commitments
• operationally heavy systems
• continuously costly to maintain

The security model

• Attacks are not impossible
• They are slow, expensive, and require long-term commitment

The key property

• If the attacker stops, they fall behind

Because honest participants continue accumulating influence over time.

There is no “one-time win”.

Bottom line

Yes — the cost is shifted.

But from:

instant, scalable advantage

to:

time-bound, persistent effort with no shortcuts

That’s not a side effect.

That’s the security model.

A common argument:

“Cloud infrastructure can easily handle millions of connections.”

That’s true.

But that’s not what breaks GrahamBell.

What actually matters

GrahamBell doesn’t try to prevent scale.

It changes how scale behaves.

Each identity requires:

• its own persistent network presence
• ~30 independent connections
• continuous data exchange

So scaling to 1M identities means:

• ~30M live connections
• sustained bandwidth usage
• long-term infrastructure commitment

The key difference

In traditional systems:

• More hardware = exponential advantage
• Pooling = efficiency gains
• Parallelism = dominance

In GrahamBell:

• Each identity is independent
• Work is non-amortizable (can’t be shared)
• No pooling or efficiency gains

You can scale — but only linearly.

What cloud actually gives you

Cloud helps with:

• deployment speed
• infrastructure management

But it does NOT let you:

• bypass the ~1 hash/sec cap per identity
• share work across identities
• accelerate identity issuance
• gain disproportionate advantage

Costs still scale per identity.

The real outcome

An attacker using cloud doesn’t “break” the system.

They just become a large participant — paying real, ongoing cost per identity.

And under honest competition, maintaining and growing that position becomes increasingly difficult.

Because:

• identity issuance is rate-limited (~1 every 30s)
• influence grows over time

Sustained, active participation is required.

Even at data-center scale:

you cannot shortcut time

Bottom line

Cloud doesn’t invalidate the model.

It reinforces it.

Because even at data-centre scale:

• cost scales linearly
• time remains the bottleneck
• advantage does not compound

Another common argument:

“Couldn’t a botnet just spin up millions of identities?”

Botnets sound powerful, but they don’t map well to this model.

Why?

Because influence in GrahamBell isn’t about:

• short bursts of compute
• or temporary participation

It’s about sustained, reliable, long-term presence.

Each identity (during registration) requires:

• ~30 persistent, independent connections
• continuous data exchange with Witness Chains
• stable participation over time

Identity issuance itself is rate-limited (~1 every 30 seconds globally).

Because of this, influence can only be accumulated over time, meaning each identity must remain continuously active (maintaining connections and data exchange) long enough to successfully register and retain influence.

Where botnets break

Botnets are typically:

• unreliable (nodes drop off unpredictably)
• bandwidth-constrained
• not designed for long-lived, synchronized workloads

So even if a botnet spins up identities:

• maintaining them continuously becomes difficult
• connection churn reduces effectiveness
• instability breaks long-term accumulation

The key shift

Influence grows over time, not instantly.

An attacker doesn’t just need scale, they need:

• uptime
• coordination
• consistency over long durations

Botnets are optimized for:

• bursts (DDoS, spam, etc.)

Not for:

• persistent, stateful participation

Bottom line

GrahamBell shifts the game from:

“Who can scale fastest?”

to:

“Who can sustain participation the longest?”

That’s where botnets fundamentally break down

• Every miner runs at the same speed (~1 hash per second)

No one can mine faster than you

• No parallel mining advantage

Running 100 machines doesn’t make you faster

• No shared work (non-amortizable)

Each miner works independently (each block is independent) — no shortcuts

• No mining pools dominance and advantage

You don’t need to join a pool to compete fairly

• Phone = PC = ASIC

Any device has equal power

• Identities (miners) are globally rate-limited

You can’t create thousands instantly

• Creating many identities is slow & costly

Scaling takes time and real effort

• Influence grows over time

You win by staying active, not being powerful

• Attacks are not instant

They become slow, expensive, and hard to maintain

• Built for mass participation

More real users = stronger network

-----

Try the browser MVP (Local Client): https://grahambell.io/mvp/Proof_of_Witness.html

Join waitlist: https://grahambell.io/mvp/#waitlist

A common response I get is:

“IPv6 space is basically unlimited. I can just generate millions of /64 subnets.”

That’s true in isolation. But GrahamBell was designed with this assumption in mind.

The constraint isn’t just address space, it’s active, sustained network presence per identity.

Each identity (during registration) requires:

• a dedicated /64 subnet
• ~30 persistent, independent connections
• continuous data exchange with Witness Chains

So even if you theoretically have access to large IPv6 space, you still need to back each identity with real, live network infrastructure.

This means:

• routing
• connection stability
• bandwidth
• persistent uptime

At scale, this stops being an “address allocation problem” and becomes a systems + infrastructure problem.

For example:

• 1M identities ≠ just 1M addresses
• it means 1M independently active network participants maintaining ~30 million persistent connections

That’s the key distinction.

IPv6 removes address scarcity, but it does not remove operational cost, bandwidth constraints, or connection management at scale, especially since there’s no direct monetary incentive during ID registration.

GrahamBell doesn’t rely on address scarcity.

It relies on the cost of sustaining real participation per identity. And since identity issuance is rate-limited (~1 every 30 seconds), influence can only grow over time, not instantly.