Great!! Unpack, start wallet, fully synchronized within one minute. |
|
|
|
PayCon has a great Community. Thanks @ALL for your help. This -> http://pastebin.com/Jh0GA75L was a bit too much for me on the last night  I've just made the changes in transactiontablemodel.cpp, line 552, 553 [ return (qlonglong)rec->status.depth; ] And now I have compiled the qt-wallet and let it sync. |
|
|
|
Try adding
#include "uint256_t.h"
to transactiontablemodel.h
try either changing uint256.h or adding the include, it's on line 4
let me know how you go
I built the wallet from source in Ubuntu 32 bit, Staked a few Blocks as well. Try adding that in and see if you can compile it and if so, let me know and I'll add it to the source. transactiontablemodel.h : #ifndef TRANSACTIONTABLEMODEL_H
#define TRANSACTIONTABLEMODEL_H
#include <QAbstractTableModel>
#include <QStringList>
#include "uint256_t.h"
class CWallet;
class TransactionTablePriv;
class TransactionRecord;
class WalletModel; hmm... does not work, can't compile  The last version I was able to compile without problems. EDIT: It may also be it's up to my Ubuntu version. I'll check it on my other GNU/Linux. |
|
|
|
Awesome, I finished up my testing and added all my changes into the master branch of Github  47 changed files with 1,115 additions and 448 deletions.
Wallet Work -Added Time estimate to Coin Control -Improved Minting information for Minting Icon (time estimation, multisend notification, weights) -Fix of wallet lock/unlock bug -Improved orphan removal -Improved connection to nodes -Date range for Minting -Added number of transactions to overview -Clearer information for rewards in Statistics -"getstaketx" RPC call (incomplete) -"getweight" RPC call -"deleteaddress" RPC call -"getconfs" RPC call getstaketx needs a little fine tuning, other than that all the rest are quite nice additions to the wallet information. Enjoy! Hello Dev My last wallet worked well. But after this recent changes I can't compile the new Qt-wallet. src/qt/transactiontablemodel.cpp:552:23: error: conversion from ‘int64_t {aka long int}’ to ‘QVariant’ is ambiguous
return rec->status.depth;
^
src/qt/transactiontablemodel.cpp:552:23: note: candidates are:
In file included from /usr/include/qt5/QtCore/qabstractitemmodel.h:45:0,
from /usr/include/qt5/QtCore/QAbstractTableModel:1,
from src/qt/transactiontablemodel.h:4,
from src/qt/transactiontablemodel.cpp:1:
/usr/include/qt5/QtCore/qvariant.h:483:5: note: QVariant::QVariant(Qt::CursorShape) <near match>
QVariant(Qt::CursorShape) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:483:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::CursorShape’
/usr/include/qt5/QtCore/qvariant.h:482:5: note: QVariant::QVariant(Qt::PenStyle) <near match>
QVariant(Qt::PenStyle) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:482:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::PenStyle’
/usr/include/qt5/QtCore/qvariant.h:481:5: note: QVariant::QVariant(Qt::BrushStyle) <near match>
QVariant(Qt::BrushStyle) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:481:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::BrushStyle’
/usr/include/qt5/QtCore/qvariant.h:480:5: note: QVariant::QVariant(Qt::GlobalColor) <near match>
QVariant(Qt::GlobalColor) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:480:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::GlobalColor’
/usr/include/qt5/QtCore/qvariant.h:473:5: note: QVariant::QVariant(QMetaType::Type) <near match>
QVariant(QMetaType::Type) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:473:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘QMetaType::Type’
/usr/include/qt5/QtCore/qvariant.h:466:12: note: QVariant::QVariant(void*) <near match>
inline QVariant(void *) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:466:12: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘void*’
/usr/include/qt5/QtCore/qvariant.h:216:24: note: QVariant::QVariant(const char*) <near match>
QT_ASCII_CAST_WARN QVariant(const char *str);
^
/usr/include/qt5/QtCore/qvariant.h:216:24: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘const char*’
/usr/include/qt5/QtCore/qvariant.h:214:5: note: QVariant::QVariant(float)
QVariant(float f);
^
/usr/include/qt5/QtCore/qvariant.h:213:5: note: QVariant::QVariant(double)
QVariant(double d);
^
/usr/include/qt5/QtCore/qvariant.h:212:5: note: QVariant::QVariant(bool)
QVariant(bool b);
^
/usr/include/qt5/QtCore/qvariant.h:211:5: note: QVariant::QVariant(qulonglong)
QVariant(qulonglong ull);
^
/usr/include/qt5/QtCore/qvariant.h:210:5: note: QVariant::QVariant(qlonglong)
QVariant(qlonglong ll);
^
/usr/include/qt5/QtCore/qvariant.h:209:5: note: QVariant::QVariant(uint)
QVariant(uint ui);
^
/usr/include/qt5/QtCore/qvariant.h:208:5: note: QVariant::QVariant(int)
QVariant(int i);
^
/usr/include/qt5/QtCore/qvariant.h:199:5: note: QVariant::QVariant(QVariant::Type) <near match>
QVariant(Type type);
^
/usr/include/qt5/QtCore/qvariant.h:199:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘QVariant::Type’
make: *** [build/transactiontablemodel.o] error 1
mysonix1@homebase:~/PayCon$
Is it necessary to install certain packages or dependencies for Qt5? Or what mistake I made? I work with Ubuntu. I added all the main files I had, I'm recompiling it now to check on my Ubuntu 32 bit. Are you running 32 bit or 64 bit? Ubuntu 64-bit My apologies, seems as though I missed a couple files I changed and going through it all now. No problem  |
|
|
|
Awesome, I finished up my testing and added all my changes into the master branch of Github 47 changed files with 1,115 additions and 448 deletions.
Wallet Work -Added Time estimate to Coin Control -Improved Minting information for Minting Icon (time estimation, multisend notification, weights) -Fix of wallet lock/unlock bug -Improved orphan removal -Improved connection to nodes -Date range for Minting -Added number of transactions to overview -Clearer information for rewards in Statistics -"getstaketx" RPC call (incomplete) -"getweight" RPC call -"deleteaddress" RPC call -"getconfs" RPC call getstaketx needs a little fine tuning, other than that all the rest are quite nice additions to the wallet information. Enjoy! Hello Dev My last wallet worked well. But after this recent changes I can't compile the new Qt-wallet. src/qt/transactiontablemodel.cpp:552:23: error: conversion from ‘int64_t {aka long int}’ to ‘QVariant’ is ambiguous
return rec->status.depth;
^
src/qt/transactiontablemodel.cpp:552:23: note: candidates are:
In file included from /usr/include/qt5/QtCore/qabstractitemmodel.h:45:0,
from /usr/include/qt5/QtCore/QAbstractTableModel:1,
from src/qt/transactiontablemodel.h:4,
from src/qt/transactiontablemodel.cpp:1:
/usr/include/qt5/QtCore/qvariant.h:483:5: note: QVariant::QVariant(Qt::CursorShape) <near match>
QVariant(Qt::CursorShape) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:483:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::CursorShape’
/usr/include/qt5/QtCore/qvariant.h:482:5: note: QVariant::QVariant(Qt::PenStyle) <near match>
QVariant(Qt::PenStyle) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:482:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::PenStyle’
/usr/include/qt5/QtCore/qvariant.h:481:5: note: QVariant::QVariant(Qt::BrushStyle) <near match>
QVariant(Qt::BrushStyle) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:481:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::BrushStyle’
/usr/include/qt5/QtCore/qvariant.h:480:5: note: QVariant::QVariant(Qt::GlobalColor) <near match>
QVariant(Qt::GlobalColor) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:480:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::GlobalColor’
/usr/include/qt5/QtCore/qvariant.h:473:5: note: QVariant::QVariant(QMetaType::Type) <near match>
QVariant(QMetaType::Type) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:473:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘QMetaType::Type’
/usr/include/qt5/QtCore/qvariant.h:466:12: note: QVariant::QVariant(void*) <near match>
inline QVariant(void *) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:466:12: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘void*’
/usr/include/qt5/QtCore/qvariant.h:216:24: note: QVariant::QVariant(const char*) <near match>
QT_ASCII_CAST_WARN QVariant(const char *str);
^
/usr/include/qt5/QtCore/qvariant.h:216:24: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘const char*’
/usr/include/qt5/QtCore/qvariant.h:214:5: note: QVariant::QVariant(float)
QVariant(float f);
^
/usr/include/qt5/QtCore/qvariant.h:213:5: note: QVariant::QVariant(double)
QVariant(double d);
^
/usr/include/qt5/QtCore/qvariant.h:212:5: note: QVariant::QVariant(bool)
QVariant(bool b);
^
/usr/include/qt5/QtCore/qvariant.h:211:5: note: QVariant::QVariant(qulonglong)
QVariant(qulonglong ull);
^
/usr/include/qt5/QtCore/qvariant.h:210:5: note: QVariant::QVariant(qlonglong)
QVariant(qlonglong ll);
^
/usr/include/qt5/QtCore/qvariant.h:209:5: note: QVariant::QVariant(uint)
QVariant(uint ui);
^
/usr/include/qt5/QtCore/qvariant.h:208:5: note: QVariant::QVariant(int)
QVariant(int i);
^
/usr/include/qt5/QtCore/qvariant.h:199:5: note: QVariant::QVariant(QVariant::Type) <near match>
QVariant(Type type);
^
/usr/include/qt5/QtCore/qvariant.h:199:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘QVariant::Type’
make: *** [build/transactiontablemodel.o] error 1
mysonix1@homebase:~/PayCon$
Is it necessary to install certain packages or dependencies for Qt5? Or what mistake I made? I work with Ubuntu. I added all the main files I had, I'm recompiling it now to check on my Ubuntu 32 bit. Are you running 32 bit or 64 bit? Ubuntu 64-bit |
|
|
|
Awesome, I finished up my testing and added all my changes into the master branch of Github 47 changed files with 1,115 additions and 448 deletions.
Wallet Work -Added Time estimate to Coin Control -Improved Minting information for Minting Icon (time estimation, multisend notification, weights) -Fix of wallet lock/unlock bug -Improved orphan removal -Improved connection to nodes -Date range for Minting -Added number of transactions to overview -Clearer information for rewards in Statistics -"getstaketx" RPC call (incomplete) -"getweight" RPC call -"deleteaddress" RPC call -"getconfs" RPC call getstaketx needs a little fine tuning, other than that all the rest are quite nice additions to the wallet information. Enjoy! Hello Dev My last wallet worked well. But after this recent changes I can't compile the new Qt-wallet. src/qt/transactiontablemodel.cpp:552:23: error: conversion from ‘int64_t {aka long int}’ to ‘QVariant’ is ambiguous
return rec->status.depth;
^
src/qt/transactiontablemodel.cpp:552:23: note: candidates are:
In file included from /usr/include/qt5/QtCore/qabstractitemmodel.h:45:0,
from /usr/include/qt5/QtCore/QAbstractTableModel:1,
from src/qt/transactiontablemodel.h:4,
from src/qt/transactiontablemodel.cpp:1:
/usr/include/qt5/QtCore/qvariant.h:483:5: note: QVariant::QVariant(Qt::CursorShape) <near match>
QVariant(Qt::CursorShape) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:483:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::CursorShape’
/usr/include/qt5/QtCore/qvariant.h:482:5: note: QVariant::QVariant(Qt::PenStyle) <near match>
QVariant(Qt::PenStyle) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:482:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::PenStyle’
/usr/include/qt5/QtCore/qvariant.h:481:5: note: QVariant::QVariant(Qt::BrushStyle) <near match>
QVariant(Qt::BrushStyle) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:481:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::BrushStyle’
/usr/include/qt5/QtCore/qvariant.h:480:5: note: QVariant::QVariant(Qt::GlobalColor) <near match>
QVariant(Qt::GlobalColor) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:480:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘Qt::GlobalColor’
/usr/include/qt5/QtCore/qvariant.h:473:5: note: QVariant::QVariant(QMetaType::Type) <near match>
QVariant(QMetaType::Type) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:473:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘QMetaType::Type’
/usr/include/qt5/QtCore/qvariant.h:466:12: note: QVariant::QVariant(void*) <near match>
inline QVariant(void *) Q_DECL_EQ_DELETE;
^
/usr/include/qt5/QtCore/qvariant.h:466:12: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘void*’
/usr/include/qt5/QtCore/qvariant.h:216:24: note: QVariant::QVariant(const char*) <near match>
QT_ASCII_CAST_WARN QVariant(const char *str);
^
/usr/include/qt5/QtCore/qvariant.h:216:24: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘const char*’
/usr/include/qt5/QtCore/qvariant.h:214:5: note: QVariant::QVariant(float)
QVariant(float f);
^
/usr/include/qt5/QtCore/qvariant.h:213:5: note: QVariant::QVariant(double)
QVariant(double d);
^
/usr/include/qt5/QtCore/qvariant.h:212:5: note: QVariant::QVariant(bool)
QVariant(bool b);
^
/usr/include/qt5/QtCore/qvariant.h:211:5: note: QVariant::QVariant(qulonglong)
QVariant(qulonglong ull);
^
/usr/include/qt5/QtCore/qvariant.h:210:5: note: QVariant::QVariant(qlonglong)
QVariant(qlonglong ll);
^
/usr/include/qt5/QtCore/qvariant.h:209:5: note: QVariant::QVariant(uint)
QVariant(uint ui);
^
/usr/include/qt5/QtCore/qvariant.h:208:5: note: QVariant::QVariant(int)
QVariant(int i);
^
/usr/include/qt5/QtCore/qvariant.h:199:5: note: QVariant::QVariant(QVariant::Type) <near match>
QVariant(Type type);
^
/usr/include/qt5/QtCore/qvariant.h:199:5: note: no known conversion for argument 1 from ‘int64_t {aka long int}’ to ‘QVariant::Type’
make: *** [build/transactiontablemodel.o] error 1
mysonix1@homebase:~/PayCon$
Is it necessary to install certain packages or dependencies for Qt5? Or what mistake I made? I work with Ubuntu. |
|
|
|
You will be able to check the source code at launch You should publish the link to the source code before. Where is the problem? |
|
|
|
Und ich hoffe sehr, Du hast ordentlich Geld verloren. Nein, nur weniger gewonnen. Du glaubst doch nicht wirklich, das er den Scheiß nur hier gespamt hat? Und: Wenn es nichts bringen würde, würde es keiner machen. Ergo gibt es ausreichend Trottel, die da drauf reinfallen und irgendjemandem Geld schenken. Was mich am meisten wundert: Warum ist der thread noch da? Ich bin nicht gläubig  Ich weiß allerdings, daß die Ponzis genau so funktionieren. Die ersten User gewinnen meist. Diese machen dann natürlich massiv Werbung, damit das Ding so lange wie möglich aufrecht erhalten wird. So stecken immer mehr Leute ihre Kohle rein, die dann auch wieder werben oder Reflinks spammen, damit noch mehr Leute einzahlen und sie möglichst auch noch die Auszahlung bekommen. Ich habe z.B. CryptoDouble lange beobachtet. Dort lief es genau so... Ob Psynova nun Urheber der Seite oder Einzahler war, weiß ich natürlich nicht. |
|
|
|
Gefunden,getestet und für gut befunden ! www.twice-btc.wls.netBeeilt euch solang die Page noch online ist,sind ja in letzterzeit einige Down gegangen Lol, was für ein Idiot. Diesmal war aber jemand schneller und hat den Ponzi Mist geschlossen. Und ich hoffe sehr, Du hast ordentlich Geld verloren. |
|
|
|
@Crestington
How do I get the best performance for staking?
For example: I buy 20000 CON on ccex.
Should I use one or several addresses in my wallet?
And how should I split the coins? Blocks of 1000 or 2000 Coins?
Cheers
s0nix
Best performance is splitting your Blocks up into 500 each and they would Stake after roughly 2-3 days. After 5 days if you have Blocks that have not Staked, Blocks under 500 Coins, in the same address, will combine together until larger than 500 Coins (plus reward) into one Block. Using multiple addresses helps to increase your anonymity but you want atleast 1-2k per address to Coins can combine with each other. You can see an example here on the PayCon Block explorer http://blockexperts.com/con/height/75742If you are a bit savvy with compiling from source as well, you can also change the split and combine thresholds in the wallet.cpp file to help you split and combine your Blocks more efficiently and at a later date, user adjustable thresholds will be part of a wallet update. We also have https://paycon.slack.com/ now which works like an instant messaging and filesharing service, it's free and you can signup with a fake email if you want, you just have to be able to use the email supplied because I would need to send an invite. Nice Thanks for your help. |
|
|
|
|
@Crestington
How do I get the best performance for staking?
For example: I buy 20000 CON on ccex.
Should I use one or several addresses in my wallet?
And how should I split the coins? Blocks of 1000 or 2000 Coins?
Cheers
s0nix
|
|
|
|
Alle 4 Letztgenannten zahlen regelmäßig aus. Zahlen und Entwicklung gibts nur noch mit Ref-Link Möglichkeit. Die gibts hier leider nicht.
Okay, trotzdem danke. |
|
|
|
@maximal
Gibt es denn neue Zahlen?
Ich fand den Thread bisher recht interessant.
Ich bin raus, waren alles Ponzis :C Waren? Wird nicht mehr ausgezahlt oder woran machst Du das fest? Erreichbar sind die 4 Seiten ja noch. |
|
|
|
|
@maximal
Gibt es denn neue Zahlen?
Ich fand den Thread bisher recht interessant.
|
|
|
|
Vielen Dank. Das hat funktioniert. |
|
|
|
If you have problems with your wallet, follow this instructions: I tried it for the second time... all is well. My wallet is working good and staking cool  Thx |
|
|
|
Hallo zusammen, ich habe eine Frage. Vor einiger Zeit hatte ich mir die Wallet von Securitycoin installiert bzw. aus dem Source Code von GitHub kompiliert. Das lief dann auch zwei Wochen recht gut. Am Montag dann synchronisierte die Wallet nicht mehr. Auf der Seite von SCSY war zu lesen, daß die primären Server unter einer DDoS-Attacke stehen... https://bitcointalk.org/index.php?topic=921241.msg10416899#msg10416899Nun bin ich den Hinweisen einiger User im Forum gefolgt und habe die Wallet neu erstellt, vollständig synchronisieren lassen und die vorher gesicherte wallet.dat (Backup der alten Wallet) geladen. Dann funktionierte es ca. einen Tag, Synchronisation & Stake liefen einwandfrei. Seit heute morgen habe ich aber wieder das gleiche Problem, die Synchronisation funktioniert nicht. Daher meine Frage: muß ich warten, bis die Dev's ihre Server wieder in Ordnung bekommen oder kann man bis dahin auf andere Möglichkeiten zurückgreifen, bespielsweise durch Modifikation der config-Datei? Das Eintragen der Nodes dort hat bisher auch nichts gebracht. Aber ich gehe davon aus, daß die primären eh im Code implementiert sind... oder? Mein Betriebssystem ist Ubuntu 14.04 LTS. Ich bin sicher nicht die erste Person mit einer solchen Frage  , wäre für Hinweise aber dankbar. Diese müssen sich nicht unbedingt auf diese spezielle Wallet beziehen sondern können auch allgemein sein, also was generell in einem solchen Fall zu tun wäre. Grüße s0nix |
|
|
|
It worked one day, now I have the same problem. No sync. @sciak I followed the instructions of @AllCryptoAllDay and @Poly#Crypto. My OS is Ubuntu 14.04 LTS. When I compile the wallet from GitHub, the seeds are implemented? Is there a way to bypass this nodes? Perhaps in the config? My gut tells me it only works properly if your servers are running correctly. But I'm not a programmer or coder, only a user...
|
|
|
|
|
Nachtrag:
Auf Anfrage beim Dev bakam ich nur die Antwort: compile and run, open port 11082... habe fast das Gefühl, daß ist wieder so ein Copy & Paste Wallet und der Dev weiß selbst nicht genau, wie es zu kompilieren ist. Aber ich möchte nicht voreilig und unfair sein. Trotzdem komisch.
|
|
|
|
@Dev
You have it tested - you said that it works. Please give me a tutorial to compile it for ubuntu.
Okay, thanks for your great support |
|
|
|
|
Show Posts
