mirror of https://github.com/vacp2p/rfc-index.git synced 2026-01-08 21:37:59 -05:00

Files

Hanno Cornelius 6672c5bedf docs: update lamport timestamps to uint64, pegged to current time (#196 )

Lamport timestamps should remain close to current time (in milliseconds)
for new joiners to be able to have their messages ordered reasonably
close to other messages in the channel.

This means that:
- the `timestamp` field should be large enough to accommodate
millisecond resolution timestamps, i.e. `uint64` (see
https://github.com/vacp2p/rfc-index/pull/195 for reasoning)
- the lamport timestamp should be updated before sending _each_ message
to `max(timeNowInMs, current_lamport_timestamp + 1)`.

The current spec only indicated that Lamport timestamps should be
_initialised_ to current time, which means that the logical timestamp
would soon drift from current time.

2025-10-02 14:07:29 +01:00

cosmetic: fix external links in 1/COSS (#100 )

2024-10-09 17:53:44 +02:00

Fix Files for Linting (#94 )

2024-09-13 16:51:09 +02:00

Fix Files for Linting (#94 )

2024-09-13 16:51:09 +02:00

Fix Files for Linting (#94 )

2024-09-13 16:51:09 +02:00

Fix Files for Linting (#94 )

2024-09-13 16:51:09 +02:00

Fix Files for Linting (#94 )

2024-09-13 16:51:09 +02:00

raw

docs: update lamport timestamps to uint64, pegged to current time (#196 )

2025-10-02 14:07:29 +01:00

README.md

Update README.md (#101 )

2024-10-11 16:49:21 +02:00

template.md

Update Waku Links (#104 )

2024-11-20 12:32:56 -05:00

README.md

Vac RFCs

Vac builds public good protocols for the decentralised web. Vac acts as a custodian for the protocols that live in the RFC-Index repository. With the goal of widespread adoption, Vac will make sure the protocols adhere to a set of principles, including but not limited to liberty, security, privacy, decentralisation and inclusivity.

To learn more, visit Vac Research