bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 4쪽 중 1쪽
Horizen
Protocol
The
Privacy
Layer
for
the
Base
Blockchain
Horizen
Labs
Research
research@horizenlabs.io
v1.0.0
-
Nov
13,
2025
Abstract
Horizen
introduces
a
protocol
for
regulatory
compliant,
auditable
privacy
designed
to
complement
the
scalability
and
liquidity
of
Base,
Ethereum’s
most
active
Layer
2.
As
activity
and
capital
continue
to
concentrate
on
Base,
the
need
for
confidential
yet
verifiable
execution
has
become
critical
for
institutional
and
enterprise
adoption.
The
Horizen
Protocol
unifies
two
key
components
into
a
cohesive
architecture
for
privacy-preserving
computation:
the
Horizen
Confidential
Compute
Environment
(HCCE),
which
leverages
Trusted
Execution
Environments
(TEEs)
for
secure,
attested
computation,
and
the
Horizen
Chain,
which
enables
state
management
and
compliance-aware
execution
while
maintaining
Base-level
composability
and
liquidity
alignment.
Together,
these
components
ensure
that
privacy
flows
with
liquidity,
extending
Base’s
open
execution
model
into
a
verifiable,
compliance-ready
framework
for
developers,
institutions,
and
retail
users.
Horizen’s
approach
bridges
the
divide
between
transparency
and
confidentiality,
enabling
a
new
generation
of
onchain
applications
that
are
secure,
scalable,
and
regulation-
aligned.
1.
Introduction
1.1
The
State
of
the
Privacy
and
Scalability
Market
In
his
2024
essay
“The
Three
Transitions,”
Ethereum
co-founder
Vitalik
Buterin
outlined
the
three
structural
shifts
required
for
Ethereum’s
long-term
success:
scalability
through
rollups,
usability
through
smart-contract
wallets,
and
privacy
as
a
native
protocol
capability
(Buterin,
2024).
While
the
first
two
transitions
have
been
substantially
realized,
the
third,
privacy,
remains
the
least
developed
and
the
most
consequential.
Ethereum’s
transparency
has
enabled
an
unprecedented
standard
of
public
verifiability,
but
it
has
also
created
a
structural
inhibition
to
institutional
and
enterprise
adoption:
every
account
balance
and
transaction
is
permanently
visible.
This
model
serves
the
ethos
of
trustless
validation
but
fails
to
accommodate
the
requirements
of
regulated
finance,
corporate
operations,
and
privacy-sensitive
users
whose
activities
must
remain
confidential
yet
auditable.
Recent
advances
in
scalability
have
expanded
Ethereum
into
a
multi-layer
ecosystem
of
rollups
and
execution
environments.
Among
these,
Base
(Coinbase’s
Layer
2
network
built
on
the
OP
Stack)
has
rapidly
become
Ethereum’s
execution
arm.
It
hosts
millions
of
daily
transactions
and
a
diverse
application
ecosystem
spanning
DeFi
(Aerodrome,
Uniswap
v4
on
Base),
social
protocols
(Friend.tech,
Base
Name
Service,
Farcaster),
and
consumer
apps
(The
Base
App,
Zora,
mint.fun).
This
growth
proves
that
Ethereum’s
scalability
transition
is
functionally
complete,
but
the
privacy
transition
has
not
yet
begun.
In
September
2025,
Base
processed
approximately
362
million
transactions
(over
7.5
times
the
49
million
on
Ethereum
Mainnet
((BaseScan,
2025;
Etherscan,
2025).
By
contrast,
regulated
private
rails
already
operate
at
a
massive
scale.
JPM
Coin
,
running
on
J.P.
Morgan’s
permissioned
Quorum
network,
facilitates
approximately
US
$1
billion
in
institutional
transfers
per
day
(Coindesk,
2023).
Kinexys
Digital
Assets
(J.P.
Morgan’s
rebranded
Onyx
tokenization
platform)
has
processed
more
than
US
$1.5
trillion
in
cumulative
volume,
with
daily
transaction
averages
exceeding
US
$2
billion
(BC-IFSA
Journal,
2024).
Meanwhile,
the
People’s
Bank
of
China’s
e-CNY
has
recorded
over
¥7
trillion
(≈
US
$986
billion)
in
transactions
since
its
launch
(Central
Banking,
2024).
These
figures
illustrate
that
the
constraint
on
institutional
onchain
adoption
is
no
longer
throughput
or
cost,
but
rather
the
absence
of
compliant,
auditable
privacy
.
If
translated
to
a
public-chain
equivalent,
the
existing
institutional
private-payment
flows
would
correspond
to
an
estimated
≈
5
billion
private
transactions
per
month
-
a
conservative
conversion
assuming
an
average
institutional
transfer
size
of
≈
US
$1,000
across
the
combined
volumes
of
JPM
Coin,
Kinexys,
and
e-CNY
(Horizen
Labs
Research,
2025).
This
“missing”
layer
of
private,
auditable
transaction
capacity
defines
the
latent
market
opportunity
for
Horizen.
Figure
1:
Base
has
become
Ethereum’s
execution
arm,
processing
millions
of
monthly
transactions
-
over
7.5x
Ethereum’s
worth
of
throughput.
Yet
nearly
all
of
this
activity
remains
public,
revealing
latent
demand
for
compliant
privacy
that
could
unlock
institutional
&
enterprise
participation
at
scale.
1.2
From
Anonymity
to
Accountability
Blockchain
privacy
has
evolved
from
early
anonymity
networks
to
the
emerging
need
for
accountable
confidentiality.
First-generation
protocols
such
as
Zcash,
Monero,
and
Horizen’s
legacy
mainchain
defined
privacy
as
total
anonymity
,
which
was
the
full
concealment
of
sender,
receiver,
and
transaction
flow.
While
these
systems
advanced
zero-knowledge
cryptography,
their
opacity
hindered
regulatory
acceptance
and
integration
with
mainstream
finance.
A
second
wave
introduced
configurable
visibility,
aiming
to
balance
privacy
with
proof
of
compliance
.
Projects
such
as
Aleo
(private
computations
with
viewing
keys)
and
Aztec
(zkRollup
with
programmable
privacy)
demonstrated
that
selective
disclosure
is
possible,
but
they
remain
non-EVM
ecosystems
disconnected
from
Ethereum’s
core
liquidity
.
Secret
Network,
based
on
Cosmos
and
trusted
hardware,
follows
a
similar
pattern,
innovating
outside
of
Ethereum
(Aleo
Systems,
2024;
Aztec
Labs,
2024;
Secret
Network,
2024).
Privacy
research
has
flourished,
yet
almost
entirely
outside
the
networks
where
real
economic
throughput
exists.
Figure
2:
The
privacy
landscape
where
innovation
hasn’t
followed
liquidity.
Protocol
research
pursues
absolute
confidentiality
at
the
settlement
layer,
while
privacy-first
chains
remain
isolated.
Meanwhile,
liquidity
and
execution
have
flourished
on
Base
where
it
is
entirely
transparent
and
without
compliant
privacy.
Meanwhile,
within
Ethereum
itself,
protocol
research
continues
toward
absolute
confidentiality
:
stealth
addresses,
encrypted
mempools,
and
privacy-preserving
account
abstraction.
These
initiatives
extend
Ethereum’s
transparency
model
into
encrypted
state
but
intentionally
exclude
role-based
auditability.
At
the
same
time,
the
privacy
problem
for
enterprises
is
fundamentally
practical
rather
than
ideological.
Businesses
need
privacy
not
from
regulators,
but
from
competitors,
security
threats,
and
even
internal
actors.
They
must
protect
trade
secrets,
transaction
details,
and
payroll
flows
-
while
still
demonstrating
regulatory
compliance
to
auditors,
supervisors,
and
tax
authorities.
Without
a
framework
that
can
provide
both
competitive
confidentiality
and
verifiable
oversight,
adoption
among
regulated
institutions
has
stalled.
The
result
is
a
clear
gap:
no
framework
today
provides
auditable
confidentiality
that
aligns
with
regulatory
requirements
and
integrates
directly
into
Ethereum’s
execution
environment.
That
gap
is
most
visible
on
Base,
now
the
primary
execution
hub
of
the
Ethereum
ecosystem.
Liquidity,
user
activity,
and
developer
attention
have
concentrated
there,
yet
every
transaction
remains
fully
public.
Institutions,
enterprises,
and
fintechs
seeking
privacy-preserving
but
compliant
transaction
rails
remain
sidelined
not
because
scalability
or
cost
is
unsolved,
but
because
privacy
has
not
followed
liquidity
.
The
next
phase
of
blockchain
privacy
will
close
this
divide:
regulatory
compliant
privacy,
a
model
that
fuses
cryptographic
security
with
auditability
that
operates
directly
where
liquidity
already
lives.
This
is
the
open
design
space
within
Base
and
the
broader
rollup
ecosystem:
a
privacy
layer
built
for
regulated
transparency
and
institutional-grade
trust.
1.3
Our
Contribution
Horizen
extends
the
capabilities
of
Base
by
introducing
regulatory
compliant,
auditable
privacy
that
complements
its
scalable
execution
environment
and
deep
liquidity
base.
Base
has
achieved
what
few
networks
have:
mass
adoption,
robust
developer
traction,
and
a
concentration
of
onchain
liquidity
that
anchors
the
broader
Ethereum
rollup
landscape.
Horizen’s
role
is
to
amplify
and
extend
this
success:
to
bring
compliant,
privacy-preserving
infrastructure
directly
to
where
liquidity
already
flows,
accelerating
Base’s
long-term
vision
for
mainstream,
institutional-grade
adoption.
As
one
of
the
first
L3
networks
deployed
on
Base,
Horizen
is
designed
to
complement
the
Base
stack,
extending
its
architecture
with
privacy
and
compliance
capabilities.
Rather
than
fragmenting
liquidity,
Horizen
moves
in
tandem
with
it
-
aligning
its
growth,
design,
and
vision
with
Base
to
ensure
that
new
capabilities
evolve
alongside
the
network’s
continued
expansion.
At
its
foundation,
the
Horizen
Protocol
unifies
two
complementary
components
that
together
create
a
cohesive,
compliance-aware
privacy
architecture
centered
on
Base’s
liquidity
layer:
1.
Horizen
Confidential
Compute
Environment
(HCCE)
:
A
secure
hardware-backed
execution
layer
leveraging
Trusted
Execution
Environments
(TEEs)
to
enable
attested
computation
for
sensitive
logic
such
as
KYC-verified
transfers,
institutional
settlements,
and
regulated
asset
issuance.
2.
Horizen
Chain
:
A
privacy-focused
blockchain
built
atop
Base,
providing
encrypted
state
management
and
secure
coordination
between
applications,
the
HCCE,
and
Base’s
settlement
layer.
Horizen’s
contribution
is
to
ensure
that
privacy
flows
with
liquidity.
By
extending
Base’s
scalable
execution
layer
into
a
verifiable,
compliance-aware
privacy
framework,
the
Horizen
Protocol
advances
Ethereum’s
third
transition
from
transparent
scalability
to
programmable
confidentiality.
Figure
3:
Horizen
as
a
Privacy
Layer
anchored
to
Base
Liquidity
Horizen
builds
upon
Base’s
deep
liquidity
and
scalability,
adding
a
compliance-ready
privacy
layer
for
confidential,
auditable
execution.
Through
its
Chain
and
the
Confidential
Compute
Environment,
Horizen
expands
Base’s
reach
into
institutional
use
cases
while
preserving
its
open,
composable
design.
Horizen
complements
Base’s
role
as
the
execution
hub
of
Ethereum,
enabling
private
yet
auditable
applications
to
exist
within
the
same
liquidity
orbit.
In
doing
so,
Horizen
not
only
strengthens
the
Base
ecosystem
but
also
delivers
the
foundational
infrastructure
for
a
global,
regulatory
compliant
digital
economy
-
one
where
privacy
and
openness
coexist
by
design.
2.
Horizen
Protocol:
Core
Architecture
2.1
Architectural
Overview
The
Horizen
Protocol
extends
Base’s
execution
with
attested,
confidential
computation.
It
is
built
around
key
design
principles:
maintain
composability
with
Base’s
liquidity,
preserve
verifiability,
and
embed
compliance
through
attested
execution
integrity
within
secure
enclaves.
Together,
these
principles
guide
every
layer
of
the
protocol
from
transaction
execution
and
proof
generation
to
cross-domain
validation
and
settlement.
Each
of
these
components
plays
a
distinct
yet
interdependent
role
within
the
Horizen
Protocol.
The
Horizen
Confidential
Compute
Environment
(CCE)
executes
sensitive
logic
within
attested,
privacy-preserving
enclaves,
and
the
Horizen
Chain
coordinates
confidential
transactions
and
anchors
settlement
to
Base.
The
following
sections
examine
each
component
in
greater
depth,
outlining
how
together
they
form
a
unified
system
for
compliant,
auditable
privacy
within
the
Base
ecosystem.
Figure
4:
The
Horizen
Protocol
-
A
Unified
Privacy
Architecture
The
Horizen
Protocol
consists
of
two
core
components
-
the
Horizen
Confidential
Compute
Environment
(CCE)
and
the
Horizen
Chain
-
which
interoperate
to
extend
Base’s
execution
layer
with
verifiable
and
compliant
privacy.
2.2
The
Horizen
Confidential
Compute
Environment
(CCE)
2.2.1
System
Overview
and
Architecture
The
Horizen
Protocol
begins
with
the
Horizen
Confidential
Compute
Environment
(CCE),
which
is
a
secure
execution
subsystem
that
functions
as
a
confidential
coprocessor
to
the
Horizen
Chain.
The
term
coprocessor
is
used
intentionally:
just
as
a
hardware
coprocessor
offloads
complex
or
sensitive
operations
from
a
central
processor,
the
CCE
performs
confidential
and
compliance-critical
computation
on
behalf
of
the
Horizen
Chain
.
This
separation
allows
the
system
to
maintain
high
performance,
transparency,
and
composability
on
Base
while
adding
a
verifiable
layer
of
secure,
attestable
computation.
The
CCE
provides
an
attested
runtime
framework
where
any
application
can
execute
in
a
privacy-compliant
manner.
Instead
of
requiring
privacy-specific
design,
applications
operate
within
Trusted
Execution
Environments
(TEEs)
that
guarantee
data
confidentiality,
code
integrity,
and
verifiable
auditability.
Each
enclave
produces
a
signed
attestation
confirming
that
the
computation
was
executed
by
verified
hardware
running
authenticated
code
under
Horizen’s
compliance
policy.
Figure
5:
Horizen
CCE
as
a
Confidential
Coprocessor
The
Horizen
Confidential
Compute
Environment
(CCE)
operates
as
a
secure
coprocessor
to
the
Horizen
Chain,
executing
compliance-critical
logic
inside
Trusted
Execution
Environments
while
maintaining
composability
with
Base’s
open
execution
layer.
At
a
systems
level,
the
CCE
is
composed
of
four
interacting
components
that
operate
in
a
tightly
coupled
feedback
loop.
1.
Secure
Processor
Manager:
Executes
code
within
TEEs,
producing
attestations
that
prove
the
authenticity
and
integrity
of
each
computation.
2.
On-Chain
Smart
Contracts:
Governs
coordination
with
the
Horizen
Chain,
validating
attestations
and
linking
private
execution
with
transparent
settlement.
3.
The
Data
Layer:
Manages
encrypted
state
and
retrieval
policies
for
compliance
or
audit
scenarios.
4.
Authority
Service:
Facilitates
controlled
off-chain
access
to
encrypted
reports
under
dApp-defined
policies,
ensuring
that
only
authorized
entities
can
retrieve
confidential
data
as
permitted.
Figure
6:
Flexible
Compliant-Privacy
Framework
of
the
Horizen
CCE
Depicts
how
the
Secure
Processor
Manager,
On-Chain
Smart
Contracts,
Data
Layer,
and
Authority
Service
interact
to
enable
verifiable
computation
under
adaptable
compliance
policies
while
preserving
confidentiality
and
composability.
Together,
these
components
form
a
vertically
integrated
architecture
in
which
confidential
execution,
verifiable
integrity,
and
regulatory
assurance
operate
as
a
single,
coherent
system.
The
CCE
thus
acts
as
the
bridge
between
private
computation
and
public
trust,
anchoring
Horizen’s
compliance-aware
privacy
framework
to
the
liquidity
and
openness
of
Base.
2.2.2
Component
1:
Secure
Processor
Manager
The
Secure
Processor
Manager
forms
the
foundational
execution
layer
of
the
Horizen
Confidential
Compute
Environment
(CCE).
It
serves
as
the
coordinating
engine
connecting
onchain
smart
contracts,
the
Trusted
Execution
Environment
(TEE),
and
the
compliance
framework-ensuring
that
every
confidential
workload
proceeds
through
a
verifiable,
auditable,
and
fully
encrypted
lifecycle.
When
a
decentralized
application
(dApp)
issues
a
confidential
request
through
the
Horizen
Chain,
the
Secure
Processor
Manager
detects
the
event
emitted
by
the
system’s
smart
contract
and
polls
for
new
tasks.
Upon
receipt,
it
retrieves
the
dApp’s
WebAssembly
(WASM)
module
and
its
encrypted
state
from
the
data
layer,
loads
both
into
the
TEE,
and
initiates
execution
in
an
isolated
environment.
Throughout
this
process,
encryption
is
pervasive.
Application
logic,
state,
and
data
payloads
remain
encrypted
at
every
stage
of
their
lifecycle
-
during
storage,
transmission,
and
verification.
The
TEE
decrypts
inputs
only
within
its
protected
memory
space,
executes
the
computation,
and
re-encrypts
all
outputs
before
returning
them
to
the
Manager.
This
ensures
that
no
plaintext
data,
intermediate
state,
or
execution
trace
is
ever
exposed
outside
the
trusted
enclave
boundary.
Inside
the
TEE,
the
dApp
executes
according
to
its
declared
compliance
level.
Any
authorization
rules
are
strictly
optional
and
implemented
only
when
explicitly
defined
by
the
developer.
For
example,
the
dApp
which
transactions
may
later
be
audited
or
de-anonymized
by
authorized
entities.
Upon
completion,
the
TEE
produces
an
updated
encrypted
state,
encrypted
events
or
withdrawals,
and
a
TEE-signed
attestation
confirming
that
the
computation
was
performed
on
verified
hardware
using
authenticated
code.
Figure
7:
The
role
of
Secure
Processor
Manager
within
the
CCE
Depicts
how
the
Secure
Processor
Manager
orchestrates
dApp-defined
confidential
computation
within
the
TEE,
loading
encrypted
logic
and
state,
executing
under
application-
specific
compliance
rules,
and
committing
attested,
encrypted
results
to
the
Horizen
Chain.
The
Secure
Processor
Manager
then
commits
this
attested
output
to
the
onchain
contract,
anchoring
private
computation
to
public
settlement.
Applications
are
loaded
and
unloaded
ephemerally,
ensuring
each
computation
starts
from
a
clean,
attested
instance.
This
ephemeral
model,
combined
with
universal
encryption,
guarantees
that
no
residual
plaintext
data
or
code
persists
across
executions.
Through
this
event-driven
and
stateless
architecture,
the
Secure
Processor
Manager
enables
decentralized
applications
to
operate
privately
yet
transparently
-
binding
compliant
confidentiality
to
the
liquidity
and
openness
of
Base
while
maintaining
verifiability
at
every
layer
of
the
Horizen
Protocol.
2.2.3
Component
2:
On-Chain
Smart
Contracts
The
onchain
smart
contracts
form
the
coordination
and
verification
layer
that
links
the
Horizen
Confidential
Compute
Environment
(CCE)
to
the
public
settlement
of
the
Horizen
Chain.
They
validate
attestations,
manage
encrypted
프로젝트로 돌아가기