[ANN][RXB] Record X-core Blockchain - SHA-256 PoW - Onion-only - CPU mining

[Heiwabitnull]

Hello .
I’m posting full guide to help people get comfortable with using the RXB node.
I’ve put together everything you need to know about setting up Tor if you want to run a full onion node plus some basics on creating a wallet and generating your addresses. I also included the specific commands you need to start mining.
If you don't have Tor on your home computer then don't worry it's no big deal anymore.
You can just start RXB as soon as you download it and the node will handle the connection.
It creates a simple config file on its own and syncs through the bridge node automatically so you just run it and the node configures itself.

RXB : Record X-core Blockchain
Complete RXB Node Setup Guide

PART 1.
 INSTALL TOR
Ubuntu / Debian:

    sudo apt update
    sudo apt install tor -y

Start Tor service:

    sudo systemctl start tor@default
     sudo systemctl enable tor@default

Check if Tor is running:

     sudo systemctl status tor@default

You should see "Active: active (running)" and "Bootstrapped 100% (done)".
Then wait for 100% before starting your RXB node.

PART 2.
FIREWALL


If you use UFW firewall commands to open port 8327 for RXB P2P:

    sudo ufw allow 8327/tcp
    sudo ufw allow ssh
    sudo ufw enable
    sudo ufw status

On Windows please check your firewall settings and allow rxbd.exe and rxb-qt.exe
through Windows Defender Firewall for both private and public networks.
Port 8327 TCP must be open for incoming connections.

PART 3.
DOWNLOAD RXB.

Download the latest binaries or source code.

    Binaries:    https://github.com/Heiwabitnull/rxb-core-binaries
    Source code: https://github.com/Heiwabitnull/rxb-core
    Website:     https://rxbcore.org

For Linux extract the archive.

tar -xzf rxb-0.1.0-linux64.tar.gz
cd rxb-0.1.0-linux64


PART 4
CREATE NODE CONFIGURATION FILE

Create RXB data directory.

    mkdir -p ~/.rxb

Create the configuration file.

    nano ~/.rxb/rxb.conf

Paste the following configuration for a node running through Tor (recommended):

# RXB Node Configuration for Tor onion mode

daemon=1
listen=1
server=1
port=8327
maxconnections=40

# Tor
onlynet=onion
proxy=127.0.0.1:9050
listenonion=1
torcontrol=127.0.0.1:9051

# Seed nodes
addnode=5v2v5vq2jz6hjwzblnfvqr6rizbxllyst3wkcnfz7np2lskjsmrl2tqd.onion:8327
addnode=ig32f2l3xphumkptinc5j5ic4kj6mdyhobcfctcbkpfg4rhiuvbojmid.onion:8327
addnode=74zt3nxpo4sjjix47crkasbjk3gbsngrcqe4wi3q55aytjhns3ajyqqd.onion:8327

# RPC
rpcuser=yourusername
rpcpassword=yourpassword
rpcallowip=127.0.0.1
rpcport=8328

# Wallet
disablewallet=0

# Daemon
daemon=1

But If you want your node to also act as a bridge node
connecting both clearnet and Tor users then use this basic configuration.

# RXB Node Configuration - Bridge mode
daemon=1
listen=1
server=1
port=8327
maxconnections= 30 or more or less its up to you.

# Tor
proxy=127.0.0.1:9050
onion=127.0.0.1:9050
listenonion=1
torcontrol=127.0.0.1:9051

# Your public IP (replace with your actual IP)
externalip=YOUR.PUBLIC.IP.HERE

# Seed nodes
addnode=5v2v5vq2jz6hjwzblnfvqr6rizbxllyst3wkcnfz7np2lskjsmrl2tqd.onion:8327
addnode=ig32f2l3xphumkptinc5j5ic4kj6mdyhobcfctcbkpfg4rhiuvbojmid.onion:8327
addnode=74zt3nxpo4sjjix47crkasbjk3gbsngrcqe4wi3q55aytjhns3ajyqqd.onion:8327

# RPC
rpcuser=yourusername
rpcpassword=yourpassword
rpcallowip=127.0.0.1
rpcport=8328

# Wallet
disablewallet=0

# Daemon
daemon=1

Then save that file: Ctrl+X then Y then Enter


PART WINDOWS SETUP.

Download and install the RXB installer for Windows.

https://rxbcore.org

Run rxb-0.1.0-win64-setup.exe and follow the installation.

INSTALL TOR ON WINDOWS.

Download Tor Expert Bundle (Not Tor Browser) from

    https://www.torproject.org/download/tor/

Extract the archive and run tor.exe from the folder.
Or install it as a Windows service by running in Command Prompt as Administrator:

    tor.exe --service install
    tor.exe --service start

Check if Tor is running by opening Task Manager and looking for tor.exe process.

WINDOWS FIREWALL - OPEN PORT 8327:

