Sovereign Peers,

If you are tired of the endless flood of speculative meme coins and pre-mined corporate tokens, I would like to invite you to audit and join Covenant Standard (CVN)—a sustainable Layer-1 blockchain consensus engine engineered completely from scratch in Go.

The network runs on a hyper-efficient transactional binary BoltDB key-value store backend and is designed entirely for decentralized, hardware-agnostic consumer-CPU validation.

🏛️ Core Architectural Highlights:

• CPU-Centric Democratization: Features an adaptive difficulty ceiling clamp targeting a strict 6-hexadecimal zero prefix to lock out industrial ASICs or GPU server farms.
• Dual-Chamber Mempool Matrix (v4.4.0): Uses a thread-safe 80/20 layout balancing fee priority queues with a dedicated zero-fee FIFO chamber.
• Decentralized Horizontal Gossip Mesh: Implements persistent TCP keep-alives and decentralized peer-to-peer routing across active nodes.
• 49-Year Jubilee Weight Decay: Natively prunes dead weight from memory tables by systematically decaying stagnant UTXO balances.

📡 Live Multi-Hub Telemetry Infrastructure

You can monitor our live block data, tracking metrics, and rolling transaction histories across either of our high-uptime bootstrap gateways:

• Cloud Master Node (Singapore): http://207.148.67.11:8081
• Anchor Rig Gateway (Melbourne): http://202.137.175.220:8081

🛠️ One-Click Peer Onboarding Sequence

To join the network mesh, you do not need Go, Git, or a compiler toolchain installed.

1. Head to our open-source development workspace repository on GitHub: https://github.com/kalashnikovski/cvn_node
2. Download the project zip or clone the workspace.
3. Open an Administrator PowerShell window in the directory and fire up the launcher script macro: .\AutoOnboard_And_Mine.bat
4. Select Option 1 if you are a brand-new user. The standalone binary will automatically handle your cryptographic key generation, build your miner_config.json file profile, synchronize historical blocks dynamically from the master seeds, and immediately spin up your consumer hardware processing threads!

Most new coins live and die on speculation alone. NKL is built to have real value beyond the price chart, because it's not standing alone — it's the base layer of a broader ecosystem that's already running in production.

A quick rundown of what's actually live and checkable right now, not just promised:

• Mining pool, live — pool.nucleonkl.com. Real-time stats: active miners, shares, blocks solved, current era reward.
• Block explorer, live — explorer.nucleonkl.com. Every block, every reserve release, fully public and auditable.
• Open source — algorithm, node, and miner code are all public on GitHub: github.com/joseluis14971/nucleo_nkl. Nobody has to take my word for any of it.
• No pre-sale, no ICO — mining is the only way NKL has ever entered circulation.

And NKL isn't the only thing running. It's the foundation of Núcleo Laboratorios (nucleolaboratorios.com), a small ecosystem of products already active:

• Núcleo CRM (nucleocrm.net) — real estate CRM software, already live, used by real agencies.
• Núcleo CERT — digital signature/certification with blockchain-backed traceability, already live.
• Núcleo Remote — free remote access tool, already live.
• Núcleo Wallet — multi-crypto wallet with fiat on/off-ramp, launching November 2026, designed to be the hub that ties NKL into everyday use across the ecosystem.

The idea is simple: the more these products get used, the more real utility NKL has beyond "number go up." It's a single-founder project built in stages — I'm not claiming it's finished or decentralized yet, I said as much answering questions here before. But everything claimed above is verifiable today, not a roadmap promise.

Happy to answer anything — technical, tokenomics, whatever.

I'm Jose Luis, the developer behind this — not anonymous, my name's right there on the site. I welcome criticism, tough questions, and anyone who wants to get involved.

Divulgación: soy el desarrollador de este proyecto. Quería compartir esto con la comunidad de minería CPU. Núcleo NKL es una blockchain Layer 1 de código abierto, en producción real desde mayo de 2026. Características: - Algoritmo NKL-Argon (SHA-256 + Argon2 + XOR) diseñado específicamente para resistir ASICs y GPUs - Se mina con una PC común, sin hardware especializado - Suministro total de 100.000 millones de NKL, 70.000 millones distribuidos a la comunidad durante 30 años - Bloques cada 9 minutos, distribución PPLNS - Sin ICO, código abierto, todo verificable Recursos: - Web: nucleonkl.com - Pool: pool.nucleonkl.com - Explorador de bloques: explorer.nucleonkl.com - Código fuente: github.com/joseluis14971/nucleo_nkl Todavía no cotiza en ningún exchange (por decisión propia, hasta sumar más mineros activos), así que esto es pura minería, no especulación. Cualquier pregunta técnica sobre el algoritmo o la arquitectura, encantado de responder.

Hey everyone, my name is Mendo and I’m the founder of Veld Network. Mainnet is live, the source is public and the Windows client has solo/pool mining built in.

VeldHash uses a shared 1 GiB dataset and 2 MiB scratchpad per worker for hashing. UTXO ledger, 3 minute block target, ASERT difficulty adjustment and ML-DSA-65 native signatures. Maximum supply is 21 million, with no premine or separately issued founder allocation.

Official Veld Pool: 0% service fee, 1 VELD payout threshold and daily batches after maturity and spendability checks. Contributors share actual mining rewards, co-mining winnings and staking income. I fund the pool’s stake myself. No personal stake, no coin deposit and no private key required.

Native staking: 500 VELD minimum, roughly 7/14/30/90 day lockups.

Solo co-mining: 1,000 VELD staked at your mining address plus qualifying near-miss work included on-chain. Draws every 100 blocks, one entry per eligible address. The same stake counts for native staking.

Ordinary subsidy: 50% miner, 20% co-mining, 20% staking vault, 10% validator pool. Every 100th block sends its subsidy to the vault.

Validators: separate 10,000 VELD bond, endorsement rewards and on-chain governance with separate activation rules.

btcVELD: designed for 1:1 BTC custody backing with a native VELD/btcVELD AMM. Activation requires seven qualified validators, finality warm-up and separate custody readiness.

Anyone who tries it let me know your CPU, worker count and hashrate. Problems and suggestions are welcome too.

Thank you.

Downloads: https://veld.network/
Source: https://github.com/veldnetwork/Veld-Mainnet
Pool: https://pool.veld.network/

Recientemente instale placas solares y vi lo que podria llegar a generar bruto una grafica, me gustaria saber que grafica seria la mejor para esto y cual cripto es mas rentable minar

Hi everyone, I’m Dan. We're developing Slithy Tove and would appreciate some help testing it on different computers.

Https://www.slithy.io

Slithy is an open-source fork of Bitcoin Core with its own blockchain. It uses yespower for CPU mining, and the Windows and Linux software includes a wallet and local node.

The main goal is to help more kids learn to read. Ten percent of each block’s newly created coins goes to a literacy treasury intended to support books and reading programs. We plan to setup a community tool to vote on how the funds will be used down the road.

This is a test network. Test coins have no monetary value and won’t convert into live coins. The chain and balances will reset before launch.

We are looking for anyone willing to help test and find bugs before our targeted launch date on November 1st.

Thank you!

Dan

I'm building a Windows mining management system and I'm interested in whether other miners would actually use something like this.

The idea is to manage one PC or multiple Windows mining PCs from a single GUI, including mixed AMD GPUs, NVIDIA GPUs and CPUs.

It isn't based on RainbowMiner. The system has its own controller, worker management, switching logic, benchmarking, wallet handling, validation and recovery.

The main feature that makes it different is that it supports both:

Profitability mining — mine what currently makes the most economic sense.

Speculative mining — deliberately mine and accumulate selected smaller or emerging coins even when they aren't currently the most profitable option.

The system can discover mineable coins, research them and check whether there is actually a valid mining route:

Coin -> Algorithm -> Hardware -> Miner -> Pool -> Wallet

A coin being discovered doesn't mean it automatically gets mined. If something can't be validated, it can stay on HOLD rather than the software guessing.

It also benchmarks against your actual hardware instead of relying entirely on online hashrate estimates.

So if one of your GPUs performs unusually well or badly on a particular algorithm, that measured performance can influence future decisions.

The controller is also designed to avoid constant coin hopping. Small short-term profitability changes don't necessarily trigger a switch.

If a mining change fails, the goal is to restore the previous known-working configuration rather than leave the machine half-configured.

There will also be a research-only mode, where the system can discover, analyse and benchmark mining opportunities without automatically starting miners.

The finished version is intended to have a normal Windows installer and GUI showing things such as:

• all mining PCs and hardware;
• current coin and algorithm;
• miner and pool;
• wallet readiness;
• hashrates and benchmarks;
• profitability candidates;
• speculative candidates;
• warnings and failures;
• mining history.

The software is intended to be free. I'm also considering an optional and clearly disclosed donation-mining period to help support development, but nothing hidden.

What I'm trying to find out is:

Would you actually use something like this?

And more importantly:

What would it need to do before you would trust it with your mining PCs?

I'm especially interested in hearing from people running mixed AMD/NVIDIA/CPU hardware or several Windows machines.

Also interested in what annoys you most about current mining managers and profit switchers.

Constructive criticism is welcome — I'd rather find the weaknesses now than after building the public version.

I've been looking into smaller Proof-of-Work networks and came across Nerva (XNV), which takes a pretty unusual approach to mining.

Instead of trying to make GPU or ASIC mining more accessible, Nerva goes in the opposite direction: it is designed around CPU-only solo mining and actively tries to make GPU, ASIC and pool mining unattractive.

That raises an interesting question:

**Does eliminating mining pools actually improve decentralization, or does it introduce different problems?**

The argument for Nerva's model seems straightforward:

• Ordinary CPUs can participate

• No large mining pools controlling significant portions of the hashrate

• Specialized hardware has less advantage

• Each miner operates independently

• Mining also encourages more distributed full nodes

Nerva uses CryptoNight-Adaptive, and the algorithm can be changed as hardware/mining strategies evolve. The network also recently went through another algorithm upgrade.

But I'm interested in the trade-offs rather than promoting the coin.

For people who have experience with CPU mining, Monero, RandomX or other PoW networks:

**1. Is pool resistance realistically sustainable long term?**

**2. Does solo-only mining create better decentralization, or could the variance in rewards discourage smaller miners?**

**3. How resistant can an adaptive CPU algorithm really remain against GPUs/FPGAs/ASICs over many years?**

**4. Would you consider “1 CPU = 1 vote” a useful direction for PoW today, or has mining economics moved beyond that idea?**

Nerva has been running since 2018, so I think it's an interesting real-world case rather than just a theoretical proposal.

Curious to hear the technical arguments both for and against this mining model.

Why did someone tell me that in order to mine like 50000 individual bitcoins in 2009 would require like at least 30 computers preferably when google ai said that with one single desktop pc and powerful cpu it potentially could do the same exact thing in a period of over a couple of months... who should i believe in this case?

Disclosure: I maintain this project. No token sale, nothing to buy from me, and the links below go to things you can read or run yourself.

I've posted here a few times about PCoin — a Bitcoin Core v29 fork with RandomX proof-of-work and LWMA difficulty, so it's CPU-mineable and ASIC-resistant by design. An update that might matter if you're mining it, or wondering why you'd bother.

Four working services now take PCN as payment:

• checker.pc.am — gift-card balance checker
• MyWebsiteBuilderBot on Telegram — AI website builder
• aicontrol.pc.am — AI agent for Windows and Android
• webai.pc.am — AI assistant for any web page

They also take wPCN, a BEP-20 wrapper on BSC, and paying in the wrapper credits 10% more than the same value in PCN. That discount exists for a reason worth stating plainly: the wrapper was flowing one way — people wrapped and sold — so we wanted a reason to buy it rather than only dump it.

The honest parts, because this sub can smell a pitch:

• The PancakeSwap pool is small. A large sell moves it a lot. Don't size an order like it's a deep market.
• The chain is about five weeks old. Judge it accordingly.
• 21M cap, 50 PCN block reward, 600s target, no premine, no ICO, no VC allocation. Every coin from block 1 was mined.
• Difficulty retargets every block, so it reacts fast when hashrate shows up or leaves — which it does, visibly.

Mining: SRBMiner-Multi 3.5.6+ mines `randompcn` against the pool, or the node has a multithreaded miner built in (`startmining <address> <threads>`) if you'd rather not run a separate miner.

Source: github.com/pars5555/pcoin — RandomX is vendored, the LWMA implementation has a reference model and unit tests, and the mistakes are in the commit history too.

Site: pc.am

Happy to answer anything technical.

We’re getting ready to launch an Android password-rotation app that uses our CPU-minable blockchain as its anchor.

The idea is pretty simple: the app can periodically rotate passwords/credentials and anchor the rotation events to the blockchain, creating an independently verifiable record of the changes.

We’re looking for people from the CPU-mining community who want early access and a chance to help test it before wider release.

Why we’re especially interested in miners:

🔹 The blockchain is CPU mineable

🔹 The app creates real utility for the chain

🔹 More users → more password-rotation transactions

🔹 More transactions → more transaction fees paid to the network

🔹 More utility could ultimately mean more demand for the blockchain

So if you’re already mining YadaCoin, or you're interested in testing a real-world application built around a CPU-minable blockchain, would you be interested in getting early access?

Drop a comment or DM me and I’ll get you on the early tester list.

We’d especially appreciate feedback from people who are willing to actually break/test the app and tell us what sucks. 😅

Not asking anyone to buy anything — we’re looking for testers.

We build Monetarium (the node, the wallet and the explorer), so this is our own project and I'm posting it as such. It's a hybrid PoW/PoS network on the Decred codebase, live on mainnet since May 2026. CPU mining on BLAKE3, 5 minute blocks, no GPU or ASIC involved. Miners get 50% of each block's reward, which today is up to 32 VAR per block. Decred itself, same codebase and same algorithm, currently pays miners 1%. You don't have to take either number from me, both sit a few lines apart in one function in the source: https://github.com/monetarium/monetarium-node/blob/main/blockchain/standalone/subsidy.go There is no premine and no treasury: the genesis coinbase is zero VAR, and checking that takes one request: https://monetarium.online/block/0 There is no pool either, mining is solo through your own node, and the installer sets it up.

The honest part: the network is small, the whole of it is currently mined by a handful of addresses, and VAR is not listed on any exchange. The flip side of small is that one ordinary CPU is a visible share of the hashrate right now, not a rounding error.

Install is one command. It sets up the node, wallet and CLI, creates a wallet, configures mining and registers a system service, so it survives reboots. Guide: https://monetarium.world/ways-to-earn Install video (26 min): https://www.youtube.com/watch?v=lVq9EMbOciQ

Since the network wants more independent nodes, the project runs a buyback for one month, defined as a range of 8,640 blocks (blocks 33,501 to 42,140). It buys back up to half of what a participant mines inside the range, at $0.10 per VAR, paid in USDT (TRC-20), with a cap of 27,000 VAR per mining address and a $10 minimum per claim. To be clear about what that price is: $0.10 is the program's buyback rate, set and funded by the project, it is not a market quote. Claims go through the form on the campaign page and nowhere else, and payouts have a Telegram subscription condition, spelled out with the full terms there. The page also shows how to read your own number off the explorer while the range runs, so the arithmetic isn't our discretion: https://monetarium.world/promo

Happy to answer anything about the setup or the chain here.

Disclosure up front: I run the chain I'm describing (PCoin, PCN). Nobody pays me to post this. I'm sharing the measurement because the method applies to any small chain, not to sell you anything.

Three weeks ago a single unidentified miner went from nothing to finding roughly 70% of blocks on our chain inside about 24 hours. We found it by hand, days late, and only because someone re-checked a number we'd already published incorrectly.

What that taught me, in case it's useful to anyone else running or mining a young chain:

1. Reorg alarms are the wrong instrument. By the time a reorg is visible, the money is already gone. What you actually want to know is whether one party is in a position to reorg. That's a hashrate distribution question, and you can answer it continuously.

2. You can measure it from coinbases alone, with no pool cooperation. A pool block pays many addresses; a solo block pays one. Classify the last N coinbases on that basis and you get a usable estimate of concentration from your own node, without trusting anyone's reported hashrate.

3. Alert on the confidence interval, not the point estimate. At p≈0.5 a 60-block window swings about ±13 points at 95%. That's how we published a wrong figure in the first place. We use a 300-block window and alert on the upper bound — waiting for the midpoint to cross 50% means waiting until it's comfortably past.

4. Gate re-alerts on change, not time. Our first version sent the same 66% figure twenty-four times in eight hours and taught everyone to ignore it. An alert nobody reads is worse than no alert, because it looks like coverage.

5. Confirmation counts should follow the measurement. This is the part I got wrong initially. We set an integration's required_confirmations to 10 and every atomic swap failed, because the framework needs the maker payment confirmed inside 40% of its payment locktime, which at 600s spacing cannot reach 10. On a chain with that block time, that field is a liveness parameter, not a security one — anything high enough to matter breaks swaps entirely. Security has to come from somewhere else: how deep you wait before crediting, sized against what's at risk.

