HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
lithdew
monte
Go2020–2020
lithdew / monte

monte

The bare minimum for high performance, fully-encrypted bidirectional RPC over TCP in Go with zero memory allocations.

2Distinct people
2Mentions
0Explicit recommenders
120GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The bare minimum for high performance, fully-encrypted bidirectional RPC over TCP in Go with zero memory allocations.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2020-06-18 12:40:20 UTC to 2020-06-18 15:41:49 UTC.

012020-06-18 12:00:00 UTC to 2020-06-18 13:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 18, 12:002020-06-18 13:00:00 UTC to 2020-06-18 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 18, 13:002020-06-18 14:00:00 UTC to 2020-06-18 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-06-18 15:00:00 UTC to 2020-06-18 16:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 18, 15:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 18, 12:002020-06-18 12:00:00 UTC2020-06-18 13:00:00 UTC101
Jun 18, 13:002020-06-18 13:00:00 UTC2020-06-18 14:00:00 UTC000
Jun 18, 14:002020-06-18 14:00:00 UTC2020-06-18 15:00:00 UTC000
Jun 18, 15:002020-06-18 15:00:00 UTC2020-06-18 16:00:00 UTC101

What Hacker News says

2 sources
All communication is quiescent unless some given node A sends data to node B (apart from TCP keepalive packets of course). For routing messages, it is expected O(log n) much like ordinary Kademlia. There isn't much resilience carefully integrated into the system for untrusted peers (complete S/Kademlia is in progress though! Static/dynamic crypto puzzles are fully implemented to prevent Sybil attacks on IDs, and the FIND_NODE RPC call is implemented to meet he guarantees documented in S/Kademlia's paper), since this framework is intended to be used in a closed environment for a set of microservices. The underlying library for networking, Monte, fully supports providing your own net.Conn's and io.Reader/Writers - all you need to do is return your modified net.Conn via implementing the monte.Handshaker interface here: https://github.com/lit
Read the rest
hdew/monte/blob/master/net.go#L36 Monte will everything else related to bidirectional RPC management. Details of the bare minimum Monte prefixes to your packets is documented on the README for it. Hope you enjoy using either Monte or Flatend!
In Show HN: Flatend – Quickly build microservices using P2P networking in Node/Go

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.