Topic: [ANN][ARG] Argentum || A New Begining || UPDATE YOUR WALLET || - page 29. (Read 59661 times)
It's also likely they upgraded and somehow forked, so they might be upgrading again right now.
There seems to be an unexpected blockchain fork.
I have created a newer up to date bootstrap file to help.
http://argcurrency.org/download/bootstrap.zip
iSpace.co.uk is up to date on the right fork, so you can refer to that for a valid block height.
ChainzID seems to be on the wrong blockchain at the moment,
all main sync nodes are on the right blockchain.
please use the new bootstrap file and resync onto the proper chain.
Thank you.
Crypt
I have created a newer up to date bootstrap file to help.
http://argcurrency.org/download/bootstrap.zip
iSpace.co.uk is up to date on the right fork, so you can refer to that for a valid block height.
ChainzID seems to be on the wrong blockchain at the moment,
all main sync nodes are on the right blockchain.
please use the new bootstrap file and resync onto the proper chain.
Thank you.
Crypt
If you take a look at the overview https://chainz.cryptoid.info/arg/#!overview it looks like CryptoID just stopped for roughly 3hrs and 17mins; look at 28 June 2016 at block 1796711 and 1796710. They've also stalled again at 1797211 for 1hr 37mins so far. It doesn't even look like they are on the correct day. From what I gather, the time depicted should be close to GMT. Why does their entire site say June 28th.I feel like I'm missing something obvious.
Working on getting another block explorer online.
There seems to be an unexpected blockchain fork.
I have created a newer up to date bootstrap file to help.
http://argcurrency.org/download/bootstrap.zip
iSpace.co.uk is up to date on the right fork, so you can refer to that for a valid block height.
ChainzID seems to be on the wrong blockchain at the moment,
all main sync nodes are on the right blockchain.
please use the new bootstrap file and resync onto the proper chain.
Thank you.
Crypt
I have created a newer up to date bootstrap file to help.
http://argcurrency.org/download/bootstrap.zip
iSpace.co.uk is up to date on the right fork, so you can refer to that for a valid block height.
ChainzID seems to be on the wrong blockchain at the moment,
all main sync nodes are on the right blockchain.
please use the new bootstrap file and resync onto the proper chain.
Thank you.
Crypt
Litecoinpool.org is ready for merged mining at block 1,800,000!
Spread the word and get your votes in for ARG on Slushpool at https://slushpool.com/proposal/detail/572/
Multipool.us, please come be our friend.
Prohashing.com is up-to-date
Still waiting on word from Cryptopia on when the wallet will be back online.
I believe CryptoID still needs to upgrade. Please reach out to them on twitter
Coinexchange.io has upgraded
Cryptopools, hash-to-coins, ispace - still in maintenance mode.
bitcoinpool.us - i have no idea
Cheers
Spread the word and get your votes in for ARG on Slushpool at https://slushpool.com/proposal/detail/572/
Multipool.us, please come be our friend.
Prohashing.com is up-to-date
Still waiting on word from Cryptopia on when the wallet will be back online.
I believe CryptoID still needs to upgrade. Please reach out to them on twitter
Coinexchange.io has upgraded
Cryptopools, hash-to-coins, ispace - still in maintenance mode.
bitcoinpool.us - i have no idea
Cheers
For Bitcoinpool.us - ARG delisted for new wallet. Working on it. Planned activation is tomorrow.
Argentum is now on CoinGecko:
https://www.coingecko.com/en/coins/argentum
Price Charts: https://www.coingecko.com/en/price_charts/argentum/btc
Widget: https://www.coingecko.com/en/widgets/ticker/argentum/btc
https://www.coingecko.com/en/coins/argentum
Price Charts: https://www.coingecko.com/en/price_charts/argentum/btc
Widget: https://www.coingecko.com/en/widgets/ticker/argentum/btc
iSpace Mining Pools have now upgraded.
If anyone is experiancing being stuck at a block height here are some nodes that are up to date.
AND WHOEVER IS USING THE ORIGINAL WALLET ON IP 178.237.35.34 (resolves to DNS of srcseed001.com) PLEASE UPGRADE TO ARGV2.0
Code:
addnode=52.58.50.77
addnode=162.251.173.208
addnode=82.29.4.122
addnode=92.3.38.174
addnode=149.210.234.234
AND WHOEVER IS USING THE ORIGINAL WALLET ON IP 178.237.35.34 (resolves to DNS of srcseed001.com) PLEASE UPGRADE TO ARGV2.0
Litecoinpool.org is ready for merged mining at block 1,800,000!
Spread the word and get your votes in for ARG on Slushpool at https://slushpool.com/proposal/detail/572/
Multipool.us, please come be our friend.
Prohashing.com is up-to-date
Still waiting on word from Cryptopia on when the wallet will be back online.
I believe CryptoID still needs to upgrade. Please reach out to them on twitter
Coinexchange.io has upgraded
Cryptopools, hash-to-coins, ispace - still in maintenance mode.
bitcoinpool.us - i have no idea
Cheers
Spread the word and get your votes in for ARG on Slushpool at https://slushpool.com/proposal/detail/572/
Multipool.us, please come be our friend.
Prohashing.com is up-to-date
Still waiting on word from Cryptopia on when the wallet will be back online.
I believe CryptoID still needs to upgrade. Please reach out to them on twitter
Coinexchange.io has upgraded
Cryptopools, hash-to-coins, ispace - still in maintenance mode.
bitcoinpool.us - i have no idea
Cheers
I have created a Bootstrap.dat file to help with BlockChain syncing.
Simply extract it and put it into the wallet folder, and the wallet will sync fom the file until it reaches its last block entry, then the wallet will revert to normal operation.
http://argcurrency.org/download/bootstrap.zip
For QT versions of the wallet you may have to use the -loadblock=
Also if you have trouble with syncing remove the existing blockchain data prior to doing this.
Simply extract it and put it into the wallet folder, and the wallet will sync fom the file until it reaches its last block entry, then the wallet will revert to normal operation.
http://argcurrency.org/download/bootstrap.zip
For QT versions of the wallet you may have to use the -loadblock=
Also if you have trouble with syncing remove the existing blockchain data prior to doing this.
Windows Wallet now available here: http://argcurrency.org/download/argentum-qt-win-v2.0.zip
Mac still in progress, Apologies to all Mac users out there.
Mac still in progress, Apologies to all Mac users out there.
Anyone else stuck at block 1572674?
It occasionally will get stuck. Add 2.0 nodes listed here hopefully it will help https://chainz.cryptoid.info/arg/#!network
Added & fixed, thanks.
Anyone else stuck at block 1572674?
It occasionally will get stuck. Add 2.0 nodes listed here hopefully it will help https://chainz.cryptoid.info/arg/#!network
Anyone else stuck at block 1572674?
Edit: Fixed
Edit: Fixed
Just to make things a little easier for those who need to have Berkeley DB v4.8 in their nix systems, here is a script that will compile Argentum v2.0 with libdb5.1 on your systems.
Do the following:
git clone https://github.com/Cryptcollector/ARG2.0.git
cd in to the ARG2.0 folder
create a file called compile.sh with the contents below and execute it with: bash compile.sh
When its done you should be compiled with libdb5.1 without having to put your libdv4.8 wallets in jeopardy
Do the following:
git clone https://github.com/Cryptcollector/ARG2.0.git
cd in to the ARG2.0 folder
create a file called compile.sh with the contents below and execute it with: bash compile.sh
Code:
BITCOIN_ROOT=$(pwd)
# Pick some path to install BDB to, here we create a directory within the argentum directory
BDB_PREFIX="${BITCOIN_ROOT}/db5"
mkdir -p $BDB_PREFIX
# Fetch the source and verify that it is not tampered with
wget 'http://download.oracle.com/berkeley-db/db-5.1.29.NC.tar.gz'
echo '08238e59736d1aacdd47cfb8e68684c695516c37f4fbe1b8267dde58dc3a576c db-5.1.29.NC.tar.gz' | sha256sum -c
# -> db-5.1.29.NC.tar.gz: OK
tar -xzvf db-5.1.29.NC.tar.gz
# Build the library and install to our prefix
cd db-5.1.29.NC/build_unix/
# Note: Do a static build so that it can be embedded into the exectuable, instead of having to find a .so at runtime
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX
make install
# Configure Argentum Core to use our own-built instance of BDB
cd $BITCOIN_ROOT
./autogen.sh
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/"
make
When its done you should be compiled with libdb5.1 without having to put your libdv4.8 wallets in jeopardy
Thanks for this. Cryptopools is syncing the blockchain now.
-tb-
Just to make things a little easier for those who need to have Berkeley DB v4.8 in their nix systems, here is a script that will compile Argentum v2.0 with libdb5.1 on your systems.
Do the following:
git clone https://github.com/Cryptcollector/ARG2.0.git
cd in to the ARG2.0 folder
create a file called compile.sh with the contents below and execute it with: bash compile.sh
When its done you should be compiled with libdb5.1 without having to put your libdv4.8 wallets in jeopardy
Do the following:
git clone https://github.com/Cryptcollector/ARG2.0.git
cd in to the ARG2.0 folder
create a file called compile.sh with the contents below and execute it with: bash compile.sh
Code:
BITCOIN_ROOT=$(pwd)
# Pick some path to install BDB to, here we create a directory within the argentum directory
BDB_PREFIX="${BITCOIN_ROOT}/db5"
mkdir -p $BDB_PREFIX
# Fetch the source and verify that it is not tampered with
wget 'http://download.oracle.com/berkeley-db/db-5.1.29.NC.tar.gz'
echo '08238e59736d1aacdd47cfb8e68684c695516c37f4fbe1b8267dde58dc3a576c db-5.1.29.NC.tar.gz' | sha256sum -c
# -> db-5.1.29.NC.tar.gz: OK
tar -xzvf db-5.1.29.NC.tar.gz
# Build the library and install to our prefix
cd db-5.1.29.NC/build_unix/
# Note: Do a static build so that it can be embedded into the exectuable, instead of having to find a .so at runtime
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX
make install
# Configure Argentum Core to use our own-built instance of BDB
cd $BITCOIN_ROOT
./autogen.sh
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/"
make
When its done you should be compiled with libdb5.1 without having to put your libdv4.8 wallets in jeopardy
We just realised that there was a problem with privkeyimport.
Now fixed
Sorry for this, but you may want to do a git pull and recompile.
Will remove the windows client temporarily until its recompiled too.
Crypt
Now fixed
Sorry for this, but you may want to do a git pull and recompile.
Will remove the windows client temporarily until its recompiled too.
Crypt
I'm getting this error compiling v2.0: libdb_cxx headers missing
What is the fix for this?
-tb-
What is the fix for this?
-tb-
The code wants to use libdb5.1.
You can either upgrade your libdb to 5.1 or if this will cause you problems with other coins on your system, then take a look at the build-unix.md https://github.com/Cryptcollector/ARG2.0/blob/master/doc/build-unix.md
In there under Berkeley DB section is a way to compile Argentum. I suppose the same method could be used to compile with 4.8, but I have not tried this.
I have libdb4.8 installed on my system and and have successfully compiled Argentum with libdb5.1 using the method. both ARG and litecoin for instance are running without problems, even though they use different libdb versions.
I'm getting this error compiling v2.0: libdb_cxx headers missing
What is the fix for this?
-tb-
What is the fix for this?
-tb-
Hi,
Is there any way to compile argentum daemon using BDB 4.8? All my merge mined coins use 4.8, so installing BDB 5.1 will break compatibility.
Thanks.
Edit: OK - I just noticed the issue on git hub & your reply. Shame your dev used the wrong BDB - it won't be merge minable with other coins using the 5.1 version - unless it's possible to install both BDB's in seperate locations & point the daemon to that particular BDB?
Is there any way to compile argentum daemon using BDB 4.8? All my merge mined coins use 4.8, so installing BDB 5.1 will break compatibility.
Thanks.
Edit: OK - I just noticed the issue on git hub & your reply. Shame your dev used the wrong BDB - it won't be merge minable with other coins using the 5.1 version - unless it's possible to install both BDB's in seperate locations & point the daemon to that particular BDB?
I've investigated and heres my new reply to the GitHub issue your referring to.
Quote
Okay, you need to use 5.1 for the wallet db, this will not hamper the AUXPOW functionality of the daemon, as it only effects the wallet.dat portability.
You can install with libdb5.1 while not breaking the compatibility of of your existing libdb4.8 wallets.
Just follow the instructions within https://github.com/Cryptcollector/ARG2.0/blob/master/doc/build-unix.md there is a section in there on how to do this, Look at the Berkely DB section, there is a script there to do this.
Incidentally, DogeCoin has the same problem, it also is 5.1 dependant and gives the exact same error, just worded a little diferently.
You can install with libdb5.1 while not breaking the compatibility of of your existing libdb4.8 wallets.
Just follow the instructions within https://github.com/Cryptcollector/ARG2.0/blob/master/doc/build-unix.md there is a section in there on how to do this, Look at the Berkely DB section, there is a script there to do this.
Incidentally, DogeCoin has the same problem, it also is 5.1 dependant and gives the exact same error, just worded a little diferently.
SO, follow the instructions on compiling with Berkeley 5.1 DB in that build-unix.md and you can have 5.1 in Argentum while still retaining your system compatibility for all 4.8 wallets.
Regards
Crypt
Hi,
Is there any way to compile argentum daemon using BDB 4.8? All my merge mined coins use 4.8, so installing BDB 5.1 will break compatibility.
Thanks.
Is there any way to compile argentum daemon using BDB 4.8? All my merge mined coins use 4.8, so installing BDB 5.1 will break compatibility.
Thanks.
I just use ./configure --with-incompatible-bdb Yeah, my wallet may not be portable, but it runs flawlessly on Debian 8.4.
Jump to: