Good to see you back Velvet  my friend, ive been behind my screens for 12+ hours so unless theres a pink elephant hidden in the tx-es i wouldnt be able to spot it haha. or was it a trick question?  maybe sigmike will respond if i ask him a more specific question. he doesnt seem to be very active on here but i found his email on github. maybe i can look for him on peercointalk too. not giving up. one thing is for sure though, i wont be cloning 1337 for w00t. im thinking of straight cloning the ppc code and modify it with the right settings etc. also, what you said earlier "actually there are little hidden bugs in any coin code, getting fixed only when triggered" is bound to give me nightmares so thnx for that not a trick, i scanned them earlier but for only a 5-byte length, now as i see 4 more shit variations i'd like very much to find a pink elephant as well, becoz of pxi network recomposing and several other things at hand. so we need 2 pink elephants total, i prefer female one... i could add some checkpoints right?( that plus the 3 sig fixes from sigmike) like ppc is using here https://github.com/peercoin/peercoin/blob/master/src/checkpoints.cpp#L26and presstab is using here https://github.com/hyperstake/HyperStake/blob/master/src/checkpoints.cpp#L251337 doesnt have any https://github.com/Velvet78/1337/blob/master/src/checkpoints.cpp#L28and.. getcheckpoint
{
"synccheckpoint" : "000004611c87517dfd29fe7f34bd6da2e1ad3d305ac12afe80a3229069390f68",
"height" : 0,
"timestamp" : "2014-07-25 14:15:16 UTC",
"policy" : "strict"
}
 edit: seems 1337 is missing the command to add manual checkpoints "// The configuration parameter 'checkpointdepth' specifies how many blocks // should the checkpoints lag behind the latest block in auto checkpoint mode. // A depth of 0 is the strongest auto checkpoint policy and offers the greatest // protection against 51% attack. A negative depth means that the checkpoints // should not be automatically generated by the checkpoint master, but instead // be manually entered by operator via the 'sendcheckpoint' command. The manual // mode is also the default mode (default value -1 for checkpointdepth). but i could still add it in the source on the next release Don't forget to add them here also..  https://github.com/Velvet78/1337/blob/master/src/kernel.cpp#L15-L18Also setting up new checkpoint server will help.. https://github.com/Velvet78/1337/blob/master/src/checkpoints.cpp#L353This requires a version/protocol change though.. While you're at it.. I think the alert keys havent been changed with the takeover right? https://github.com/Velvet78/1337/blob/master/src/alert.cpp#L22-L25Cheers! yooo Banzaiii check your skype if you have some time . yes ive been thinking of adding the alert keys in the next update, along with the checkpoints. the next halving is due for feb 25th so i will prolly implement all the changes in that release. hopefully ill get it done this week. thanks for your support |
|
|
|
my friend, ive been behind my screens for 12+ hours so unless theres a pink elephant hidden in the tx-es i wouldnt be able to spot it haha. or was it a trick question? maybe sigmike will respond if i ask him a more specific question. he doesnt seem to be very active on here but i found his email on github. maybe i can look for him on peercointalk too. not giving up. one thing is for sure though, i wont be cloning 1337 for w00t. im thinking of straight cloning the ppc code and modify it with the right settings etc. also, what you said earlier "actually there are little hidden bugs in any coin code, getting fixed only when triggered" is bound to give me nightmares so thnx for that not a trick, i scanned them earlier but for only a 5-byte length, now as i see 4 more shit variations i'd like very much to find a pink elephant as well, becoz of pxi network recomposing and several other things at hand. so we need 2 pink elephants total, i prefer female one... i could add some checkpoints right?( that plus the 3 sig fixes from sigmike) like ppc is using here https://github.com/peercoin/peercoin/blob/master/src/checkpoints.cpp#L26and presstab is using here https://github.com/hyperstake/HyperStake/blob/master/src/checkpoints.cpp#L251337 doesnt have any https://github.com/Velvet78/1337/blob/master/src/checkpoints.cpp#L28and.. getcheckpoint
{
"synccheckpoint" : "000004611c87517dfd29fe7f34bd6da2e1ad3d305ac12afe80a3229069390f68",
"height" : 0,
"timestamp" : "2014-07-25 14:15:16 UTC",
"policy" : "strict"
}
edit: seems 1337 is missing the command to add manual checkpoints "// The configuration parameter 'checkpointdepth' specifies how many blocks // should the checkpoints lag behind the latest block in auto checkpoint mode. // A depth of 0 is the strongest auto checkpoint policy and offers the greatest // protection against 51% attack. A negative depth means that the checkpoints // should not be automatically generated by the checkpoint master, but instead // be manually entered by operator via the 'sendcheckpoint' command. The manual // mode is also the default mode (default value -1 for checkpointdepth). but i could still add it in the source on the next release |
|
|
|
wow, i need to dig to find out, more a question for sigmike time-wise, (to me looks just like different kinds of test sigs with irregular length descriptors, tail is the same, prolly any tail from the blockchain, and the last is an oversized sig) btw, do you see anything irregular in block 337901..337903 tx-es ? my friend, ive been behind my screens for 12+ hours so unless theres a pink elephant hidden in the tx-es i wouldnt be able to spot it haha. or was it a trick question? maybe sigmike will respond if i ask him a more specific question. he doesnt seem to be very active on here but i found his email on github. maybe i can look for him on peercointalk too. not giving up. one thing is for sure though, i wont be cloning 1337 for w00t. im thinking of straight cloning the ppc code and modify it with the right settings etc. also, what you said earlier "actually there are little hidden bugs in any coin code, getting fixed only when triggered" is bound to give me nightmares so thnx for that |
|
|
|
Still blocking {
"version" : "v1.6.0.2-g",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 337902,
"timeoffset" : -1,
"connections" : 11,
"proxy" : "",
"ip" : "************",
"difficulty" : {
"proof-of-work" : 0.36940065,
"proof-of-stake" : 74.28758668
},
"testnet" : false,
"keypoololdest" : 1483543286,
"keypoolsize" : 101,
"paytxfee" : 0.00010000,
"mininput" : 0.00000000,
"errors" : ""
}
thanks for trying. ive sent an email to sigmike, the person who fixed the ppc issue. maybe he can give me some advice to get this damn issue fixed once and for all. fingers crossed |
|
|
|
yup, the funny thing about the issue is that several coins have different level of implementing fixes for it, and many have none, so shit hits the fan at random, then community starts to torture dev with a lot of questions since i'm not a c++ coder, would be nice if presstab look at 116/117 more closely, actually there are little hidden bugs in any coin code, getting fixed only when triggered P.S. would be nice if anemol tested full resync with fixed version i sent a pm to presstab about it, waiting for his reply. @anemol: i havent committed the changes to the repo yet but ive upload the key.cpp file for you here you can try it out. https://www.dropbox.com/s/46o4h2iwlri2fsj/key.cpp?dl=0 (just replace it with the old one in 1337/src and compile) |
|
|
|
any news on c-cex fix?
im testing the fix that desynct suggested on my test environments now. i really hope that will fix the issue but makes me wonder why the problems started around july last year and not sooner. |
|
|
|
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.. Welcome back dev and a Happy New Year to you and everyone in 1337 coin. Hopefully this year will be a great year for this coin and once we have the swap, hopefully it ignites this coin once again and we start to see it worth a lot more then what it is now. Any plans on when this swap will happen dev? and maybe once it's done we can start some promotional campaigns to help spread the word? thank you! while i was away i educated myself a bit more and im able to compile my own windows wallet and even cloned some test coins to try the pre-mine on. i was planning to release w00t this weekend. however, the issue that needs fixing has my highest attention now so i need to consult some ppl asap. its just a few lines of codes to add but at this point im being careful not to make things worse. shouldnt take too long (hopefully tomorrow)... |
|
|
|
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... |
|
|
|
|
Show Posts