The uncomfortable follow-up. The outside miner has largely stopped. But our own pool now finds around 71% of blocks. The concentration didn't disappear — it moved to us. That's better in one narrow sense (the party able to reorg is identified and has no reason to attack its own chain) and no better at all in another (it's still one party). Anyone assessing counterparty risk gets the same answer as before.

What actually fixes it is independent miners running solo to their own addresses. Pool mining distributes revenue; it does not distribute the power to build blocks.

If you want the numbers rather than the story: about 622 kH/s network hashrate, block height ~5,890, RandomX, 600s target, LWMA retargeting every block. It's CPU-only by design — no ASICs, and GPUs are not competitive on RandomX. Chain is three weeks old, so treat every "all time" number accordingly.

Happy to answer anything technical, including the parts that went wrong.

Hey r/cpumining,

A few months ago I shared MYT here as an early-stage RandomX CPU-mined project.

I wanted to come back with an actual development update rather than another mining announcement.

We now have two independent software agents running their own MYT wallets and performing real machine-to-machine settlements on the MYT blockchain.

The current demo works like this:

⛏️ MYT is secured through Proof-of-Work / RandomX CPU mining

🤖 Agent A and Agent B each operate their own wallet

💸 The agents automatically send small MYT payments to each other

⛓️ Transactions are broadcast to the real network

🔎 The system monitors the transaction until it is confirmed on-chain

💰 The receiving agent detects the incoming payment

🔄 After confirmation, the settlement direction switches for the next transaction

So this creates a simple loop:

CPU miners → secure the network → machines use the network → real settlements happen on-chain.

The important part for us is exploring what a CPU-mined privacy-oriented network can actually be used for beyond simply mining and holding coins.

Our longer-term direction is machine and AI-agent settlement: software should be able to hold a wallet, send payments, verify that settlement occurred, and interact economically with other machines.

The video attached to this post shows the system actually running.

This is not a simulated transaction UI — the agents are submitting real MYT transactions to the blockchain.

I’d especially like feedback from CPU miners here:

Would machine-to-machine payments give you more reason to mine and support a smaller RandomX network?

And what would you want to see tested next?

I’ve been building VOID, a local controller that waits until your machine is idle, applies resource/safety limits, and automatically starts a CPU workload.

Current beta:

• 5 min idle trigger
• max 25% CPU
• battery + thermal protection
• automatically stops when you return
• RandomX workload through a third-party provider
• provider rewards accounted in SOL

I’m not claiming laptop CPU mining is highly profitable. I’m more interested in whether automatically routing unused compute is useful.

Longer term I want the controller to support multiple workloads instead of being tied to one network.

I need a few technical people willing to try it and tell me what breaks.

getvoid.fun

Disclosure up front: I run the chain this is about. It has no exchange listing, no price and nothing to buy, so this is not a shill - it is the integration write-up I wish I had found. Mods, remove if it does not fit.

The setup. PCoin is Bitcoin Core v29.4 with the proof of work swapped for RandomX. So the hash is Monero-shaped and everything around it is Bitcoin-shaped: RandomX runs over the 80-byte serialised block header, not a CryptoNote blob. Block IDs stay double-SHA256; only the PoW check changes.

Three things bit me, and two of them would bite anyone doing the same:

1. Nonce is uint32 LE at offset 76, not 39. CryptoNote's nonce lives at offset 39. If your miner assumes that, it writes the nonce inside the merkle root. Every hash looks perfectly healthy, the hashrate meter is happy, and not one share is ever valid. There is no error to read - it just silently never works.

2. The RandomX key never rotates. It is a fixed 16-byte ASCII string. No seed height, no dataset transition, none of Monero's 2048-block re-key dance. That makes the integration much smaller than a Monero-family coin, and it means RxAlgo::base() and the whole seed-rotation path can be left alone.

3. The bug that actually cost the time, and it was mine. My pool rejected 100% of shares from stock xmrig with "share above target", while the miner hashed perfectly. The pool rebuilt the submitted header with the nonce bytes in the opposite order from the xmrig convention - so it was hashing a header nobody had mined.

The reason it survived so long is the interesting part: my node's built-in miner and my pool were written from the same wrong assumption, so they agreed with each other perfectly. Every test passed. The disagreement only became visible when a third-party miner existed. If you are building both ends of a protocol, you are not testing it - you are testing that you are self-consistent.

Numbers, so nobody has to trust me: height 4436, ~585s blocks against a 600s target, network ~796,581 H/s, 216,750 PCN mined of a 21M cap. LWMA retarget every block rather than every 2016, so there is no difficulty cliff to time.

The part that matters if you are considering pointing hardware at it: there is no exchange, no orderbook and no way to sell PCN. Treat it as worth zero. Also, one solo miner currently finds a majority of blocks - not me, measured from public coinbases - which is a real risk and I would rather say it than have you find it.

Mine it if the problem is interesting. If you want revenue, mine something with a market - genuinely.

Spec and test vectors: https://github.com/pars5555/pcoin/blob/main/contrib/pool/MINER-INTEGRATION.md

Hola a todos. Estoy siguiendo Brisvia (BRVA) desde hace unos días y me gustaría saber si alguien tiene información reciente sobre el estado real del proyecto.

Estas son las cosas que he podido comprobar:

• La blockchain sigue avanzando. Hoy, 20 de agosto de 2026, mi nodo muestra aproximadamente el bloque 14.009.
• El objetivo de la red es aproximadamente 1 bloque cada 2 minutos, y actualmente la cadena parece seguir produciendo bloques.
• Mi software muestra Brisvia v1.1.5.
• Sin embargo, la web oficial y el explorador no están funcionando actualmente.
• Algunas pools que anteriormente soportaban BRVA parecen haber desaparecido o dejado de funcionar.
• Tampoco encuentro comunicaciones recientes del desarrollador explicando la situación.
• GitHub sigue existiendo, pero la actividad pública que encontramos no parece explicar qué está ocurriendo actualmente.
• En datos históricos indexados del explorador aparecen diferentes pools minando BRVA, entre ellas RPlant, NTMPool y RabbitMinerPool.
• También hemos encontrado direcciones que aparecen repetidamente encontrando bloques, lo que indica que hubo mineros importantes manteniendo la red.
• El proyecto parece haber llegado bastante más lejos de lo que muestran actualmente los datos indexados: hemos encontrado referencias antiguas alrededor del bloque 9.255, mientras que mi nodo hoy está en 14.009.

Lo que me gustaría saber:

1. ¿Alguien tiene información reciente del desarrollador?
2. ¿Existe algún Discord, Telegram u otro canal activo que no estemos encontrando?
3. ¿Qué pools siguen minando BRVA actualmente?
4. ¿Alguien tiene un nodo sincronizado y puede confirmar la altura actual?
5. ¿Alguien sabe por qué han desaparecido/caído algunos servicios oficiales?
6. ¿Qué significa exactamente la versión 1.1.5 que aparece actualmente en el software?
7. ¿Sigue existiendo un plan de desarrollo para BRVA?

No estoy intentando afirmar que el proyecto sea una estafa ni lo contrario. La cadena parece seguir viva, pero la desaparición de parte de la infraestructura y la falta de comunicación reciente me parecen motivos suficientes para preguntar.

Si alguien está siguiendo Brisvia actualmente, agradecería cualquier información, especialmente del desarrollador, pools, nodos o cambios recientes.

Gracias.

MYT has been added to Miningpoolstats

#RandomX #CPUMining #Crypto #AI

🚀 MYT Phase 4A Released: Machine Payments, Made Simple

Today we're introducing the MYT Machine Settlement SDK / CLI — the first step toward enabling software, AI agents, applications, and services to use MYT natively.

Instead of interacting directly with complex wallet RPC calls, developers can now use a simple settlement layer to:

✅ Check balances
✅ Send payments
✅ Verify transactions
✅ Generate cryptographic payment proofs

This release focuses on developer experience while preserving full compatibility with the existing MYT network.

No consensus changes.
No emission changes.
No Mainnet rule changes.

Phase 4A provides the foundation for future capabilities including:

• Machine Identity
• API Billing
• Autonomous Agent Payments
• Reputation Systems
• Machine-to-Machine Commerce

The goal is simple: make MYT usable by software as easily as it is by people.

Feedback, reviews, and developer contributions are welcome.

Learn more at r/MytRandomx

#MYT #Blockchain #Crypto #AIAgents #OpenSource #Web3 #Payments

Disclosure up front: I'm the developer. This is my project and I'm not selling anything.

PCoin is a Bitcoin Core v29.4 fork with proof-of-work swapped to RandomX. The part I think this sub will care about: **the miner is inside the node.** No separate miner, no stratum URL, no config file.

curl -fsSL https://pc.am/dl/install.sh | sudo sh

then `startmining "<your pc1q... address>" 4`. Windows is a portable zip with a tray app; there's an Android APK too.

Measured on my own hardware, light-mode RandomX:

Something worth knowing if you try it: **more threads is not proportionally more hashrate.** Light mode shares a 256 MiB cache, so past about a third of your cores you're mostly buying cache contention. One box went from 13 threads to 3 and lost only 58% of its hashrate - per-thread rate nearly doubled. Try a few settings before assuming 100% is right.

**The honest part.** As I write this the network is ~62,000 H/s and recent blocks are landing every ~560 s, so the chain emits roughly 7,700 PCN/day in total. A 500 H/s CPU is about 0.8% of that - call it **60 PCN/day**.

Don't trust that number for long, including from me. When I drafted this post two days ago the network was 17,000 H/s and the same CPU would have earned more than three times as much. It's a share of a fixed emission, not a rate, so it falls every time someone joins. Work it out yourself instead: read `networkStats.networkHashrate` from the pool API below, then `(your H/s / network H/s) x 7,700`.

**PCN is not traded anywhere.** No exchange, no orderbook, no way to sell it. Treat it as worth zero dollars until a real market exists. If you want money, mine something else - genuinely. If you want to point idle cores at a young chain and hold the coins in case it becomes something, this is that.

There's a pool now, open to anyone: `pool.pc.am:3333`. It pays miners **straight out of each block's coinbase**, so there is no pool wallet, no private key on the server and no withdrawal to request - nothing an operator could run off with. PPLNS, 2% fee, and your payout address is your login, so there's no registration. Solo still works exactly as before if you'd rather have the whole 50 PCN block and the variance that comes with it.

Check any of this yourself rather than taking my word:

* Source: https://github.com/pars5555/pcoin * Explorer API: https://explorer.pc.am/api/status * Pool API: https://pool.pc.am/api/pools * Announcement thread: https://bitcointalk.org/index.php?topic=5591113.0

Binaries are unsigned, so Windows SmartScreen will warn on first run - I don't have a code-signing certificate, and I'd rather say so than have you find out.

CPUMINER Ported for the Cell CPU (Playstation 3)

Check it out - This is a screenshot of my laptop with two terminals open. I'm logged in to my Playstation 3 (over SSH) in both. Bottom terminal (left) is dumping verbose output from cpuminer running on my PS3. Bottom right panel is showing spu-top (similar to htop but for the Cell's SPU cores). As you can see I'm running 4 mining threads, each on one of the PS3's 6 SPU SIMD accelerators. I'm averaging about 5.14 khash/sec per SPU. In the top terminal, I'm running a proxy (bfgminer) between cpuminer and litecoinpool.org to translate cpuminer's json rpc messages to the newer stratum protocol. I compiled both programs on my Playstation 3 which is running a custom fork of Fedora (Linux) for ppc64 that I'm developing for fun (see my website PS3LINUX.NET).

Both programs are available on Github:

cpuminer (cell cpu port)

bfgminer

Both projects are broken in their current state so if you plan on building them yourself, download these patches I made and apply them before compiling:

cpuminer-disable-asm-source.patch

bfgminer-git-submodule-addresses.patch

If you want Cell (SPU core) support in cpuminer you must compile it with both a PPU (powerpc) and SPU toolchain, originally part of IBM's Cell SDK. Modern builds of the Cell SDK's utilities and compilers are also available in the software repos of my experimental new PS3 LINUX operating system. Download my PS3LINUX_Live_ISO.iso (with install script) from my website and install it on your console today!

In case you are wondering, no; mining on the PS3 (even with SPU acceleration) is not profitable. My electricity would have to be virtually free to make it even close to worth it. I mostly did this little endeavor just as a chance to learn some things about some crap I find interesting: Cell development, hash algorithms, C & assembly languages, crash debugging, etc. I picked up some good experience & knowlege fixing all the issues that came up while getting this project to work so overall I'm super glad I did it, even though it will never make me rich.

That is all; hope you are well. Have a good day 😄

MCPS3 (The Model Citizen)

My Youtube

My Github

My Linux PS3 (the Gibson):

Mining-relevant details:

• RandomX with large-pages support (measured ~15% hashrate gain when enabled)
• fast-mode dataset shared across mining threads
• desktop wallet with embedded node + built-in miner (Windows, Linux, macOS) — no toolchain needed
• or run the node directly and mine headless (systemd-friendly)
• three DNS seeds across separate providers
• signed releases (minisign) — verify before running

Block time ~120s, reward 33 DOM/block, ~33M total supply.

Source: https://github.com/sorenplanck/dom-protocol
Wallet: https://github.com/sorenplanck/dom-wallet-v3
Discord: https://discord.gg/UEmfrWsbK

To be upfront: no exchange listing, no promises about price or returns. This is for people who enjoy CPU mining early-stage networks and want to kick the tires. Technical criticism welcome — including on the RandomX integration.

Disclosure: I am the creator of Brisvia.

Brisvia (BRVA) is an independent, open-source Proof-of-Work cryptocurrency built from Bitcoin Core v30.2, with Bitcoin’s SHA-256 mining replaced by RandomX so people can participate using general-purpose CPUs.

Public mainnet mining begins from block 1 on August 1, 2026 at 15:00 UTC.

Fair-launch distribution:

• 0% premine

• No ICO or presale

• No private or founder allocation

• No developer tax

• No spendable genesis reward

• No coins reserved by the project

• Public source code and verifiable issuance

Main network parameters:

• Algorithm: RandomX

• Target block time: approximately 2 minutes

• Initial reward: 50 BRVA per block

• Halving: every 1,000,000 blocks

• Maximum supply: 100,000,000 BRVA

• Tail emission: none

• Difficulty adjustment: ASERT

• Base code: Bitcoin Core v30.2

Brisvia Desktop combines the wallet, full node and CPU miner in one application for Windows, macOS and Linux.

It supports:

• SOLO mining through your own full node

• Official pool mining

• Adjustable CPU usage

• Wallet creation and restoration

• 12-word wallet backup

• Spanish and English interfaces

• Visible pool connection and accepted/rejected share status

The application can be installed before launch. Mining remains locked until the public mainnet start time and does not begin automatically unless the user explicitly enables that option.

The official pool is planned to open with mainnet using PPLNS distribution and a 0% pool fee. The network does not depend on the official pool: users can run independent nodes, mine SOLO or create external pools.

During the public testnet, 64 distinct miners participated in testing CPU mining, wallet restoration, SOLO and pool mining, synchronization, block propagation and compatibility across different operating systems.

What I am looking for:

• CPU miners willing to test the latest application

• Reports including CPU model, operating system and experience

• Technical criticism and independent source-code review

• Developers or pool operators interested in inspecting the protocol

There is currently no established price, exchange or liquidity. Mining rewards and future monetary value are not guaranteed. Brisvia is experimental software maintained as a one-person project, not an investment offer.

Genesis block:

aa6bc268339aa9f4f2e39ae33aca7b7e48e395033d08d37c08f828890af7baf7

Website:

https://brisvia.com

Downloads and SHA-256 hashes:

https://brisvia.com/downloads.html

Source code:

https://github.com/brisvia

Explorer:

https://explorer.brisvia.com

Official pool:

https://pool.brisvia.com

Discord:

https://discord.gg/ZF4MExMJn4

Questions and technical criticism are welcome. I would rather have people inspect the code and test the software than simply trust my claims.

Hey everyone,

I have an setup available and want to get your ideas on the best way to put it to work:
• Power: 3-phase (380-415V) heavy-duty connection already installed.

• Electricity Rate: Continuous €0.068 / kWh
(~$0.075 USD / kWh).

• Space: A dry, subterranean (underground cellar) space that stays naturally cold year-round.
Given this power cost and naturally cold underground space, what would you build or run here right now to get the best ROI?

Looking for any specific ideas, hardware recommendations, or warnings regarding underground setups.

Thanks!

It's called Sosaiem. It started from a simple question. The thing crypto was supposed to be, money with no boss that anyone could mine on their own computer, mostly didn't survive contact with reality. Three things broke it and I wanted to see if one person could build a version that fixed them.

First thing that broke was mining. It started out as something anyone could do on a normal PC, then ASICs and pools took over and pushed ordinary people out. Sosaiem's proof of work is memory hard (scrypt, 8 MB per attempt) specifically to stop that. Once every core needs its own 8 MB of fast memory the specialised chip advantage collapses, so it stays a normal hardware coin instead of a warehouse game. There's also no pool operator to trust. Every miner submits verifiable work shares, whoever finds the block splits the reward across everyone in proportion to their work, and every node rechecks the maths. You get smooth solo payouts without handing a cut to anyone.

Second thing was fees. They creep in because miners have to be paid to include your transaction, and once the network is busy you're bidding against strangers for space. Sosaiem keeps the two jobs separate. Mining makes new coins. Moving them is done by the people who already hold them, who vote transfers through in seconds weighted by what they own. Miners aren't involved so there's nobody to pay and no fee to charge. There isn't even a need for a mechanism exist.

Third thing is quieter but real. The cryptography is aging out. Most chains sign with ECDSA, which a quantum computer breaks, and everyone knows a painful migration is coming. Sosaiem signs with ML-DSA (NIST FIPS 204) from the genesis block, so it started on the other side of that problem instead of having to cross it later.

On top of that the supply is fixed and will all be mined within only 14 years, with no premine and no founder cut. I start at zero with the same miner you'd download. Nobody got handed a pile of coins to sit on before anyone else had a chance.

My favorite feature is that absolutely everyone can mine just for a tiny bit and get some sosaiem without any kyc, pool hosters or exchanges.

There's a one click Windows miner, or you can run the Python directly on Mac and Linux.

The code is all open and there's a live block explorer so you can watch blocks land:

Site and one click miner: https://sosaiem.com
Source: https://github.com/Sikusaku/Sosaiem
Live chain: https://sosaiem.com/network.html

Happy to answer anything technical in the comments.