TRANSFER_01
Direct IP Route
Machine-to-machine or mobile-to-machine transfers stay local when the peers are on the same reachable network.
ROUTE // DIRECT
DarkMatter Software // Proof-of-Concept Release
RIFT
dmrift/1 Protocol
A local transfer fabric for machines that should be able to see each other, trust each other, and move data without the usual detours. RIFT links Linux systems and mobile devices over IP, then gets out of the way.
01 // protocol layer
A small protocol with a very large doorway.
dmrift/1 is the common language between RIFT peers. The public idea is simple: identify the peer, offer the payload, stream it directly, verify the result, and leave a receipt. The implementation details stay behind the curtain.
rift://protocol-session
> dmrift/1 session initialized
peer.discovery :: local fabric scan
peer.ready :: linux-node / mobile-node
route.select :: direct IP transport
payload.offer :: awaiting receiver
payload.accepted :: stream opened
integrity :: sha256 verification
transfer.complete :: receipt written
> listening
MOBILE
dmrift/1 sender
LINUX
dmrift/1 peer
RIFT
FABRIC
FABRIC
02 // transfer behavior
Files move now. Not after a cloud round trip.
RIFT treats the local network as the shortest path between two devices. Once the route is known, transfers stream directly between peers with live progress, queue state, and integrity verification.
TRANSFER_02
Streamed Payloads
Large files are sent as a stream instead of being swallowed whole into memory first. The wire stays busy while the application stays responsive.
STATE // FLOWING
TRANSFER_03
Verified Arrival
A transfer is not considered complete merely because bytes arrived. RIFT verifies the payload before finalizing it.
VERIFY // SHA-256
TRANSFER_04
Always-Ready Linux Peer
Open RIFT and the Linux node becomes both TX and RX ready. The desktop application handles both directions from one interface.
PEER // TX+RX
TRANSFER_05
Mobile Sender
Android speaks the same dmrift/1 contract. Pick a file, route it to a Linux peer, and send without changing protocols between platforms.
ANDROID // ONLINE
TRANSFER_06
Queue Control
Transfers can be queued, paused, cancelled, retried, observed, and logged instead of disappearing into a single opaque progress dialog.
QUEUE // CONTROLLED
03 // trust boundary
Open when you want it. Selective when you do not.
The POC security model is intentionally readable. A peer can receive from the local network broadly, or narrow acceptance to explicitly trusted hosts. This is the first trust layer, not the final one.
RX SERVICEAlways-ready local receiver
TRUSTED HOST MODERestrict inbound transfers to known peers
INTEGRITY CHECKVerify completed payload before finalizing
LOCAL RECEIPTSRecord transfer status and peer history
Security without theater.
RIFT does not pretend that “local” automatically means “trusted.” The proof-of-concept already exposes a practical host-trust boundary while keeping the user in control of when the receiver is permissive and when it is selective.
The next security milestones belong above this layer: stronger peer identity, cryptographic pairing, encrypted sessions, and richer trust policy. dmrift/1 is being built so those layers can arrive without changing the basic user experience.
POC SECURITY MODEL // designed for trusted local networks. Host trust and payload integrity are active; stronger cryptographic identity is a future protocol layer.
04 // proof of concept
The receipts exist.
RIFT has moved beyond diagrams. The Linux peer runs as a unified sender/receiver, and the Android build has successfully delivered files from a physical mobile device into that Linux endpoint using the same protocol.
ANDROID DEVICEphysical mobile client
TX // VERIFIED WORKING
⇢
LINUX PEERunified TX / RX desktop endpoint
RX // VERIFIED WORKING
poc-receipt.logdmrift/1
[PASS] Linux receiver online
[PASS] Linux sender online
[PASS] Android APK built and installed
[PASS] Android → Linux file transfer completed
[PASS] payload integrity verified
> proof-of-concept status: ALIVE
dmrift/1 // local transfer fabric
One protocol.
Any peer that can speak it.
RIFT is being built around a simple idea: nearby devices should not need a distant intermediary to move a file across the room.
RETURN TO SIGNAL