WRITE LOCK
TWO TRANSACTIONS RUN AT ONCE UNLESS THEY TOUCH THE SAME ACCOUNT.
An experiment in declared access, parallel lanes, and the etiquette of shared state.
MOST THINGS ARE NOT IN EACH OTHER'S WAY.
A single-file queue treats every transaction as a possible collision with every other. Most are not. A payment between two strangers has nothing to do with a trade on the far side of the network.
If each transaction says in advance what it will read and what it will write, the unrelated ones can be told apart from the contested ones, and only the contested ones need to wait.
MARK THE ACCOUNTS. WATCH THE LANES.
Click grid cells to cycle between Untouched (-), Read (R), and Write (W). Observe how locks construct parallel execution steps.
| TX ID | ACCT A | ACCT B | ACCT C | ACCT D | ACCT E |
|---|
THE WHOLE RULE FITS ON THREE CARDS.
Access declarations dictate parallel eligibility instantly before execution starts.
READ / READ
Both may look at once. Nothing changes, so nothing collides.
SHARE LANEREAD / WRITE
One of them changes it. They take turns.
WRITE WAITSWRITE / WRITE
Both change it. One at a time, always.
EXCLUSIVE LOCKPLEASE HOLD.
conflicts: 3
steps: 3
waiting on: account C
RULES OF THE LANE.
WRITE LOCK / $LOCK
Write Lock is a community-driven Solana meme coin inspired by parallel execution and the plain idea of declaring what you touch. The token is the cultural artifact. The schedule is the story.
| PROJECT | Write Lock |
| SYMBOL | $LOCK |
| NETWORK | Solana |
| PLATFORM | pump.fun |
THE SCHEDULED PATH
DECLARED
An idea names what it will touch.
SCHEDULED
People find lanes that do not cross.
RUNNING
Many things happen at once, politely.
UNKNOWN
Whatever is next in the queue.