Lewin Kelly Heliodex

Introduction

Recently I was out for a walk and I think I convinced myself that any given asic owner should theoretically make more money by pointing their asic at a hashrate market instead of directly at a particular pool, but only if there is no broker.

When I began thinking that way, there was something counterintuitive about it, which I'd like to address first.

Definitions

I'll start by defining three terms: "Owner" refers to a person who owns an asic and lists it for rent on a hashrate market. "Renter" refers to a person who visits a hashrate market and pays to temporarily rent someone else's asic. "Broker" refers to a person who runs a hashrate market — e.g. whoever bought the domain name, assuming it has a website.

The Problem

Recently I got the idea described in this document from @maveth6 on twitter. I know of three hashrate markets: Nicehash, Braiins, and Mining Rig Rentals. I define their niche as a type of broker. They not only play a matchmaking role between asic owners and would-be renters, they also custody the funds of renters while the mining is happening, and release it to asic owners bit by bit if there are no complaints from the renters. Brokers charge a fee for this work, which reduces the efficiency of the market, and, since they have custody of user funds, they are subject to various regulations. Those introduce additional friction: they KYC their users, they run incoming bitcoin through chainalysis software, they potentially seize funds if red flags are thrown, they are a honeypot for thieves, and user funds are at constant risk.

A Solution

My idea is to get rid of the broker. Instead, have people with asics publish an ad on nostr or similar stating how much hashrate they control and a price

Heliodex project update – March 2026

I return with another monthly update. Mostly with information on Mercury, as usual. Hope you're having a great easter if you celebrate that, or otherwise having a more relaxed holiday than I am if you have one at the moment. Here's what I was doing throughout March:

Mercury

Mercury 3 has 105 user accounts. As is tradition for the first day in April, we did a lovely CSS rewrite for the website, including plenty of new fonts, crazy animations, and rainbow colour scheme. I was only able to put in about an hour of work for this, so not as full on as the 2024 April Fools design & rebrand, but still fun nonetheless. It was of course reverted after a day. Some users requested that we bring it back as a website theme, though we already have that feature in Custom CSS (funnily enough that page 500s for some reason, must fix...) I suppose.

Work

Shall i implement it?
No ...

Heliodex project update – February 2026

Oh wow, look at the size of this one. Yeah, these posts are most definitely getting longer, to the great detriment of all 0 readers. Grab some of your preferred snack to make this seemingly less boring to read if you so please, and welcome back to the monthly project update!

Mercury

Mercury 3 has 91 user accounts. The number of beta testers is smaller than that but still growing, and other user-generated areas like the Forums and Catalog are of course growing as well.

Recent news includes the migration of the database from SurrealDB v2 to v3 after its recent new release, mainly by following their migration guide, though plenty of manual intervention was required. As such, the Site was [down for about 2 hours](https://github.com/tp-l

	const std = @import("std");
	const assert = std.debug.assert;

	entropy: []const u8,

	pub const Error = error{OutOfEntropy};

	const FRNG = @This();

	pub fn init(entropy: []const u8) FRNG {

	ExifTool Version Number : 13.52
	File Name : art002e000192.jpg
	Directory : /Users/hannes/Downloads
	File Size : 6.2 MB
	File Modification Date/Time : 2026:04:03 23:12:02+02:00
	File Access Date/Time : 2026:04:03 23:12:03+02:00
	File Inode Change Date/Time : 2026:04:03 23:12:02+02:00
	File Permissions : -rw-r--r--
	File Type : JPEG
	File Type Extension : jpg

	#!/bin/sh
	# ISC License

	# Copyright (c) 2026 Alexandre Gomes Gaigalas <alganet@gmail.com>

	# Permission to use, copy, modify, and/or distribute this software for any
	# purpose with or without fee is hereby granted, provided that the above
	# copyright notice and this permission notice appear in all copies.

	# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES

	RFC 454545 Human Em Dash Standard
	Status: Informational March 2026
	Authors: Janice Wilson, Jeff Auriemma

	RFC 454545 — Human Em Dash Standard

	Abstract

	This document proposes the Human Em Dash (HED), a Unicode character
	visually indistinguishable from the traditional em dash (—) but encoded

	package require Tk

	set count 0

	# Label that displays the count
	label .lbl -text "Count: $count" -font {Helvetica 18}
	pack .lbl -padx 20 -pady 10

	proc update {} {
	global count