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.
Topic: [ANN] 1337 [MANDATORY UPDATE] 41.78% APR| POS ONLY - page 101. (Read 259582 times)
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
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.
I believe my explorer is now up to date. Keep in mind that the richlist is not live, and is refreshed every 12 hours.
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
Good to see you back Velvet 
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..
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!
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
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"
}
{
"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?
Good to see you back Velvet
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..
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!
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
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"
}
{
"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 
Good to see you back Velvet
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..
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!
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
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"
}
{
"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!
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
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"
}
{
"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
ok im almost done with adding all 3 fixes but got stuck with the last part in src/test/key_test.cpp
@desynct please take a look at https://github.com/peercoin/peercoin/blob/9ab59647e58aa849a2896c9213cfb5ce8a6a7bfb/src/test/key_tests.cpp#L147
where can i find the values for the different ParseHex lines?
@desynct please take a look at https://github.com/peercoin/peercoin/blob/9ab59647e58aa849a2896c9213cfb5ce8a6a7bfb/src/test/key_tests.cpp#L147
where can i find the values for the different ParseHex lines?
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
ok im almost done with adding all 3 fixes but got stuck with the last part in src/test/key_test.cpp
@desynct please take a look at https://github.com/peercoin/peercoin/blob/9ab59647e58aa849a2896c9213cfb5ce8a6a7bfb/src/test/key_tests.cpp#L147
where can i find the values for the different ParseHex lines?
@desynct please take a look at https://github.com/peercoin/peercoin/blob/9ab59647e58aa849a2896c9213cfb5ce8a6a7bfb/src/test/key_tests.cpp#L147
where can i find the values for the different ParseHex lines?
Still blocking
Code:
{
"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" : ""
}
"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
Still blocking
Code:
{
"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" : ""
}
"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" : ""
}
I will test soon. (but it will the last try for me)
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.
that shit is rare, prolly only intentional chain hack (read ppc blog),
selectively affects Linux 64 clients - that's why the supposition came to mind.
the longer the chain - the more risk of encounter, may never happen at all.
i tried to find an irregular length descriptor around blocks at which anemol got stuck to no luck,
so maybe absolutely not related, though that fix is necessary anyways
i implemented the fix from https://github.com/peercoin/peercoin/commit/9b40cd5b12b518a3a40d39016f30955a20ea0bf5 and it compiled fine and its synching BUT i was digging in the ppc repo and found 2 additional fixes:
https://github.com/peercoin/peercoin/pull/116/commits/f301a3add0aa39c3651dcc1fbeaf49af368c38d7
https://github.com/peercoin/peercoin/pull/117
seems to me those need to be implemented too to prevent forks? i checked hyp's repo an noticed presstab didnt add those
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.
that shit is rare, prolly only intentional chain hack (read ppc blog),
selectively affects Linux 64 clients - that's why the supposition came to mind.
the longer the chain - the more risk of encounter, may never happen at all.
i tried to find an irregular length descriptor around blocks at which anemol got stuck to no luck,
so maybe absolutely not related, though that fix is necessary anyways
i implemented the fix from https://github.com/peercoin/peercoin/commit/9b40cd5b12b518a3a40d39016f30955a20ea0bf5 and it compiled fine and its synching BUT i was digging in the ppc repo and found 2 additional fixes:
https://github.com/peercoin/peercoin/pull/116/commits/f301a3add0aa39c3651dcc1fbeaf49af368c38d7
https://github.com/peercoin/peercoin/pull/117
seems to me those need to be implemented too to prevent forks? i checked hyp's repo an noticed presstab didnt add those
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.
any news on c-cex fix?
Dear 1337 investors - Developers,
We would love to announce that your coin is currently taking the 10th place in PumpMyCoin Community public votes.
Wish you all best and good luck.
sincerely
PumpMyCoin Team
We Pump But Never Dump
www.pumpmycoin.com
We would love to announce that your coin is currently taking the 10th place in PumpMyCoin Community public votes.
Wish you all best and good luck.
sincerely
PumpMyCoin Team
We Pump But Never Dump
www.pumpmycoin.com
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.
I've seen this problem with lots of coins lately..
Banzai-san, i don't like minimalistic "Verify" in 1337, how about you ?
https://github.com/Velvet78/1337/blob/master/src/key.cpp#L392
compared to:
https://github.com/hyperstake/HyperStake/blob/master/src/key.cpp#L377
history:
https://github.com/peercoin/peercoin/issues/100
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..
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.
I've seen this problem with lots of coins lately..
Banzai-san, i don't like minimalistic "Verify" in 1337, how about you ?
https://github.com/Velvet78/1337/blob/master/src/key.cpp#L392
compared to:
https://github.com/hyperstake/HyperStake/blob/master/src/key.cpp#L377
history:
https://github.com/peercoin/peercoin/issues/100
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)...
Anything plans for 1337 coin in 2017 I have a good amount been staking it will be nice to see what's in store
hopefully we could swap them to the new coin which will have a greater value.
i also look for bitcoin price to fall because it will push all other altcoins price up.
Jump to: