|
Arsenay
|
 |
October 17, 2014, 04:00:56 AM |
|
The final beta version of 1.5 is now ready. https://github.com/Tranz5/HoboNickels/releases/tag/1.4.9.99I have 1 important message you should follow, if you are using Beta 1 or 2 and have S4C enabled, please disable it before shutting down the client. If you fail to do this you will get a wallet warning when starting the new version. To fix this warning(if you missed this), just press disable in the Stake For Charity dialog box, and then shut down and restart the client. You can then enable it as normal. Click here https://cryptocointalk.com/topic/13199-preparing-hbn-v15/?p=139751 for change log from Version 1.4 to now. All of this will be included in the final version 1.5, plus the hard forks. Which means you will still be required to upgrade to 1.5. wanted to look at the coin I only use Linux OMG, with qt5 build and new boost ?)) No, this is too much ... This is compatible with qt4 and 5 as well as boost below 1.5. If you are having a specific build issue, let us know. yes, of course )) Debian 6, amd64: .... cd /home/vit/build/wallets/HoboNickels-1.4.0.0; /bin/sh share/genbuild.sh /home/vit/build/wallets/HoboNickels-1.4.0.0/build/build.h fatal: Not a git repository (or any parent up to mount point /home) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). g++ -c -pipe -fstack-protector-all --param ssp-buffer-size=1 -msse2 -O2 -D_REENTRANT -fdiagnostics-show-option -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DBOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN -D__NO_SYSTEM_INCLUDES -DUSE_UPNP=1 -DSTATICLIB -DUSE_IPV6=1 -DUSE_LEVELDB -DHAVE_BUILD_INFO -DLINUX -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4 -Isrc -Isrc/json -Isrc/qt -Isrc/leveldb/include -Isrc/leveldb/helpers -I../boost_1_55_0 -Ibuild -Ibuild -o build/bitcoingui.o src/qt/bitcoingui.cpp src/qt/bitcoingui.cpp: In member function ‘void BitcoinGUI::connectionIconClicked()’: src/qt/bitcoingui.cpp:638: error: ‘currentDateTimeUtc’ is not a member of ‘QDateTime’ ../boost_1_55_0/boost/system/error_code.hpp: At global scope: ../boost_1_55_0/boost/system/error_code.hpp:222: warning: ‘boost::system::posix_category’ defined but not used [-Wunused-variable] ../boost_1_55_0/boost/system/error_code.hpp:223: warning: ‘boost::system::errno_ecat’ defined but not used [-Wunused-variable] ../boost_1_55_0/boost/system/error_code.hpp:224: warning: ‘boost::system::native_ecat’ defined but not used [-Wunused-variable] |
|
|
|
|
|
|
|
|
|
|
|
You get merit points when someone likes your post enough to give you some. And for every 2 merit points you receive, you can send 1 merit point to someone else!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
|
Biomech
Legendary
 Offline
Activity: 1372
Merit: 1022
Anarchy is not chaos.
|
|
October 17, 2014, 04:05:16 AM |
|
I am currently running v1.4.0.0-g4ddc7a0a-hobo. Do I need to upgrade now, or can it wait for a bit?
|
|
|
|
|
Tranz (OP)
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
October 17, 2014, 04:16:08 AM |
|
I am currently running v1.4.0.0-g4ddc7a0a-hobo. Do I need to upgrade now, or can it wait for a bit?
You can wait. |
|
|
|
Tranz (OP)
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
October 17, 2014, 04:32:06 AM |
|
The final beta version of 1.5 is now ready. https://github.com/Tranz5/HoboNickels/releases/tag/1.4.9.99I have 1 important message you should follow, if you are using Beta 1 or 2 and have S4C enabled, please disable it before shutting down the client. If you fail to do this you will get a wallet warning when starting the new version. To fix this warning(if you missed this), just press disable in the Stake For Charity dialog box, and then shut down and restart the client. You can then enable it as normal. Click here https://cryptocointalk.com/topic/13199-preparing-hbn-v15/?p=139751 for change log from Version 1.4 to now. All of this will be included in the final version 1.5, plus the hard forks. Which means you will still be required to upgrade to 1.5. wanted to look at the coin I only use Linux OMG, with qt5 build and new boost ?)) No, this is too much ... This is compatible with qt4 and 5 as well as boost below 1.5. If you are having a specific build issue, let us know. yes, of course )) Debian 6, amd64: .... cd /home/vit/build/wallets/HoboNickels-1.4.0.0; /bin/sh share/genbuild.sh /home/vit/build/wallets/HoboNickels-1.4.0.0/build/build.h fatal: Not a git repository (or any parent up to mount point /home) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). g++ -c -pipe -fstack-protector-all --param ssp-buffer-size=1 -msse2 -O2 -D_REENTRANT -fdiagnostics-show-option -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DBOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN -D__NO_SYSTEM_INCLUDES -DUSE_UPNP=1 -DSTATICLIB -DUSE_IPV6=1 -DUSE_LEVELDB -DHAVE_BUILD_INFO -DLINUX -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4 -Isrc -Isrc/json -Isrc/qt -Isrc/leveldb/include -Isrc/leveldb/helpers -I../boost_1_55_0 -Ibuild -Ibuild -o build/bitcoingui.o src/qt/bitcoingui.cpp src/qt/bitcoingui.cpp: In member function ‘void BitcoinGUI::connectionIconClicked()’: src/qt/bitcoingui.cpp:638: error: ‘currentDateTimeUtc’ is not a member of ‘QDateTime’ ../boost_1_55_0/boost/system/error_code.hpp: At global scope: ../boost_1_55_0/boost/system/error_code.hpp:222: warning: ‘boost::system::posix_category’ defined but not used [-Wunused-variable] ../boost_1_55_0/boost/system/error_code.hpp:223: warning: ‘boost::system::errno_ecat’ defined but not used [-Wunused-variable] ../boost_1_55_0/boost/system/error_code.hpp:224: warning: ‘boost::system::native_ecat’ defined but not used [-Wunused-variable] Thanks that was just a typo. Please try the Beta version, it will be release version soon enough. git clone git://github.com/Tranz5/HoboNickels |
|
|
|
|
Arsenay
|
|
October 17, 2014, 04:46:18 AM |
|
ok
exhaust:
....
g++ -c -pipe -fstack-protector-all --param ssp-buffer-size=1 -msse2 -O2 -D_REENTRANT -fdiagnostics-show-option -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DBOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN -D__NO_SYSTEM_INCLUDES -DUSE_UPNP=1 -DSTATICLIB -DUSE_LEVELDB -DHAVE_BUILD_INFO -DLINUX -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4 -Isrc -Isrc/json -Isrc/qt -Isrc/leveldb/include -Isrc/leveldb/helpers -Ibuild -Ibuild -o build/transactiontablemodel.o src/qt/transactiontablemodel.cpp
src/qt/transactiontablemodel.cpp: In member function ‘virtual QVariant TransactionTableModel::data(const QModelIndex&, int) const’:
src/qt/transactiontablemodel.cpp:525: error: conversion from ‘int64_t’ to ‘QVariant’ is ambiguous
/usr/include/qt4/QtCore/qvariant.h:425: note: candidates are: QVariant::QVariant(void*) <near match>
/usr/include/qt4/QtCore/qvariant.h:222: note: QVariant::QVariant(Qt::GlobalColor) <near match>
/usr/include/qt4/QtCore/qvariant.h:192: note: QVariant::QVariant(const char*) <near match>
/usr/include/qt4/QtCore/qvariant.h:190: note: QVariant::QVariant(float)
/usr/include/qt4/QtCore/qvariant.h:189: note: QVariant::QVariant(double)
/usr/include/qt4/QtCore/qvariant.h:188: note: QVariant::QVariant(bool)
/usr/include/qt4/QtCore/qvariant.h:187: note: QVariant::QVariant(qulonglong)
/usr/include/qt4/QtCore/qvariant.h:186: note: QVariant::QVariant(qlonglong)
/usr/include/qt4/QtCore/qvariant.h:185: note: QVariant::QVariant(uint)
/usr/include/qt4/QtCore/qvariant.h:184: note: QVariant::QVariant(int)
/usr/include/qt4/QtCore/qvariant.h:175: note: QVariant::QVariant(QVariant::Type) <near match>
src/qt/transactiontablemodel.cpp:531: error: conversion from ‘int64_t’ to ‘QVariant’ is ambiguous
/usr/include/qt4/QtCore/qvariant.h:425: note: candidates are: QVariant::QVariant(void*) <near match>
/usr/include/qt4/QtCore/qvariant.h:222: note: QVariant::QVariant(Qt::GlobalColor) <near match>
/usr/include/qt4/QtCore/qvariant.h:192: note: QVariant::QVariant(const char*) <near match>
/usr/include/qt4/QtCore/qvariant.h:190: note: QVariant::QVariant(float)
/usr/include/qt4/QtCore/qvariant.h:189: note: QVariant::QVariant(double)
/usr/include/qt4/QtCore/qvariant.h:188: note: QVariant::QVariant(bool)
/usr/include/qt4/QtCore/qvariant.h:187: note: QVariant::QVariant(qulonglong)
/usr/include/qt4/QtCore/qvariant.h:186: note: QVariant::QVariant(qlonglong)
/usr/include/qt4/QtCore/qvariant.h:185: note: QVariant::QVariant(uint)
/usr/include/qt4/QtCore/qvariant.h:184: note: QVariant::QVariant(int)
/usr/include/qt4/QtCore/qvariant.h:175: note: QVariant::QVariant(QVariant::Type) <near match>
src/qt/transactiontablemodel.cpp:564: error: conversion from ‘int64_t’ to ‘QVariant’ is ambiguous
/usr/include/qt4/QtCore/qvariant.h:425: note: candidates are: QVariant::QVariant(void*) <near match>
/usr/include/qt4/QtCore/qvariant.h:222: note: QVariant::QVariant(Qt::GlobalColor) <near match>
/usr/include/qt4/QtCore/qvariant.h:192: note: QVariant::QVariant(const char*) <near match>
/usr/include/qt4/QtCore/qvariant.h:190: note: QVariant::QVariant(float)
/usr/include/qt4/QtCore/qvariant.h:189: note: QVariant::QVariant(double)
/usr/include/qt4/QtCore/qvariant.h:188: note: QVariant::QVariant(bool)
/usr/include/qt4/QtCore/qvariant.h:187: note: QVariant::QVariant(qulonglong)
/usr/include/qt4/QtCore/qvariant.h:186: note: QVariant::QVariant(qlonglong)
/usr/include/qt4/QtCore/qvariant.h:185: note: QVariant::QVariant(uint)
/usr/include/qt4/QtCore/qvariant.h:184: note: QVariant::QVariant(int)
/usr/include/qt4/QtCore/qvariant.h:175: note: QVariant::QVariant(QVariant::Type) <near match>
|
|
|
|
|
georgidimitrov
Member
Offline
Activity: 101
Merit: 10
|
|
October 17, 2014, 11:06:30 AM |
|
I had a strange experience yesterday, a single block created thirteen orphans in a row trying to stake. Is this normal?
Not normal, but as long as you are in sync and have gotten an accepted stake now, I wouldn't worry too much about it. If you have the debug.log file from the time during the orphans I wouldn't mind taking a look at it. Also what version are you on, and were you doing anything on the computer or with the client at the time. here's a part of it: 16.10.2014 J. 12:57:33 ProcessBlock: ORPHAN BLOCK, prev=b0722e1fe60a4ed31dc1 16.10.2014 J. 12:57:33 received block 00000000032de6dee6d0 sent from 79.146.214.37:7372 16.10.2014 J. 12:57:33 ProcessBlock: ORPHAN BLOCK, prev=c8e90545655b8b735bae 16.10.2014 J. 12:57:33 received block 0bc3ba11f0459412fa9a sent from 79.146.214.37:7372 16.10.2014 J. 12:57:33 ProcessBlock: ORPHAN BLOCK, prev=00000000032de6dee6d0 16.10.2014 J. 12:57:33 received block 40f4f0d9ae80e1d749a9 sent from 79.146.214.37:7372 16.10.2014 J. 12:57:33 ProcessBlock: ORPHAN BLOCK, prev=0bc3ba11f0459412fa9a 16.10.2014 J. 12:57:33 received block 00000000088a1f227e04 sent from 79.146.214.37:7372 16.10.2014 J. 12:57:33 ProcessBlock: ORPHAN BLOCK, prev=40f4f0d9ae80e1d749a9 16.10.2014 J. 12:57:33 received block 0000000003c5ec72c5d1 sent from 79.146.214.37:7372 16.10.2014 J. 12:57:33 ProcessBlock: ORPHAN BLOCK, prev=00000000088a1f227e04 16.10.2014 J. 12:57:33 received block ca7d54cdb24e93b49227 sent from 79.146.214.37:7372 16.10.2014 J. 12:57:33 ProcessBlock: ORPHAN BLOCK, prev=0000000003c5ec72c5d1 16.10.2014 J. 12:57:33 received block 0000000000fbcd16f9b5 sent from 79.146.214.37:7372 16.10.2014 J. 12:57:33 ProcessBlock: ORPHAN BLOCK, prev=ca7d54cdb24e93b49227 16.10.2014 J. 12:57:33 received block 6589145c6aed9bce5f1f sent from 79.146.214.37:7372 16.10.2014 J. 12:57:33 ProcessBlock: ORPHAN BLOCK, prev=0000000000fbcd16f9b5 16.10.2014 J. 12:57:33 Added time data, samples 6, offset -45 (+0 minutes) 16.10.2014 J. 12:57:33 receive version message: version 70005, blocks=1310502, us=46.237.89.248:1248, them=31.28.101.173:7372, peer=31.28.101.173:7372 16.10.2014 J. 12:57:33 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000000fbcd16f9b59bc93ceee09478117e7cb0bb9cbbfcfc5f040e25ecb2 16.10.2014 J. 12:57:33 ProcessSyncCheckpoint: pending for sync-checkpoint 6589145c6aed9bce5f1f604748e47573c03e3b2a75957e6e809b6fdd2ba052d8 16.10.2014 J. 12:57:34 received block 7552ee6ac7cf007f4d34 sent from 86.35.134.224:7372 16.10.2014 J. 12:57:34 ProcessBlock: ORPHAN BLOCK, prev=42029d8e08caefd0cebf |
|
|
|
|
|
|
|
PressF1
|
|
October 17, 2014, 02:16:26 PM |
|
Maybe because Cryptsy has some issues at the moment and HBN isn't really traded elsewhere. |
HBN & CAP: F1PressF1PCxEyESGk6Fe1om1RfiHqX5gg
|
|
|
sigesang
Member
Offline
Activity: 84
Merit: 10
|
|
October 17, 2014, 05:19:37 PM
Last edit: October 17, 2014, 05:48:35 PM by sigesang |
|
ok
exhaust:
....
/usr/include/qt4/QtCore/qvariant.h:425: note: candidates are: QVariant::QVariant(void*) <near match>
/usr/include/qt4/QtCore/qvariant.h:222: note: QVariant::QVariant(Qt::GlobalColor) <near match>
/usr/include/qt4/QtCore/qvariant.h:192: note: QVariant::QVariant(const char*) <near match>
/usr/include/qt4/QtCore/qvariant.h:190: note: QVariant::QVariant(float)
/usr/include/qt4/QtCore/qvariant.h:189: note: QVariant::QVariant(double)
/usr/include/qt4/QtCore/qvariant.h:188: note: QVariant::QVariant(bool)
/usr/include/qt4/QtCore/qvariant.h:187: note: QVariant::QVariant(qulonglong)
/
...
that's the start, futher on I get these: src/qt/walletmodel.cpp: In member function 'WalletModel::SendCoinsReturn WalletModel::sendCoins(const QList<SendCoinsRecipient>&, const CCoinControl*)':
src/qt/walletmodel.cpp:232:108: error: no matching function for call to 'CWallet::CreateTransaction(std::vector<std::pair<CScript, long long int> >&, CWalletTx&, CReserveKey&, qint64&, bool, const CCoinControl*&)'
bool fCreated = wallet->CreateTransaction(vecSend, wtx, keyChange, nFeeRequired, false, coinControl);
^
src/qt/walletmodel.cpp:232:108: note: candidates are:
In file included from src/init.h:8:0,
from src/qt/walletmodel.cpp:6:
src/wallet.h:248:10: note: bool CWallet::CreateTransaction(const std::vector<std::pair<CScript, long int> >&, CWalletTx&, CReserveKey&, int64_t&, bool, const CCoinControl*)
bool CreateTransaction(const std::vector<std::pair<CScript, int64_t> >& vecSend, CWalletTx& wtxNew, CReserveKey& reservekey, int64_t& nFeeRet, bool fAllowS4C=false, const CCoinControl *coinControl=NULL);
^
src/wallet.h:248:10: note: no known conversion for argument 1 from 'std::vector<std::pair<CScript, long long int> >' to 'const std::vector<std::pair<CScript, long int> >&'
src/wallet.h:249:10: note: bool CWallet::CreateTransaction(CScript, int64_t, CWalletTx&, CReserveKey&, int64_t&, bool, const CCoinControl*)
bool CreateTransaction(CScript scriptPubKey, int64_t nValue, CWalletTx& wtxNew, CReserveKey& reservekey, int64_t& nFeeRet, bool fAllowS4C=false, const CCoinControl *coinControl=NULL);
^
src/wallet.h:249:10: note: no known conversion for argument 1 from 'std::vector<std::pair<CScript, long long int> >' to 'CScript'
src/qt/walletmodel.cpp: In member function 'void WalletModel::getStakeWeight(quint64&, quint64&, quint64&)':
src/qt/walletmodel.cpp:456:68: error: no matching function for call to 'CWallet::GetStakeWeight(CWallet&, quint64&, quint64&, quint64&)'
wallet->GetStakeWeight(*wallet, nMinWeight, nMaxWeight, nWeight);
^
src/qt/walletmodel.cpp:456:68: note: candidate is:
In file included from src/init.h:8:0,
from src/qt/walletmodel.cpp:6:
src/wallet.h:251:10: note: bool CWallet::GetStakeWeight(const CKeyStore&, uint64_t&, uint64_t&, uint64_t&)
bool GetStakeWeight(const CKeyStore& keystore, uint64_t& nMinWeight, uint64_t& nMaxWeight, uint64_t& nWeight);
^
src/wallet.h:251:10: note: no known conversion for argument 2 from 'quint64 {aka long long unsigned int}' to 'uint64_t& {aka long unsigned int&}'
src/qt/walletmodel.cpp: In member function 'quint64 WalletModel::getTotStakeWeight()':
src/qt/walletmodel.cpp:472:72: error: no matching function for call to 'CWallet::GetStakeWeight(CWallet&, quint64&, quint64&, quint64&)'
pwallet->GetStakeWeight(*pwallet, nMinWeight,nMaxWeight,nWeight);
^
src/qt/walletmodel.cpp:472:72: note: candidate is:
In file included from src/init.h:8:0,
from src/qt/walletmodel.cpp:6:
src/wallet.h:251:10: note: bool CWallet::GetStakeWeight(const CKeyStore&, uint64_t&, uint64_t&, uint64_t&)
bool GetStakeWeight(const CKeyStore& keystore, uint64_t& nMinWeight, uint64_t& nMaxWeight, uint64_t& nWeight);
^
src/wallet.h:251:10: note: no known conversion for argument 2 from 'quint64 {aka long long unsigned int}' to 'uint64_t& {aka long unsigned int&}'
src/qt/walletmodel.cpp: In member function 'void WalletModel::getStakeWeightFromValue(const qint64&, const qint64&, quint64&)':
src/qt/walletmodel.cpp:481:59: error: no matching function for call to 'CWallet::GetStakeWeightFromValue(const qint64&, const qint64&, quint64&)'
wallet->GetStakeWeightFromValue(nTime, nValue, nWeight);
^
src/qt/walletmodel.cpp:481:59: note: candidate is:
In file included from src/init.h:8:0,
from src/qt/walletmodel.cpp:6:
src/wallet.h:252:10: note: bool CWallet::GetStakeWeightFromValue(const int64_t&, const int64_t&, uint64_t&)
bool GetStakeWeightFromValue(const int64_t& nTime, const int64_t& nValue, uint64_t& nWeight);
^
src/wallet.h:252:10: note: no known conversion for argument 3 from 'quint64 {aka long long unsigned int}' to 'uint64_t& {aka long unsigned int&}'
src/qt/walletmodel.cpp: In member function 'void WalletModel::checkWallet(int&, qint64&, int&)':
src/qt/walletmodel.cpp:486:82: error: no matching function for call to 'CWallet::FixSpentCoins(int&, qint64&, int&, bool)'
wallet->FixSpentCoins(nMismatchSpent, nBalanceInQuestion, nOrphansFound, true);
^
src/qt/walletmodel.cpp:486:82: note: candidate is:
In file included from src/init.h:8:0,
from src/qt/walletmodel.cpp:6:
src/wallet.h:376:10: note: void CWallet::FixSpentCoins(int&, int64_t&, int&, bool)
void FixSpentCoins(int& nMismatchSpent, int64_t& nBalanceInQuestion, int& nOrphansFound, bool fCheckOnly = false);
^
src/wallet.h:376:10: note: no known conversion for argument 2 from 'qint64 {aka long long int}' to 'int64_t& {aka long int&}'
src/qt/walletmodel.cpp: In member function 'void WalletModel::repairWallet(int&, qint64&, int&)':
src/qt/walletmodel.cpp:491:76: error: no matching function for call to 'CWallet::FixSpentCoins(int&, qint64&, int&)'
wallet->FixSpentCoins(nMismatchSpent, nBalanceInQuestion, nOrphansFound);
^
src/qt/walletmodel.cpp:491:76: note: candidate is:
In file included from src/init.h:8:0,
from src/qt/walletmodel.cpp:6:
src/wallet.h:376:10: note: void CWallet::FixSpentCoins(int&, int64_t&, int&, bool)
void FixSpentCoins(int& nMismatchSpent, int64_t& nBalanceInQuestion, int& nOrphansFound, bool fCheckOnly = false);
^
src/wallet.h:376:10: note: no known conversion for argument 2 from 'qint64 {aka long long int}' to 'int64_t& {aka long int&}'
Linux amd64 platform 1.4.99 from github.com/Tranz5/HoboNickels did fast hack fix, diff is here http://pastebin.com/Jh0GA75L |
BTC 1basemmmcpVWVfzZMyLA1r2DJMTMnZYoX LTC LiTeTipdGNcXRjTw5pVnMXjB5FFoEfxPAZ
|
|
|
|
ElTomeko27
|
|
October 17, 2014, 06:13:04 PM
Last edit: October 17, 2014, 06:26:20 PM by ElTomeko27 |
|
|
|
|
|
|
Tranz (OP)
Legendary
Offline
Activity: 1540
Merit: 1052
May the force bit with you.
|
|
October 17, 2014, 10:44:52 PM |
|
Thanks, what version of QT were you using? I'll play with this over the weekend and see if I can get a cleaner version out there. |
|
|
|
sigesang
Member
Offline
Activity: 84
Merit: 10
|
|
October 18, 2014, 01:13:27 AM |
|
Thanks, what version of QT were you using? I'll play with this over the weekend and see if I can get a cleaner version out there. did use Qt 4.8.5 |
BTC 1basemmmcpVWVfzZMyLA1r2DJMTMnZYoX LTC LiTeTipdGNcXRjTw5pVnMXjB5FFoEfxPAZ
|
|
|
|
PressF1
|
|
October 18, 2014, 08:47:49 AM |
|
The final beta version of 1.5 is now ready. https://github.com/Tranz5/HoboNickels/releases/tag/1.4.9.99I have 1 important message you should follow, if you are using Beta 1 or 2 and have S4C enabled, please disable it before shutting down the client. If you fail to do this you will get a wallet warning when starting the new version. To fix this warning(if you missed this), just press disable in the Stake For Charity dialog box, and then shut down and restart the client. You can then enable it as normal. Click here https://cryptocointalk.com/topic/13199-preparing-hbn-v15/?p=139751 for change log from Version 1.4 to now. All of this will be included in the final version 1.5, plus the hard forks. Which means you will still be required to upgrade to 1.5. Great! I've installed this version on a couple of machines and they all work perfectly. From version 1.4.0.1 and up it was done without a glitch and in minutes. Coming from 1.4.0.0 worked as well though it took about 24 hours to re-sync. Had to restart on one computer, the other just went all the way without any need for a restart. I am really happy with the introduced possibility to control the return output of S4C. Now I am curious to see how the recombining is working out. Got some old small blocks so I need to wait for a bit. The network monitor is another addition I found myself using more than once. So many innovations and improvements. I am really impressed. |
HBN & CAP: F1PressF1PCxEyESGk6Fe1om1RfiHqX5gg
|
|
|
Majormax
Legendary
Offline
Activity: 2534
Merit: 1129
|
|
October 19, 2014, 10:12:18 AM
Last edit: October 19, 2014, 10:28:08 AM by Majormax |
|
Please consider this carefully :
Is it now time to increase the % stake ?
HBN is in the 'High Stake' group, and has reasonable distribution, but needs a lot more trade volume.
Anyone who has been watching Hyperstake in the past 6 weeks will have noted the steadily increasing trade volume, along with price. That is distributing, and strengthening the network.
I believe that other PoS coins will increase their % as this benefit becomes clearer, and HBN should be one of the leaders in this.
I believe high PoS is going to be the 'next boom' and we are in the early stages, but only those coins with really high % will benefit. It will be like a % bidding war, but the upper limits will be determined by trial and error.
This makes sense because the 100's of dying coins out there are all needing network support,and fiat trade is not going to help them individually because of the dilution in the broad market. High PoS will be seen as a driver of activity generally, and therefore a lifeline for the fading (and a boom for the real leaders)
|
|
|
|
|
|
ElTomeko27
|
|
October 19, 2014, 10:31:32 AM |
|
Please consider this carefully :
Is it now time to increase the % stake ?
HBN is in the 'High Stake' group, and has reasonable distribution, but needs a lot more trade volume.
Anyone who has been watching Hyperstake in the past 6 weeks will have noted the steadily increasing trade volume, along with price. That is distributing, and strengthening the network.
I believe that other PoS coins will increase their % as this benefit becomes clearer, and HBN should be one of the leaders in this.
I believe high PoS is going to be the 'next boom' and we are in the early stages, but only those coins with really high % will benefit. It will be like a % bidding war, but the upper limits will be determined by trial and error.
This makes sense because the 100's of dying coins out there are all needing network support,and fiat trade is not going to help them individually because of the dilution in the broad market. High PoS will be seen as a driver of activity generally, and therefore a lifeline for the fading (and a boom for the real leaders)
Hyper price after The Peak will fall...My opinion. |
|
|
|
|
Majormax
Legendary
Offline
Activity: 2534
Merit: 1129
|
|
October 19, 2014, 10:36:52 AM |
|
Please consider this carefully :
Is it now time to increase the % stake ?
HBN is in the 'High Stake' group, and has reasonable distribution, but needs a lot more trade volume.
Anyone who has been watching Hyperstake in the past 6 weeks will have noted the steadily increasing trade volume, along with price. That is distributing, and strengthening the network.
I believe that other PoS coins will increase their % as this benefit becomes clearer, and HBN should be one of the leaders in this.
I believe high PoS is going to be the 'next boom' and we are in the early stages, but only those coins with really high % will benefit. It will be like a % bidding war, but the upper limits will be determined by trial and error.
This makes sense because the 100's of dying coins out there are all needing network support,and fiat trade is not going to help them individually because of the dilution in the broad market. High PoS will be seen as a driver of activity generally, and therefore a lifeline for the fading (and a boom for the real leaders)
Hyper price after The Peak will fall...My opinion. Of course, yes, and other high PoS coins will benefit as the speculative money flows elsewhere. The coins which position themselves now will be in a good position....but this is not so much about price, it's about network support. I can forsee a possible upsurge in adoption of the coins with highest % stake. |
|
|
|
|
|
ElTomeko27
|
|
October 19, 2014, 10:44:40 AM |
|
Please consider this carefully :
Is it now time to increase the % stake ?
HBN is in the 'High Stake' group, and has reasonable distribution, but needs a lot more trade volume.
Anyone who has been watching Hyperstake in the past 6 weeks will have noted the steadily increasing trade volume, along with price. That is distributing, and strengthening the network.
I believe that other PoS coins will increase their % as this benefit becomes clearer, and HBN should be one of the leaders in this.
I believe high PoS is going to be the 'next boom' and we are in the early stages, but only those coins with really high % will benefit. It will be like a % bidding war, but the upper limits will be determined by trial and error.
This makes sense because the 100's of dying coins out there are all needing network support,and fiat trade is not going to help them individually because of the dilution in the broad market. High PoS will be seen as a driver of activity generally, and therefore a lifeline for the fading (and a boom for the real leaders)
Hyper price after The Peak will fall...My opinion. Of course, yes, and other high PoS coins will benefit as the speculative money flows elsewhere. The coins which position themselves now will be in a good position....but this is not so much about price, it's about network support. I can forsee a possible upsurge in adoption of the coins with highest % stake. More sake % = more coins to dump. You saying its not so much about price but when ppl see the falling prices they dumping coins and moving their money somewhere else... |
|
|
|
|
Majormax
Legendary
Offline
Activity: 2534
Merit: 1129
|
|
October 19, 2014, 10:54:41 AM |
|
Please consider this carefully :
Is it now time to increase the % stake ?
HBN is in the 'High Stake' group, and has reasonable distribution, but needs a lot more trade volume.
Anyone who has been watching Hyperstake in the past 6 weeks will have noted the steadily increasing trade volume, along with price. That is distributing, and strengthening the network.
I believe that other PoS coins will increase their % as this benefit becomes clearer, and HBN should be one of the leaders in this.
I believe high PoS is going to be the 'next boom' and we are in the early stages, but only those coins with really high % will benefit. It will be like a % bidding war, but the upper limits will be determined by trial and error.
This makes sense because the 100's of dying coins out there are all needing network support,and fiat trade is not going to help them individually because of the dilution in the broad market. High PoS will be seen as a driver of activity generally, and therefore a lifeline for the fading (and a boom for the real leaders)
Hyper price after The Peak will fall...My opinion. Of course, yes, and other high PoS coins will benefit as the speculative money flows elsewhere. The coins which position themselves now will be in a good position....but this is not so much about price, it's about network support. I can forsee a possible upsurge in adoption of the coins with highest % stake. More sake % = more coins to dump. You saying its not so much about price but when ppl see the falling prices they dumping coins and moving their money somewhere else... HBN has 100% PoS already : it has the principle correct, just not the degree. Most communities consider 25% far too much and make the argument about inflation/dumping, but IMO that is a complete fallacy. |
|
|
|
|
Majormax
Legendary
Offline
Activity: 2534
Merit: 1129
|
|
October 19, 2014, 10:57:03 AM |
|
When a coin has really high PoS, the activity in the community can focus around staking and acquisition. More coins are held within the wallets, and do not come to exchanges. Therefore prices are maintained by less exchange volume. But the real benefit then is having a big active network.
|
|
|
|
|
|
