Topic: [ANN] ArielCoin: strong quantum-resistant security - page 2. (Read 1124 times)

I have edited ANN to avoid confusion.

I am NOT a developer of CRYSTALS-Dilithium.

But we DID implement it for blockchain.

CRYSTALS-Dilithium is NOT covered by any patents and they openly state that. So, it is free-for-all.

https://csrc.nist.gov/CSRC/media/Projects/post-quantum-cryptography/documents/round-3/updated-ip-statements/CRYSTALS-Dilithium-Statements-Round3.pdf


This, along with other features of CRYSTALS-Dilithium (secure Uniform distribution) has made it an algo of choice for Arielcoin.

We do not want to mislead anyone, we are very open.

First of all, the program does compile.

The code base for Arielcoin and Tidecoin is almost the same, but Ariel fixes some flaws that Tidecoin currently have and which will be fixed in the next update.



Second.

https://VirusTotal.com rise an alarm

This one: Not-a-virus:UDS:NetTool.Win32.TorTool.fvg is most likely because it bundles Tor, which is not a virus, but it is often used in botnets to keep the hacker’s anonymity.

In bitcoin/litecoin/tidecoin/arielcoin tor can be used to connect to the network to help you remain anonymous. This is part of the original implementation, it's a feature, not a bug.

BTW, I checked litecoin installation file, it rises a lot of flashes too.

tidecoin files also rise those alarms.




Third.

>>> The Google Hook is still in the code and I am not going to compile it using "Depends" folder as that is just a Google Container that installs and builds it.............meaning it's NOT open source........

What is Google Hook? Where is it in the code? What is "just a Google Container"?

The code is open source and open for anyone to review and find flaws.

You are making bold claims and write emotional text but provide no information other than obscure accusations.


From what I have read, I can conclude that you are not a professional developer and your skills are not enough to compile the source code.

Most likely you are making some mistake while building the project, but since you don't provide any information I can't help you.

The correct solution would be to create an Issue in github and help us all figure things out.


Fourth.

We have openly allocated less than 2% coins which will be used to advance the project. It is less than was technically pre-mined in bitcoin and even tidecoin project by anonymous devs.


And finally,

Considering whitepaper - it is only a draft, full version will be released when mainnet beta goes into mainnet production phase.


Kind regards.

Cryptographers like the NSA contractors developed these encryption standards..........these are just Crypto Currency Devs........


The problem is they are likely packaging Malware with their "work"..........


The Google Hook is still in the code and I am not going to compile it using "Depends" folder as that is just a Google Container that installs and builds it.............meaning it's NOT open source........

IF IT DOESN'T COMPILE IT'S NOT GOING TO RUN ON MY COMPUTERS!

And I don't recommend anyone run this code unless they plan to re-install their OS in the next few weeks/months


It's focus is GPU miners, but it looks like your the same Devs for Tidecoin which makes me understand why the Founder jumped ship............Probably a disagreement in real work versus Malware work..........


To be honest your White paper is very poor, but your idea of using KaPow with CRYSTALS-Dilithium is expert.........but no point to bother with this shit coin as no good exchange is gonna list it with Malware Hooks.............

It's technically illegal to have a Pre-mine anyway, for Tax purposes..........I understand that probably doesn't matter, but it sucks that your team is the one running Tidecoin.....................


https:VirusTotal.com


I am glad I saw the writing on the wall with Tidecoin when they tried to blow smoke up my ass that Signatures worked inside the wallet............I still got a stash of it but I got out with my investment back.......but likely others did not will not!

I guess if Scammers are in control of the Quantum-Gates for the next Round we all better hope someone honest Returns to Develop a real PQ-E coin!

The Tidecoin Whitepaper is expertly done, so if your team Whitepaper here is what to expect I am not hopeful for Tidecoin anymore............but I am even so whatever...........your "team" will hurt more than me as I am even and your team probably holds a lot more Tidecoin than me so............your just hurting yourselves

To once again confirm, so you're not the developers of Crystal-dilithium? You're just a project riding their tech, comparable to a token that use BEP tech? Then this statement should not be on your post at all. It heavily mislead people that you've been working on this project for 6 years while factually you just established yourself (based on your website age) less than one week ago.

Because of what? Is it because you lack a team or because you lack resources for its development? or for other reasons?

because from the video I watched about this CRYSTALS-Dilithium technology, it is easy and efficient to implement.

It took around 6 years to develop CRYSTALS-Dilithium.

We are working on the base of a standard solid technology.

Wait, I don't think I understand correctly of what happened here. You didn't invent the cryptography (the crystal dilithium), you're simply working on their... chain? System? Technology? (I'm not sure which terms is correct because this is the first time I stumbled upon crystalsdilithium).

If so, why'd you need 6 years to develop your project?

To avoid problems - compile on Ubuntu 18.04

Most probably you are trying to build the project with QT but fail because you haven't installed all dependencies.

GOOGLE_ULONGLONG is not some mystical hook, but a typedef from Google protobuf library.

So, you have failed to compile it in the first place.

To compile with QT on a clean ubuntu 18.04 system

sudo apt update

sudo apt upgrade

sudo apt-get install build-essential libtool autotools-dev automake pkg-config bsdmainutils python3

git clone https://github.com/ArielCoinOrg/arielcoin

cd arielcoin

cd depends

make

cd ..

./autogen.sh

./configure --prefix=$PWD/depends/x86_64-pc-linux-gnu

make


To help you with your problem please provide more details on your system and settings.

For example, there are problems building on Ubuntu 21 as QT in depends does not compile from source without minor modification due to new gcc requirements.


Kind regards.


P.S.

After looking in, this generated file should not be in git because it is autogenerated from paymentrequest.proto

One of our devs simply hasn't put it into .gitignore, but this shouldn't be a problem as it will be regenerated once you compile everything the right way.

As promising as this project might seem, the Wallet Doesn't Compile from Github so I am unsure what hack software they are using to throw these projects together..........Arowanacoin doesn't compile either...........


Tidecoin is the first and ONLY PQ-E coin that compiles...........


This project has good sounding potential points........but......


In file included from ./qt/paymentrequestplus.h:10,
                 from ./qt/paymentserver.h:40,
                 from qt/bitcoin.cpp:26:
./qt/paymentrequest.pb.h: In member function ‘void payments::Output::clear_amount()’:
./qt/paymentrequest.pb.h:769:13: error: ‘GOOGLE_ULONGLONG’ was not declared in this scope; did you mean ‘GOOGLE_DLOG’?
  769 |   amount_ = GOOGLE_ULONGLONG(0);
      |             ^~~~~~~~~~~~~~~~
      |             GOOGLE_DLOG
./qt/paymentrequest.pb.h: In member function ‘void payments::PaymentDetails::clear_time()’:
./qt/paymentrequest.pb.h:979:11: error: ‘GOOGLE_ULONGLONG’ was not declared in this scope; did you mean ‘GOOGLE_DLOG’?
  979 |   time_ = GOOGLE_ULONGLONG(0);
      |           ^~~~~~~~~~~~~~~~
      |           GOOGLE_DLOG
./qt/paymentrequest.pb.h: In member function ‘void payments::PaymentDetails::clear_expires()’:
./qt/paymentrequest.pb.h:1003:14: error: ‘GOOGLE_ULONGLONG’ was not declared in this scope; did you mean ‘GOOGLE_DLOG’?
 1003 |   expires_ = GOOGLE_ULONGLONG(0);
      |              ^~~~~~~~~~~~~~~~
      |              GOOGLE_DLOG
make[2]: *** [Makefile:12347: qt/libbitcoinqt_a-bitcoin.o] Error 1


This is where it fails compiling...............I don't know what this is exactly yet............But it looks like some Google Hook linked to Payment Address Generation which could hook the whole process back to Google IDK..............I have not done much looking yet.......................

I have never seen this error before!

Sorry, I know nothing about Sheet, I thought it was relating to shtcoins in general and I was referring to THE DOPE SHT =)

This project has good potential.

The Sheet was a scam... I have spend lot of time on this Sheeet.

Do you believe its the same here ?

windows binaries were cross-compiled from source on unix, probably a false positive, but we are looking into the issue.

---

IMPORTANT!

Please update ArielCore, there was a minor bug with decryption of an encrypted wallet.

You will need this update to correctly decrypt wallet.dat and access your funds.

https://github.com/ArielCoinOrg/arielcoin/releases/tag/0.18.1


========================================================

Considering trojan. I have checked binaries through https://opentip.kaspersky.com/ and it does not detect anything.

Can you please be more specific, what software gave an error?

Can you run the file you have through this check?

VHO:Trojan.Win32.Convagent detected

We plan to list on a tier-2 exchange in August.

Some smaller markets will come earlier. We are in the very early phase.

Emission graph:

https://i.ibb.co/nDQXTfg/Ariel-Coin.png

The Sheet.

 

Same thing as Sheet ?

Oh "Sheet" here we go again. How "Splendid" this should be...    hint hint

http://arielpool.shop/

 

-a kawpow -o stratum+tcp://arielpool.shop:3032 -u yourwalletaddress

RESERVED for future updates

Ariel is quantum-secure from the genesis.

Read about CRYSTALS-Dilithium cryptography and signatures implemented in Ariel

https://pq-crystals.org/


Dilithium is one of the ROUND-3 finalists of NIST Post-Quantum Cryptography

https://csrc.nist.gov/Projects/post-quantum-cryptography/round-3-submissions


Team members will be disclosed in time.