cryptmebro
|
|
June 17, 2016, 06:02:17 PM |
|
It's good to see more nodes coming online. Still have a loner on the old version though :\. The IP appears to be from Netherlands. If that's you, please upgrade!
|
|
|
|
cryptmebro
|
|
June 19, 2016, 02:54:14 AM |
|
Argentum is going Dual Algo
We will be both SCRYPT and SHA256D.
We are also going to become merge minable, so all you Pools out there get ready.
The other changes are BlockReward will be fixed at 3 removing the random reward and BlockTime will be increased to 45 seconds.
To top it all we are bringing the Codebase up to date.
Please Donate a little to the cause! ARG Donation Address: AakDQNZm1GDbtEaAvJFG2MzZGKFSqUSFPg BTC Donation Address: 1LxXw9CRunb5mJfa99aTWQMCqmbroVBUxi What about wallets? Should we move to new or our .dat files and blockchain will work? Coolindark, your pool is paying out individual blocks at a time.
|
|
|
|
|
|
cryptcollector (OP)
|
|
June 25, 2016, 10:18:02 PM |
|
I'll be amending the main post soon. We have the new source for the upgraded wallet up on my github. Could all Pools and Exchanges listing Arg please update? ARG v2.0 Source: https://github.com/Cryptcollector/ARG2.0.gitBlockchain Bootstrap File: http://argcurrency.org/download/bootstrapARG.tar.gzBlockchain is set to Fork at 1800000 This update brings us up to date code, Dual Scrypt and SHA256D Algo plus adds AUXPOW for merge mining capabilities. Block time has been increased to 1 minute and block rewards are now fixed at 3. Windows Wallets and Mac Wallets will be coming soon.
|
|
|
|
IconFirm
|
|
June 26, 2016, 09:35:56 PM Last edit: June 26, 2016, 09:51:54 PM by IconFirm |
|
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?
|
|
|
|
Chris Sokolowski
|
|
June 27, 2016, 05:29:12 AM |
|
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. I just use ./configure --with-incompatible-bdb Yeah, my wallet may not be portable, but it runs flawlessly on Debian 8.4.
|
Prohashing - Professional Mining Made Simple Visit us at https://prohashing.comOptimized for performance - 15 algorithms - Payouts in 200 coins - PPS, PPLNS, or solo
|
|
|
cryptcollector (OP)
|
|
June 27, 2016, 09:10:02 AM |
|
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?
I've investigated and heres my new reply to the GitHub issue your referring to. 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. 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
|
|
|
|
techbytes
Legendary
Offline
Activity: 1694
Merit: 1054
Point. Click. Blockchain
|
|
June 27, 2016, 12:28:33 PM |
|
I'm getting this error compiling v2.0: libdb_cxx headers missing
What is the fix for this?
-tb-
|
|
|
|
cryptcollector (OP)
|
|
June 27, 2016, 12:51:49 PM |
|
I'm getting this error compiling v2.0: libdb_cxx headers missing
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.mdIn 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.
|
|
|
|
cryptcollector (OP)
|
|
June 27, 2016, 01:26:49 PM |
|
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
|
|
|
|
cryptcollector (OP)
|
|
June 27, 2016, 02:29:43 PM |
|
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.gitcd in to the ARG2.0 folder create a file called compile.sh with the contents below and execute it with: bash compile.sh 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
|
|
|
|
techbytes
Legendary
Offline
Activity: 1694
Merit: 1054
Point. Click. Blockchain
|
|
June 27, 2016, 03:08:15 PM |
|
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.gitcd in to the ARG2.0 folder create a file called compile.sh with the contents below and execute it with: bash compile.sh 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-
|
|
|
|
IconFirm
|
|
June 27, 2016, 03:10:19 PM Last edit: June 27, 2016, 04:24:08 PM by IconFirm |
|
Anyone else stuck at block 1572674? Edit: Fixed
|
|
|
|
|
|
|
cryptcollector (OP)
|
|
June 28, 2016, 08:27:26 AM |
|
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.zipFor QT versions of the wallet you may have to use the -loadblock=<file.> switch when starting the wallet. Also if you have trouble with syncing remove the existing blockchain data prior to doing this.
|
|
|
|
protonn
|
|
June 29, 2016, 05:40:43 AM |
|
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
|
|
|
|
cryptcollector (OP)
|
|
June 29, 2016, 09:59:12 AM |
|
If anyone is experiancing being stuck at a block height here are some nodes that are up to date. 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
|
|
|
|
|