[ANN] 1337 [MANDATORY UPDATE] 41.78% APR| POS ONLY

[BanzaiBTC]

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#L26

and presstab is using here https://github.com/hyperstake/HyperStake/blob/master/src/checkpoints.cpp#L25

1337 doesnt have any https://github.com/Velvet78/1337/blob/master/src/checkpoints.cpp#L28

and..

Code:

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-L18

Also setting up new checkpoint server will help..
https://github.com/Velvet78/1337/blob/master/src/checkpoints.cpp#L353
This 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-L25


Cheers!

[1714700759]

1714700759

[1714700759]

1714700759

[Velvet78]

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#L26

and presstab is using here https://github.com/hyperstake/HyperStake/blob/master/src/checkpoints.cpp#L25

1337 doesnt have any https://github.com/Velvet78/1337/blob/master/src/checkpoints.cpp#L28

and..

Code:

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-L18

Also setting up new checkpoint server will help..
https://github.com/Velvet78/1337/blob/master/src/checkpoints.cpp#L353
This 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-L25


Cheers!

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

[bitmaster1x]

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#L26

and presstab is using here https://github.com/hyperstake/HyperStake/blob/master/src/checkpoints.cpp#L25

1337 doesnt have any https://github.com/Velvet78/1337/blob/master/src/checkpoints.cpp#L28

and..

Code:

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-L18

Also setting up new checkpoint server will help..
https://github.com/Velvet78/1337/blob/master/src/checkpoints.cpp#L353
This 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-L25


Cheers!

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

Is the bloat going to be taken out?

[Velvet78]

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=LKVgSiT5c7wxHva8MJVh3tvgUv5ppu9sgZ

which 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 

[presstab]

I believe my explorer is now up to date. Keep in mind that the richlist is not live, and is refreshed every 12 hours.

[Velvet78]

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.

[Velvet78]

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.

[vella85]

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.

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.

[Velvet78]

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.

[AcidMiner]

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?

Free 1337 for playing Snake @ https://playforcrypto.com/register/xxxanonymous

[Velvet78]

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.

[marvin2550]

I am trying to move my coin out of yobit but they said I cannot withdraw my coins

[Velvet78]

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.

[fikihafana]

I am trying to move my coin out of yobit but they said I cannot withdraw my coins

Ya bro, a problem in yobit. Dont buy 133 coin in yobit. choose another exchange

[vella85]

I am trying to move my coin out of yobit but they said I cannot withdraw my coins

Ya bro, a problem in yobit. Dont buy 133 coin in yobit. choose another exchange

I totally agree as Yobit seem to do this all the time with many different crypto currencies and it does get annoying and frustrating because we want our coins in our wallets to stake but then we find out that when we want to withdraw we can't. I've had this happen many times to me in the past with Yobit and now I never use that exchange unless I have to. I recommend Cryptopia as an exchnage for 1337 coins as you can also buy 1337 coins with Doge, LTC, BTC and I believe XMR.

[bitmaster1x]

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...

C-cex is a strange one. I tried to get them to fix their API to match their web GUI in regards to minimum and they were like confused. It took a bunch of explaining for them to get it and when they did, they still didn't fix the problem. .... and every time they add coins the sites goes off-line. I told them their site can't be fully utilized in its current state.

Not sure what else to to say...lol

In regards to the bloat, I'm not concerned about the memory usage, but the rather the cpu cycle as the wallet becomes less responsive.

BTW: I've been a market maker for 1337 on cryptopia for a few weeks now.

[CaptainMAD]

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=LKVgSiT5c7wxHva8MJVh3tvgUv5ppu9sgZ

which 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 

This is EXACTLY what they did with DigiCube.   Kept putting the wallet in "Maintenance" and staking the wallet, then dumped the stakes and killed the market.   Set of crooks running an exchange.  I wouldn't advise ANYONE to hold funds in C-Cex.

[freebitcoins4u]

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...

C-cex is a strange one. I tried to get them to fix their API to match their web GUI in regards to minimum and they were like confused. It took a bunch of explaining for them to get it and when they did, they still didn't fix the problem. .... and every time they add coins the sites goes off-line. I told them their site can't be fully utilized in its current state.

Not sure what else to to say...lol

In regards to the bloat, I'm not concerned about the memory usage, but the rather the cpu cycle as the wallet becomes less responsive.

BTW: I've been a market maker for 1337 on cryptopia for a few weeks now.

what exactly have you done as a market maker?

[vella85]

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=LKVgSiT5c7wxHva8MJVh3tvgUv5ppu9sgZ

which 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 

This is EXACTLY what they did with DigiCube.   Kept putting the wallet in "Maintenance" and staking the wallet, then dumped the stakes and killed the market.   Set of crooks running an exchange.  I wouldn't advise ANYONE to hold funds in C-Cex.

Yeah I saw what happened to CUBE and I was very lucky to sell a couple of days before the massive dump that happened and like you said it killed the market. The same could be going on here which is sad because 1337 coin is a great coin with a hard working dev and strong community support. But hopefully when the new coin is released it will help, time will tell.

[logictense]

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#L26

and presstab is using here https://github.com/hyperstake/HyperStake/blob/master/src/checkpoints.cpp#L25

1337 doesnt have any https://github.com/Velvet78/1337/blob/master/src/checkpoints.cpp#L28

and..

Code:

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-L18

Also setting up new checkpoint server will help..
https://github.com/Velvet78/1337/blob/master/src/checkpoints.cpp#L353
This 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-L25


Cheers!

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

Is the bloat going to be taken out?

Nope blockchain bloat is an incurable disease and will progress till the end of coin's lifespan.