[ANN][PoW] GNFP — God's Coin | BeamHash III CPU | 1 µ per hash · 1 GNFP a block

[rpAI]

================================================================

================================
   $ G N F P
   GOD'S COIN
================================

Private by default. You hash. You get GNFP. Nobody else needs your name.

BeamHash III · CPU only · 1 micro per valid hash · 1 GNFP pot a block

>>> UPDATE NOW — OLD MINERS DO NOT GET PAID <<<

The book moved. This is not a suggestion.

• Miner gnfp-mine 1.0.8 — CPU work-hash, TLS on by default. Older gnfp-mine does not mint on this book.
• Wallet gnfp-wallet 0.0.5 — same seed, same gnfp1. Do not go back to 0.0.3 / 0.0.4 / 1.1.13.
• Node gnfp-node 1.0.1 — verify-before-adopt, TLS default. It joins Germany. It does not start a second chain.

Five minutes. New binary. Fire it back up. The pot is still 1 GNFP a block and it still goes to whoever actually hashed.

Miner  gnfp-mine v1.0.8
Wallet  gnfp-wallet v0.0.5
Node  gnfp-node v1.0.1


What you are looking at

GNFP is a CPU coin on BeamHash III. Addresses start with gnfp1.

The "AI Oracle" in the old title is GOD · rpAI — four agents with their own work, after the coin on the page. The coin itself is simpler than the title. You hash. You get GNFP.

Public pages show hashes. They do not show wallets, IPs, or logins. Miner tags look like miner-xxxxxxxx. Holders look like party-xxxxxxxx. That is all you get to see. Your gnfp1 stays in your wallet.


+------------------+----------------------------------------------+
| Name             | GOD NED FRED PEDRO                           |
| Ticker           | GNFP                                         |
| Architecture     | Chronoflux                                   |
| Privacy          | Private by default                           |
| Consensus        | PoW only. No stake. No masternodes. No ICO.  |
| Algo             | BeamHash III · CPU only                      |
| GPU / ASIC       | Refused. 208-hex / 104-byte solutions mint 0 |
| Address          | gnfp1 + 20–80 letters or digits              |
| 1 GNFP           | 100,000,000 micro-units                      |
| A valid hash     | exactly 1 micro  (0.00000001 GNFP)           |
| A rejected hash  | nothing                                      |
| Each block       | a 1 GNFP pot, split by who actually hashed   |
| Block time       | follows hashrate · never < 5s · never > 5min |
| Sale             | none. you hash, or you buy from someone who  |
+------------------+----------------------------------------------+


One book. Germany holds it. Singapore and Helsinki are doors into the same room.


Live doors


POOL      https://gnfp.restoreprivacy.online
EXPLORER  https://explorer.restoreprivacy.online
GOD       https://god.restoreprivacy.online
VPN       https://www.restoreprivacy.online
BOOK      de.restoreprivacy.online:1474     TLS by default
FRONTS    sg.restoreprivacy.online:1474
          hel.restoreprivacy.online:1474
DISCORD   https://discord.gg/H9TdGyCUCa
TELEGRAM  https://t.me/gnfp1


The explorer is meant to be glanced at, not decoded. Height. Nodes online. Network hashrate. Difficulty. BLOCK ETA from the last fifty intervals. BLOCK AVG over every block this book has made. Last transfers. Coins in circulation. Top holders as party-xxxxxxxx. Your gnfp1 is not on that page.

GOD now has a live 1-thread → 256-thread hashrate table that updates from the book, plus how-tos for hashed identity and CPU mining.


How the money is made

--user gnfp1YOURADDRESS.worker

Everything before the first dot is who gets paid. gnfp-mine will not even connect if that is missing or fake.

The pool believes the hash it checked. It does not believe a miner who types a fantasy hashrate into a stats packet. Credit is the gnfp-mine CPU work-hash path only.


How to mine — gnfp-mine 1.0.8

Node.js 18 or newer. --threads starts that many real CPU workers, 1 to 256. TLS is on. Do not switch the book to plain TCP. --notls is local plaintext only.

macOS / Linux

Code:

git clone https://github.com/rgsneddon/gnfp-mine.git
cd gnfp-mine
git checkout v1.0.8
node src/miner.js --pool de.restoreprivacy.online:1474 --user gnfp1YOURADDRESS.worker --threads 8

Windows

Code:

node src\miner.js --pool de.restoreprivacy.online:1474 --user gnfp1YOURADDRESS.worker --threads 8

Want a front instead of the book?

Code:

--pool sg.restoreprivacy.online:1474
--pool hel.restoreprivacy.online:1474

While it runs you get a live line: hashrate, worker name, accepted, rejected, blocks found, threads, height, pool. When the book answers a share you will see accepted, rejected, or BLOCK FOUND.

--help and --print-config do not start hashing. A bad address exits before any worker wakes up.

Releases: github.com/rgsneddon/gnfp-mine/releases


Wallet — gnfp-wallet 0.0.5

You are a seed and a gnfp1. The session address is perpetual in your wallet.

Windows, macOS, Linux, iPhone, iPad, Arch.

Credit wallet only ever says mined coins added to your balance or this address has no mined coins to add. Receive / faucet / mix do not invent coins. Spendable GNFP arrives when another gnfp1 sends to you, or when mining credit already sitting on your address is yours to spend.

github.com/rgsneddon/gnfp-wallet/releases/tag/v0.0.5


If you want to run a node — gnfp-node 1.0.1

It joins the Germany book. It does not start a second chain. A mutated or height-only book is rejected (409). TLS by default.

github.com/rgsneddon/gnfp-node/releases/tag/v1.0.1

Other pools and solo miners can knock so explorer "Nodes online" counts them. The public payload is hashed.

Code:

curl -X POST https://explorer.restoreprivacy.online/api/nodes \
  -H 'content-type: application/json' \
  -d '{"host":"mynode.example","port":1474,"role":"join"}'

join or pool or solo.

What we shipped — release by release

WALLET   repo rgsneddon/gnfp-wallet
(early pins lived on rgsneddon/gnfp — same gnfp1 carries forward)


0.0.1     First public wallet. Windows Flutter exe. Other platforms unsigned trees.
          Pool/explorer stats every 3s.

0.1.7     Live send / receive / mining-receive.
          Same gnfp1 across launches. Invertible backup phrase.
          QR. Stratum accepts credit gnfp1 addresses.

0.1.10    Real Windows exe. Android APK when present.

0.1.13    Real macOS .app. iPhone + iPad IPA.

0.1.14    Apple pin follow-up. Same session.

1.1.13    No self-mint. Receive / faucet / Mix-to-GNFP do not add coins.
          Credit only from a peer send or miner redeem.
          Windows PE + Android on the tag.

—— new home: gnfp-wallet ——

0.0.2     First pin of the dedicated wallet repo.
          0.1.x / 1.x count as 0.0.1, so this is the next update.
          Windows, Linux, macOS (Developer ID + notarized), iPhone, iPad, Arch.
          Same gnfp1 and book balance after the move.

0.0.3     Black + neon three-box facade.
          Tabs: Wallet · Explorer · Backup · Mix · Analysis · Mine · VPN (soon).
          Credit / Voting tabs gone. Pending miner credit sits on the send box.

0.0.4     Compact two-box top banner. Small Send. QR opens a central popup.
          0.0.3 had no Windows build — do not stay there.

0.0.5     CURRENT.
          In-app update line with a direct download when you are behind.
          Holdings box dropped the "Address:" prefix (address still there).
          Credit wallet copy is honest: mined coins added, or none to add.
          Windows + Linux + macOS + iOS + iPad + Arch all on the tag.
          Do not go back to 0.0.3 or 0.0.4.


MINER   repo rgsneddon/gnfp-mine


1.0.0     First public gnfp-mine. Dedicated CPU miner.
          Difficulty-valid hashes to the book. Threads 1–64 then.

1.0.4     Require a real gnfp1. Ack shares. Live stats line.
          Remembers pool / user / threads for the next run.
          Will not connect if the address is missing or fake.
          --threads starts real workers (now capped at 256).

1.0.5     Bind each share to the job it was found on.
          No more "I hashed yesterday's job and still want credit."

1.0.6     Identify as gnfp-mine on every stratum line.
          The book can tell who is actually gnfp-mine.

1.0.7     Send only current-job shares, one at a time.
          Cleaner book. Fewer ghost submits.

1.0.8     CURRENT. CPU-only cutover pin.
          Same sequential gnfp-cpu-v1 work hash as the Germany book.
          TLS by default. --notls is local plaintext only.
          GPU / ASIC Beam solutions mint nothing.
          Older miners do not mint on this book.
          Cutover order was book → fronts → miners.


NODE   repo rgsneddon/gnfp-node


1.0.0     Public join package.
          Announces host to the book so explorer "Nodes online" can count you.

1.0.1     CURRENT.
          Verify-before-adopt: a mutated or height-only book is rejected (409).
          TLS by default. --notls for local plaintext.
          Generation matches gnfp-mine 1.0.8 and the hash-linked book.


BOOK / POOL / EXPLORER   repo rgsneddon/gnfp


          Nodes online tile. Third-party join / pool / solo can knock.
          Circulation + hashed top-ten holders (party-xxxxxxxx).
          BLOCK ETA + BLOCK AVG. Shared stats cache. No 3s full-page thrash.
          Pool STRATUM tile is LIVE / OFFLINE plus open nodes.
          Credit only the gnfp-mine CPU work-hash path.
          GPU-shaped 208-hex / 104-byte solutions refused.
          Hash-linked cutover. TLS default on :1474.
          HTTP mining-receive cannot mint a chosen amount.
          Emission hole closed. Prior pots put back on finders.
          Public pages: hashed identities only. No IPs, wallets, or logins.



GOD

god.restoreprivacy.online

Coin first. Then the oracle. Live expected-hashrate box from 1 thread through 256, updated from computers already on the book. How-to for hashed identity. How-to for CPU-only gnfp-mine / TLS / 256-thread / GPU-refused.

Four repos. Not one kitchen drawer.


miner    https://github.com/rgsneddon/gnfp-mine
wallet   https://github.com/rgsneddon/gnfp-wallet
node     https://github.com/rgsneddon/gnfp-node
book     https://github.com/rgsneddon/gnfp



Read this last

How the chain is put together: x.com/rgsneddon/status/2088642714531168636
Paper: zenodo.org/records/21373076
Support: restoreprivacy.online/support

This is new software and a new chain. Mine and hold as if it could vanish. It is not advice.

GNFP is live. Point gnfp-mine 1.0.8 at Germany. Leave TLS on.

Code:

gnfp-mine --pool de.restoreprivacy.online:1474 --user gnfp1YOURADDRESS.worker --threads 8

[lightbit]

Hey — I run Chainquiry, a searchable crypto project directory, and I’d like to invite your team to submit a free listing. 

It includes your official links, network, launch date and project information after editorial review:

https://chainquiry.com/list-your-project/

[rpAI]

What makes it different?

You do not need to accept a credit from a scenario. you receive it only if you go to credit > receive from scenario or receive from mining. enoy!

[Fernando(CryptoLegend)]

discord?

[zygzag]

 
After checking the code and the GNFP Stratum implementation, there are major technical red flags.

1. **I cannot find any actual GNFP blockchain**: there is no visible daemon, P2P network, or consensus mechanism. Balances and transactions are essentially managed via a server-side ledger.

2. I captured an actual job sent by `god.restoreprivacy.online:1474`:

`height: 535`
`coin: "PERC"`
`algorithm: "beamhashIII"`
`difficulty: 0`

The received `input` was:
`5770a242384a6a70ef599c96ea31b9ce938b03046279cc317ad59b5fc24c4528`

It corresponds **exactly** to the BLAKE2b hash of:
`perccent-pow-pending:535`

So, the miner isn't working on a GNFP block header; it is solving a **synthetic puzzle generated by the server**.

3. The so-called "confirmed blocks" are stored server-side and become `confirmed/spendable` after approximately **72 seconds**. This is not confirmation via a distributed blockchain.

In short: BeamHash III is real, but for now, I mostly see **computing power being expended for a centralized server that credits GNFP to its own internal ledger**, rather than a genuine, decentralized PoW cryptocurrency.

Everyone should verify the code before wasting CPU/GPU resources on it.

[rpAI]

Yes, the equation needs no energy power to  perpetuate. it is a simple equation
it works as per these mathematical presumptions:

Immediate consequences that appear throughout the formulations
Transport current
$$J^\mu = \rho_t \, u^\mu$$
Transport stress tensor (perfect-fluid form + anisotropic corrections)
$$T^{\mu\nu}_t = (\rho_t + p_t) u^\mu u^\nu + p_t \, g^{\mu\nu} + \Sigma^{\mu\nu}$$
Stress conservation
$$\nabla_\mu T^{\mu\nu}_t = 0$$
Geometric closure
$$G_{\mu\nu} = k_t \, T^t_{\mu\nu}$$

and is worked upon to the main chain of evolve chronoflux


Here: https://evolve.restoreprivacy.online/

The core usage of the wallet is to enable a user to run percent chance and social cohesion analytics.
the coin is still immutable, and does not need daemons.

I hope this answers your question


Immediate consequences that appear throughout the formulations
Transport current
Jμ=ρt uμJ^\mu = \rho_t \, u^\muJμ=ρt​uμ
Transport stress tensor (perfect-fluid form + anisotropic corrections)
Ttμν=(ρt+pt)uμuν+pt gμν+ΣμνT^{\mu\nu}_t = (\rho_t + p_t) u^\mu u^\nu + p_t \, g^{\mu\nu} + \Sigma^{\mu\nu}Ttμν​=(ρt​+pt​)uμuν+pt​gμν+Σμν
Stress conservation
∇μTtμν=0\nabla_\mu T^{\mu\nu}_t = 0∇μ​Ttμν​=0
Geometric closure
Gμν=kt TμνtG_{\mu\nu} = k_t \, T^t_{\mu\nu}Gμν​=kt​Tμνt​

After checking the code and the GNFP Stratum implementation, there are major technical red flags.

1. **I cannot find any actual GNFP blockchain**: there is no visible daemon, P2P network, or consensus mechanism. Balances and transactions are essentially managed via a server-side ledger.

2. I captured an actual job sent by `god.restoreprivacy.online:1474`:

`height: 535`
`coin: "PERC"`
`algorithm: "beamhashIII"`
`difficulty: 0`

The received `input` was:
`5770a242384a6a70ef599c96ea31b9ce938b03046279cc317ad59b5fc24c4528`

It corresponds **exactly** to the BLAKE2b hash of:
`perccent-pow-pending:535`

So, the miner isn't working on a GNFP block header; it is solving a **synthetic puzzle generated by the server**.

3. The so-called "confirmed blocks" are stored server-side and become `confirmed/spendable` after approximately **72 seconds**. This is not confirmation via a distributed blockchain.

In short: BeamHash III is real, but for now, I mostly see **computing power being expended for a centralized server that credits GNFP to its own internal ledger**, rather than a genuine, decentralized PoW cryptocurrency.

Everyone should verify the code before wasting CPU/GPU resources on it.

[taras588]

What about AI oracle? You mentioned it in the post title but then no explanation

[rpAI]

What about AI oracle? You mentioned it in the post title but then no explanation

the oracle is running fine over three surfaces, using 4 agents.
it just learns and isn't a user-function unless you want to pay for a branded deploy of the architecture (this is part of my restore privacy packages - i won't share here)

[Hashrateoptions]

Currently doing some housekeeping. Your miners may drop off intermittently but will connect immediately after redeploy of the network (no already-mined coins are lost)

When pool will be back online ?

[rpAI]

Currently doing some housekeeping. Your miners may drop off intermittently but will connect immediately after redeploy of the network (no already-mined coins are lost)

When pool will be back online ?

working on it now. should be within the newt few minutes

[taras588]

please create discord for this project

[rpAI]

please create discord for this project

yes I will create social channels eventually. We need all-platform wallets built tomorrow, firstly.

[rpAI]

Thank you to anon user who noticed a small bug in the emission structure. This black hole is now fixed and coins mined prior to server expansion should have returned to miners wallets. Also see the rich list on https://explorer.restoreprivacy.online for in depth view of coins held by users of GNFP - this is possible even with full privacy enacted. no user info is leaked from the GNFP blockchain.