g++ -c -fpermissive -fstack-protector-all --param ssp-buffer-size=1 -O2 -D_REENTRANT -fdiagnostics-show-option -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector -fPIE -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DQT_DISABLE_DEPRECATED_BEFORE=0 -DUSE_QRCODE -DUSE_UPNP=1 -DSTATICLIB -DUSE_IPV6=1 -DHAVE_BUILD_INFO -DLINUX -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_NETWORK_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I/usr/local/qt5/mkspecs/linux-g++ -Isrc -Isrc/json -Isrc/qt -isystem /usr/local/include -Isrc/leveldb/include -Isrc/leveldb/helpers -I/usr/local/qt5/include -I/usr/local/qt5/include/QtWidgets -I/usr/local/qt5/include/QtNetwork -I/usr/local/qt5/include/QtGui -I/usr/local/qt5/include/QtCore -Ibuild -Ibuild -o build/addresstablemodel.o src/qt/addresstablemodel.cpp
In file included from src/qt/addresstablemodel.cpp:3:0:
src/qt/walletmodel.h:103:74: error: ‘uint64_t’ has not been declared
Makefile:7465: recipe for target 'build/addresstablemodel.o' failed
This was with qt5.3.2, so it-s definetly not the compiler. 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. I'll try it too. This happens now: g++ -c -fpermissive -fstack-protector-all --param ssp-buffer-size=1 -O2 -D_REENTRANT -fdiagnostics-show-option -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector -fPIE -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DQT_DISABLE_DEPRECATED_BEFORE=0 -DUSE_QRCODE -DUSE_UPNP=1 -DSTATICLIB -DUSE_IPV6=1 -DHAVE_BUILD_INFO -DLINUX -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_NETWORK_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I/usr/local/qt5/mkspecs/linux-g++ -Isrc -Isrc/json -Isrc/qt -isystem /usr/local/include -Isrc/leveldb/include -Isrc/leveldb/helpers -I/usr/local/qt5/include -I/usr/local/qt5/include/QtWidgets -I/usr/local/qt5/include/QtNetwork -I/usr/local/qt5/include/QtGui -I/usr/local/qt5/include/QtCore -Ibuild -Ibuild -o build/addresstablemodel.o src/qt/addresstablemodel.cpp
In file included from src/qt/addresstablemodel.cpp:3:0:
src/qt/walletmodel.h:103:74: error: ‘uint64_t’ has not been declared
Makefile:7465: recipe for target 'build/addresstablemodel.o' failed
make: *** [build/addresstablemodel.o] Error 1
So i went into walletmodel.h and changed that uint64_t to int64_t. Didn't fail yet so.. lol, I hate integer types. I'll check it out soon, rested eyes makes the world much clearer. |
|
|
|
@sOnix If it does not work with compiling, check out the following file: /home/yourUser/PayCon/src/qt/transactiontablemodel.cpp.
552 /* return rec->status.depth; */
553 return (qlonglong)rec->status.depth;
So it should work. I'll check it out tomorrow, I have been doing some interesting stuff with seeing how to create faster syncing of fresh wallets. I made up this full copy of the Blockchain from scratch in Windows https://www.dropbox.com/s/i7eshtfqn5ok9e2/PayCon2.zip?dl=0I'm curious if a new node could use it to sync right to the highest chain without having to painstakingly wait to sync. The sync times are actually really good, I just want super-fast sync times and wondering about how torrents might be used and Blockchain trimming. If you could have a Coin in which you can always sync quickly and always have a small Blockchain then you've already won half the battle. Perfect, it works! For a fresh install: So in Windows you would go to the appdata/roaming directory and create a PayCon folder, and download the PayCon2.zip to that directory, unzip it and start PayCon-QT I Linux it would be just as easy, mkdir .PayCon cd .PayCon wget https://www.dropbox.com/s/i7eshtfqn5ok9e2/PayCon2.zipunzip PayCon2.zip Start PayCond I think I synced to the highest chain from fresh in about 5 minutes, lol |
|
|
|
Oops i think someone is going to be pissed off come morning.
Just saw over 30k of buy wall get eaten at 0.00032.
700 more XPY and the next resistance is 4.3k at 0.0003168 if its not pulled first and the way someone just dumped what they hafd it wont last long.
Has the honour amongst thieves broken down and someone just dumped into someone elses fake support wall? If these scammers cant even trust each other....
Edit: Never mind they just ate the last bit and the next wall was pulled before it could get eaten. Not a lot of support left
Poopcoin still trading at 0.0003 BTC. Amazing, thought was below 100 Sat now. Not for long, Hyper-Inflators still have the runs. |
|
|
|
|
Hey
What are the RPC and P2P ports for MaryJaneCoin?
|
|
|
|
@sOnix If it does not work with compiling, check out the following file: /home/yourUser/PayCon/src/qt/transactiontablemodel.cpp.
552 /* return rec->status.depth; */
553 return (qlonglong)rec->status.depth;
So it should work. I'll check it out tomorrow, I have been doing some interesting stuff with seeing how to create faster syncing of fresh wallets. I made up this full copy of the Blockchain from scratch in Windows https://www.dropbox.com/s/76mxqd0tp2fi1v2/PayCon.zip?dl=0I'm curious if a new node could use it to sync right to the highest chain without having to painstakingly wait to sync. The sync times are actually really good, I just want super-fast sync times and wondering about how torrents might be used and Blockchain trimming. If you could have a Coin in which you can always sync quickly and always have a small Blockchain then you've already won half the battle. |
|
|
|
Getting this. Suspecting is not related to qt4 but seems similar to the other problem
Scr/qt/walletmodel.h:103:74: error Unit64_t has not been declared.
I'll take a look, I also have Lindows with 64 bit Ubuntu as well I can build with, I just never use it because it takes up more ram and harder to build on. Check out the pastebin a couple page ago or so and see what you can find, muddafudda's repository is on 1.05 as well so you can also build from that if you need to. |
|
|
|
I go on vacation for a few days and come back to some pretty advanced staking conversation. I like it  Presstab is back!  |
|
|
|
"Additionally, the company CEO fled the United States for the United Arab Emirates (UAE), leaving no employees in the company to address consumer requests, until being returned to the United States, less than two months later, by the U.S. government, due to violations of financial responsibility laws in the UAE, which would have required imprisonment." That's new. What's the source for the information in the charge-back request? How is that new? It's been posted all over this thread as it happened. Where? Where in this thread does it say that the United States Government forcefully returned Josh Garza to the United States because I haven't seen it. Did they send Marshalls over to get him or did they write him a polite letter? Also, if Josh Garza had committed offences in Dubai he would have been dealt with, IN DUBAI. You don't hand over people who have committed crimes in your country to somebody else, you prosecute. "Additionally, the company CEO fled the United States for the United Arab Emirates (UAE),
leaving no employees in the company to address consumer requests, until being returned to
the United States, less than two months later, by the U.S. government, due to violations of
financial responsibility laws in the UAE, which would have required imprisonment."Something seriously doesn't add up with that statement. And the fact that he isn't even in custody in the US makes it even more bizarre. He could have been imprisoned in Dubai but they sent him to America where he walks free. That makes total sense. /s You didn't read the follow-up post. He wasn't TAKEN from Dubai by the feds. He was facing jail in dubai due to legal troubles there. The us Consulate/Embassy had to rescue him and get him to the US, he flew to Texas. Because as he stated "I am still an american citizen" Since the SEC/FBI work like molasses in antarctica there was no charges filed by the time he got stateside and he is now free in the US most likely attempting to get to belgium. Again, I have personally spent my own time and business resources this past month while in the region to confirm first hand there is no proven and/or actionable evidence Garza was EVER in Belgium or Dubai at any time in the past 12 months. All this talk of Garza overseas at any time for personal, "business", or legal reasons looks to be without standing. Scott- What about his cars? apparently they were shipped to Dubai and were sold once there, they would be the best point of reference to get some information. |
|
|
|
I was able to find some active nodes via block explorer. It's giving me 4 active connections now.
For the record, I started mining this coin right when it launched.
A word of advice for any newcomer looking at getting/mining this coin. Don't.
The current developer (Vic) appears to have a god complex going on and a chip the size of Africa on the shoulder.
Dev also refuses to let original Dev and community to take over. Instead threatens legal action.
Then comes here and says LTCD is dead. That is was a pump n dump scam coin from the start. Now this is based on the word of a hired 3rd party programmer who "couldn't fix/update the code". That may well be the case, but we will never know for sure. Dev refuses to let the code be vetted by the community.
What I've learned from all this, is that any future coin this Dev is involved with, I shall steer clear of.
I left him negative feedback saying the same thing and left this thread as reference, good to know that other people share the same view. |
|
|
|
I also fixed the statistics page to correctly read the moneysupply and easier to read Block Rewards.  |
|
|
|
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. src/qt/transactiontablemodel.cpp:552:23: error: conversion from ‘int64_t {aka long int}’ to ‘QVariant’ is ambiguous return rec->status.depth; try changing it to return (qlonglong)rec->status.depth; Presstab told me once that he never changed HYP to int64_t from int64 because it tends to be a pain in the ass when it comes to compatibility. |
|
|
|
hi guys , i need help , what do you think abou XPY ? i buy 16000 XPY at rate 0.00049 and still hold until now , maybe i should sell or stiil Hold until $20/XPY very soon ?
Not sure if you are trolling but market fundamentals point to a 25% decline over the next week |
|
|
|
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. 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 |
|
|
|
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. |
|
|
|
Buhbyes support wall @ .00032:  Are Those Who Have Endless Free XPY who have been working together for this last pump breaking ranks and devouring each others push walls? I have been watching that same ~20 BTC wall being pushed up and pulled away right before dumpage for a couple of weeks, and all of a sudden someone dumped into it. P.S: Got ninja'd by Clownius-LOL. Looks like he is thinking the same thing I am. The current buy support is at 0.00025, that 100k order blew out the only support. Do people forget that there are free hyper-inflating wallet keys and can use them if you have more than 125k Coins? Once it gets low enough I am sure you will have people with enough Coins that they will use these keys to compound and sell into the market. Flawed by design, if you have specific wallet keys you can add to get hyper-inflation then eventually these keys will get released and people will use them because it's in the rules of the Blockchain. Any word on what Cryptsy is doing with their Hyper-inflating wallet? |
|
|
|
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  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. |
|
|
|
How about technical advancement for the pursuit of profit? Depends on how you go about it, is it through lies an deception, or are you making money because you can do things other people can't do and using that to further advance the technology. Anyone saying they are in it solely for the technical advancement is lying to themselves.
Not true. Do you know what Einstein's average salary was? "The reasonable figure that Einstein suggested was the modest sum of $3,000 [about $46,800 in today's dollars]. Flexner upped it to $10,000 and offered Einstein an annual pension of $7,500, which he refused as "too generous," so it was reduced to $6,000. When the Institute hired a mathematician at an annual salary of $15,000, with an annual pension of $8,000, Einstein's compensation was increased to those amounts. "http://www.wsj.com/articles/SB10001424052748703906204575027503446091776Obviously you need some money to live, and more money to be comfortable. But the culture of people treating money as an end in itself needs to stop. Major corporations and the filthy rich simply hoard money like it was a stake in a shitcoin, and even though the federal government can't buy ink fast enough to print more money, 99% of it goes directly into the pockets of the 1%. And what about the people who claim they are bringing about technological advancements but all they really do is flex their superior sales skills or ability to put clients under their mind control? This seems to be what at least 50% of all business in America is comprised of. Well played, I think it's a bit different with Crypto though as when drawing money from a particular Coin it reduces the amount that everyone else can get out of it so I think that falls under the category of "floating all boats" and spending as little as possible. Would you be happy with receiving 50-100k a year rather than millions if it also meant that others could also make money as well? Then the question is, how do you achieve that? And what about the people who claim they are bringing about technological advancements but all they really do is flex their superior sales skills or ability to put clients under their mind control? This seems to be what at least 50% of all business in America is comprised of.
You could have the best product but without good marketing then how would people be excited enough to buy the product? I'd say a business with an average product and great marketing could outperform a great product with average marketing. |
|
|
|
@Crestington, I was thinking the same after posting man..
I too *only got involved because of the chance of maybe making some money.
so I like to think I got into this stuff for 50% profit and 50% tech stuff or what ever.
What has worried me is when too many guys are ONLY here for the profit side.
My own brother told me Fuck Bitcoin I just want money when we mentioned this matter
and I was kind of disgusted at that attitude..
reality is many guys here are, loitering around for nothing but money reasons *only.
and the top 10% of the money (richest) play by their own rules.
Well I really like the tech and it is a pursuit for me to advance the tech and learn as much as I can but I also want to make profit and do this stuff fulltime and make money at it. You said it yourself during the whole Blocknet debacle "why don't people try to float all boats" Maybe you aren't making millions of dollars and have less profit but then everyone can make money and that resonates. Let say someone IS in the pursuit of profit purely for their own gain through ICO's, hidden premines, scammy exchanges etc. Well on the internet you really cannot hide anything you do so eventually someone will leak the truth so your name is shot and the ones that are working hard and making a go of it would never want any association so what would be left is to either give up or continue scamming people until it blows up in your face. If you are working for the pursuit of the tech and to make a business out of it, there is lots of room to make money especially if you can learn so much that you can become a sort of guru (I'm not a guru). If you know that much then others will come to you for advice and help and you can charge what you want depending on the complexity of the work. Nasdaq and Wallstreet are only just getting into Crypto so where are they going to get help? All the most experienced people are here, not on wallstreet, they have money and we have experience. If you are wondering, I haven't really made any money at Crypto and spent probably $2k over the last year for help from various people. I've also helped a lot of people with problems where I could and haven't asked for money from them, even turned down some offers because I wasn't confident enough as to what I was doing (and lack of time). Maybe the goal should not be how much money you can make, but how little money you can spend? lol |
|
|
|
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 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 |
|
|
|
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. |
|
|
|
|
Show Posts
