aboutsummaryrefslogtreecommitdiffstats
path: root/src/swarm
Commit message (Collapse)AuthorAgeFilesLines
...
* add simulation testtv13 days1-1/+4
|
* require catch-up source to make progresstv13 days2-1/+92
|
* late messages don't flip peer's epoch backtv13 days3-12/+56
|
* allow to persist documenttv13 days1-22/+145
|
* add files module to consistently track statstv13 days3-91/+34
|
* warn about unresolvable seeds once; log successtv13 days1-7/+22
|
* add disk I/O statstv13 days3-24/+78
|
* add possibility to start with a documenttv13 days1-4/+61
| | | | The --recover-from option allows a node start with a given document.
* add state filetv14 days4-2/+222
| | | | | This allows storing the swarm ID and additionally discovered seeds, which prevents a formerly genesis node to start a new document.
* put swarm ID into the documenttv14 days1-3/+19
|
* add genesis flag and never give uptv14 days1-65/+87
| | | | | | | | | The --genesis flag has been introduced to start with a new document. This prevents restarts to accidentally start with a new document and accept reads/writes, causing a second swarm to appear. Additionally, bootstrapping doesn't timeout anymore as that's of no use for nobody.
* bound stable-hub degreetv2026-10-241-4/+46
| | | | | | Each stable member can be preferred at most by 4*k members. The budget is spent in key order, which is the same on every node, so the graph stays deterministic, symmetric and connected.
* coalesce announcementstv2026-10-241-2/+56
|
* cache headstv2026-10-243-6/+11
| | | | To reduce the number of write locks, heads are now cached.
* being caught up needs some headstv2026-10-241-5/+9
| | | | | | | | | | | A sync message from a ready peer only completes the initial sync if that peer has at least one head. A peer with an empty document can no longer make a joiner ready on an empty store: a misconfigured second swarm, or a genesis node in its first seconds. Effect on a brand-new swarm: a joiner now waits until the genesis node has registered itself in the member list, which happens within about 5 s of it becoming ready.
* put remake content into blobstv2026-10-241-4/+21
|
* add chunked download and use it during rejointv2026-10-245-1/+502
|
* add electoratetv2026-10-241-8/+101
| | | | | For an upcoming change in remake coordination, nodes now maintain their self-assessed liveness in the document.
* aliases are not in logs (fixup)tv2026-10-241-1/+1
|
* measure document saved-size only after changestv2026-10-241-17/+39
|
* add endpoint to export the documenttv2026-10-241-0/+9
| | | | GET /admin/document to retrieve the automerge document.
* add node aliasestv2026-10-241-11/+78
|
* add throughput statstv2026-10-244-1/+192
|
* add propagation statstv2026-10-242-0/+89
|
* add swarm statstv2026-10-247-1/+235
|
* add traffic countertv2026-10-241-0/+4
| | | | | | | | | | This introduces a new wrapper that counts messages and payload bytes per peer, split by kind (hello, helloReply, sync, ping, pong), each sent, received and refused. The traffic counter goes around the firewall, which means messages dropped outbound are still counted as sent, and messages dropped inbound don't count as received.
* nodes prefer stable neighbourstv2026-10-241-10/+89
|
* assess swarm stabilitytv2026-10-244-11/+321
|
* record RTT sampling instanttv2026-10-242-27/+95
|
* prefer closer sources to catch uptv2026-10-241-3/+42
|
* record RTT from keepalive messagestv2026-10-244-14/+130
|
* pull missing changestv2026-10-245-5/+159
| | | | | | Nodes push changes to their neighbours but don't relay them directly. In a partial mesh, nodes can learn about missing changes via keepalive messages and can pull them from their neighbours.
* find reachable neighbourstv2026-10-242-55/+132
|
* sync with neighbourstv2026-10-243-4/+142
|
* add neighbour graphtv2026-10-242-0/+180
|
* add member registrytv2026-10-243-0/+69
|
* use nonce in handshaketv2026-10-241-2/+14
| | | | | To prevent stale hello replies to cause joins and thus stale sessions, each run gets a random ID, which used as nonce in the handshake.
* consolidate backoff codetv2026-10-241-29/+15
|
* retry using fresh messagestv2026-10-241-158/+127
| | | | | Don't store encoded messages but retry using a newly generated one. That way any accumulated changes can be delivered at once.
* drop stall breaker; resend needed changestv2026-10-241-65/+21
| | | | | | The stall breaker was superseded by regular re-handshaking Re-handshaking also gets triggered, when a node needs some of the heads its peer believes it has already sent. In that case the peer now resends what's needed.
* no heal during catch-uptv2026-10-231-1/+6
|
* peers that just became ready get syncstv2026-10-231-0/+9
| | | | | | When keepalive says ready and we didn't have taht on record before, the peer is queued for sync. Hello and hello reply don't do this because the handshake already queues a sync.
* both sides may open sync after resettv2026-10-233-42/+28
| | | | | | | | | | Ready nodes will leave the first message to the pear that isn't ready. Hello and hello reply now carry ready, so readiness is known from the very first contact, before any sync. Together with the sync messages and keepalives, reports_ready is always current. After epoch switch, pings go to everyone except ready members already on the new epoch, these learn from the lagging peer's opening.
* perform handshake in one round triptv2026-10-233-78/+68
|
* drop pre-membership sync messagestv2026-10-233-43/+10
| | | | | The handshake resets the session anyway, and the sender's reply timeout resends what still matters.
* bump number of heads in keepalive messagestv2026-10-231-0/+1
| | | | | Instead of arbitrarily limiting the number to 16, allow filling keepalive messages as long as they don't cause mycelium to chunk it.
* probe sync source during catch-uptv2026-10-233-106/+14
| | | | This allows changing sources without the fixed 30 s stall duration.
* enrich keepalive contenttv2026-10-232-26/+208
| | | | | | | Add ready and syncs_with_you flags as well as actual heads, so the peer - ready: same meaning as in the sync message - syncs_with_you: sender counts recipient as member and in same epoch - heads: allows to tell who's behind or if both sides have changes
* use only ready peers as sync sourcetv2026-10-231-11/+52
| | | | | | Sync messages now carries a ready flag, telling whether the sending peer itself is joined or is itself still (re-)joining. In the latter case, the peer won't be used as sync source.
* catch up with a single source onlytv2026-10-231-1/+86
|