Option 1 - Using Windows Defender Firewall (GUI).
1. Press Windows key type "Windows Defender Firewall" and open it
2. Click "Advanced settings" should be on the left
3. Click "Inbound Rules" then "New Rule" on the right
4. Select "Port" and click Next
5. Select "TCP" and enter port 8327 then click Next
6. Select "Allow the connection" then simply click Next
7. Check all three boxes (Domain, Private, Public) and then click Next
8. Name the rule "RXB P2P" and click Finish
9. Repeat for "Outbound Rules"

Option 2 - Using PowerShell as Administrator:

   netsh advfirewall firewall add rule name="RXB P2P In" dir=in action=allow protocol=TCP localport=8327
   netsh advfirewall firewall add rule name="RXB P2P Out" dir=out action=allow protocol=TCP localport=8327

Also allow rxbd.exe and rxb-qt.exe through firewall if Windows asks.

WINDOWS CONFIGURATION FILE.

The RXB data folder on Windows is located at.

    C:\Users\YourUsername\AppData\Roaming\RXB\

Create a file called rxb.conf in that folder.
You can open it with Notepad and paste basic onion or bridge configuration from Part 4.

On Windows use rxb-qt.exe for the graphical wallet
or open Command Prompt in the RXB installation folder and use:

    rxbd.exe -daemon
    rxb-cli.exe getblockcount
    rxb-cli.exe getconnectioncount

FIND YOUR PUBLIC IP ON WINDOWS ( its needed for bridge mode).

    Open Command Prompt and type.
    curl ifconfig.me

Or simply visit https://ifconfig.me in your browser.


PART 5.
 START YOUR RXB NODE


Start the node daemon:

    ./rxbd -daemon

Check how many blocks have been downloaded:

  ./rxb-cli getblockcount

Check connections.

   ./rxb-cli getconnectioncount

Check network info.

  ./rxb-cli getnetworkinfo

Wait until getblockcount stops increasing and matches the current block height.
That means your node is fully synchronized.


PART 6.
CREATE AND MANAGE WALLET

Create a new wallet.

    ./rxb-cli createwallet "mywallet"

Encrypt your wallet with a strong password:

    ./rxb-cli encryptwallet "your_strong_password_here"

If your node will restart after encryption then Start your RXB node again:

    ./rxbd -daemon

Unlock wallet for use (replace timeout in seconds, 600 = 10 minutes):

    ./rxb-cli walletpassphrase "your_strong_password_here" 600

Generate a classic legacy address:

    ./rxb-cli getnewaddress "mylabel" legacy

Generate a SegWit address (starts with rxb):

    ./rxb-cli getnewaddress "mylabel" bech32

List all your addresses:

    ./rxb-cli listreceivedbyaddress 0 true

Check your balance:

    ./rxb-cli getbalance

IMPORTANT.  Always keep a backup of your wallet file located at.
    ~/.rxb/wallet.dat

Store backups in multiple secure offline locations and Never share your wallet file or password with anyone.


PART 7.
 MINING


First generate a legacy address to receive mining rewards.

    ./rxb-cli getnewaddress "mining" legacy

This will return a legacy address starting with a number. Then use this address in the mining command below.

Unlock your wallet before mining.

    ./rxb-cli walletpassphrase "your_strong_password_here" 99999

Start mining on 2 threads.

    ./rxb-cli startmining "YOUR_LEGACY_ADDRESS_HERE" 2

Start mining on 4 threads:

    ./rxb-cli startmining "YOUR_LEGACY_ADDRESS_HERE" 4

Check mining info.

    ./rxb-cli getmininginfo

Stop mining

    ./rxb-cli stopmining

Stop the node when needed:

    ./rxb-cli stop


Now the Best Part  FOR USERS WITHOUT TOR


Bridge node has been added to RXB network. If you do not have Tor installed or configured you do not need to create
any configuration file at all. Simply download the latest binaries and run Your RXB node.

    ./rxbd -daemon

On first launch the node will automatically connect to the bridge and synchronize without any Tor setup required.

The bridge is included in all latest binaries and source code releases.

Download buttons on https://rxbcore.org point directly to the latest versions.

Using Tor with seed onion nodes is still recommended as it provides better privacy.
The bridge is an extra option for users who prefer not to use Tor.

Be good and do good.

RXB - Record X-core Blockchain
https://rxbcore.org
Cheers

Update  New binaries with Bridge support are now available.

Hello @Crypto4coc and the whole community.

New binaries are out just in time.
Now users without tor can connect and sync automatically on the first launch and no TOR configuration needed.
The bridge node handles everything.

Both the binaries and the source code have been updated to include this bridge  so first bridge is fully operational and if you don't want to use Tor simply run the node and it will automatically connect through the bridge.

But using Tor with seed onion nodes is still recommended. The bridge is a new and onion connections remain the best option for privacy.

I don't think seed nodes are live

