how come dgb is still alive ?
Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1297. (Read 3058812 times)
August 15, 2014, 06:45:50 AM
August 15, 2014, 05:44:06 AM
Debian latest amd64 bit release. Or Ubuntu, as you wish. You could also go with Ubuntu 12.x version, as that one has 4.8 libdb by default, which enables portable wallet.dat file.
The new versions do come with 5.1 libdb, and wallet.dat are not portable between 4.8 and 5.1 systems. ( you can open 4.8 created wallet in a 5.1 libdb system, but can not go back than, as wallet.dat becomes corrupt, as I understood).
Thanks! I'll have a go...
August 15, 2014, 05:09:01 AM
Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....
I wonder if some of my issues are trying to solo mine from Linux (more or less... Raspberry Pi MinePeon) via my 32 bit Windows wallet. As I said I did have this working previously, but now it just doesn't want to know... even with the exact same config.
Think I might deploy a Linux VM to act solely as a solo mining client/wallet. What variant of Linux are folks here running? My preference is headless... strictly SSH access for day to day stuff...
PS. I know I can't compile just yet until 3.0.1 is released, but I want to get a base build done to prepare...
Debian latest amd64 bit release. Or Ubuntu, as you wish. You could also go with Ubuntu 12.x version, as that one has 4.8 libdb by default, which enables portable wallet.dat file.
The new versions do come with 5.1 libdb, and wallet.dat are not portable between 4.8 and 5.1 systems. ( you can open 4.8 created wallet in a 5.1 libdb system, but can not go back than, as wallet.dat becomes corrupt, as I understood).
August 15, 2014, 05:05:26 AM
I have some dutch Language correction inserted.
Also in this picture below you see a Bitcoin adres. Not that big of a deal.
Also in this picture below you see a Bitcoin adres. Not that big of a deal.
August 15, 2014, 04:46:21 AM
Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....
I wonder if some of my issues are trying to solo mine from Linux (more or less... Raspberry Pi MinePeon) via my 32 bit Windows wallet. As I said I did have this working previously, but now it just doesn't want to know... even with the exact same config.
Think I might deploy a Linux VM to act solely as a solo mining client/wallet. What variant of Linux are folks here running? My preference is headless... strictly SSH access for day to day stuff...
PS. I know I can't compile just yet until 3.0.1 is released, but I want to get a base build done to prepare...
August 14, 2014, 11:16:12 PM
chinese version have some issues.
translate "比特币" to "极特币"
and change the bitcoin address to digibyte address.
August 14, 2014, 10:12:52 PM
chinese version have some issues.
translate "比特币" to "极特币"
and change the bitcoin address to digibyte address.
Nice job on catching that! We should make sure all of our translations are solid within the next week... Don't want anything keeping anyone out of DGB!
August 14, 2014, 10:00:57 PM
chinese version have some issues.
translate "比特币" to "极特币"
and change the bitcoin address to digibyte address.
August 14, 2014, 07:36:36 PM
Ok, we have the fix implemented and we are in the process of double checking everything and testing it. Thank you for your patience everyone!
August 14, 2014, 05:54:55 PM
Latest pull from git does not compile for me
miner.cpp: In function 'CBlockTemplate* CreateNewBlock(const CScript&, int)':
miner.cpp:137:9: error: 'pindexBest' was not declared in this scope
miner.cpp:138:101: error: expected ')' before 'PRI64d'
main.cpp: In function 'unsigned int GetNextWorkRequiredV1(const CBlockIndex*, const CBlockHeader*, int)':
main.cpp:1298:13: warning: variable 'retargetSpacing' set but not used [-Wunused-but-set-variable]
CXX noui.o
Yes, we put that in there for the time being to keep people from pulling 3.0.0 code. We can't make the repo private so that is the next best option. We are still working on getting 3.0.1 out there.miner.cpp: In function 'CBlockTemplate* CreateNewBlock(const CScript&, int)':
miner.cpp:137:9: error: 'pindexBest' was not declared in this scope
miner.cpp:138:101: error: expected ')' before 'PRI64d'
main.cpp: In function 'unsigned int GetNextWorkRequiredV1(const CBlockIndex*, const CBlockHeader*, int)':
main.cpp:1298:13: warning: variable 'retargetSpacing' set but not used [-Wunused-but-set-variable]
CXX noui.o
haha, ok, nice. was wondering what is wrong.
August 14, 2014, 05:03:56 PM
Latest pull from git does not compile for me
miner.cpp: In function 'CBlockTemplate* CreateNewBlock(const CScript&, int)':
miner.cpp:137:9: error: 'pindexBest' was not declared in this scope
miner.cpp:138:101: error: expected ')' before 'PRI64d'
main.cpp: In function 'unsigned int GetNextWorkRequiredV1(const CBlockIndex*, const CBlockHeader*, int)':
main.cpp:1298:13: warning: variable 'retargetSpacing' set but not used [-Wunused-but-set-variable]
CXX noui.o
Yes, we put that in there for the time being to keep people from pulling 3.0.0 code. We can't make the repo private so that is the next best option. We are still working on getting 3.0.1 out there. miner.cpp: In function 'CBlockTemplate* CreateNewBlock(const CScript&, int)':
miner.cpp:137:9: error: 'pindexBest' was not declared in this scope
miner.cpp:138:101: error: expected ')' before 'PRI64d'
main.cpp: In function 'unsigned int GetNextWorkRequiredV1(const CBlockIndex*, const CBlockHeader*, int)':
main.cpp:1298:13: warning: variable 'retargetSpacing' set but not used [-Wunused-but-set-variable]
CXX noui.o
August 14, 2014, 04:50:57 PM
Latest pull from git does not compile for me
miner.cpp: In function 'CBlockTemplate* CreateNewBlock(const CScript&, int)':
miner.cpp:137:9: error: 'pindexBest' was not declared in this scope
miner.cpp:138:101: error: expected ')' before 'PRI64d'
main.cpp: In function 'unsigned int GetNextWorkRequiredV1(const CBlockIndex*, const CBlockHeader*, int)':
main.cpp:1298:13: warning: variable 'retargetSpacing' set but not used [-Wunused-but-set-variable]
CXX noui.o
miner.cpp: In function 'CBlockTemplate* CreateNewBlock(const CScript&, int)':
miner.cpp:137:9: error: 'pindexBest' was not declared in this scope
miner.cpp:138:101: error: expected ')' before 'PRI64d'
main.cpp: In function 'unsigned int GetNextWorkRequiredV1(const CBlockIndex*, const CBlockHeader*, int)':
main.cpp:1298:13: warning: variable 'retargetSpacing' set but not used [-Wunused-but-set-variable]
CXX noui.o
August 14, 2014, 03:30:37 PM
We will release all the .conf info once we get this issue resolved. Thanks again for all your patience. This is a very complicated update. All will be normal again soon!
Keep up the good work, no one expected everything to be silky smooth. I'm sure you have everyone's 100% support.
August 14, 2014, 03:29:17 PM
Glad I haven't updated yet. Let's wait for more fixes.
Appreciate the constant dedication Jared!
YC
Appreciate the constant dedication Jared!
YC
August 14, 2014, 03:14:36 PM
Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....
August 14, 2014, 03:14:27 PM
Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....
Don't worry... we're all just pumped to get on it again.... you're obviously on it so no worries!
August 14, 2014, 03:10:16 PM
Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....
August 14, 2014, 03:09:45 PM
Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....
Ok, good to know. But no worries... can't friggin' get it to work anyway
August 14, 2014, 03:07:54 PM
Anyone solo mining care to share their digibyte.conf file? I had this working previously but now can't seem to get it going....
August 14, 2014, 03:04:26 PM
@ Digibyte... trying to solo mine Scrypt... why does your digibyte.conf as listed on the first post contain an rpcport=14022 AND a port=12024? Also... are the nodes as listed still correct?
The nodes listed need to be updated. The ports are correct.
Jump to: