Bitcoin Forum
August 22, 2026, 12:27:09 PM *
News: Latest Bitcoin Core release: 31.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 [8]  All
  Print  
Author Topic: Parano1d ① Proof-native Layer 1 ordered by PoW  (Read 1950 times)
chn520
Newbie
*
Offline

Activity: 42
Merit: 0


View Profile
August 21, 2026, 04:29:26 PM
 #141

end,sleeping
Ima_o_lambao
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
August 21, 2026, 04:30:13 PM
 #142

hit a total of 0 blocks so far with a ryzen 9 5950x
Arttemkaaa
Newbie
*
Offline

Activity: 8
Merit: 0


View Profile
August 21, 2026, 04:35:36 PM
 #143

hit a total of 0 blocks so far with a ryzen 9 5950x

10 CPU 7950x got  2 block
IgnotusNemo (OP)
Jr. Member
*
Offline

Activity: 67
Merit: 3


View Profile
August 21, 2026, 04:54:06 PM
 #144

Could somebody write a private GPU miner? For nonce search, yes.

But nonce search is only the second phase of Parano1d mining. First, the node must build a new HistoryStep proof for every parent. The current prover is CPU-only and optimized for binary-field arithmetic through AVX2/AVX-512 VPCLMUL on x86 and PMULL on ARM. There is no CUDA or OpenCL prover. A GPU nonce kernel cannot build this proof. It must wait for the CPU, and if another block arrives first, the prepared work becomes obsolete.

A GPU may still gain something during nonce search because it can run many independent attempts. How much is unknown. Poseidon2b over GF(2^128) is not SHA-256. Modern CPUs have native carryless multiplication instructions for this arithmetic, while GPUs would need to emulate it. Their parallelism may compensate for that, but only a real implementation and benchmark can answer the question.

The 240 MH/s shown by the GUI is not hardware telemetry and does not detect GPUs. It is an estimate calculated from difficulty and observed block time. Payout addresses also tell us nothing about hardware. One address may represent one CPU, a 200-core server or several machines.
GofyGofy
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
August 21, 2026, 04:59:06 PM
 #145

Could somebody write a private GPU miner? For nonce search, yes.

But nonce search is only the second phase of Parano1d mining. First, the node must build a new HistoryStep proof for every parent. The current prover is CPU-only and optimized for binary-field arithmetic through AVX2/AVX-512 VPCLMUL on x86 and PMULL on ARM. There is no CUDA or OpenCL prover. A GPU nonce kernel cannot build this proof. It must wait for the CPU, and if another block arrives first, the prepared work becomes obsolete.

A GPU may still gain something during nonce search because it can run many independent attempts. How much is unknown. Poseidon2b over GF(2^128) is not SHA-256. Modern CPUs have native carryless multiplication instructions for this arithmetic, while GPUs would need to emulate it. Their parallelism may compensate for that, but only a real implementation and benchmark can answer the question.

The 240 MH/s shown by the GUI is not hardware telemetry and does not detect GPUs. It is an estimate calculated from difficulty and observed block time. Payout addresses also tell us nothing about hardware. One address may represent one CPU, a 200-core server or several machines.

Do you hear yourself? before at fail start chain was at max 10 MH with all those people now it is 300 MH I saw even 400+ at some blocks so before was ok now looks pure GPU
Tongpu
Member
**
Offline

Activity: 157
Merit: 10


View Profile
August 21, 2026, 05:22:52 PM
 #146

Wonder what you guys will say when the network starts hitting the GH/s range. ASICs? Grin
Ima_o_lambao
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
August 21, 2026, 06:11:13 PM
 #147

0 blocks for 2 hrs, with a ryzen 9 5950x, turning off now
Arttemkaaa
Newbie
*
Offline

Activity: 8
Merit: 0


View Profile
August 21, 2026, 07:29:12 PM
 #148

I think a new start and reset is needed.
Seikar
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
August 21, 2026, 07:41:48 PM
 #149

Now, approaching 4 hours since launch, the current rich list is probably the below.  (Caveat: I used a script to get a list formatted so.  If my script errors, the below would have reduced accuracy).

1  o1y4jgqw0vwhxh6409xaqa40s2ngyhm3h78z2phvz58ctgkv50xjrsre9c9s | 18360.15182 NOID | 58.96% | 408 utxos
2  o1r0v66vwx88jdvp8vrnqwdlthsgpgc4vdmxt7c2y25uwtxtak2kns9jnteg | 3451.780532 NOID | 11.08% | 13 utxos
3  o1tus5dgna07ncyfmxzy0l04xw3nrajkcsu9x8xju4rzdjxcueu3ksw7200h | 2385 NOID | 7.66% | 53 utxos
4  o1xwd45sz97gnq3gmtd2pmm4024ll2hzzutcgse9p6ze87sd4h3hnqkpzsd9 | 2007.29925 NOID | 6.45% | 9 utxos
5  o1tfr3tjerg0k50080z26xzej99syulppzcz236w7x6p5zur2pjtjqnfmne3 | 865.862431 NOID | 2.78% | 10 utxos
6  o18fddlr2zuntxssqad23kr96a8aw0vljj93tles2g6543l2jnsnkqtel2nn | 495 NOID | 1.59% | 11 utxos
7  o1c8ur982fggryluamvg0748gdj7aa07qqf2e8rrrswm5lce6x9txq3740s8 | 449.916 NOID | 1.44% | 11 utxos
8  o13cprf6pny6q726xknez284gt857hwtr65xaj0e3fxkzgtw6vxxhsqq3nr7 | 391.441175 NOID | 1.26% | 25 utxos
9  o189d72tcej2y5f8rr9mhhu2pjvlg2mjuaa34q5sceexsrpp8ghm3st7s8wa | 303.415422 NOID | 0.97% | 10 utxos
10  o1h80k2rhx0etpq3pzcsczhrq503ye6dt309wyt376s2gtwslevuls4xnpyf | 270.02315 NOID | 0.87% | 6 utxos
11  o17zpmm04x8q8mqwd64r32lxx0px50xz8nn0f8k7wyllrl8eskjqmq4klrh7 | 225.0065 NOID | 0.72% | 5 utxos
12  o1a5qkxsff756pc0vzml0uqrmt2mhtxrjmx5624xmpff7lvrjkfgrsgm0keh | 135.0065 NOID | 0.43% | 3 utxos
13  o1fj83dk7vqtq5vustge2xfnuc6ekfajjspr4a6tdvsdsj8ua44hfq5xar2m | 135 NOID | 0.43% | 3 utxos
14  o1k2anw4p2m7um5n6aqj20wvzur9lu7v3fz707lvh9cxhfnuzej3psrzr95f | 90.01422 NOID | 0.29% | 2 utxos
15  o1xgytpgysc7z9yse0h6m0zw5qrtzggpgz9nv3lkm4jts9gwfwfqwswu7z63 | 90.0065 NOID | 0.29% | 2 utxos
16  o105qs6n3tzywq7krprz4ml42z7ud3s0x8lwx3gggeh2tmquyu4l6stzjxhc | 90 NOID | 0.29% | 2 utxos
17  o10j9j7pk7r4d32fj4h2g3j0xczlclvv7hxxzr7upupk67uf2ru9fqpqsxu6 | 90 NOID | 0.29% | 2 utxos
18  o17g08l6z3mznqdum2ndf9q7529chjsl773d28lv5yldynpj69g57qfdneat | 90 NOID | 0.29% | 2 utxos
19  o1e4qez0s83a34u09je2auwauvtnyp2lcgjrfq256ak8ewdyvs57rs5n4fm9 | 90 NOID | 0.29% | 2 utxos
20  o1p09rawd6m7awzj5z8355rqtyenphktl4v5y258k79l5mau09rwescafq0u | 90 NOID | 0.29% | 2 utxos
21  o1wll9ch2n0twwmj2c3j6z640qthxgjla2x68jnk3crvhwqw88e3nspnuvet | 90 NOID | 0.29% | 2 utxos
22  o1z7wp2gt942ppaq57xkek8xz0ycyryvxnltw9355cxy0cm8txy9sqt7tewa | 90 NOID | 0.29% | 2 utxos
23  o1d0vp8yt7wv87rk0qcwua2yent4uzvcqd7eqn947z53rjt2ll208sv5mrsm | 67.991 NOID | 0.22% | 2 utxos
24  o1ewv88pp6d5t69zexj5k0az7x9eqf02vnwkc8nylkwm5q7d5240usq4apdq | 67 NOID | 0.22% | 2 utxos
25  o1vhlu94kn7k0z7vha82t9et0k7qp9prpgca0tnw0smud3aekmjn8q0gw0jh | 45.0081 NOID | 0.14% | 1 utxo
26  o17h2pgpuk5d7ec6ndmhk7dtd87ywctq7pzl8ccg0wdkd70veylmtqaae87g | 45.0065 NOID | 0.14% | 1 utxo
27  o12a7z3d0xchfz97pxapjr9gre6xgwup8s6qkx8krdt4d83m9k425s8nmx42 | 45 NOID | 0.14% | 1 utxo
28  o14g629pkwqr6aemurmdym3kps600m7f3cx25lcpzz5eqgv7jzjg3sddwg8l | 45 NOID | 0.14% | 1 utxo
29  o1707qzej3zl3anl3gtgx7dn8uhmsd6eeyhw5s73ehynk4pdasv84sd9g44t | 45 NOID | 0.14% | 1 utxo
30  o17am0dqhwasg3asnx9qkq34cg326t800nh8ftnlsqxyfzwjzsykpsaafysu | 45 NOID | 0.14% | 1 utxo
31  o17qwej4y927nngzynqnsnu32e9ef4627u200m6e9kj6xxylm0vylsexvg00 | 45 NOID | 0.14% | 1 utxo
32  o19yjrv0ehrluj8ax3daa07sp3c0xrhsveula4qpthl84c4ue92k3qspkuw8 | 45 NOID | 0.14% | 1 utxo
33  o1ez6czddc2x4qzpzgq44xtm8467k566m66x7qtg82yr2ce6lnz7ws0t36sp | 45 NOID | 0.14% | 1 utxo
34  o1kyt62get0vrgd20qsm6u6tfvn0q2ncy6a35h7n4f9qa82gf2gyfs3lggkk | 45 NOID | 0.14% | 1 utxo
35  o1p65w56k407fkph05u775w6u0t43v8v633wxqutf39eefnvdn838qegv9g3 | 45 NOID | 0.14% | 1 utxo
36  o1r2uvld2tpk6p5em4yr3qyplkd3undc4t8985w5r59nzt2dmgucvs0zhd44 | 45 NOID | 0.14% | 1 utxo
37  o1sn8eswh3x4ls8taf4d66g5jg7368dtjqdhxrq782udfx3dyfrhhqv09gc7 | 45 NOID | 0.14% | 1 utxo
38  o1wnpu77v46rk58zl8nf5ja39thp0fc28zcmjv5q0c3j2sr8dug67q9k3cnj | 45 NOID | 0.14% | 1 utxo
39  o1xqz3tpyy0ypn8z6fz66fyrme85mfxqxyg5uewezwp93jyrh8vdlqpptwqn | 45 NOID | 0.14% | 1 utxo
40  o1yn8rdmc9ux9ncw0dt4ere9v7gh8s4nzkjhdvqmkxve7a4uzfxhlq5amdxf | 45 NOID | 0.14% | 1 utxo
41  o136ptktd9meuhes57xtmd54dw2gpc38vdg20fsd49pfguvj6uj99q4m0302 | 0.0105 NOID | 0.00% | 1 utxo
42  o1vz8x436mw0sezzqpnr8wekltg726gjdsr8krr0qs0sjly529dypsaujsu4 | 0.009 NOID | 0.00% | 1 utxo
43  o1gp3h8m3x4sgwww0afn4g4gdfpjr7unf70t22rjfeflhcjr585sfstzesk7 | 0.001 NOID | 0.00% | 1 utxo
44  o1p40dqug07x57a6xdsap5enlugtfj8nvtzfe5uxzu4km96sfd6sfq2hllrj | 0.0004 NOID | 0.00% | 1 utxo

