Topic: Qogecoin - We started to work on Qogecoin 2.0(with EVM) (Read 3461 times)

An interesting project, more than 1 year without new and discussions. 

Looks like another dead topic for a dead coin on a dead forum.

Its a meme thing carved out of pure compassion toward humans largely lost around coinmarketcap charts and rankings. No one knows why dipshits make meme coins in coin constructor in copious amounts. Not even them. I guess the reason is that crypto collective anticipates a looming bull market starting just in days or maybe weeks, with its sweeping effect on every crypto thing out there.

Is this coin a scam and currently premine dumping takes place ? I guess so...

What post quantum cryptography do you plan to implement ?

How will the future of Qogecoin look? It will be Quantum Safe!
We wrote a mini wallet with quantum-safe signatures. It is highly beta, we will use FALCON Round 3 in production,
but liboqs supports only the round 2 standard right now.


https://github.com/eomii/toolbox

I don't know,
TBH i keep mining because i have some hope on this. let's see

Project is still alive?

We started to work on Qogecoin 2.0
Qogecoin 2.0 will be a completely new Layer 1 chain and quantum-safe from block 0.
We will deprecate the Bitcoin Codebase, Qogecoin 2.0 will be based on Ethereum.
It will be 100% EVM compatible, so you can build amazing projects with smart contracts on it.
When we are done with development, you can swap your Qogecoin 1.0 for Qogecoin 2.0.
It will be also based on POW.

The merge is coming. We will made a new release with a checkpoint. Many GPU miners will be looking for new chains and we want to make sure they can't change the Qogecoin history with more hashing power.

This will be the last release from this Qogecoin repository. We will soon release a new codebase with a much cleaner commit history. This will make it easier for us to always stay upstream to Bitcoin. The new codebase will replace Qogecoin/Qogecoin on Github so that nothing will change for you

https://github.com/qogecoin/qogecoin/releases/tag/v.23.100.0

Potentially interesting discussion from Discord:

modnar()
 —
Yesterday at 9:52 PM
What makes Qogecoin better than other cryptocurrencies that boast some form of hardness to a quantum threat?
securefreak
 —
Today at 5:07 AM
I'll answer, since no one else has. Nothing, right now.
and it will remain that way until something tangible is produced that can take advantage of the coin.
Right now the only way to hold QOGE is a wallet that requires a desktop computer and that only works on Windows and Linux right now. An Mac wallet apparently is being worked on but unsure if it works with the new macs with M1/2 processors
So until either the people who created the coin get things out or there is more involvement in the community to help them, there is not really anything that stands out at all right now
neqochan
 —
Today at 8:13 AM
Additionally to what @securefreak said, it should be mentioned that we are the only QS-focused cryptocurrency that is upstream with Bitcoin. This means that we build on a very stable, well tested codebase.

This is a stark contrast to most other Altcoins in general, which are usually based on very old versions of bitcoin or litecoin. We were originaly also based on such an old codebase and had a hardfork a few weeks ago to migrate all functionality such as segwit. This makes Qogecoin a lot feature-richer by default than most altcoins regardless of quantum safety.

Some currencies have completely custom codebases, but unless one has a huge team like Solana, I don't think it is feasible to implement something from scratch. We have very high standards regarding production quality of software in general and completely writing a Blockchain from scratch that satisfies these requirements is currently unrealistic for us.

Apart from Quantum safety we focus heavily on infrastructure that is viable in the long term. I don't think there are many other Altcoins where the developers are contributing fixes to open source projects like Clang/LLVM and hipSYCL (and likely the experimental Carbon language soon) to make the absolute bleeding edge of software infrastructure usable for their Project.

Taproot? Nice 
How many coins have Schnorr signatures?

The hard fork was successful
We have Taproot and Segwit now 

We made a new release: https://github.com/qogecoin/qogecoin/releases/tag/v.23.100.0

There was a bug in the new wallet, so we had to change the bech32 prefix.
The bech32 prefix will be "bq" and the harfork will happen in about 24h.

The Qogecoin hardfork will happen in less than 3 days (at block 400.000). The update will activate segwit and other features. 
Please update your nodes.

yesterday (21.06) there was an etherium meetup in frankfurt a.m. (germany) => https://twitter.com/_brainbot/status/1535188418468118530
one of the devs (jannis) was one of the speaker. he talked about the problem of quantum computers vs crypto (encryption).

the video will be uploaded on youtube. if it happens i will link the video here.

hopefully soon  

Introduced relative_includes, relative_angled_includes, transitive_relative_includes and transitive_relative_angled_includes in https://github.com/eomii/rules_ll/releases/tag/20220612.0. These let us use workspace-relative imports in our build files. This makes custom dependency overlays much easier to maintain.

Before this change we had to use something like to use custom include paths. This was already not pretty before bzlmod, but didn't really manifest itself as an issue since old workspace includes had no version numbers and as such would stay usable across updates.

With bzlmod every dependency has a version number, so these paths became This made it very painful to maintain overlays, as we had to bump that version in every instance of these include attributes.

With the new relative attributes we can now simply use to achieve the same. So we no longer need to update every attribute instance when we bump a version. The old way is still present so that we can use out-of-tree local include paths such as
A big quality of life improvement

Some thoughts on the implementation of Quantum safe Signatures and the future of Qogecoin:

There are 3 ways to do it:

1 Way: We take something like Falcon, Dilithium or Sphincs+
The advantage: Stateless
The disadvantage: Big signatures, big blockchain size

2. Way: We take something like Merkle signature schemes, like XMSS
The advantage: Little Public keys, little Signatures
The disadvantage: State

3. Way: We take a signature that has a very little Signature size and a big public key. We only use the hashes of the public keys in the blocks.
We additionally introduce a key pool that contains all public keys. An alternative would be to make the public key reveal only 1 time, after that
you just can use the hash maybe with a block number reference.
The advantage: Scalable, Efficient, little Blocks
The disadvantage: It's a big redesign

yes, i confirm problem was solved. I wrote here before writing on discord.
my fault, i was using wrong address.

@marco89

please check discord. :-)