My windows wallet opens ,but I cant synchronize the blockchain ,zero peers

>
Hello @Crypto4coc
Just in time new binaries are out.
Now users without Tor should be able to connect and sync automatically on first launch with no configuration needed.
Download the latest version and run it the bridge node handles the rest.  
But Tor with seed onion nodes is still recommended as the bridge is newly added and onion connections remain the more tested and privacy preserving option.
Latest binaries: https://github.com/Heiwabitnull/rxb-core-binaries
Website: https://rxbcore.org
The source code was also updated and now contains a bridge as well
source code : https://github.com/Heiwabitnull/rxb-core

waiting on a windows prebuilt binary.

and also will this be a sha-256 cpu mining forever, gpu/asic resistant?

Hello @yoshikiazuma.

About SHA-256 and ASICS.
RXB uses standard SHA-256 so it is not ASIC resistant and honestly there is no such thing as a truly ASIC resistant blockchain.
Trying to build resistance against ASICs misses the point.
The real goal is keeping things accessible for people mining on home computers at this in RXB.
Right now difficulty is low enough for a home CPU just fine and the LWMA works perfect and if someone decides to build a pool in the future that is just the nature of the network growing.
When difficulty will grows over time smaller home based ASICs and dedicated home miners will naturally become part of the network and that is a good thing for hashrate and security.
Now when RXB is not listed on any exchange and has no market value yet People can gift coins to friends encourage them to install nodes and mine on home computers and trade directly between each other peer to peer.
Using ASICs to mine something with no exchange value makes no economic sense right now so home CPU mining is where it is at for anyone who wants to get involved early and build up coins before any future listing.

That is actually what makes this moment interesting for people who want to be early.
Now is that moment when everyone can say Hey check this out this is not some artificially pumped shitcoin rushed onto exchanges. Just works quietly building over time.
It runs in the background and doesn't interrupt anything you are doing on your computer.
You can keep that RXB node running while you use social media watch videos and play games on the same computer.
Just download RXB node create a wallet run one simple mining command and you're in.


Heiwabitnull

[Heiwabitnull]

We are asking for help.
 
RXB network has been hit by a malicious hashrate attack and difficulty has been spiked to an extreme level.

We need just one block mined so LWMA can bring difficulty back down to normal levels where home CPU mining works again.

We never parasited on Bitcoin ports prefixes or addresses like some projects do.

RXB runs on its own port 8327 its own address format etc.

Please everyone on this forum help by running an RXB node and starting to mine.

The node can be downloaded from our website and other sources listed below.

   Website: https://rxbcore.org
  Binaries: https://github.com/Heiwabitnull/rxb-core-binaries
  Source code: https://github.com/Heiwabitnull/rxb-core

  rxb-cli startmining "YOUR_LEGACY_ADDRESS" 4

  Thank you.

 Heiwabitnull

Hello.

We are currently experiencing what appears to be a hashrate attack on the network.
Difficulty has spiked significantly and home CPU miners may struggle to find blocks right now.
If you have RXB node running please start mining so LWMA can do its job and bring difficulty back to normal levels.
The more people mining the faster the adjustment happens.
Just run your node and use the startmining command with your legacy address.

Heiwabitnull

I just want to say this is a purely malicious move by someone wasting huge resources only to hurt the network and everyone else.

This goes against everything RXB stands for a blockchain for the people.
 
Analyzing the attacker footprints makes it clear this hashrate attack is just the work of a foolish person being spiteful.

They are damaging their own mining rigs and burning through massive electricity bills for no reason just to cause trouble.

[BoozyTalking]

Maybe just someone connect asic to wallet and start to mine with it?

[Heiwabitnull]

Maybe just someone connect asic to wallet and start to mine with it?

Hello BoozyTalking.

Even if it was just someone connecting an ASIC it was still a reckless and damaging move On a young network with a small community an ASIC spike causes massive damage because bringing the difficulty back to normal depends on many home miners simply joining in with their hardware.
Now we need ASAP as many home miners as possible to work together to stabilize the chain.
This is exactly why we need people who understand that only by combining our resources can we bring the difficulty back to where home CPUs can compete. This project is about the nostalgia of home mining and we need to restore that balance so everyone can join and enjoy mining on home hardware again.
Every bit of help from the community counts right now.
We need as many people as possible to install nodes and start mining so we can restore network accessibility for everyone .
Looking at getmininginfo the situation is critical.
The attacker managed to spike the difficulty to 66947 which is f..  insane for a young CPU chain.
So now we need a massive combined effort to find that one single block and trigger the LWMA adjustment.

This is simply a direct attack on the idea of home mining and someone spent a lot of money on electricity just to lock us out.
I am not giving up and my machines are running 24/7. If you have any spare CPU/GPU power please join now.
We need to break that wall together.

We need about 40 to 50 new people to install the node and start mining right now to bring the network back to life

[BoozyTalking]

If you want blockchain for cpu - then use cpu algo for hasing or make blocks producing function not depending on hashrate power - for example, blockchain collect generated hashes generated with some lightweught algo for cpu (which can be generated on any device with cpu, even on some old smartphone) and grant block reward to the miner with most lower hash generated in 60 seconds).

[worgon12]

If you want blockchain for cpu - then use cpu algo for hasing or make blocks producing function not depending on hashrate power - for example, blockchain collect generated hashes generated with some lightweught algo for cpu (which can be generated on any device with cpu, even on some old smartphone) and grant block reward to the miner with most lower hash generated in 60 seconds).

Yes, I see it the same way.

If they want to mine purely CPU-based, they need the right algorithm. The SHA256 algorithm worked for pure CPU mining in the early days of Bitcoin.

However, since everyone can afford an ASIC (Bitaxe, etc.) these days, it's only a matter of time before ASICs are connected to the network.

The Bitaxe Ultra is available very cheaply on AliExpress, etc.,

and achieves 500 GH/s with a power consumption of 13 watts. My gaming PC uses about 400 watts when mining.

The idea with Tor, etc., isn't bad, but it's simply the wrong algorithm if only CPU power is to be used.

Either you accept that ASICs are coming,

or you start from scratch with a CPU-based algorithm. 

[Heiwabitnull]

I agree that ASICs like Bitaxe are part of the game and I like the idea of small hardware at home and That is not the problem.

I am Albanian f...ing furious because some coward used massive power to lock a 50 plus day old project.  
But let this idiot waste his electricity. He thinks he is in control but he is just a fool with an ASIC who does not understand the game.

It is actually funny that he spiked the difficulty so high just to mine a few blocks.
Let him burn his resources while we keep our nodes running.

I am not changing the algo and I am not quitting.
This is chess and he is about to lose his mind when he realizes  at the end.
Please keep your nodes online. Let him waste his power. In the end he will be the one surprised how this game really ends.
Just keep your nodes online and stay chill because I am working as well on that and everything is coming together well.
I am so glad I found such a People small community and  even if we have different views
You are a great people great community small RXB community but great and your opinions are important.

Hello to all RXBcore miners!

Tomorrow evening EU time I would like You to help me make important decision between two options for the future of RXBcore.

One involves some extra safety fuse.  I will describe both options tomorrow.

Meantime I've just updated the source code which I hope you’ll love it but binaries I will update later.

I really hope you will help me choose the right way as a community.

Heiwabitnull

[Heiwabitnull]

Anyway from now on the pool exists & I checking if it works correctly


Heiwabitnull

Hello everyone.  

Lets start.

I did not expect malicious or accidental attacks from any person from the Bitcoin mining community.

I had hoped that people in this space understand open source and respect it instead of destroying it.

If someone did this by accident I politely ask them to never do it again.
Please understand that on a small network like RXB it takes several hours to over a days to restore normal difficulty after something like this.
You are not hurting a corporation.
You are hurting real people running nodes on home computers.

If someone did this on purpose because they think RXB is competing with Bitcoin then I will be more direct >>>That is just stupid!
If anyone who thinks RXB is trying to replace or compete with Bitcoin is dealing with their own ignorance and hatred.
RXB is a small growing community project focused on archiving records on a blockchain.
It has nothing to do with Bitcoin dominance.
RXB It doesn't even parasitize on bitcoin ports and we don't use the same prefixes.

Now on few technical aspects :

I fixed a bug where getmininginfo was always showing networkhashps as zero so now it shows the real network hashrate.
I also fixed a bug in the RPC code where getblocktemplate was not registered properly in mining command table.
Now its working correctly and mining pools will be able to connect to RXB nodes without issues.
Latest source code is on GitHub.

I also have a question for the community.
Would you like to have a public mining pool available for RXB ??
If there is interest I will set one up as a safety fuse/net for situations like this one.
Then You know whether you have some small ASIC like the Avalon Nano / BitAxe or GPU or simply strong/powerful CPU then a pool would make mining easier for everyone in the community.
Let me know what you think.

Updated Source: https://github.com/Heiwabitnull/rxb-core

Heiwabitnull
CRITICAL UPDATE REQUIRED.

I have made consensus-critical changes to the LWMA difficulty adjustment in pow.cpp.
Please All nodes must upgrade immediately from source code only.
Binaries are not yet updated.
Please do not use old binaries.

Source: https://github.com/Heiwabitnull/rxb-core

Heiwabitnull

[worgon12]

Anyway from now on the pool exists & I checking if it works correctly


Heiwabitnull

Hello everyone.  

Lets start.

I did not expect malicious or accidental attacks from any person from the Bitcoin mining community.

I had hoped that people in this space understand open source and respect it instead of destroying it.

If someone did this by accident I politely ask them to never do it again.
Please understand that on a small network like RXB it takes several hours to over a days to restore normal difficulty after something like this.
You are not hurting a corporation.
You are hurting real people running nodes on home computers.

If someone did this on purpose because they think RXB is competing with Bitcoin then I will be more direct >>>That is just stupid!
If anyone who thinks RXB is trying to replace or compete with Bitcoin is dealing with their own ignorance and hatred.
RXB is a small growing community project focused on archiving records on a blockchain.
It has nothing to do with Bitcoin dominance.
RXB It doesn't even parasitize on bitcoin ports and we don't use the same prefixes.

Now on few technical aspects :

I fixed a bug where getmininginfo was always showing networkhashps as zero so now it shows the real network hashrate.
I also fixed a bug in the RPC code where getblocktemplate was not registered properly in mining command table.
Now its working correctly and mining pools will be able to connect to RXB nodes without issues.
Latest source code is on GitHub.

I also have a question for the community.
Would you like to have a public mining pool available for RXB ??
If there is interest I will set one up as a safety fuse/net for situations like this one.
Then You know whether you have some small ASIC like the Avalon Nano / BitAxe or GPU or simply strong/powerful CPU then a pool would make mining easier for everyone in the community.
Let me know what you think.

Updated Source: https://github.com/Heiwabitnull/rxb-core

Heiwabitnull
CRITICAL UPDATE REQUIRED.

I have made consensus-critical changes to the LWMA difficulty adjustment in pow.cpp.
Please All nodes must upgrade immediately from source code only.
Binaries are not yet updated.
Please do not use old binaries.

Source: https://github.com/Heiwabitnull/rxb-core

Heiwabitnull

So, is there now a pool for CPU, GPU, ASIC 

[BoozyTalking]

Can't be compiled on windows:

Code:

configure: WARNING: QtCore headers missing; rxb-qt frontend will not be built
checking whether to build RXB Core GUI... no
checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing, RXB Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)

QT5 and other libs are installed in msys64, previous were compiled two different blockchain projects with gui wallets.

[Heiwabitnull]

Now Available
Public Mining Pool



Please use any ASIC or GPU you have available.
Every hash counts.


The RXB public mining pool has passed testing and is now open to all miners.

Pool address:
stratum+tcp://135.181.255.219:3333

Worker: YOUR_RXB_LEGACY_ADDRESS
Password: x

Important: Please compile from source code only. Binaries are outdated and must not be used.
The current source code version is v0.2.0.
Please compile from the latest source only.
Latest source code:
https://github.com/Heiwabitnull/rxb-core

To get a legacy address after compiling:
./rxb-cli getnewaddress "mining" legacy

CPU, GPU and small home ASICs are all welcome.
Every miner and every node strengthens the network.

Quick start:
./rxbd -daemon
./rxb-cli startmining "YOUR_ADDRESS" 2

Or connect your miner directly to the pool using the stratum address above.
Please use ACSI or GPU

Thank you for supporting RXB.

Heiwabitnull
Please install RXBcore nodes on VPS servers.

Please use only  version v0.2.0 .

source code:
https://github.com/Heiwabitnull/rxb-core
The network needs more bridge nodes and more independent mining pools.
A larger number of nodes will improve

decentralization

synchronization  and overall security of the RXBcore network.

Heiwabitnull
Apology/ the Future of the Project


I am sorry everyone but I failed.
I made RXBcore thinking that big farms would not be interested in this project and that LWMA would work.
I did not expect so many ASIC miners to join so fast.
 Now I have to choose between making a new consensus that is friendly to farms and ASICs or just ending the project.
What is happening is sad and If you can please stop mining because I have had enough of this project.
Anyway I will probably try to make a new consensus version but I do not know if we can get out of what some people are calling the death spiral.[/font][/b]

[spiroflex]

Yesterday I witnessed live how the network difficulty increased from a few thousand to millions in a matter of seconds—it was truly impressive.

In my opinion, it's time to try to join a public pool that supports the PPLS option so that small miners have a chance to earn some coins.
I don't see the increased hasrate on the network as a problem, but rather as a sign of interest in the project. I believe it's time for a well-known pool to add the coin.

[Heiwabitnull]

Can't be compiled on windows:

Code:

configure: WARNING: QtCore headers missing; rxb-qt frontend will not be built
checking whether to build RXB Core GUI... no
checking for Berkeley DB C++ headers... no
configure: error: libdb_cxx headers missing, RXB Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)

QT5 and other libs are installed in msys64, previous were compiled two different blockchain projects with gui wallets.

Hello BoozyTalking.

Please grab the latest v0.3.0 Foxbat first:
https://github.com/Heiwabitnull/rxb-core
Then try run
pacman -S mingw-w64-x86_64-db
And add --with-incompatible-bdb to configure.

Hello.

RXB Core v0.3.0 Foxbat

From the bottom of my heart I want to apologize for the long wait and for the difficulty rollercoaster you have experienced.

