no answer about the 1 month parking ?
Hello easyrimka!
1 month period will implemented in MinexBank shortly.
Topic: Minexcoin - A new era of payments - page 857. (Read 646965 times)
Hello easyrimka!
1 month period will implemented in MinexBank shortly.
i just want to check out what is possible with a VPS.
but after i checked the pool stats i think that GPUs are already mining. is this correct?
but after i checked the pool stats i think that GPUs are already mining. is this correct?
yes for sure...
i installed the needed package. but still this error.
sudo apt-file find libstdc++.so.6
then i found this
libstdc++6: /usr/lib/x86_64-linux-gnu/libstdc++.so.6
thats why i installed with
sudo apt-get install libstdc++6
but still the same error.
i installed the needed package. but still this error.
sudo apt-file find libstdc++.so.6
then i found this
libstdc++6: /usr/lib/x86_64-linux-gnu/libstdc++.so.6
thats why i installed with
sudo apt-get install libstdc++6
but still the same error.
Quote
~/Linux x64# strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_DEBUG_MESSAGE_LENGTH
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_DEBUG_MESSAGE_LENGTH
The problem is that the mxminer binary is built against a too-recent version of gcc-glibc++. The vast majority of (installed) linux distributions use older toolchains. The binary needs to be rebuilt, it is not a dependency problem (unless you want to upgrade your entire linux system which is not a good option).
switching from 14.4 to 16.4 ubuntu solved it.
.... which is not a good solution (unless you don't care about breaking everything else on your server, potentially).
yes for sure...
i installed the needed package. but still this error.
sudo apt-file find libstdc++.so.6
then i found this
libstdc++6: /usr/lib/x86_64-linux-gnu/libstdc++.so.6
thats why i installed with
sudo apt-get install libstdc++6
but still the same error.
i installed the needed package. but still this error.
sudo apt-file find libstdc++.so.6
then i found this
libstdc++6: /usr/lib/x86_64-linux-gnu/libstdc++.so.6
thats why i installed with
sudo apt-get install libstdc++6
but still the same error.
Quote
~/Linux x64# strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_DEBUG_MESSAGE_LENGTH
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_DEBUG_MESSAGE_LENGTH
The problem is that the mxminer binary is built against a too-recent version of gcc-glibc++. The vast majority of (installed) linux distributions use older toolchains. The binary needs to be rebuilt, it is not a dependency problem (unless you want to upgrade your entire linux system which is not a good option).
switching from 14.4 to 16.4 ubuntu solved it.
no answer about the 1 month parking ?
yes for sure...
i installed the needed package. but still this error.
sudo apt-file find libstdc++.so.6
then i found this
libstdc++6: /usr/lib/x86_64-linux-gnu/libstdc++.so.6
thats why i installed with
sudo apt-get install libstdc++6
but still the same error.
i installed the needed package. but still this error.
sudo apt-file find libstdc++.so.6
then i found this
libstdc++6: /usr/lib/x86_64-linux-gnu/libstdc++.so.6
thats why i installed with
sudo apt-get install libstdc++6
but still the same error.
Quote
~/Linux x64# strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_DEBUG_MESSAGE_LENGTH
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_DEBUG_MESSAGE_LENGTH
The problem is that the mxminer binary is built against a too-recent version of gcc-glibc++. The vast majority of (installed) linux distributions use older toolchains. The binary needs to be rebuilt, it is not a dependency problem (unless you want to upgrade your entire linux system which is not a good option).
yes for sure...
i installed the needed package. but still this error.
sudo apt-file find libstdc++.so.6
then i found this
libstdc++6: /usr/lib/x86_64-linux-gnu/libstdc++.so.6
thats why i installed with
sudo apt-get install libstdc++6
but still the same error.
i installed the needed package. but still this error.
sudo apt-file find libstdc++.so.6
then i found this
libstdc++6: /usr/lib/x86_64-linux-gnu/libstdc++.so.6
thats why i installed with
sudo apt-get install libstdc++6
but still the same error.
Quote
~/Linux x64# strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_DEBUG_MESSAGE_LENGTH
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_DEBUG_MESSAGE_LENGTH
you're missing some dependancies
A Linux version of the pool miner is now available. New binaries are up @ eu.minexpool.nl
This also includes Windows binaries with experimental cuda support. Instructions in the readme file.
x64 bit only.
For any questions please join T.me/mxpool on telegram.
This also includes Windows binaries with experimental cuda support. Instructions in the readme file.
x64 bit only.
For any questions please join T.me/mxpool on telegram.
any help with this:
./mxminer: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./mxminer)
./mxminer: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by ./mxminer)
bugs ive noticed while signing up on minexbank
1. the wallet is missing a "unlock" feature, its possible with walletpassphrase command but a qt should have the button
2. 2fa doesnt work when i set it up its saying "otp validation failed"
1. the wallet is missing a "unlock" feature, its possible with walletpassphrase command but a qt should have the button
2. 2fa doesnt work when i set it up its saying "otp validation failed"
Hello tehMoonwalker!
In answer to your recent question please be advised about the following:
1. It will be implemented according to development plan.
2. This is caused by bad time adjustment. Google 2FA feature will be replaced by another security algorithm shortly.
Not everyone has there coins from bounties and ICO. They should have their coins before we get on ANY exchange. It's not right or fair. So STOP IT.
Hello Flunder707!
This is the exact reason why we are not on exchange and we informed the community about it earlier in thread.
No no no, that is not right, the reason your coin not list at exchange is because no listing accept you coin
dont lie dude, just tell people the truth.
Just wait patiently because they are working in the background sometimes it is very tough for technical people to build the end project. Already they mentioned dates please give some time to them.
today my parking went to pending @dev can you plz check
add: XNBo2ujju1KqNti4zJa6vjtbocjR9vYjuf
add: XNBo2ujju1KqNti4zJa6vjtbocjR9vYjuf
Hello deep4u!
Please check your PM.
When the market opened for minexcoin sales, I wait as soon as possible. And I hope the price is maintained with the price ico sales thank you.
Is Minexcoin already in some exchange? If you do not have a forecast? I need to remove my ...Hello!
We are planning to launch on exchange several weeks after the MinexBank release (Aug 9, 2017)
Why again do you write SeveraL WeekS AfteR LauncH- this makes me hopeless... Awwe!!!
Hello sieemma!
We will be able to tell the date by the end of August. We will announce it as soon as it is set.
Not everyone has there coins from bounties and ICO. They should have their coins before we get on ANY exchange. It's not right or fair. So STOP IT.
Hello Flunder707!
This is the exact reason why we are not on exchange and we informed the community about it earlier in thread.
No no no, that is not right, the reason your coin not list at exchange is because no listing accept you coin
dont lie dude, just tell people the truth.
When the market opened for minexcoin sales, I wait as soon as possible. And I hope the price is maintained with the price ico sales thank you.
Hello!
We are planning to launch on exchange several weeks after the MinexBank release (Aug 9, 2017)
We may be able to understand if you can explain the problem even we are ready to help if needed
Don't act as if you were some artificial intelligence.
Hello!
The date is not set as we have not distributed all the ICO and bounty coins yet, so we simply cannot announce it.
As informed earlier in the thread, we are as much interested in launching to the exchange you are, however we cannot tolerate any kind of discrimination of even one single participant of Bounty or ICO campaigns. This is because after we launch in the exchange, participants who have already received their coins will find themselves in a much more advantageous situation than those whose applications have not been processed for various reasons.
We are working hard to complete distribution as soon as possible.
Thank you for being patient.
Not everyone has there coins from bounties and ICO. They should have their coins before we get on ANY exchange. It's not right or fair. So STOP IT.
Hello Flunder707!
This is the exact reason why we are not on exchange and we informed the community about it earlier in thread.
i dont think minexcoin would be able to pass howey test and get listed on bittrex, correct me if i m wrong.
yes you are right, Bittrexx never accept MNX, also Yobit never accept MNX
this MNX no where to go for listing, probably dead coin allready.
lol.. Maybe you have MNX from bounty. I will buy it at 1 satoshi since you believe that this is already a dead project.
...
1. the minexbank site is clean very nice and works good, only a few minor bugs (2fa needed refreshing alot etc)
...
1. the minexbank site is clean very nice and works good, only a few minor bugs (2fa needed refreshing alot etc)
...
While we're on the subject of 2FA, right now I can't get it to work at all. Possibly because I'm too slow in getting the QR code scanned.
It needs to be debugged to work even if someone (like me) takes 2-3 minutes to get from scanning to inputting the code. Right now by the time it takes me to scan the QR code, the 2FA code is invalid.
Also on the main web page for minexbank, it needs to say "Get Started" not "Get start"... (Get smart?)
Thanks
Rob.
Hello robbieburns!
Thank you for the feedback, we will correct the wording.
We are aware of the QR-code issue and currently working to fix it. In the meantime you can enter the code in your phone.
A Linux version of the pool miner is now available. New binaries are up @ eu.minexpool.nl
This also includes Windows binaries with experimental cuda support. Instructions in the readme file.
x64 bit only.
For any questions please join T.me/mxpool on telegram.
This also includes Windows binaries with experimental cuda support. Instructions in the readme file.
x64 bit only.
For any questions please join T.me/mxpool on telegram.
Good job mate, I'll be running that on my server ASAP.
OK trouble in paradise
Code:
$ ./start_mining.sh
./mxminer: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./mxminer)
./mxminer: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by ./mxminer)
./mxminer: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./mxminer)
./mxminer: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by ./mxminer)
Can you please build this with a more legacy version of gcc and/or provide statically linked binaries?
Thanks
Rob.
i dont think minexcoin would be able to pass howey test and get listed on bittrex, correct me if i m wrong.
yes you are right, Bittrexx never accept MNX, also Yobit never accept MNX
this MNX no where to go for listing, probably dead coin allready.
Jump to: