Happy New Year and all the best to all of you. now to get back to work... i'll look into this issue asap. thanks to everyone for being so helpful and supportive while i was away. Nice find, and thanks for the discussion link  That said.. I'm not the developer of this coin.. I only assisted Velvet with some wallet work.. So I guess it's waiting for him to address this issue.. |
|
|
|
Thank you very much Sir Velvet, Do I need to delete all files in roaming except wallet.dat? to resync? yes its probably best to do a fresh install. will take a few hours Sir Velvet, 100% sync and running, but 700K plus 1337 coins missing. Why? This problem sounds familiar with DigiCube, 10K cube missing. So sad. do you have the same amount of total blocks as http://www.presstab.pw/phpexplorer/1337/index.php is showing? could it be possible that you staked that 700k on the old wallet after 25th of november? I have screen shot taken last Nov. 30, 2016. But the overall total I think it was before Nov. 25, I have lots of generated but not accepted of about 150k 1337 coins only, 700k is too much. I only open my 1337 wallet 3 time a week only. Now is not the same total, before the new wallet it was 8,851,726.029123 1337Coins in presstab.tw, but now is 8,088,000 more or less in my wallet transaction record, I can't total because still staking. From November 26 to December 1 most coin generated but not accepted, I used latest Wallet version 1602. But lots of transaction not accepted. And why I always got "generated but not accepted" 1337 coins UNTIL NOW. Thank you. please pm me your address |
|
|
|
Thank you very much Sir Velvet, Do I need to delete all files in roaming except wallet.dat? to resync? yes its probably best to do a fresh install. will take a few hours Sir Velvet, 100% sync and running, but 700K plus 1337 coins missing. Why? This problem sounds familiar with DigiCube, 10K cube missing. So sad. do you have the same amount of total blocks as http://www.presstab.pw/phpexplorer/1337/index.php is showing? could it be possible that you staked that 700k on the old wallet after 25th of november? |
|
|
|
Since I was given no notice of the fork (literally day of), the explorer has to be resynced. Hopefully up and running some time today.
thanks! and again, my apologies for the short notice |
|
|
|
velvet cryptopia isnt working at all... my withdrawn still pending...
yes i posted that 2 days ago. but good news, wallet is out of maintenance now and i can confirm that deposits and withdrawals are currently working. |
|
|
|
Thank you very much Sir Velvet, Do I need to delete all files in roaming except wallet.dat? to resync? yes its probably best to do a fresh install. will take a few hours |
|
|
|
The wallet v1.6.0.1-g fell down suddenly without connection, I opened the wallet v1.5.04-g and it works.
Because?
can you do it again ? one error means nothing No longer works for days! try this: go to your 1337 data folder and delete everything except wallet.dat file and restart your wallet. also make sure that no anti-virus or firewall software is blocking access or connections. |
|
|
|
I can report that the 1337 wallet on POSWallet seems to be working just fine. I have some 1337 coins stored on that wallet and never had any issues so far. I will download the 1337 wallet once I know for sure all the issues are fixed and then I'll transfer all my 1337 coins from POSWallet to my own desktop wallet.
I am planning to do this too when all issues will be gone  so why you two leaving poswallet? i thought that this site is the heaven of staking for 1337 if you cant keep your computer on all day long. the only issue i encounter with this site is that you need to keep on deposit coins in order to continue get the exact or more of the same share. if you dont keep deposit than your percentage of the share is going down day by day. poswallet provides a good service so far but its always better to keep full control of your coins if possible |
|
|
|
since presstab hasnt updated the blockexplorer you can use this one to check https://poswallet.com/blockChain/1337/cryptopia updated their 1337 wallet but none of my 2 test deposits went through. i notified them about this already. |
|
|
|
hmm... I'm missing 70% of my coins on the latest wallet.
sync 100% what about strb wallet milly6 ? You gave up ? Theres a guy that claims to know how to remove the negative balance from strb. AFAIK he's working on it. i would like to remind you that this is the ANN for 1337 though, not STRB... |
|
|
|
got home to find I've forked again, resynced but can anyone confirm I'm on the correct chain?  yes i get the same hash |
|
|
|
hmm... I'm missing 70% of my coins on the latest wallet.
please try to rescan your wallet. that should be pretty much impossible to occur... |
|
|
|
from my windows wallet: {
"version" : "v1.6.0.2-g",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 487552792.40756738,
"newmint" : 0.00000000,
"stake" : 55822622.78118500,
"blocks" : 597578,
"timeoffset" : 0,
"connections" : 6,
"proxy" : "",
"ip" : "snip",
"difficulty" : {
"proof-of-work" : 0.36940065,
"proof-of-stake" : 50.64498017
},
"testnet" : false,
"keypoololdest" : 1447022351,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"errors" : ""
}from my linux daemon: "version" : "v1.6.0.1-g",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 597578,
"timeoffset" : -1,
"connections" : 40,
"proxy" : "",
"ip" : "212.24.106.51",
"difficulty" : {
"proof-of-work" : 0.36940065,
"proof-of-stake" : 50.64498017
},
"testnet" : false,
"keypoololdest" : 1471552345,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
Nodes on 1.6.0.2 addnode=173.48.167.209
addnode=212.24.106.51
addnode=186.203.197.12
addnode=69.120.140.117
addnode=73.173.71.115
addnode=109.89.155.161
addnode=198.74.56.141
addnode=93.33.170.142
addnode=109.60.201.34
addnode=109.81.210.60
addnode=96.60.246.99
addnode=86.5.28.9
addnode=89.23.100.31
addnode=86.189.168.51
addnode=82.193.155.224
addnode=2.93.222.236
addnode=88.206.186.58
addnode=84.117.67.186
addnode=149.56.154.75
addnode=78.144.97.243
addnode=77.111.159.249
addnode=77.121.108.134
addnode=169.255.197.79
addnode=76.106.178.142
addnode=213.242.28.247
addnode=85.24.143.58
addnode=2a02:c207:2008:6519::1
addnode=185.24.14.2
addnode=185.57.31.152
addnode=195.200.244.73
addnode=5.189.136.83
addnode=185.59.56.103
addnode=31.129.12.127
addnode=2600:3c03::f03c:91ff:fe9b:253e
addnode=70.124.220.80
addnode=94.209.4.129
List of nodes available at https://www.coinexchange.io/network/peers/1337poswallet.com and coinexchange.io are up2date. blockexplorer hasnt updated yet |
|
|
|
"version" : "v1.6.0.1-g",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 589190,
"timeoffset" : -1,
"connections" : 84,
"proxy" : "",
"ip" : "212.24.106.51",
"difficulty" : {
"proof-of-work" : 0.36940065,
"proof-of-stake" : 125.76997466
},
"testnet" : false,
"keypoololdest" : 1471552345,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
just as a FYI, my node is fully synched without any errors as you can see.
and FYI i never said is node problem, but coin code problem 1.6.0.1? yeah disregard the version number. i was a bit too lazy to change it on my vps but the rest is the same as in 1.6.0.2 look, when i took over the coin everything was working fine. after BanzaiBTC helped me with adding some new features to it, it started to fork on ccex (but only ccex). it became obvious that this was caused because ccex was staking their users coins so i assumed that caused the problems on their end. after that i hired presstab to add the multi-send feature and asked him to take a look at the code. both devs are good at what they do IMHO. otherwise i wouldnt have hired them. im thinking of releasing a 'plain' wallet without the extra features in it because this sucks for both the users as for me. |
|
|
|
|
"version" : "v1.6.0.1-g",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 589190,
"timeoffset" : -1,
"connections" : 84,
"proxy" : "",
"ip" : "212.24.106.51",
"difficulty" : {
"proof-of-work" : 0.36940065,
"proof-of-stake" : 125.76997466
},
"testnet" : false,
"keypoololdest" : 1471552345,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
just as a FYI, my node is fully synched without any errors as you can see.
|
|
|
|
this coin is very very broken!
oh yeah? whats broken according to you? please refrain from posting rubbish without any value whatsoever ive tested the wallet both on windows and linux, with an existing install and with a fresh install. the only error i made was corrected in the v1.6.0.2 that i released. besides that, i really didnt make any funky changes to the source as you can see for yourself on github. ERROR: ConnectBlock() : coinstake pays too much(actual=198363238939931 vs calculated=-184254036296721)
i dont know what went wrong there. anything related to coinstake rewards is in order in the source. both my windows and linux wallets have been running flawless on my end. you can try adding this to your conf file so it will only connect to the dedicated node im running: connect=212.24.106.51 listen=0 i am not the only one having problem to sync it, had it open for 12 hours and was still stuck on same block i left it whats your OS? |
|
|
|
this coin is very very broken!
oh yeah? whats broken according to you? please refrain from posting rubbish without any value whatsoever ive tested the wallet both on windows and linux, with an existing install and with a fresh install. the only error i made was corrected in the v1.6.0.2 that i released. besides that, i really didnt make any funky changes to the source as you can see for yourself on github. ERROR: ConnectBlock() : coinstake pays too much(actual=198363238939931 vs calculated=-184254036296721)
i dont know what went wrong there. anything related to coinstake rewards is in order in the source. both my windows and linux wallets have been running flawless on my end. you can try adding this to your conf file so it will only connect to the dedicated node im running: connect=212.24.106.51 listen=0 |
|
|
|
|
Show Posts