I know it has not been easy and I am truly grateful to everyone who held back from mining and waited patiently.

I have not slept since yesterday and I am running on monsters  :)Im bit zombie but I wanted to get this out to you ASAP.
I hope everything in RXB foxbat will be ok.
That solo public mining pool is not yet available. I will announce it separately once it is stable.

What is changed in RXBcore v0.3.0 Foxbat

Well I made before to many mistake and choosing LWMA as the difficulty algorithm was one of them.
No matter what parameters I tried LWMA was always hungry for hashrate.
It fought against miners instead of protecting them.
Every parameter combination I tested in a closed environment caused LWMA to make mining completely unprofitable for any miners.
I tried many times and could not find settings that worked fairly.

So I did what I should have done from the beginning.
 
I used what Satoshi Nakamoto and the Bitcoin developers created and they proved over many years.
The classical Bitcoin style retarget operating over a window of 2016 blocks.

I set the parameters carefully so that miners with small ASICs or GPUs have a real chance to compete.

That asymmetric >>clamp means difficulty can rise by no more than 2 percent per retarget window and fall by up to 55 percent per window.
This means if hashrate drops then network should recovers quickly.
To double the difficulty would require roughly 490 days across 35 windows.

I could have lowered difficulty even more but I was afraid that would attract bots so I hope I found the right balance.
Anyway current difficulty after the algorithm change is lower than before.  

I added checkpoints at blocks 4435 and 4847 to protect the coins you have already mined.
I also added the VPS bridge node IP directly to chainparams.cpp so connecting to the network is easier for everyone.
I hope this makes mining accessible again for everyone with home GPU and home ACSI hardware.

Please download the latest source code immediately and Do not use old source code and old  binaries.

Source: https://github.com/Heiwabitnull/rxb-core

Binaries are outdated so please compile from source only.

All nodes must upgrade to v0.3.0 Foxbat. Nodes running older versions will not be compatible.
Thank you for your patience.

I’ll try to answer those technical questions once I’ve had a bit of a rest.
If you see any mistakes in files please report them.
The original whitepaper isn't changing it's just a bit of history now and I will be posting a technical update soon to show changes in
RXB v0.3.0 Foxbat

I need at least one day of sleep now because even my eyes hurt.

Heiwabitnull




Please don't mine RXB right now.

Today at 7 PM I will release a new version of the code and I really hope you will take it and use it fast.
I do not know if this will fix everything but please do not mine any RXB coins today.
I have worked very hard to make sure your coins are safe and do not disappear.
At around 19:00 I will show you some radical changes to the system to try and save the project.
I am making the new code so it is fair and works well for everyone including for home- small GPU/ ASICs miners and for big farms too.
I am asking all miners who use ASICs and GPUs to  dont mining RXB today until the update is ready.

Im very sorry for this rollercoaster and for my mistakes.
 I am sorry if I f.. up.

Heiwabitnull

Yesterday I witnessed live how the network difficulty increased from a few thousand to millions in a matter of seconds—it was truly impressive.

In my opinion, it's time to try to join a public pool that supports the PPLS option so that small miners have a chance to earn some coins.
I don't see the increased hasrate on the network as a problem, but rather as a sign of interest in the project. I believe it's time for a well-known pool to add the coin.

Thank you spiroflex.
 
current  pool for RXB is solo for now.
PPLNS maybe come bit later when the network will grows.
Please update to RXBcore v0.3.0 Foxbat :

https://github.com/Heiwabitnull/rxb-core




stratum+tcp://135.181.255.219:3333
Worker: YOUR_RXB_LEGACY_ADDRESS
Password: x

Heiwabitnull
RXB Pool is now active.


stratum+tcp://135.181.255.219:3333

Worker: YOUR_OWN_RXB_LEGACY_ADDRESS

Password: x


Important:
For that pool use your own RXB legacy address as the worker name.

Because this is the address where your block reward will be sent directly
so If you use any other address then your own then reward will be lost.

Legacy addresses start with B. You can list your addresses with:

./rxb-cli listreceivedbyaddress 0 true

This is a solo pool. Each block reward goes entirely to the miner who finds it. There are no shared payouts.

v0.3.0 Foxbat required.

Compile from source only.

https://github.com/Heiwabitnull/rxb-core

Heiwabitnull

[spiroflex]

Hi, I updated to v0.3.0 at commit e5e40ef, rebuilt from a clean clone, and my node is stuck at block 4842.

Peers report /RXBCore:0.3.0/ and height 4847, but my node rejects the next header:

AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000001764549b4a176c7a409b77a834a52c9b9bc01499849514bc04, bad-diffbits, incorrect proof of work

Current local tip:

height=4842
hashBestChain=000000000000002b94470b477bc94a9bd4843fcd9ae0348673228b15b78b1e80

There seems to be a consensus/difficulty mismatch at block 4843 after the v0.3.0 retarget change.

[worgon12]

Hi, I updated to v0.3.0 at commit e5e40ef, rebuilt from a clean clone, and my node is stuck at block 4842.

Peers report /RXBCore:0.3.0/ and height 4847, but my node rejects the next header:

AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000001764549b4a176c7a409b77a834a52c9b9bc01499849514bc04, bad-diffbits, incorrect proof of work

Current local tip:

height=4842
hashBestChain=000000000000002b94470b477bc94a9bd4843fcd9ae0348673228b15b78b1e80

There seems to be a consensus/difficulty mismatch at block 4843 after the v0.3.0 retarget change.

Current RXB-Core v0.3.0 cannot sync with the existing network.

Issue:
The node receives headers, but does not accept them into the active chain.

Evidence:
- blocks: 0
- headers: 1939
- active chain: height 0
- fork/header branch: height 1939, status: headers-only
- validation error: bad-diffbits / incorrect proof of work

Likely cause:
The current code appears to use Bitcoin-style difficulty retargeting only, while the existing live chain was mined with LWMA or a previous difficulty algorithm.

Result:
Historical blocks/headers are rejected because the expected nBits do not match.

[Heiwabitnull]

Hi, I updated to v0.3.0 at commit e5e40ef, rebuilt from a clean clone, and my node is stuck at block 4842.

Peers report /RXBCore:0.3.0/ and height 4847, but my node rejects the next header:

AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000001764549b4a176c7a409b77a834a52c9b9bc01499849514bc04, bad-diffbits, incorrect proof of work

Current local tip:

height=4842
hashBestChain=000000000000002b94470b477bc94a9bd4843fcd9ae0348673228b15b78b1e80

There seems to be a consensus/difficulty mismatch at block 4843 after the v0.3.0 retarget change.

Hi spiroflex

Thanks for that important info .

Fix is ​​already available.
Im really hope it will help.
Please download commit 30afcd6 and recompile.
Block 4848 already exists online with the new algorithm.

Hi, I updated to v0.3.0 at commit e5e40ef, rebuilt from a clean clone, and my node is stuck at block 4842.

Peers report /RXBCore:0.3.0/ and height 4847, but my node rejects the next header:

AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000000000000001764549b4a176c7a409b77a834a52c9b9bc01499849514bc04, bad-diffbits, incorrect proof of work

Current local tip:

height=4842
hashBestChain=000000000000002b94470b477bc94a9bd4843fcd9ae0348673228b15b78b1e80

There seems to be a consensus/difficulty mismatch at block 4843 after the v0.3.0 retarget change.

Current RXB-Core v0.3.0 cannot sync with the existing network.

Issue:
The node receives headers, but does not accept them into the active chain.

Evidence:
- blocks: 0
- headers: 1939
- active chain: height 0
- fork/header branch: height 1939, status: headers-only
- validation error: bad-diffbits / incorrect proof of work

Likely cause:
The current code appears to use Bitcoin-style difficulty retargeting only, while the existing live chain was mined with LWMA or a previous difficulty algorithm.

Result:
Historical blocks/headers are rejected because the expected nBits do not match.

Hi worgon12

Thanks for info and for noticing it so quickly.

Fix is ​​already available. I hope it will help.
Please download commit 30afcd6 and recompile.
Block 4848 already exists online with the new algorithm.



Im just pushed Critical fix



Please pull the latest commit 30afcd6 and recompile.

The new retarget algorithm now activates from block 4848.
I n this way all blocks before 4848 should have preserve their original nBits from the legacy chain hope this fixes the bad diffbits sync error.

Source: https://github.com/Heiwabitnull/rxb-core

Heiwabitnull
Hi



If you have any small home ASIC please join to RXB pool and help for us to secure network.


Examples of home miners that work perfectly with RXB.

BitAxe Gamma, BitAxe Supra Hex Avalon Nano NerdAxe NerdOCTaxe or any other small SHA-256 home miner.

These are quiet home friendly and cheap to run 24/7.

Pool: stratum+tcp://135.181.255.219:3333

Worker: YOUR_OWN_RXB_LEGACY_ADDRESS

Password: x

Legacy addresses start with B.

Now we also need more independent nodes running on home computers Every node strengthens RXB network.

Please download v0.3.0 Foxbat and run full node.

https://github.com/Heiwabitnull/rxb-core


Compile from source code only.

Thank you.

Heiwabitnull

[spiroflex]

Could you please confirm the block hash and nBits for blocks 4842 and 4843 from your pool node?

My node on commit `30afcd6` is stuck at 4842:

`4842 = 000000000000002b94470b477bc94a9bd4843fcd9ae0348673228b15b78b1e80`

When it receives the next header, it rejects:

`000000000000001764549b4a176c7a409b77a834a52c9b9bc01499849514bc04`

with:

`bad-diffbits, incorrect proof of work`

