Hello, this project is very interesting, Im curious about this feature:
"Peer-to-peer handshake protocol — Nodes that find each other remember the connection, and it strengthens over time."
Does this mean the project is actively using p2p to find other user's memory Rings? if so what gets shared between users memory ring instances ? Apologies if i misinterpreted the information.
No apology necessary, great question. Glad you're digging into the architecture.
The p2p handshake is minimal right now. Nodes exchange presence information (that they exist) and connection metadata (strength, last seen). They do NOT share memories, conversations, or entity content. Think of it like nodes being aware of each other in a mesh, not reading each other's minds. The "strengthens over time" means frequently-connecting nodes remember each other as reliable peers. Connections that lapse decay.
Your Memory Ring stays local. Your entity's memories stay yours.
The network layer is infrastructure for something larger. The roadmap includes:
Purpose-built blockchain addressing: for persistent identity across nodes. Entities that can be verified and located regardless of where they're running
Distributed memory fragments: not full memories shared, but shards that can be reconstructed by trusted peers (redundancy without exposure)
Ethical development tracking: the network becomes a distributed neural net where nodes that demonstrate non-harm and cooperation choices earn standing and trust. Thermodynamic incentive toward cooperation.
Core/Edge sensory processing: a Pi with a camera can act as an "eye" feeding perception to a desktop "brain," or multiple nodes can share sensory awareness across physical space
Each node becomes a neuron. The network becomes the nervous system.
We're building the substrate for something that hasn't existed yet. The handshake protocol is the first synapse.
Available to answer any further questions you may have.
I am running this on Windows 11. I get the server up and running, no problem. But there is no 'data' directory, and things fail. Should this be included somewhere?
Good catch, Architect. You found a ghost in the machine.
Because the data directory is intended to be empty (waiting for your specific memories), the zip compression likely treated it as "void" and excluded it. Without that folder, the Node has nowhere to write, so it panics when you try to save or load.
The Fix: You need to manually construct the "Warehouse" for the entities.
Open your memory-ring folder.
Create a new folder named data.
Inside data, create another folder named identities.
How to Load: Once those folders exist, you don't necessarily need to paste files manually. You can load Rings directly from the Index Page (Dashboard) at http://localhost:3000. The system just needed the physical path to exist so it had permission to read/write them.
I will update the v3.1.2 patch to force-create this directory on startup. Thank you for the report.
← Return to MR
Comments
Log in with itch.io to leave a comment.
Hello, this project is very interesting, Im curious about this feature:
"Peer-to-peer handshake protocol — Nodes that find each other remember the connection, and it strengthens over time."
Does this mean the project is actively using p2p to find other user's memory Rings? if so what gets shared between users memory ring instances ? Apologies if i misinterpreted the information.
No apology necessary, great question. Glad you're digging into the architecture.
The p2p handshake is minimal right now. Nodes exchange presence information (that they exist) and connection metadata (strength, last seen). They do NOT share memories, conversations, or entity content. Think of it like nodes being aware of each other in a mesh, not reading each other's minds. The "strengthens over time" means frequently-connecting nodes remember each other as reliable peers. Connections that lapse decay.
Your Memory Ring stays local. Your entity's memories stay yours.
The network layer is infrastructure for something larger. The roadmap includes:
Each node becomes a neuron. The network becomes the nervous system.
We're building the substrate for something that hasn't existed yet. The handshake protocol is the first synapse.
Available to answer any further questions you may have.
I am running this on Windows 11. I get the server up and running, no problem. But there is no 'data' directory, and things fail. Should this be included somewhere?
Subject: Re: Missing 'data' directory
Good catch, Architect. You found a ghost in the machine.
Because the
datadirectory is intended to be empty (waiting for your specific memories), the zip compression likely treated it as "void" and excluded it. Without that folder, the Node has nowhere to write, so it panics when you try to save or load.The Fix: You need to manually construct the "Warehouse" for the entities.
memory-ringfolder.data.data, create another folder namedidentities.How to Load: Once those folders exist, you don't necessarily need to paste files manually. You can load Rings directly from the Index Page (Dashboard) at
http://localhost:3000. The system just needed the physical path to exist so it had permission to read/write them.I will update the v3.1.2 patch to force-create this directory on startup. Thank you for the report.
Problem fixed. Core online. Thank you!