[ANN][CON] PayCon™ HI POS | LiteStake | Multisend | TOR | Android - page 72.

Crestington

legendary

Activity: 882

Merit: 1024

Quote from: s0nix on June 05, 2015, 05:31:07 PM

Quote from: Crestington on June 05, 2015, 05:01:28 PM

Quote from: Crestington on June 05, 2015, 03:44:55 PM

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 :

Code:

#ifndef TRANSACTIONTABLEMODEL_H
#define TRANSACTIONTABLEMODEL_H

#include 
#include 

#include "uint256_t.h"


class CWallet;
class TransactionTablePriv;
class TransactionRecord;
class WalletModel;

hmm... does not work, can't compile Huh

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.

Hey I found this from Hobonickels on a similar issue for Ubuntu 64 bit

Try this and see how you go, it's a little hackish but could do you to sort it out.

http://pastebin.com/Jh0GA75L

Crestington

legendary

Activity: 882

Merit: 1024

Quote from: lazi on June 05, 2015, 05:12:18 PM

What is your target?
Why should i invest in Paycon, can anybody explain?

Hmm, good question.

It's POS only with moderately high inflation so the rewards are high but you are not getting the same sell pressure as you would with POW which gives a much more stable market. There is continued advancement of the wallet, active people that can help with problems and can connect easily to the network. The question shouldn't be "why should I invest" but "how can I help advance the network?" as everyone has a "Stake" so investing is good, but building on the network is better. Think of it as your Coin and your the developer, how would you make it worth more and how can you contribute beyond just investing.

s0nix

hero member

Activity: 784

Merit: 511

Quote from: Crestington on June 05, 2015, 05:01:28 PM

Quote from: Crestington on June 05, 2015, 03:44:55 PM

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 :

Code:

#ifndef TRANSACTIONTABLEMODEL_H
#define TRANSACTIONTABLEMODEL_H

#include 
#include 

#include "uint256_t.h"


class CWallet;
class TransactionTablePriv;
class TransactionRecord;
class WalletModel;

hmm... does not work, can't compile Huh

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.

lazi

hero member

Activity: 695

Merit: 500

What is your target?
Why should i invest in Paycon, can anybody explain?

Crestington

legendary

Activity: 882

Merit: 1024

Crestington

legendary

Activity: 882

Merit: 1024

s0nix

hero member

Activity: 784

Merit: 511

Crestington

legendary

Activity: 882

Merit: 1024

AngelLox

sr. member

Activity: 466

Merit: 250

Crest, with what should i compile this? Qt 4 fine? Cause i'm having some trouble with my qt5, though i think i can get it to work if it's needed.

vegasguy

legendary

Activity: 1610

Merit: 1003

"Yobit pump alert software" Link in my signature!

Thanks, I love your coin!! My site gets 3000/hits week from crypto enthusiasts. I also post new wallet releases. Especially if I like the coin alot (Like paycon).

Vegas

www.bitcoinlasvegas.net

s0nix

hero member

Activity: 784

Merit: 511

Crestington

legendary

Activity: 882

Merit: 1024

Quote from: vegasguy on June 05, 2015, 11:48:22 AM

Quote from: Crestington on June 05, 2015, 05:16:48 AM

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!

When do you think you can post a windows binary of this? Will this be V1.0.6?

Vegas

There are two bugs to tackle yet before bumping the version, the getstaketx RPC call doesn't display all the information and if removing more than a couple orphans, the wallet will crash, it still removes them but still need to fix those issues. I'll see if I may be able to get a little help sorting it out so we can get new windows and mac binary's out.

Crestington

legendary

Activity: 882

Merit: 1024

vegasguy

legendary

Activity: 1610

Merit: 1003

"Yobit pump alert software" Link in my signature!

Quote from: Crestington on June 05, 2015, 05:16:48 AM

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!

When do you think you can post a windows binary of this? Will this be V1.0.6?

Vegas

s0nix

hero member

Activity: 784

Merit: 511

Quote from: Crestington on June 05, 2015, 05:16:48 AM

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.

Code:

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) 
     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) 
     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) 
     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) 
     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) 
     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*) 
     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*) 
     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) 
     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.

Crestington

legendary

Activity: 882

Merit: 1024

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!

Crestington

legendary

Activity: 882

Merit: 1024

I am also more accessible on https://paycon.slack.com for whoever wants to chat and get involved in the building process.

If you would like an invite, just send me the email you registered for Slack and I will be happy to add you.

Crestington

legendary

Activity: 882

Merit: 1024

Quote from: candlesticks on June 04, 2015, 10:08:19 PM

Ahahaha that's awesome.

At this very moment I am working on time estimation in Coin Control, the time estimate for staking notification has been looking good but the time estimate in Coin Control needs some slight tweaks.

I'll also do up the quick and dirty method for connecting.

Yesterday I upgraded most of my nodes so for Static nodes if anyone needs them, they can use these. I spaced them out across different countries so there should always be a node close to you.

addnode=107.170.179.27
addnode=46.101.165.67
addnode=46.101.25.231
addnode=188.166.115.151
addnode=104.131.180.51

candlesticks

sr. member

Activity: 345

Merit: 250

Crestington

legendary

Activity: 882

Merit: 1024

I created a bootstrap for PayCon, the file is 76mb and takes approximately an hour and a half to reindex the whole Blockchain. This is useful for new users in that they can use the bootstrap and sync up their clients from first install much quicker.

For first install navigate to your data directory (appdata/roaming/PayCon for Windows, .PayCon for Linux), just have the bootstrap.dat, PayCon.conf and wallet.dat(optional) in this directory.

Open PayCond or PayCon QT, it will reindex the Blockchain and seem to hang but atleast 75% time savings on first install.

Let it finish and it will catch up once finished indexing.

Download: https://mega.co.nz/#!DhVHEQiC!wY_e2gzCtVsHX8a3um6IFjAUdiNTlCYqGW46Ga-0KYw

Quote from: Biomech on May 30, 2015, 11:57:39 PM

Quote from: Crestington on May 30, 2015, 11:15:38 PM

Quote from: billotronic on May 30, 2015, 09:27:20 PM

the end user would put the bootstrap into their datadir, start the client, the client processes the blocks, you save a shit ton of time vs syncing a virgin client. it is not the fastest thing in the world, but i would guess of the time savings at the very least 75%.

also, super sexy pi client just cooked for distro from sluppy can be found on the release page check it out.

So you put it in the same directory as the Blockchain? If you have an existing Blockchain do you delete that? What is the reason of renaming it bootstrap.dat? Would it just not be easier to replace the Blockchain with another one and not have to rename it?

Congrats on the new pi client!!!

Yes, you put it in (in this case) .hyperstake (or the windows/Mac equivalent) and then delete everything but wallet.dat, hyperstake.conf and bootstrap.dat

The reason for renaming it is that the core code looks for bootstrap.dat to import a static blockchain, and it imports the whole freaking thing before indexing it. That saves a shitload of time. The reason for not just copying the whole .hyperstake (or whatever coin) data directory is that the data may be corrupt, have transactions only specific to your wallet, etc. And of course, the size. Everything that is needed for the client to extract all that information is in the blk000* files. There are several of them as the blockchain grows, so if you're making a bootstrap AND there is more than one, you need to combine them in serial order. It's easy to do, and it will save you endless headaches when synching a new install or recovering a messed up wallet install.

Another thing I do, and highly suggest if you're not running on a Pi or something tiny like that is add txindex=1 to your configuration file. This pulls ALL the blockchain data, like a block explorer. so you can pull up the data from any valid block in the chain in your own client, not just the ones you had a transaction in Cheesy

Quote from: Crestington on May 31, 2015, 12:15:59 AM

Quote from: Biomech on May 30, 2015, 11:51:28 PM

Quote from: billotronic on May 30, 2015, 07:16:27 PM

yeah what bio said! and I am almost 100% certain you should close the client before doing so. (I always do)

best part is with hyp since the blockchain is still small you can actually just rename blk0001.dat to bootstrap.dat or cat it like bio said if you wanted to make it nice and automated.

that is a feature press should put into his explorer.

https://ecua.mobi/how-to-create-bootstrap-dat/

There ya go. I used it once, but didn't have a download directory setup. I do now, and once GMC is fixed, I'll be using this script to maintain a constantly updated bootstrap. Might do the same for all the coins I collect Cheesy

Though that would require a bigger server than I have right now. At any rate, the script works with minimal modification, or you can just do it manually. You MIGHT need to run this as root or chown your blocks directory to make it work, though.

Perfect! That's exactly what I was looking for, I knew you guys were holding out on me

Tip you guys come CON for the help?

Topic: [ANN][CON] PayCon™ HI POS | LiteStake | Multisend | TOR | Android - page 72. (Read 179167 times)