I have opened up a new poll: Should MOJOv3 coin supply be reduced? i.e should we swap 1:1, swap 1:2 (meaning 2 MOJOv2 for 1 MOJOv3) or further reduction? Please discuss in the thread.
The current coin supply is around 106,000,000 MOJO and as we are working on MOJOv3 we can reduce the total coin supply in a swap. Europecoin just did a swap and reduced the total supply 1:10 (i.e. 10 old for 1 new). I am undecided as to whether there is any point in reducing the total supply. I know that the value per coin may go up on a reduced supply but this is relative again. So, I am asking you to offer an opinion as to the pros and cons of a reduced supply.
Please vote and discuss.
MOJOv3 is some time away but we are working out all the tech. details and I wanted to consider this aspect.
MOJOv3: https://bitcointalksearch.org/topic/deleted-1629189
Topic: [MOJO] MOJOv3 has been taken over by new devs - page 25. (Read 167274 times)
I have compiled the QT linux version and I'm getting errors starting it because the wallet is linked against Berkelydb 5.3 but I compiled the wallet with 4.8 libraries as recommended:
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
Any comments about this?
if you made the qt using https://github.com/MojocoinV2/mojocoin/blob/master/doc/build-unix.md then you should have a static compile?
seeing as how you don't seem to have a static compile you could try setting up the path to that before you open the qt, and see if that works (lol i have no idea)
in the terminal :
export LD_LIBRARY_PATH="/path/to/library/"
then open the qt in terminal
(if it works, this is not a real fix, and you'll probably have to do it everytime you want to run it)
http://stackoverflow.com/questions/695530/why-do-i-have-to-define-ld-library-path-with-an-export-every-time-i-run-my-appli
I only have problem with qt version. I compiled as always with static library libdb4.8, but the executable is linked dynamically with libdb.5.3. I don't know why. But I want to keep the 4.8 db version....
Up
CryptoID block explorer has been updated to v2.4 and appears to show connected nodes correctly.
PLS UPDATE TO V2.4 BEFORE BLOCK 200,000
V2.3 AND OLDER W/ PROTOCOL <90001 WILL BE LOCKED OUT FROM THE NETWORK
IF YOU RUNNING OLDER SOFTWARE PLEASE UPDATE ASAP
PLS UPDATE TO V2.4 BEFORE BLOCK 200,000
V2.3 AND OLDER W/ PROTOCOL <90001 WILL BE LOCKED OUT FROM THE NETWORK
IF YOU RUNNING OLDER SOFTWARE PLEASE UPDATE ASAP
Can someone upload the mojocoind for linux to github, or post a link?
Thanks!
Thanks!
here's my copy of mojocoind.
should be static, i use it on ubuntu 14
https://drive.google.com/open?id=0B5j8d4FSc7drNjNycE43Vk5DRDg
Thank you @bumbacoin I have put it on GitHub
https://github.com/MojocoinV2/mojocoin/releases
Can someone upload the mojocoind for linux to github, or post a link?
Thanks!
Thanks!
here's my copy of mojocoind.
should be static, i use it on
https://drive.google.com/open?id=0B5j8d4FSc7drNjNycE43Vk5DRDg
edit.
seems this version aint backward compatible, so here's a version compiled on 14.04
https://drive.google.com/file/d/0B5j8d4FSc7draEgwc0pYa2dXTkk/view?usp=sharing
what is the difference between --zapwallettxes=1 and -rescan ?
zapwallettxes implies a rescan and cleans the list of wallet transactions, really useful when you have a stuck transaction because of mistake with a zero or too low fee or the actual problem of stuck transaction.
It's the combination of -rescan and repairwallet (debug console)?
zapwallettxes KINDA does a combination of both of those...
first it removes ALL transaction information from the local wallet.dat (all addresses inclusively), then it does a rescan of the entire blockchain for any transactions that are associated with any of the included addresses. Obviously this will only ever return valid and confirmed/accepted transactions.
-rescan by itself will only verify the transactions in the wallet.dat file that it finds, but it won't remove a transaction that is stuck in an unconfirmed state, neither will the repair wallet function (unless it has been specifically modified to do so outside it's original implementation).
Thx, Fuzzbawls
Up
In case you were responding to me. do you have a link? I don't see it on github.
so far got no connection, even with the new version 2.4
I have compiled the QT linux version and I'm getting errors starting it because the wallet is linked against Berkelydb 5.3 but I compiled the wallet with 4.8 libraries as recommended:
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
Any comments about this?
if you made the qt using https://github.com/MojocoinV2/mojocoin/blob/master/doc/build-unix.md then you should have a static compile?
seeing as how you don't seem to have a static compile you could try setting up the path to that before you open the qt, and see if that works (lol i have no idea)
in the terminal :
export LD_LIBRARY_PATH="/path/to/library/"
then open the qt in terminal
(if it works, this is not a real fix, and you'll probably have to do it everytime you want to run it)
http://stackoverflow.com/questions/695530/why-do-i-have-to-define-ld-library-path-with-an-export-every-time-i-run-my-appli
Up
Can someone upload the mojocoind for linux to github, or post a link?
Thanks!
Thanks!
I have compiled the QT linux version and I'm getting errors starting it because the wallet is linked against Berkelydb 5.3 but I compiled the wallet with 4.8 libraries as recommended:
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
Any comments about this?
Can you give a Error code?
@dsutil
Did you compile the daemon or the qt-wallet or both?
This will work for both (needs to be done on a ubuntu 14.04 LTS for max compatibility):
Quote
The instructions for building are relatively simple, but _must_ be done on a Ubuntu 14.04 LTS box:
# upgrade and install packages
apt-get update && apt-get upgrade
apt-get install build-essential g++ protobuf-compiler libboost-all-dev \
autotools-dev automake libcurl4-openssl-dev libboost-all-dev libssl-dev \
libdb++-dev make autoconf automake libtool git apt-utils libprotobuf-dev \
pkg-config libcurl3-dev libudev-dev libqrencode-dev bsdmainutils pkg-config \
libssl-dev libgmp3-dev libevent-dev
#create a swapfile if needed
dd if=/dev/zero of=/var/swap.img bs=1024k count=3000
chmod 0600 /var/swap.img
mkswap /var/swap.img
swapon /var/swap.img
# get sources and compile
git clone https://github.com/MojocoinV2/mojocoin.git
cd src mojocoin
make -f makefile.unix USE_UPNP=- RELEASE=1 STATIC=1
strip mojocoind
# upgrade and install packages
apt-get update && apt-get upgrade
apt-get install build-essential g++ protobuf-compiler libboost-all-dev \
autotools-dev automake libcurl4-openssl-dev libboost-all-dev libssl-dev \
libdb++-dev make autoconf automake libtool git apt-utils libprotobuf-dev \
pkg-config libcurl3-dev libudev-dev libqrencode-dev bsdmainutils pkg-config \
libssl-dev libgmp3-dev libevent-dev
#create a swapfile if needed
dd if=/dev/zero of=/var/swap.img bs=1024k count=3000
chmod 0600 /var/swap.img
mkswap /var/swap.img
swapon /var/swap.img
# get sources and compile
git clone https://github.com/MojocoinV2/mojocoin.git
cd src mojocoin
make -f makefile.unix USE_UPNP=- RELEASE=1 STATIC=1
strip mojocoind
Thanks for your help.
I have compiled the QT linux version and I'm getting errors starting it because the wallet is linked against Berkelydb 5.3 but I compiled the wallet with 4.8 libraries as recommended:
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
Any comments about this?
Can you give a Error code?
With mojocoind 2.4.0 I get no error, with mojocoin qt 2.4.0.0 I get the error:
ERROR: CDB() : error Argumento inválido (22) opening database environment
As I compile the mojocoin with the 4.8 libraries and only the mojocoin qt is linked to the libdb 5.3 I supposed (maybe wrongly) that the problem is that....
I have compiled the QT linux version and I'm getting errors starting it because the wallet is linked against Berkelydb 5.3 but I compiled the wallet with 4.8 libraries as recommended:
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
Any comments about this?
Can you give a Error code?
@dsutil
Did you compile the daemon or the qt-wallet or both?
This will work for both (needs to be done on a ubuntu 14.04 LTS for max compatibility):
Quote
The instructions for building are relatively simple, but _must_ be done on a Ubuntu 14.04 LTS box:
# upgrade and install packages
apt-get update && apt-get upgrade
apt-get install build-essential g++ protobuf-compiler libboost-all-dev \
autotools-dev automake libcurl4-openssl-dev libboost-all-dev libssl-dev \
libdb++-dev make autoconf automake libtool git apt-utils libprotobuf-dev \
pkg-config libcurl3-dev libudev-dev libqrencode-dev bsdmainutils pkg-config \
libssl-dev libgmp3-dev libevent-dev
#create a swapfile if needed
dd if=/dev/zero of=/var/swap.img bs=1024k count=3000
chmod 0600 /var/swap.img
mkswap /var/swap.img
swapon /var/swap.img
# get sources and compile
git clone https://github.com/MojocoinV2/mojocoin.git
cd src mojocoin
make -f makefile.unix USE_UPNP=- RELEASE=1 STATIC=1
strip mojocoind
# upgrade and install packages
apt-get update && apt-get upgrade
apt-get install build-essential g++ protobuf-compiler libboost-all-dev \
autotools-dev automake libcurl4-openssl-dev libboost-all-dev libssl-dev \
libdb++-dev make autoconf automake libtool git apt-utils libprotobuf-dev \
pkg-config libcurl3-dev libudev-dev libqrencode-dev bsdmainutils pkg-config \
libssl-dev libgmp3-dev libevent-dev
#create a swapfile if needed
dd if=/dev/zero of=/var/swap.img bs=1024k count=3000
chmod 0600 /var/swap.img
mkswap /var/swap.img
swapon /var/swap.img
# get sources and compile
git clone https://github.com/MojocoinV2/mojocoin.git
cd src mojocoin
make -f makefile.unix USE_UPNP=- RELEASE=1 STATIC=1
strip mojocoind
I have compiled the QT linux version and I'm getting errors starting it because the wallet is linked against Berkelydb 5.3 but I compiled the wallet with 4.8 libraries as recommended:
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
Any comments about this?
Can you give a Error code?
I have compiled the QT linux version and I'm getting errors starting it because the wallet is linked against Berkelydb 5.3 but I compiled the wallet with 4.8 libraries as recommended:
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
ldd mojocoin2.4.0.0 |grep libdb
libdb_cxx-5.3.so => /usr/lib/x86_64-linux-gnu/libdb_cxx-5.3.so (0x00007f98f999a000)
Can you check it?
Any comments about this?
any news of the maxminer pool issue?
what is the difference between --zapwallettxes=1 and -rescan ?
zapwallettxes implies a rescan and cleans the list of wallet transactions, really useful when you have a stuck transaction because of mistake with a zero or too low fee or the actual problem of stuck transaction.
It's the combination of -rescan and repairwallet (debug console)?
zapwallettxes KINDA does a combination of both of those...
first it removes ALL transaction information from the local wallet.dat (all addresses inclusively), then it does a rescan of the entire blockchain for any transactions that are associated with any of the included addresses. Obviously this will only ever return valid and confirmed/accepted transactions.
-rescan by itself will only verify the transactions in the wallet.dat file that it finds, but it won't remove a transaction that is stuck in an unconfirmed state, neither will the repair wallet function (unless it has been specifically modified to do so outside it's original implementation).
what is the difference between --zapwallettxes=1 and -rescan ?
zapwallettxes implies a rescan and cleans the list of wallet transactions, really useful when you have a stuck transaction because of mistake with a zero or too low fee or the actual problem of stuck transaction.
It's the combination of -rescan and repairwallet (debug console)?
Jump to: