Our great sponsors
-
PiNodeXMR
Monero Node for Single Board Computers with Web Interface and additional tools pre-configured. Self Installing.
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Hi there all. I'd really appreciate a short chat with someone who develops professionally and can point me in the direction I need to go next with my project "PiNodeXMR" . The project is very script heavy and based on Raspberry Pi OS / Armbian Debian (depending on the hardware a user has) and the recent uplift to "Bullseye" has highlighted to me the fragility of my current methods. It is not very resilient to change and the resulting errors.
One example of a problem: Installing/building Monerod from source worked fine for years on Debian Jessie and Buster. Bullseye is released it's caused an as yet unsolvable issue . However I'm not convinced it's a Monero issue. Part of me is blaming something to do with the OS/kernel, despite trying different hardware https://github.com/monero-project/monero/issues/8098
Second example: So as a patch for the issue above, PiNodeXMR is using the pre-compiled binaries. However we built from source in able to use the onion-Block-Explorer. For which I raised an issue a while back when random-x was introduced. https://github.com/moneroexamples/onion-monero-blockchain-explorer/issues/211 And this is an error that I can only get (and still get) with Raspberry Pi (again suspecting the OS/Kernel). Now subsequently I cannot build this on Bullseye either.
Related posts
- Was the bug that revealed information about Monero transactions if they were sent within the same block the xmr unlocks fixed?
- Hi Monero Community, want to send crypto anonymously between two wallets.
- show balance on a webpage?
- what is the best and most anonymous monero wallet?
- monero public ipv6-only node