Dylan

Dylan's avatar
Dylan
npub1840x...59sx
Developing Hashrate Heating Sats are the standard 13%er 80 IQ (Former) Structural Engineer Co-founder, Exergy Co-founder, The Space Denver, CO
Here's a fun thing I vibe coded. A dashboard to control the @Exergy office thermostat. The thermostat is tied to a Canaan Avalon Mini 3. image Once a sat is paid to either invoice, @BTCPay Server triggers a webhook on our @Home Assistant. HA then increases or decreases the thermostat by 1°F depending on which was paid. Simple, nothing glamorous but super fun nonetheless. I didn't have a use case for this functionality until @The Nuclear Bitcoiner approached me with the idea and got me thinking. For example: My utility, Xcel Energy, has an opt-in program, which for a small yearly credit, they can limit your how low you can set your thermostat during high-demand periods in the summer. You shouldn't do this IMO, but this functionality would be a way for them to pay the customer LIVE via lightning when needed instead of paying for control on an annual basis. This is my first public repo release. Go easy, please:
Today I started an experiment to compare @OCEAN and @Braiins. I got asked a lot during Vegas which pays more, so I decided it'll be nice to have some actual data. Splitting the hashrate of an s9 50/50 so running conditions (temp, wattage, dirty boards, run times etc) are the exact same for each pool. It'll be interesting to see how it plays out. I chose an s9 because: 1) that's what I have 2) plebs use them as space heaters and I'm here for the plebs There are cheaper FPPS pools out there, but Braiins has lightning payouts and is used by a lot of hashers. OCEAN too, thankfully. I'll need it for this miniscule amount of hashrate. The s9 will have a pretty small % of the share window for OCEAN, so I also plan to compare how the data shapes up on a per block basis as well. Can't wait to have a data set to play with. I'll share regular updates on here and heatpunks.org