The code is not public yet and will not be until released.
The algorithm has be chosen as sha3d (sha3-256 double round). We are currently in the testing phase to make sure miners (CPUMiner/SRB) and pools are compatible with the selection.



To be clear, there will be no premine, no dev fee, no tail emissions, no airdrops  and no promise of future value.

(Blazr2 approved this message)

Unobtanium is being reborn with BTC's most current stable code base (27.1).
(hereby referred to as Un)

This will not be a by-product of mining other coins (aka Merge mining, AUXPOW), it will be it's own unique chain. The maximum coin emission (250000) with remain the same with a different schedule.

The mining algorithm is being researched and has yet to be decided. Emerging cryptocurrencies are experimenting with novel mining algorithms that seek to improve efficiency, reduce environmental impact, or enhance security. The majority of these are based from the SHA3 winner (Keccak) and/or candidates list (BLAKE, Grøstl, JH, Skein, CubeHash, Echo, Fugue, Hamsi, Luffa, Shabal, SHAvite-3, SIMD). Multiple round algorithms (x11, x12, x13, x14, x15, x16r, x16rv2, x16s, x17, x22i) of this type do not offer any hardware based acceleration. That being said - the official SHA3 winner (Keccak) which does offer hardware based acceleration is seriously being considered.

The idea of a possible chainswap is not out of the question. Although based on Cryptoid's Rich List - most of the current Un remains dormant or lost through the multiple forks that have occurred. Perhaps it's best to start from scratch.

The logic in the original source code for total coin emission is infinite and not limited to 250000 coins (even though it will take forever to mine). 0.01 UNO is the perpetual block subsidy.  This would require a hard fork to fix.
The difficulty (modified KGW) algorithm is also broken. It only averages the previous block (not a days worth of blocks as it was initially intended). This would account for the difficulty spikes and uneven block times the current chain is facing. This also would require a hard fork to fix.

The preliminary code has already been made. We would like the support of the current community. Any concerns or recommendations will be considered.
This project was born for the sake of having something to do on Friday night.

We are still old school, you know where to find us on IRC (Libera)

Unfortunately we will have to wait for all nodes (mostly mining/pool nodes) to update for the patch to take affect. At the time of this writing there are only three updated nodes out of fifty two.

Sample of updated pool node:
http://bits.silentpatriot.com/tx/f146b8894661be29c83036977ec9da8791638a24ee123b65160edf60a81fb7c2

This has been fixed in the master repository. Re-pull your source, re-compile, delete mncache.dat in the data directory and all should be well.
Enjoy your day.

Suggested that you use the depends compilation method via the source, otherwise a mismatched version of OpenSSL will cause errors with signatures with this ancient software.

e.g.
(via Docker Debian:buster for best results)
git clone ...
cd depends
make
cd ..
./autogen.sh
./configure --prefix=`pwd`/depends/x86_64-pc-linux-gnu (or whatever host you built it for)
make