You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
site: emphasize event ordering, and tunable sub-second precision vs blockchains
Strengthen the LOTI landing page on two fronts:
- Event ordering is elevated from a tail clause to a foundational
message: hero lead, a new 'Order is the bedrock' paragraph in the
idea section, a 'Proves order?' compare-table row, and a new
'Is this just timestamping?' FAQ. Frames a proof as a native
happened-before ordering that stands without any clock.
- Precision is presented as a tunable dial (clock interval + network
topology), reaching sub-second — contrasted against Bitcoin/Ethereum
stamping, whose resolution is pinned to the block interval. Added a
'Time resolution' compare row and reworked the precision FAQ.
Also updated meta/OG descriptions and footer tagline.
<metaname="description" content="A peer-to-peer network for provable time. Prove that any document, photo, message, or measurement existed within a narrow window — and which came first — with no central authority, no blockchain, and no fees.">
7
+
<metaname="description" content="A peer-to-peer network for provable time and order. Prove that any document, photo, message, or measurement existed within a narrow window — and prove which of two events came first — with no central authority, no blockchain, and no fees. Precision scales with clock rate and network density, down to sub-second.">
8
8
<metaproperty="og:title" content="LOTI — Prove when it happened">
9
-
<metaproperty="og:description" content="Provable time, without a middleman. Get a portable proof anyone can verify offline.">
9
+
<metaproperty="og:description" content="Provable time and event order, without a middleman. Get a portable proof anyone can verify offline — with precision that scales down to sub-second, unlike a blockchain.">
<pclass="eyebrow">Proof of when · peer‑to‑peer · no middleman</p>
420
420
<h1>Prove <em>when</em> it happened.<br>To anyone. Without<br>trusting anyone.</h1>
421
-
<pclass="lead">LOTI weaves every digital event into a shared fabric of time — so you can prove, mathematically, that a document, photo, message, or measurement existedwithin a narrow window, and which of two events came first.</p>
421
+
<pclass="lead">LOTI weaves every digital event into a shared fabric of time — so you can prove, mathematically, both <em>when</em>a document, photo, message, or measurement existed, to within a narrow window, and <em>which of two events came first</em>. It's not just timestamping; underneath, it's a provable ordering of events.</p>
<pclass="drop">Instead of one clock everyone must trust, LOTI lets everyone keep time <b>together</b>. Nodes across the network keep a steady heartbeat and constantly nod to their neighbors — weaving a tamper-evident fabric of "this came before that."</p>
492
492
<p>To prove when your event happened, LOTI finds the two heartbeats that bracket it. To fake it, you'd have to unravel the whole fabric — and the mathematics simply won't allow it. You can't forge the past, and you can't pre-compute the future.</p>
493
493
<p>There's no global vote and no winner. Everyone is free to form their own view of the timeline — but nobody can ever prove a <em>contradiction</em>. It's agreement where it counts, freedom everywhere else.</p>
494
+
<p><b>Order is the bedrock; time is the readout.</b> Before any calendar date enters the picture, the fabric already fixes <em>which event came before which</em> — a tamper-proof <em>happened-before</em> ordering that stands on its own. Attach a clock you trust and that ordering becomes a date you can read; take the clock away and the order still holds. Two events can be conclusively ranked against each other even when neither carries a trusted timestamp. LOTI is an event-ordering network first, and a timestamping one because of it.</p>
494
495
</div>
495
496
</div>
496
497
</section>
@@ -714,6 +715,8 @@ <h2>Between a notary and a blockchain — the sweet spot.</h2>
714
715
</thead>
715
716
<tbody>
716
717
<tr><thscope="row">Who you trust</th><tdclass="col-loti">A reference you choose — or the math</td><td>The authority</td><td>The chain & its validators</td></tr>
718
+
<tr><thscope="row">Proves order?</th><tdclass="col-loti">Yes — a native happened-before ordering, clock or no clock</td><td>No — stamps each event alone</td><td>Only within its own global ledger</td></tr>
719
+
<tr><thscope="row">Time resolution</th><tdclass="col-loti">Tunable — sub-second if you push the clock and topology</td><td>The authority's clock</td><td>Capped by block time — seconds to minutes</td></tr>
717
720
<tr><thscope="row">Cost per proof</th><tdclass="col-loti">Effectively free</td><td>Per-stamp fees</td><td>Transaction / gas fees</td></tr>
718
721
<tr><thscope="row">Your content</th><tdclass="col-loti">Stays private</td><td>Shared with the authority</td><td>Public forever</td></tr>
719
722
<tr><thscope="row">Resilience</th><tdclass="col-loti">No single point of failure</td><td>Central</td><td>Robust, but heavy</td></tr>
<pclass="fine reveal">Reach is nearly free — it costs chains, not storage — so almost the whole budget goes to precision. Worst case, an aged event is bracketed to a fraction of its age: <b>~0.09%</b> on a Pi, <b>~0.004%</b> on a phone, <b>~0.00008%</b> on a server. Push the tick faster than one per second and even recent bounds drop below a second.</p>
791
+
<pclass="fine reveal">Reach is nearly free — it costs chains, not storage — so almost the whole budget goes to precision. Worst case, an aged event is bracketed to a fraction of its age: <b>~0.09%</b> on a Pi, <b>~0.004%</b> on a phone, <b>~0.00008%</b> on a server. Push the tick faster than one per second — or lean on a denser, better-connected patch of the network — and even recent bounds drop well below a second, a resolution no block-time-bound chain can reach.</p>
789
792
790
793
<h3class="subhead reveal">What it takes to build the graph</h3>
791
794
<divclass="grid g-3 reveal">
@@ -882,6 +885,10 @@ <h2>The things people ask first.</h2>
882
885
<summary>Is this a blockchain?<spanclass="plus"></span></summary>
883
886
<p>No. There's no global ledger, no coin, and no mining. Everyone keeps their own local timeline and cross-checks their neighbors, which makes LOTI far lighter, private, and free compared with a blockchain.</p>
884
887
</details>
888
+
<details>
889
+
<summary>Is this just timestamping?<spanclass="plus"></span></summary>
890
+
<p>No — timestamping is only half of it. Underneath, LOTI is an event-<em>ordering</em> network: the fabric fixes which event happened before which, as a tamper-proof partial order, whether or not you ever attach a date. Two events can be conclusively ordered against each other even when neither carries a trusted timestamp. Pin that ordering to a reference clock and you get a readable date; leave the clock out and the order still holds. A timestamp, here, is simply ordering measured against a clock you chose.</p>
891
+
</details>
885
892
<details>
886
893
<summary>Does it cost money?<spanclass="plus"></span></summary>
887
894
<p>Publishing an event is effectively free. Running a node costs a bit of bandwidth and a fixed slice of storage — capped at a budget you choose and flat forever. There are no per-proof fees.</p>
@@ -892,7 +899,7 @@ <h2>The things people ask first.</h2>
892
899
</details>
893
900
<details>
894
901
<summary>How precise is a proof?<spanclass="plus"></span></summary>
895
-
<p>It depends on the network. How tight the window is comes down to the heartbeat interval of the nodes on the chain — which might be well under a second, or more than a minute. Faster-ticking nodes give a tighter bracket, slower ones a wider one; as a general rule, expect something on the order of a minuteor less, measured against the clock you choose to prove it against. Either way it's a rigorous bound, never a claim of an exact instant.</p>
902
+
<p>It depends on the network — and precision is a dial, not a fixed floor. How tight the window is comes down to two things you can scale: the heartbeat interval of the nodes on the chain, and the topology around your event — a denser, better-connected, faster-ticking stretch of the network brackets it more tightly. Push the clock faster and gather a few close neighbors and the window drops well below a second; leave it at one slow tick a node and it widens toward a minute. That tunability is something Bitcoin or Ethereum stamping can't match: there, resolution is pinned to the block interval — minutes on Bitcoin, seconds on Ethereum — and can't go finer. Either way, a LOTI proof is a rigorous bound, never a claim of an exact instant.</p>
896
903
</details>
897
904
<details>
898
905
<summary>Is my content made public?<spanclass="plus"></span></summary>
@@ -928,7 +935,7 @@ <h2>The things people ask first.</h2>
0 commit comments