The top miner is curious.  I wonder if it is a server farm with tens of processors mining to a shared payout address.

Still, despite heavy competition, my mining is getting some coins over the hours.
Tongpu
Member
**
Offline

Activity: 157
Merit: 10


View Profile
August 21, 2026, 07:56:12 PM
 #150

Mining pool (not mine)
https://pool.ariabrain.com/noid.html
IgnotusNemo (OP)
Jr. Member
*
Offline

Activity: 67
Merit: 3


View Profile
August 21, 2026, 08:34:26 PM
Last edit: August 21, 2026, 09:45:32 PM by IgnotusNemo
 #151

Ive been watching the network since launch. It has now crossed 1 GH/s on the short window. Over the last 100 blocks it averaged around 0.79 GH/s, with a 21.2 second average block time and a 19 second median. The target is 20 seconds, so difficulty is tracking the load well.

At this level of competition, several blocks are often produced at the same height. The deepest reorg happened near launch at height 56 and was three blocks. There were a few depth 2 reorgs after that. During the last hour they were all depth 1. Every node I checked converged on the same block hash and State root.

P2P also looks healthy. The nodes I checked have between 26 and 93 peers. Queues are small, there is no starvation, and nodes that briefly miss a tip recover through exact suffix sync. Even slower machines may fall one block behind for a moment, but they catch up automatically.

No consensus, database or proof verification failures so far. Scaling looks really good. Now I can finally congratulate all Parano1ds on a successful launch!


UPDATE

The network briefly touched almost 3 GH/s today. Across the last 100 blocks, actual accumulated work averaged 1.36 GH/s. More hashrate means more blocks competing at the same height. That is happening, but every reorg during the last 45 minutes was only one block deep. P2P queues never exceeded five objects, all nodes kept converging and even the slowest 4 CPU node stayed synced. Block distribution has also become much more balanced. The top four payout addresses found 30, 28, 17 and 16 of the last 100 blocks, with no address holding a majority.

The network has barely noticed the load.
alt_x
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
August 21, 2026, 11:31:13 PM
Last edit: August 21, 2026, 11:42:29 PM by alt_x
 #152

Tested results on a 32 core VPS and through the pool show around 1.558 NOID per hour.
That means roughly 1121 NOID per month, while the VPS costs 200e per month.

For mining to break even, NOID would therefore need to reach around 0.1783e per coin.
That is quite a high requirement for a newly launched coin, especially before we know where and if it will be traded.

Has anyone else calculated their mining cost?
GofyGofy
Newbie
*
Offline

Activity: 4
Merit: 0


View Profile
Today at 09:16:52 AM
 #153

Tested results on a 32 core VPS and through the pool show around 1.558 NOID per hour.
That means roughly 1121 NOID per month, while the VPS costs 200e per month.

For mining to break even, NOID would therefore need to reach around 0.1783e per coin.
That is quite a high requirement for a newly launched coin, especially before we know where and if it will be traded.

Has anyone else calculated their mining cost?

Man !, You already speak about costs and trading when we don't have a proper community server like Discord or Telegram. Grin
minerminer3456
Newbie
*
Offline

Activity: 30
Merit: 0


View Profile
Today at 10:38:33 AM
 #154

discord pls
Grumo
Member
**
Online Online

Activity: 431
Merit: 22

Professional user


View Profile WWW
Today at 12:02:24 PM
 #155

GPU miner for NOID — measured, and it works

The maintainer asked in discussion #12 whether a GPU could help with the nonce search, and said only a real implementation and a benchmark could answer it. I built one. Here is the answer.

Why a GPU can't mine Parano1d alone — and why that stops mattering behind a pool

Every block needs a fresh HistoryStep proof before there is anything to search, and that proof is CPU work. A GPU cannot build it. On its own, a GPU would sit idle between blocks waiting for a CPU, and if a new block landed first the prepared work would be thrown away.

A pool removes that: its node builds and proves the template once, and every GPU attached to it searches nonces on that same template in parallel. The GPU never touches the proof. It only does the part it is good at.

The arithmetic question, answered with numbers

Poseidon2b over GF(2^128) needs carryless multiplication. CPUs have it in silicon (VPCLMUL, PMULL); GPUs have to emulate it, which is expensive per operation. The open question was whether parallelism pays for that emulation. It does, and not marginally.

Measured per card, from the pool's own share accounting — the rate implied by shares actually delivered, not what the miner claims about itself:

Code:
  RTX 5090      62 MH/s per card
  RTX 4090      42 MH/s per card
  RTX 5080      32 MH/s per card
  RTX 5070 Ti   26 MH/s per card

One process drives every card in a machine. A four-card rig has been running at ~130 MH/s for hours against a live pool, with rejects in the low single digits per thousand.

Download

github.com/lucasan123/noid-gpu-miner — Windows, Linux, and a HiveOS custom-miner package.

Releases: https://github.com/lucasan123/noid-gpu-miner/releases/tag/v1.0



Code:
  noid-gpu --gpu --coinbase o1YOURADDRESS --worker rig1

Tried and supported pools:
Ariapool: https://pool.ariabrain.com/noid.html
My pool: http://185.189.45.186:3783/

Your NOID address is your login and your payout address; there is no registration. Generate it on your own machine and give out only the public address — never a seed phrase or a wallet file. Mining does not need them, and anyone asking you for them is stealing from you.

Needs an NVIDIA driver 580 or newer. On HiveOS, a jammy or noble image. Verify what you downloaded against SHA256SUMS.txt in the release.

The dev fee, stated plainly

10% of the shares are submitted under the dev fee address instead of yours.


That address is used for nothing else, so anyone can see on chain exactly what this software earns. The fee never changes the coinbase of a block, and never switches mid-search — only between jobs. It is printed in the header on every single run, with the address in full: you do not have to take my word for it, just read the screen. And if the fee cannot be delivered, the miner stops instead of mining, rather than run while showing you something different from what it does.

Yes, 10% is higher than the 1–3% that is usual. It is disclosed, it is verifiable, and nobody has to use it.

Source

Only binaries are published. If you would rather run something you can read, the official parano1d-miner is right there and that is a completely fair choice — I am not going to argue against it.

No warranty of any kind. Mining software moves money; run it only from a source you decided to trust, and decide that for yourself.

bTCBTCbiᴛcoinᗷTCethDOGEzecⅬTCUSDT
Pages: « 1 2 3 4 5 6 7 [8]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!