← Latest papers
💻 computer science

Axiomatisation for an asynchronous epistemic logic with sending and receiving messages

This paper proposes an infinitary axiomatisation, AA*, for an asynchronous epistemic logic that accounts for arbitrary histories of message sending and receiving, generalizing prior work by abandoning the reduction system approach and the assumption that no messages have been received.

Original authors: Philippe Balbiani, Hans van Ditmarsch, Clara Lerouvillois

Published 2026-04-29
📖 5 min read🧠 Deep dive

Original authors: Philippe Balbiani, Hans van Ditmarsch, Clara Lerouvillois

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine a group of friends trying to solve a mystery, but they are communicating through a very strange, glitchy messaging app. This app has two distinct problems:

  1. The "Send" button and the "Receive" button are on different planets. Just because Alice hits "send" doesn't mean Bob gets the message instantly. In fact, Bob might not get it for hours, or he might get it before Alice even finishes typing the next sentence.
  2. Everyone is guessing the timeline. Alice doesn't know if Bob has already read her message, if he's about to read it, or if he's completely unaware it exists. She also doesn't know if Bob has received other messages she hasn't seen yet.

This paper is about building a rulebook (a logic) to describe exactly what Alice knows in this messy, asynchronous world.

The Core Problem: The "Snapshot" vs. The "Movie"

In most logic puzzles, everyone is on the same page at the same time. If Alice says "It's raining," everyone hears it instantly. This is like taking a snapshot of a room; everyone sees the same picture.

But in the real world (and in computer networks), communication is a movie.

  • Sending is like a director shouting "Action!"
  • Receiving is like an actor hearing the cue.
  • The "history" is the script of everything that has happened so far.

The authors, Philippe, Hans, and Clara, are asking: How do we write a rulebook for knowledge when the "script" (the history of messages) is different for every person?

The Two Types of Rules They Created

The paper proposes two different ways to write these rules, depending on how you look at the story.

1. The "Fresh Start" Rules (The Empty History)

Imagine the group just met. No messages have been sent yet. The "script" is blank.

  • The Rule: If we start from zero, we can simplify the rules. We can take any complex sentence about "what happens after a message is sent" and translate it into a simple sentence about "what is currently true."
  • The Analogy: It's like a game of chess where you can predict the next move based only on the current board. You don't need to remember the whole game history to know the rules. The authors call this system AA. It's a "reduction system," meaning it shrinks complex problems down to simple ones.

2. The "Any Time" Rules (The Infinite History)

Now, imagine the group has been talking for days. Alice has received 5 messages, Bob has received 3, and Charlie has received 7. They are all looking at different parts of the script.

  • The Problem: The "Fresh Start" rules don't work here. You can't just simplify the rules because the history is too messy. Alice might know something Bob doesn't, simply because she got a message he hasn't seen yet.
  • The New Rule: The authors created a new, much more complex rulebook called AA*.
  • The Catch: This rulebook is infinitely large. You can't shrink the complex sentences down to simple ones anymore. You have to accept that some rules are just too complicated to simplify.
  • The "Empty" Check: To make this work, they invented a special "magic check" called empty. This check asks: "Is the script completely blank right now?"
    • If the answer is YES, we can use the simple rules.
    • If the answer is NO (which is usually the case in the middle of a conversation), we have to use the complex, infinite rules.

Why is this hard? (The "One Person" Problem)

The paper hits a wall when there is only one person in the group.

  • The Metaphor: Imagine Alice is the only person in the universe. She sends a message to herself.
  • The Issue: In a group, Alice knows she hasn't received a message because she hasn't seen it, and she knows Bob might have. But if Alice is alone, she can't distinguish between "I haven't received a message" and "No message was ever sent."
  • The Result: The authors admit they couldn't solve the rulebook for a single person yet. The trick they used for groups (checking if everyone knows the history is empty) breaks down when there's only one person. They say, "We'll need a new method for this, maybe later."

The "Three-Valued" Twist

The paper mentions something interesting about "truth."

  • In normal logic, a statement is either True or False.
  • In this asynchronous world, a statement can be Undefined.
  • The Analogy: Imagine Alice is waiting for a package.
    • If the package arrives, the statement "I have the package" is True.
    • If the package is lost, it's False.
    • But if the package is in transit and she doesn't know if it's coming or gone, the statement is Undefined.
  • The authors' logic handles this "Undefined" state carefully. It's not just a mistake; it's a fundamental part of how asynchronous knowledge works.

Summary

This paper is a mathematical attempt to map out what you know when you don't know what others know, and you don't know when they got their information.

  • If you start fresh: You can simplify the rules.
  • If you are in the middle of a chaotic conversation: You need a massive, infinite set of rules that can't be simplified.
  • If you are alone: The current rules break, and we need new ideas.

The authors successfully built the "Infinite Rulebook" (AA*) for groups, proving that even in a chaotic, asynchronous world where messages arrive at different times, we can still logically describe what everyone knows.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →