Qogecoin - We started to work on Qogecoin 2.0(with EVM)

[r0mx1]

@ Hellworker

Why you think so? Where is your proof?

The Developer didnt sell any Qogecoin till now and the Whales buy more and more. The price is really low. Scam makes here no sense.

Nowadays you could tell Scam-Alert to any Altcoin.

For me it is a good project. And soon the Whitepaper will be released.

[1715464762]

1715464762

[1715464762]

1715464762

[1715464762]

1715464762

[SecureFreak]

============ SCAM COIN ALERT ==============

This is a group of people who fork multiple coins, pretends it to be a better project, joins Exbitron exchange and dumps everything.
Then they stop development.

============ SCAM COIN ALERT ==============

Simple way to prove your claims is to let us know what other projects this group is associated with. Since you have it all figured out.

[PostQuantumChain]

============ SCAM COIN ALERT ==============

This is a group of people who fork multiple coins, pretends it to be a better project, joins Exbitron exchange and dumps everything.
Then they stop development.

============ SCAM COIN ALERT ==============

We invite you to check our rule_ll GitHub repository and watch us working

https://github.com/qogecoin/rules_ll

[r0mx1]

rplant mining pool has server issues.


please use for mining qogecoin:

https://zergpool.com/
or
https://zpool.ca/
or
https://murkapool.it/


more pools: https://miningpoolstats.stream/qogecoin

[PostQuantumChain]

We doxed our Team Greetings from Frankfurt and follow us on Twitter

Jannis
https://twitter.com/odysseytospace
https://www.linkedin.com/in/jannis-fengler-250a351b7/

Aaron
https://twitter.com/aaronmondal
https://www.linkedin.com/in/aaron-siddhartha-mondal-24b888233/

Jaro
https://www.uni-frankfurt.de/115631621/M_Sc__Jaro_Eichler
https://www.linkedin.com/in/jaro-eichler-95071a237/

A reminder, we are just doing open source development, we are not operating this Blockchain.
Qogecoin is complete decentral and operated by full nodes, mining pools, and miners.

[TheRecuperater]

Doxed Team members from Germany? NIIIIICE! The future is bright.

[SecureFreak]

We doxed our Team Greetings from Frankfurt and follow us on Twitter

Jannis
https://twitter.com/odysseytospace
https://www.linkedin.com/in/jannis-fengler-250a351b7/

Aaron
https://twitter.com/aaronmondal
https://www.linkedin.com/in/aaron-siddhartha-mondal-24b888233/

Jaro
https://www.uni-frankfurt.de/115631621/M_Sc__Jaro_Eichler
https://www.linkedin.com/in/jaro-eichler-95071a237/

A reminder, we are just doing open source development, we are not operating this Blockchain.
Qogecoin is complete decentral and operated by full nodes, mining pools, and miners.

Awesome. Look forward to seeing how development progresses.

[r0mx1]

from discord: 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.




besides, there was a team meeting:

https://twitter.com/odysseytospace/status/1517667170632744960

[PostQuantumChain]

We have great news: Check out our GitHub repository, Qogecoin is now based on Bitcoin v. 23.99.0
If you are an exchange or a mining pool, please update now. We will soon release the windows build.

Before you update: BACK UP YOUR WALLET

The database is different now, you have to delete your .qogecoin folder BUT: Your wallet is inside that folder.
So: BACK UP YOUR WALLET

Qogecoin will support now Segwit(after blog 400.000), Taprot, MultiSig, Atomic Swaps, Lightning, ...

[PostQuantumChain]

We are really happy to announce the Qogecoin Whitepaper:
https://www.qogecoin.org/_downloads/fd0f7c423eaa00b6deef76295c7a9822/qogecoin_whitepaper.pdf

In the Whitepaper, we are explaining blockchain transactions, classical computers, quantum computers, and Shor's algorithm.
Enjoy! 

[marco89]

We have great news: Check out our GitHub repository, Qogecoin is now based on Bitcoin v. 23.99.0
If you are an exchange or a mining pool, please update now. We will soon release the windows build.

Before you update: BACK UP YOUR WALLET

The database is different now, you have to delete your .qogecoin folder BUT: Your wallet is inside that folder.
So: BACK UP YOUR WALLET

Qogecoin will support now Segwit(after blog 400.000), Taprot, MultiSig, Atomic Swaps, Lightning, ...

I installed 2 days ago the new wallet and started mining (i saw that until pool are not updated i was using wrong address)
where to get an old address/wallet to start mining until they won't update?

[r0mx1]

@marco89

please check discord. :-)

[marco89]

@marco89

please check discord. :-)

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

[PostQuantumChain]

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

[neqochan]

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

Code:

includes=['external/dependency/somepath']

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

Code:

includes=['external/dependency.version/somepath']

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

Code:

relative_includes=['somepath']

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

Code:

includes=['/usr/local/include']

A big quality of life improvement

[r0mx1]

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  

[PostQuantumChain]

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.

[PostQuantumChain]

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.

[PostQuantumChain]

The hard fork was successful
We have Taproot and Segwit now 

[TheRecuperater]

Taproot? Nice 
How many coins have Schnorr signatures?