@Velvet. If you get the "Repairwallet" to work so that it'd get rid of the orphan, it would definitely help to optimize the wallet so it would run better.
its in the new coin ive been working on (w00t) for the swap. sorry guys, i messed up my build environment so i'll need to install and compile everything again. took a lil break today but ill get back to work tomorrow. |
|
|
|
any exchange another yobit exchange?
Yes there is and I highly recommend Cryptopia if you want to buy and sell 1337 coins as it is a trusted exchange and also you can trade in LTC, Doge, XMR and a few other crypto coins. I used to use Yobit a lot but not any more as you never know what you'll get with that exchange, I got sick and tired of the wallets always being in maintenance and that is why I changed over to Cryptopia for 1337 coin. https://www.cryptopia.co.nz/Please can you ask yobit to release my coin as I wanted to send it to poswallet for staking for about 5 days now I cannot im not sure on which chain they are but it doesnt look like the right one... "Wallet status: Online (607508 blocks)" and my wallet shows 680483 blocks... i dont think your coins are lost though. once yobit is back on the right blockchain they should appear in your balance again. i'll post an update later. |
|
|
|
"Woot" is the name of the new coin? lol  no, i was just happy to see you again... w00t w00t I criticize you unjustly. I'm sorry. I really want to have your new project has been successful  no need to be sorry. i understand that 1337 investors who got in late are probably a bit frustrated because the price is getting lower and lower. i hope things will be better for everyone soon. |
|
|
|
"Woot" is the name of the new coin? lol no, i was just happy to see you again... w00t w00t |
|
|
|
... Aw I like the graph Tbh. Stop teasing us and give us a date for w00t  hey there I'd love to but still needs some finishing up to do and i need to run a few tests and monitor the network etc etc. ive been working on 1337 and w00t continuously since i got back. i might need to take a lil break after the release cause im exhausted  gives us something to look forward too we can wait, go somewhere warm and enjoy some of natures finest  They failed, man. They were busy polishing the code and forgot to turn off the gas in the kitchen. Someone lit a matcha and lighted a cigarette with it, causing the kitchen to blow up and everyone else in the room to die in an explosion. If I was in ur shoes I would drop my shares and move on instantly. Who would follow a coin whose team burned alive? what are you talking about? who are 'they'? shares?  |
|
|
|
Nope blockchain bloat is an incurable disease and will progress till the end of coin's lifespan.
Wasn't talking about blockchain. Was referring to graph. it may please you to hear that there wont be a graph in w00t. well not in the first release anyway... i might add it later and yes ladies and gentlemen, the time of the release is near! its based on another source code and it will hopefully be more stable compared to 1337's source code because it uses a more recent version of PPC, the mother of all POS coins. keep an eye on this thread in the next week p.s: it wont look as good as the 1337 wallet though but we can always improve things later. its my first (and hopefully last) coin to be released and it took me many frustrating hours and the help of several friends to get to this point so dont be too hard on me ok thank you all for being so patient. Aw I like the graph Tbh. Stop teasing us and give us a date for w00t hey there I'd love to but still needs some finishing up to do and i need to run a few tests and monitor the network etc etc. ive been working on 1337 and w00t continuously since i got back. i might need to take a lil break after the release cause im exhausted |
|
|
|
Nope blockchain bloat is an incurable disease and will progress till the end of coin's lifespan.
Wasn't talking about blockchain. Was referring to graph. it may please you to hear that there wont be a graph in w00t. well not in the first release anyway... i might add it later and yes ladies and gentlemen, the time of the release is near! its based on another source code and it will hopefully be more stable compared to 1337's source code because it uses a more recent version of PPC, the mother of all POS coins. keep an eye on this thread in the next week p.s: it wont look as good as the 1337 wallet though but we can always improve things later. its my first (and hopefully last) coin to be released and it took me many frustrating hours and the help of several friends to get to this point so dont be too hard on me ok thank you all for being so patient. |
|
|
|
I am trying to move my coin out of yobit but they said I cannot withdraw my coins
have a bit more patience please. im working on it. |
|
|
|
This is good to see a dev wanting to help people get back their 1337 coins from an exchange. Most devs would just give up and not worry about it but you sir are going above all to help fix this problem with C-cex exchange. Now lets just hope C-cex goes along with it and works with you to sort out the issues because it has gone on for far too long now.
thank you for the kind words its the least i can do to try to get the coins back to their rightful owners. sorry for the delays btw. lots of stuff that needs my attention now but hopefully im able to finish the update this week and after that i can focus on the new coin. Nice to see that this coin is not dead yet and development is going further. I know you have a lot of work on your ToDo-List, but may you find some time to contact yobit also, i have some 1337 there. Their Wallet is still broken, typically for yobit they doesn't answer on support tickets, maybe you as the coin dev get more attention to your requests. Does anybody else have 1337 there? yes i'll contact them to see what the problem is. the next halving of the apr is on februari 25th but im working on releasing that update this week so they dont have to wait till then. maybe im pushing it a bit with the hard forks every 3 months but i havent found a better solution yet sadly. thanks for the notification. |
|
|
|
This is good to see a dev wanting to help people get back their 1337 coins from an exchange. Most devs would just give up and not worry about it but you sir are going above all to help fix this problem with C-cex exchange. Now lets just hope C-cex goes along with it and works with you to sort out the issues because it has gone on for far too long now.
thank you for the kind words its the least i can do to try to get the coins back to their rightful owners. sorry for the delays btw. lots of stuff that needs my attention now but hopefully im able to finish the update this week and after that i can focus on the new coin. |
|
|
|
A recent copy of the blockchain can be found at http://cryptochainer.com/dir/?page_id=365dev doesnt seem to be willing to hand over the github but thats fine. i'll see if i can get RUB added to some more services etc. if anyone is interested in putting up a service or do a translation they can pm me for a bounty. i also paid to extend the hosting for the blockexplorer. i caught most of the dump a lil while ago and keep the coins off the exchanges. im glad to see that theres some trading activity going on. the price is still low enough for anyone to get in cheap. |
|
|
|
|
I received a pm today regarding the issue with C-cex. one of the questions was "Have you considered other options for resolving the issue, or are you writing it off?"
to be frank, the coins must still be somewhere in c-cex's possession and ive been told that users can still see them in their c-cex balance but with the notice "Wallet Broken".
Ive never run an exchange or anything remotely similar but i assume they must have a wallet.dat file that contains the coins of their users, in this case 1337. So your coins are not lost, we just have to find a way to get them back to you, the rightful owner.
Maybe im thinking too simple but what is stopping them from loading the coins in a windows wallet and sending them to the withdrawal address the users provide them with? is it too much work? Apparently it is, otherwise they would have thought of this a long time ago...
Well, if its too much work for them I'll offer my assistance to get things sorted and do the dirty job myself. They can send me their unencrypted wallet.dat file along with a list of users and their balances and send the users to me to claim their coins.
Actually, i dont even need the usernames in the list, maybe just the amounts would be enough. I would need a screenshot from the users 1337 balance so they can proof how many coins they had on c-cex, along with an address where they want to receive their coins and thats it... you get your coins back.
For those who are shy or who rather want to stay anonymous and dont want to pm me on here, i can find another way for you to contact me ( like through email or something). I dont mind doing some extra work for my community and im not interested in stealing anyones coins either cause i have plenty of my own.
Let me hear your thoughts on this and we will take it from there. It will also depend on c-cex ofc if they are willing to cooperate but im not writing anything off and will always keep looking for a solution.
|
|
|
|
I believe my explorer is now up to date. Keep in mind that the richlist is not live, and is refreshed every 12 hours.
thanks for the quick response looks like anemol's linux wallet has problems with processing stake modifiers,
at least some of them #337903, #630595,
anybody who's up to that level are welcome to analyze,
maybe makes sense to place checkpoints right there idk
yeah i was thinking of that too but if there really was some prick who intentionally screwed with the chain we need to prevent that from happening again. lets see if sigmike is willing to help us again. |
|
|
|
thanks steve sent you some coins I am considering maintaining an inventory of .999 silver 1 gram, 10 gram and 1 oz. ingots with custom engraving and trading them for Stablecoins. I wonder if this is feasible because Stablecoin holders with millions of Stablecoin in their possession could deplete my inventory, quickly. Also, I would be trading at a loss. The only way the price will change is if the Stablecoins are bought on an exchange.
Cryptopia only has a few million coins for trade. The other over 20 million Stablcoins are being horded. Possibly I could limit the orders from individual traders.
maybe start with the smaller ingots and put them on topia's marketplace? and yes, a limit on the amount that one can buy would be the best way imho. gl |
|
|
|
Is the bloat going to be taken out?
nope, i like the 'bloat'. its like looking at the pulse of the network. memory usage seems normal too. by looking at the 'bloat' i found out that ccex started staking their (users) 1337 yesterday  http://www.presstab.pw/phpexplorer/1337/address.php?address=LKVgSiT5c7wxHva8MJVh3tvgUv5ppu9sgZwhich is odd cause they delisted 1337. since they have plenty of coins, im sure they'll find a good solution to send the coins to the rightful owners... just to make it more obvious: DONT SEND COINS TO C-CEX |
|
|
|
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 |
|
|
|
|
Show Posts
