Pages:
Author

Topic: Qogecoin - We started to work on Qogecoin 2.0(with EVM) - page 2. (Read 3673 times)

newbie
Activity: 2
Merit: 0
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 Cheesy
copper member
Activity: 27
Merit: 0
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
member
Activity: 157
Merit: 10
@marco89

please check discord. :-)

yes, i confirm problem was solved. I wrote here before writing on discord.
my fault, i was using wrong address.
newbie
Activity: 17
Merit: 0
@marco89

please check discord. :-)
member
Activity: 157
Merit: 10
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?
copper member
Activity: 27
Merit: 0
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! 
copper member
Activity: 27
Merit: 0
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, ...
newbie
Activity: 17
Merit: 0
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

newbie
Activity: 4
Merit: 0
We doxed our Team Smiley Greetings from Frankfurt and follow us on Twitter Wink

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.
newbie
Activity: 9
Merit: 0
Doxed Team members from Germany? NIIIIICE! The future is bright.
copper member
Activity: 27
Merit: 0
We doxed our Team Smiley Greetings from Frankfurt and follow us on Twitter Wink

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.
newbie
Activity: 17
Merit: 0
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
copper member
Activity: 27
Merit: 0
============ 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 ============== Kiss

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

https://github.com/qogecoin/rules_ll
newbie
Activity: 4
Merit: 0
============ 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 ============== Kiss

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.
newbie
Activity: 17
Merit: 0
@ 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.
newbie
Activity: 2
Merit: 0
============ 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 ============== Kiss
sr. member
Activity: 1419
Merit: 275
Community built, Privacy driven
Fingers crossed guys, I think that Qoge has chance to rise nice in the near future. You are doing nice work.
copper member
Activity: 27
Merit: 0
The white paper is slowly taking shape. We had a super productive meeting yesterday in which we went through it line by line and fixed errors and ambiguities. In a few days our team will meet again and we will continue.  💪
newbie
Activity: 17
Merit: 0
Quote
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 .

Source: Discord



Quote
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

Source: Discord



Welcome to QOGE everyone 
https://youtu.be/yhPsyoVPdSQ

Video done by Community Member Cyrik!

[moderator's note: consecutive posts merged]
newbie
Activity: 4
Merit: 0
Get it while it's hot. Mining hash rate has nearly doubled over the last few hours.
Pages:
Jump to: