Oblivious Compute – distributed state progression without history

InfiniteMass1 pts0 comments

ObliviousCompute (InfiniteMass) · GitHub

" data-turbo-transient="true" />

Skip to content

Type / to search

Sign in<br>Sign upAppearance settings

You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

{{ message }}

ObliviousCompute

Follow

More

Overview

Repositories

Projects

Packages

Stars

ObliviousCompute

Follow

🚀

How much spacetime?

InfiniteMass

ObliviousCompute

🚀

How much spacetime?

Follow

Human from Earth

follower<br>&middot;<br>following

Block or report user

Block or report ObliviousCompute

-->

Block user

Prevent this user from interacting with your repositories and sending you notifications.<br>Learn more about blocking users.

You must be logged in to block users.

Add an optional note

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.

Block user

Report abuse

Contact GitHub support about this user’s behavior.<br>Learn more about reporting abuse.

Report abuse

More

Overview

Repositories

Projects

Packages

Stars

ObliviousCompute/README.md

🪬 Oblivious Compute 🪬

No History. No Logs. No Problems.

Oblivious Compute (OC) is an open-source distributed computation primitive that determines correctness through admissibility rather than agreement and historical coordination.

State ≡ State .

Instead of preserving logs, ordering messages, or reconstructing the past, OC allows multiple candidate states to briefly exist and then admits only one.

The admitted state is truth.

Everything else falls into oblivion.

🌀 The Path

Start with the Theory to understand the ideas that underpin OC .

From there, Skeleton demonstrates the core mechanism in its simplest form.

Continue with Hydra to see how shared state behaves within a compact constraint system.

Then explore Byzantium to watch the same principles operate at a larger scale.

Finally, check out Mowsie to see where this is going.

🪶 Note

Oblivious Compute is not presented as a variation of Paxos , Raft , or a CRDT . Instead, it explores a different approach to distributed consensus , where coherence emerges through admissible transitions and preserved invariants rather than the reconstruction of shared history. As far as I know, this represents a distinct computational model. If you've encountered similar ideas, know of relevant prior work, or simply have thoughts on how this framework should be classified, I'd sincerely appreciate hearing from you. Please get in touch.

💀 Skeleton 💀

Pure, hyper-legible expression of the primitive.

Skeleton is the structure that makes the system lawful.

The structure is the explanation.

(the lift diagram)

🐍🐍 Hydra 🐍🐍

The minimal distributed demonstration of the same primitive.

Hydra shows how state moves and collapses across a small network without logs or traditional coordination.

A simple admissibility gate, expressed in under a thousand lines of code.

(the 1-minute flight)

⚔️ Byzantium ⚔️

A live, networked terminal game for up to 24 players.

Byzantium is the primary expression of Oblivious Compute—a shared projection where multiple participants interact with a single, continuously evolving state.

Connect multiple terminals on the same machine or across a network and you’re immediately inside the same system.

Just a live board, shaped in real time by the people inside it.

(the 10-minute flight)

🐭 Mowsie 🐭

The first real-world application of Oblivious Compute.

🚧 Implementation is currently under construction. 🚧

The theoretical foundation is available below. Source code will be published at the first stable milestone.

Mowsie is a shared-state system for value—designed to replace punch cards, gift cards, and local loyalty systems with a cache of distributed truth .

Users don’t create accounts.

They receive value.

Vendors don’t manage infrastructure.

They define an invariant.

It is the simplest expression of the primitive in the real world.

(the 1-hour flight)

📡 Contact

If you see this and want to talk, reach out — ObliviousCompute@yahoo.com

Support

bc1qc69hm4smfvp4q2xwrn95926ljztxahe0q7fa8x

📜 License

This project is released under the terms of the LICENSE .

Use it, study it, modify it—just respect the terms outlined there.

Popular repositories

Loading

ObliviousCompute<br>ObliviousCompute<br>Public

Python

Something went wrong, please refresh the page to try again.

If the problem persists, check the GitHub status page<br>or contact support.

Uh oh!

There was an error while loading. Please reload this page.

You can’t perform that action at this time.

obliviouscompute state oblivious compute distributed block

Related Articles