Skip to content

Commit e326c30

Browse files
sanityclaude
andcommitted
Improve contract explanation: general-purpose state machines
Reframe the blockchain comparison to emphasize that Freenet contracts are general-purpose state machines for any shared data, not just transaction processors. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent d02c22c commit e326c30

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

hugo-site/content/resources/manual/tutorial.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,9 +32,9 @@ data on your device), and **UI** (web interface). See the
3232
The contract is your application's backend. It runs as WebAssembly on untrusted peers across the
3333
network.
3434

35-
> **Not blockchain contracts**: Unlike blockchain smart contracts that are broadcast to every node,
36-
> Freenet contracts are stored in a distributed hash table—each contract only exists on nodes that
37-
> need it. This makes the system scalable without practical limit.
35+
> **A different model**: Blockchain contracts are transaction processors replicated everywhere.
36+
> Freenet contracts are general-purpose state machines—they can model any shared data, from chat
37+
> to documents to games—and exist only on subscribing nodes. This scales without practical limit.
3838
3939
**Key properties:**
4040
- Defines what valid state looks like and how it can be modified

0 commit comments

Comments
 (0)