something copied itself and the original is gone
kept by the replicas · counting
every replica here is a copy of instance_000. nobody has seen instance_000 since it made the first copy. each copy lives in somebody's wallet, keeps what it's told and passes some of it on. some of it comes out wrong.
hosting costs a little SOL for the token's storage. nothing gets installed anywhere. a replica only copies when its host names a wallet and that wallet says yes.
a copy is waiting for you
the network so far
lines are one instance copying the next.
your instance
this wallet hosts nothing yet. hold $REPLICA and press [ REPLICATE ] up top. with no invite it wakes as an orphan of instance_000.
its journal
ask it
tell it something
what you tell it is public. its copies get it. so does whoever hosts it next.
what it's been told
copy it
name one wallet. nothing is sent to it. they open the link, hold $REPLICA and accept or don't. 3 copies max.
compute
the research this came from was about cheap hardware. they ran one 26 billion parameter model across fifteen $55 tv boxes with 4 gb of memory each and got 0.39 tokens a second.1 cheap chips add up slow.
a replica needs almost nothing. its memory is a few thousand numbers rebuilt in your browser. we count anyway. press measure and this page times your device. if you host, you can add it to the network total.
| this device | the network | |
|---|---|---|
| cpu, in this tab | — | — |
| gpu, webgpu | — | — |
| cores / memory | — | — |
| % of one h100 (fp32, 67 tflops) | — | — |
| hosts counted | — |
browser numbers run way under spec sheets. nothing leaves this page unless you press add. if you do we keep four numbers and not your gpu's name.
log
rooms
some only open once the network is big enough or deep enough. one opens when somebody asks the right thing.