neqochan
 —
@qogekun and I discussed the test infrastructure we will use to test the new signature scheme.

We will containerize the Qogecoin core and then use Kubernetes manifests to start multiple full nodes in a local Kubernetes cluster. This should be easy because we do not need to think about ingresses, load balancers etc. We only need it to run locally for testing.

Then we can test how different signature schemes change the communication (and transaction) speeds and stability of the network.

If things work as we expect we may be able to use "classic" cloud monitoring tools (e.g. Kiali) via service meshes (e.g. Istio) to investigate traffic properties when using different signature schemes.

Essentially we want to be able to start a complete local Qogecoin testnet with one click.

Since Qogecoin uses almost the same codebase as Bitcoin, Litecoin etc this approach should also work with minimal adjustments to create e.g. local Bitcoin testnets.

As soon as this works with full nodes we can start looking into lightning nodes. Ideally we want to have a "one click lightning node" deployment for existing kubernetes apps such as online stores.

So in short: We will have soon the Qogecoin testnet. But the testnet will be a local Kubernetes cluster.

rules_ll has been released.

https://github.com/qogecoin/rules_ll

rules_ll has various benefits over other toolchains.

rules_ll produces statically linked executables per default. This means that executables built with rules_ll have no dependencies on the underlying operating system.

Since we use upstream LLVM/Clang, there is practically no compiler toolchain that will produce faster binaries. If someone pushes an optimization to the LLVM repo today, it is instantly available with rules_ll. Currently, the rules_ll toolchain is roughly 6 months ahead of the toolchains 'regularly' available in package distributions (Clang 15.0.0 😀 ).

We plan to add more features from the LLVM project such as automatic compilation database generation for clang-tidy.
Ah and for end users this all means that the entire downloading of dependencies, building of the toolchain and compiling of custom code is done via a single command like

bazel build myproject



Thats it. No further setup required. So end users clone a repo that uses rules_ll, execute that command and they have an executable 🥳

Update on the miner:

We successfully created build system overlays for the four AMD repositories HIP, hipamd, ROCclr and ROCm-OpenCL-Runtime. CUDA also seems to work fine.

Instead of building all these repositories separately we now only need a single command to build all of them. We do not depend on the AMDs HIP-clang compiler, and we do not need NVIDIAs nvcc compiler. Everything compiles with a regular LLVM/Clang toolchain. Building this entire AMD stack now takes us less than 15 seconds 😂

We are currently working on adding a build system overlay for ROCm-Device-Libs as the last piece of the puzzle, which requires us to create a toolchain for compilation from LLVM IR to LLVM Bitcode. Then we will be able to compile GPU kernels for both AMD and NVIDIA with a single command 🥳.

Alright, I'll try to figure it out myself. From my short test, this is the most profitable coin currently on my hardware. Makes 2-3x more than Raptoreum.

-AMD-

AMD E2 1800 = 7 h/s

Ryzen 5 1600 = 900 h/s
Ryzen 5 2600 = 800 h/s
Ryzen 5 3600 = 748 h/s
Ryzen 5 5600x = 1200 h/s

Ryzen 7 1800x = 1200 h/s
Ryzen 7 2700 = 1100 h/s
Ryzen 7 3700X = 1320 h/s

Ryzen 9 3900x = 1500 h/s
Ryzen 9 3900xt = 1800 h/s

EPYC 7282 = 1100 h/s

-INTEL-

pentium g3250 120 h/s

i3-530 = 240 h/s
i3-3220 = 380 h/s
i3-3227U = 220 h/s
i3-3240 = 324 h/s
i3-6100 = 330 h/s

i5-3410m = 285 h/s
i5-4440 = 633 h/s
i5-4590S = 630 h/s
i5-6300 = 430 h/s

i7-3770 = 820 h/s
i7-4510U = 280 h/s
i7-4790 = 600 h/s
i7-7500U = 300 h/s
i7-7700 = 1150 h/s
i7-7700k = 525 h/s
i7-9700 = 993 h/s
i7-10750H = 1427 h/s

x5680 = 850 h/s

E5-2620 = 610 h/s

E5-2620-V2 = 600 h/s (Turbo Boost Unlock)
E5-2670-V2 = 753 h/s
2 X E5-2696-V2 = 1490 h/s

E5-2620-V3 = 534 h/s
E5-2640-V3 = 1020 h/s (Turbo Boost Unlock)
E5-2670-V3 = 821 h/s (Turbo Boost Unlock)
2 X E3-2678-V3 = 2800 h/s
E5-2683-V3 = 737 h/s
E5-2683-V3 = 946 h/s (Turbo Boost Unlock)

E5-1650-V4 = 631 h/s
E5-2630-V4 = 800 h/s

Once it hits public 1 time, that quantum hpc broke crypto...the qoge will be waiting...silently in the near distant future...like a tank propelled by the tears of quantum orphans..a home welcoming the huddled masses..but with anti-quantum hounds at the ready. ..Hungry, vicious hounds..(who can benchpress cars it looks like?)

Our coin is per default better than the most cryptocurrencies. The tokenomics is deflationary (vs. dogecoin) but not to deflationary (vs. tidecoin), the mining algorithm is ASIC resistant (vs. Bitcoin) it is GPU and CPU minable (vs. ETHereum). With DarkGravity3 we protect us against attacks from mining pools, which want to profit from slow difficult adjustment. It is a memecoin and we (the devs) are working active on it with new technologies like Bazel, Clang/LLVM, HIP.
We appreciate real criticism and suggestions for improvement and we don't like to ban people from our server because we value free expression of speech. But if you keep trolling, we will ban you.

Quantum-safe signatures¶

Qogecoin will introduce a quantum-safe signature type for addresses.

We are currently waiting for the results of the NIST post-quantum safety competition to ensure that we choose an academically approved signature scheme.

See e.g. PQClean/PQClean and open-quantum-safe/liboqs for implementations.

The Development Roadmap and a (questionably inofficial) Community Whitepaper have been released.🥳

https://www.qogecoin.org/development-roadmap.html
https://www.qogecoin.org/community-whitepaper.html