CON - PayCon - Get your CON on! - GetHashing Crypto Community Forum

CON - PayCon - Get your CON on!

cyberdexter 2015-05-04 17:28:47 UTC #21

No worries just sharing the things I come across.

I'm liking the wallet. The integrated IRC is a nice thing to have as well as the links to social and the various exchanges. Keep up the good work

jonnybravo0311 2015-05-06 14:13:32 UTC #22

I don't know if this is the proper place to report bugs/issues with the PayCon wallet, and if not, I apologize.

This one isn't a big deal, it's more of an annoyance. When looking at transactions, you've got the option to sort and filter with dropdown lists for dates and transaction types. Well, the transaction type list is missing the ability to sort on mined transactions. See the screenshot:

In other news, the functionality of "About PayCon" menu brings up the "Stake for Charity" box. That seems a bit odd, and I wouldn't have expected it. I never would have figured out Stake for Charity, except I was looking to see what version of the PayCon wallet I was running, so I clicked the About PayCon menu and up popped the Stake for Charity box .

Crestington 2015-05-06 14:29:49 UTC #23

All places are good places, we can make a list to tackle little issues and hone the code because after all bug fixing is development. I am hoping that GHashing might want to create a section for PayCon, then there could be threads about different issues and ideas. I think it might be too crowded on this one thread to do development and marketing but there is also https://cryptoplays.com and the forum link in the wallet will take you there, we can also use Github issues, and PayCon.slack.com.

cyberdexter 2015-05-06 21:53:47 UTC #24

Very odd I can't re-produce this on the windows-qt. My about works fine

However, my wallet still hasn't staked since I got it which has been easily a week now. I have in avg 16 connections to the network and believe that my config is fine, Got the nodes in there etc.

Still debating setting up sponsored sub-forums.

Crestington 2015-05-06 22:36:29 UTC #25

Staking is dependent on your Block sizes and age, if you are sending a lot of Coins then it pushes out the time at which you are going to Stake unless you are choosing from your youngest Blocks. Blocks of around 1000 Coins should Stake at 2-3 days, 200-300 Coin Blocks may be 4-6 days.

jonnybravo0311 2015-05-06 23:10:27 UTC #26

I probably should have noted that I'm using the OS X version of the wallet No clue why it's doing what it is... I'll probably take a look at the source code, and the make files to see if there's something wrong with the Mac build scripts.

Crestington 2015-05-07 00:19:40 UTC #27

I will take a look when I can as well.

Along with that there are a couple small things to improve upon.

A small list would be:

Wallet re-lock in Stake only mode

Mac version the about links to the Stake for Charity

Coin Control Fees are slightly off (between where you are provided with the Fee to what is actually being sent)

Improvement on orphan removal, rescanning of balances and general connection.

maizenblueminer 2015-05-07 01:21:24 UTC #28

Does this include when the wallet loses a network connection (such as when the host computer goes to sleep)? I just realized after I woke my computer up that it said that the wallet was unlocked but "getstakinginfo" reported "staking: false". I had to lock the wallet and then unlock it to turn staking back on.

cyberdexter 2015-05-07 02:12:47 UTC #29

I've set aside the stake of course from my coin splashing address. The blocks make sense though. I guess I should try smaller ones

Figured from the UI but though the menu would be the same. Guess you found a

Crestington 2015-05-07 11:48:26 UTC #30

I updated all my nodes and added more static connections to them which should help with connectivity.

jonnybravo0311 2015-05-07 14:01:39 UTC #31

@Crestington I'm not sure if this is related in any way... but right about the time you posted this, my wallet stopped properly synchronizing. It's been sitting at block 172273 for quite some time. I've done the restart... would hate to have to wipe and re-download the blockchain...

Also, I've noticed that I now only have 1 or 2 connections to the network, whereas before I had like 15.

Are there any new nodes I should be connected up to? I've got the following list of nodes in my paycon.conf file:

addnode=107.170.179.27 addnode=162.243.155.75 addnode=128.199.231.68 addnode=168.235.149.145 addnode=46.233.40.104 addnode=pay.suprnova.cc

jonnybravo0311 2015-05-07 14:57:54 UTC #32

So... some more investigation...

I blasted the blockchain/db/etc and resynchronized everything. From doing so, I realized that in reality, things stopped working sometime around 21:30 EDT yesterday. My last successful stake was at that time. All stakes after that time are showing in my wallet now as generated but not accepted.

And, I'm stuck again. this time at 172368.

semismiling 2015-05-07 15:26:28 UTC #33

Yeah, mine fell over around 10pm yesterday, and I'm currently also stuck, but at 172485

cryptojumper 2015-05-07 15:28:48 UTC #34

Not working for me too

cyberdexter 2015-05-07 19:41:13 UTC #35

No working three!!

Such CON, such ponzi!!

Just as promised

On a more serious note, what happened?

semismiling 2015-05-07 19:55:56 UTC #36

rofl

I put this elsewhere, but this is the only thing that worked for me, now i have 36 stable connections:

backup wallet just in case.
close paycon
create a plaintext file called PayCon.conf in the paycon data directory (case is important, exact filename for mac/linux is necessary -- windows data dir is %appdata%/roaming/paycon )
Paste these details in, then restart the wallet.

listen=1
daemon=1
rpcuser=LOCAL USERNAME
rpcpassword=YOUR PASS
rpcport=9456
port=9455
rpcallowip=127.0.0.1
addnode=107.170.179.27
addnode=162.243.155.75
addnode=128.199.231.68
addnode=168.235.149.145
addnode=46.233.40.104

if it doesn't work then you should try deleting all but wallet.dat and PayCon.conf and try again, the chain will re-download.

cyberdexter 2015-05-07 19:58:57 UTC #37

Yeah I had the config setup for a while. don't think that's the problem. My local wallet is fine, the server wallet went baba-bobo. At lest I think local is fine. It shows in sync so not sure.

semismiling 2015-05-07 20:01:07 UTC #38

@Crestington changed some node addresses, I think,so check this. I thought mine was fine, and I thought latest client didn't need this conf file..... either they fixed it and it's a coincidence, or it';s something to do with this, lol, because now I have zero problems.

ed: of course, your problem may be totally different, I just know I went through the same thought process ^^ - hope you fix it soon!

cyberdexter 2015-05-07 20:08:24 UTC #39

Just looked at my configs and they are the same. I have addnode=pay.suprnova.cc in there too but the remaining ones are matching with yours. What wallet version you on? 1.5.0.0?

This is what I see on this particular wallet.

I've gone from 144 blocks remaining to 277 blocks and apparently the last received block is 4 hours old. Which can't be right

semismiling 2015-05-07 21:02:07 UTC #40

Oh. Sorry, was worth checking though I guess... I had the EXACT same thing happen 3 times in last 24 hours, and limited connections, mostly 4. Was bloody annoying.

I removed last line by accident, so if that's the only difference, try lol...

How many connections you got?

Wallet version v1.5.0.0PayCon-1.0.5