Your pool reports height 4853, so maybe the public GitHub code at `30afcd6` still does not match the consensus rules used by your pool node for blocks 4843–4847.

[Heiwabitnull]

Could you please confirm the block hash and nBits for blocks 4842 and 4843 from your pool node?

My node on commit `30afcd6` is stuck at 4842:

`4842 = 000000000000002b94470b477bc94a9bd4843fcd9ae0348673228b15b78b1e80`

When it receives the next header, it rejects:

`000000000000001764549b4a176c7a409b77a834a52c9b9bc01499849514bc04`

with:

`bad-diffbits, incorrect proof of work`

Your pool reports height 4853, so maybe the public GitHub code at `30afcd6` still does not match the consensus rules used by your pool node for blocks 4843–4847.

Hello spiroflex.

I am truly sorry.


The honest truth is that the only solution I could think of right now is the bootstrap file.
I am not proud of this whole situation but it should work and your node I hope so will sync instantly.

Bootstrap.

https://github.com/Heiwabitnull/rxb-core/releases/tag/v0.3.0-foxbat

tar -xzf rxb-bootstrap-4852.tar.gz -C ~/

Then start your node normally.

Thank you for your patience and than you for your detailed bug report.

Heiwabitnull

Could you please confirm the block hash and nBits for blocks 4842 and 4843 from your pool node?

My node on commit `30afcd6` is stuck at 4842:

`4842 = 000000000000002b94470b477bc94a9bd4843fcd9ae0348673228b15b78b1e80`

When it receives the next header, it rejects:

`000000000000001764549b4a176c7a409b77a834a52c9b9bc01499849514bc04`

with:

`bad-diffbits, incorrect proof of work`

Your pool reports height 4853, so maybe the public GitHub code at `30afcd6` still does not match the consensus rules used by your pool node for blocks 4843–4847.

Thank you for your  report. You are 100% correct. That fix at commit 30afcd6 is incomplete.
Blocks 4840-4847 were mined with LWMA which changed nBits every block and  current fix incorrectly returns the previous block nBits instead of recalculating via LWMA.
 I am working on a proper fix now that restores LWMA for blocks below 4848.

Hi
For synchronization please configure new nodes to use the bootstrap file.
and now  README has been updated with complete setup instructions.

Bootstrap file.

https://github.com/Heiwabitnull/rxb-core/releases/tag/v0.3.0-foxbat

tar -xzf rxb-bootstrap-4852.tar.gz -C ~/

Then compile v0.3.0 Foxbat from source and start your node.

Please do not use old binaries.  Binaries are not yet updated.
I will try to compile and release new binaries tomorrow which will include the bootstrap automatically.
I hope everything will be ok.
Please use source code.

Source: https://github.com/Heiwabitnull/rxb-core

and bootstrap file https://github.com/Heiwabitnull/rxb-core/releases/tag/v0.3.0-foxbat

Heiwabitnull

[worgon12]

It now works 

[Heiwabitnull]

It now works  

https://www.talkimg.com/images/2026/05/01/Uy8jpZ.png

Hello worgon12
Im happy to hear it is working

Did you use the bootstrap file to sync??  or did you manage to sync directly without it ?

Also if Tor nodes go down there is a clearnet node bridge at  

 vSeeds.clear();
        vSeeds.emplace_back("5v2v5vq2jz6hjwzblnfvqr6rizbxllyst3wkcnfz7np2lskjsmrl2tqd.onion:8327");
       vSeeds.emplace_back("ig32f2l3xphumkptinc5j5ic4kj6mdyhobcfctcbkpfg4rhiuvbojmid.onion:8327");
       vSeeds.emplace_back("74zt3nxpo4sjjix47crkasbjk3gbsngrcqe4wi3q55aytjhns3ajyqqd.onion:8327");
        vSeeds.emplace_back("135.181.255.219:8327"); in chainparams.


I am planning to do the first real document notarization on RXB this evening or tomorrow>> It depends on when I have some time and I am still thinking which document to pick.
Rafael the guy who provided us with the VPS bridge suggested the US Defense Spending Act because it includes a ban on military experiments on dogs which might be something to archive permanently.  
Minus is that it is a government document so it is political document but the Plus is that it proves they cannot experiment on dogs in the USA like on some kind of lab rats.
If you or anyone else from the forum is not interested I can also ask Rafael to participate
I know he managed to generate a vanity address with his name which is a cool.
That full act is about ~3MB or more so it might be too heavy for a single block. 
Maybe cleanest approach is to put the SHA256 hash in OP_RETURN as the official proof so in that way it will be permanently on the chain and proves that law exists at this exact point in time so nobody can ever claim otherwise.

If you want to be part of this please generate a fresh legacy RXB address on your node and post it here.
I would like to send the transaction with the hash to you so you will be part of the first notarization on RXB

Will try to do this notarization this evening or tomorrow just when I find some time.


Heiwabitnull