dont worry griff - get well soon - best excuse ever 
Topic: ECCoin (ECC) Takeover by Trusted-Cryptos Team [Griffith] - page 3. (Read 91207 times)
dont worry griff - get well soon - best excuse ever 
alright guys. i know i said new wallet today. but ive been throwing up for most of the day. i had some swordfish last night. got food poisoning. it sucks
update of the new ecc wallet:
it will not be released this weekend. all rerlease dates as stated on the Griffith Code Section of the www.trustedcryptos.com will be delayed ONE WEEK.
Reason:
New wallet code base has some very inherent BAD problems and minor setbacks,
1. You WILL HAVE to resync. it will not read the old block index files and a resync is mandatory. because of this i will let some nodes do it first then paste the block index files so that everyone else doesnt have to wait for it.
2. there is a very bad problem with checking for proof of work blocks ||| aka, it doesnt work. it errors out and the only way i am getting it to sync right now for PoS testing is i am ignoring several PoW checkpoints.
for obvious reasons i want to address and fix that problem before i release the new wallet.
3. incomplete testing on whether or not the new code actually fixes what i thought it would fix. so i need to sync a wallet first and test the opening times before anything else. if the opening time isnt improved there is something else wrong and the new wallet wont do anything different anyway,
4. need to test that it can read the wallet.dat files. if it cant. then we have an obvious problem.
5. code base is a mess. a lot of hack fixes atm and i feel like the code is being held together by duct-tape. id prefer not to release it like that.
TL;DR code base messy, 2 Major bugs, new wallet will be delayed 1 week
considering ive done nothing for the past 72 hours besides work on this and sleep. i dont think a week is too long to ask (i do have school assignments during the week otherwise id say 3 days)
it will not be released this weekend. all rerlease dates as stated on the Griffith Code Section of the www.trustedcryptos.com will be delayed ONE WEEK.
Reason:
New wallet code base has some very inherent BAD problems and minor setbacks,
1. You WILL HAVE to resync. it will not read the old block index files and a resync is mandatory. because of this i will let some nodes do it first then paste the block index files so that everyone else doesnt have to wait for it.
2. there is a very bad problem with checking for proof of work blocks ||| aka, it doesnt work. it errors out and the only way i am getting it to sync right now for PoS testing is i am ignoring several PoW checkpoints.
for obvious reasons i want to address and fix that problem before i release the new wallet.
3. incomplete testing on whether or not the new code actually fixes what i thought it would fix. so i need to sync a wallet first and test the opening times before anything else. if the opening time isnt improved there is something else wrong and the new wallet wont do anything different anyway,
4. need to test that it can read the wallet.dat files. if it cant. then we have an obvious problem.
5. code base is a mess. a lot of hack fixes atm and i feel like the code is being held together by duct-tape. id prefer not to release it like that.
TL;DR code base messy, 2 Major bugs, new wallet will be delayed 1 week
considering ive done nothing for the past 72 hours besides work on this and sleep. i dont think a week is too long to ask (i do have school assignments during the week otherwise id say 3 days)
Why do not we start with a new blockchain instead of a full re-sync? It's would accelerate the wallet launch time, and would reduce the synchronization time and the size of the chain.
Actually, I'm starting to think that a new chain becomes necessary every ~2 years of cryptocurrency life.
no need. you will have the option to sync by downloading an almost complete blockchain, i will be providing a link for you when everythign is ready. also, i believe i have found a way for the wallet to start without loading every block into memory. this means only the last 50,000 blocks will be loaded and the load time for block index (based on testing) averages about 29 seconds when i do it this way, which is a large improvement from the multiple minutes that we are currently dealing with. essentially im making checkpoint loading blocks.
announcement: the new wallet is going to have a DECREASE in the amount of features. There will no longer be: an in wallet block explorer, in wallet IRC chat, or automatic donations from staking (although this will come back later)
we are on track for a release this friday (tomorrow) (assuming something doesnt go crazy wrong in that time)
update of the new ecc wallet:
it will not be released this weekend. all rerlease dates as stated on the Griffith Code Section of the www.trustedcryptos.com will be delayed ONE WEEK.
Reason:
New wallet code base has some very inherent BAD problems and minor setbacks,
1. You WILL HAVE to resync. it will not read the old block index files and a resync is mandatory. because of this i will let some nodes do it first then paste the block index files so that everyone else doesnt have to wait for it.
2. there is a very bad problem with checking for proof of work blocks ||| aka, it doesnt work. it errors out and the only way i am getting it to sync right now for PoS testing is i am ignoring several PoW checkpoints.
for obvious reasons i want to address and fix that problem before i release the new wallet.
3. incomplete testing on whether or not the new code actually fixes what i thought it would fix. so i need to sync a wallet first and test the opening times before anything else. if the opening time isnt improved there is something else wrong and the new wallet wont do anything different anyway,
4. need to test that it can read the wallet.dat files. if it cant. then we have an obvious problem.
5. code base is a mess. a lot of hack fixes atm and i feel like the code is being held together by duct-tape. id prefer not to release it like that.
TL;DR code base messy, 2 Major bugs, new wallet will be delayed 1 week
considering ive done nothing for the past 72 hours besides work on this and sleep. i dont think a week is too long to ask (i do have school assignments during the week otherwise id say 3 days)
it will not be released this weekend. all rerlease dates as stated on the Griffith Code Section of the www.trustedcryptos.com will be delayed ONE WEEK.
Reason:
New wallet code base has some very inherent BAD problems and minor setbacks,
1. You WILL HAVE to resync. it will not read the old block index files and a resync is mandatory. because of this i will let some nodes do it first then paste the block index files so that everyone else doesnt have to wait for it.
2. there is a very bad problem with checking for proof of work blocks ||| aka, it doesnt work. it errors out and the only way i am getting it to sync right now for PoS testing is i am ignoring several PoW checkpoints.
for obvious reasons i want to address and fix that problem before i release the new wallet.
3. incomplete testing on whether or not the new code actually fixes what i thought it would fix. so i need to sync a wallet first and test the opening times before anything else. if the opening time isnt improved there is something else wrong and the new wallet wont do anything different anyway,
4. need to test that it can read the wallet.dat files. if it cant. then we have an obvious problem.
5. code base is a mess. a lot of hack fixes atm and i feel like the code is being held together by duct-tape. id prefer not to release it like that.
TL;DR code base messy, 2 Major bugs, new wallet will be delayed 1 week
considering ive done nothing for the past 72 hours besides work on this and sleep. i dont think a week is too long to ask (i do have school assignments during the week otherwise id say 3 days)
Why do not we start with a new blockchain instead of a full re-sync? It's would accelerate the wallet launch time, and would reduce the synchronization time and the size of the chain.
Actually, I'm starting to think that a new chain becomes necessary every ~2 years of cryptocurrency life.
My wallet show error message "Checkpoint is too old". But wallet full synced (latest version).
Don't pay attention to this message. It will be fixed in the next release of the wallet.
My wallet show error message "Checkpoint is too old". But wallet full synced (latest version).
Don't pay attention to this message. It will be fixed in the next release of the wallet.
My wallet show error message "Checkpoint is too old". But wallet full synced (latest version).
"making a new one to prepare for a transition into a new phase of crypto coins". But two days of ECC prices are still falling!
I've said it before and, I'll say it again, don't worry so much about the price, especially right now. The market will make a correction when it's ready...
"making a new one to prepare for a transition into a new phase of crypto coins". But two days of ECC prices are still falling!
We have been going up for a month now... and the big jump still has to come starting with the new wallet
"making a new one to prepare for a transition into a new phase of crypto coins". But two days of ECC prices are still falling!
New wallet is necessary, the old wallet are always checkin, dont staking 
the old wallet works perfectly fine. im just making a new one to prepare for a transition into a new phase of crypto coins. an believe me. after working with this new wallet. i know how coins work forwards, backwards and every which way
old wallet is good but slow
This is a good news, is big gospel for ECC supporters 
New wallet is necessary, the old wallet are always checkin, dont staking
the old wallet works perfectly fine. im just making a new one to prepare for a transition into a new phase of crypto coins. an believe me. after working with this new wallet. i know how coins work forwards, backwards and every which way
New wallet is necessary, the old wallet are always checkin, dont staking
i contacted blockexplorers to fix the rich list last night before i went to bed.
Have you got the answer? Unfortunately, it doesn't work.i think i posted eariler.... but they said it was still compiling the richlist
Must be still compiling a lot of transactions : the latest one on my main address, according to the explorer, is 1 year ago !!
i contacted blockexplorers to fix the rich list last night before i went to bed.
Have you got the answer? Unfortunately, it doesn't work.i think i posted eariler.... but they said it was still compiling the richlist
i contacted blockexplorers to fix the rich list last night before i went to bed.
Have you got the answer? Unfortunately, it doesn't work.i think i posted eariler.... but they said it was still compiling the richlist
i contacted blockexplorers to fix the rich list last night before i went to bed.
Have you got the answer? Unfortunately, it doesn't work. update of the new ecc wallet:
it will not be released this weekend. all rerlease dates as stated on the Griffith Code Section of the www.trustedcryptos.com will be delayed ONE WEEK.
Griffith
Thanks for the update, we really appreciate everything you have done so far.
School is important as well (I don't wanna sound like an old guy, but it just is...)
Beside that, I'd rather have a decent wallet next weekend, than a quick, messy fix right now, peopel will understand that...
Regards
Goldmaxx
it will not be released this weekend. all rerlease dates as stated on the Griffith Code Section of the www.trustedcryptos.com will be delayed ONE WEEK.
Griffith
Thanks for the update, we really appreciate everything you have done so far.
School is important as well (I don't wanna sound like an old guy, but it just is...)
Beside that, I'd rather have a decent wallet next weekend, than a quick, messy fix right now, peopel will understand that...
Regards
Goldmaxx
Agree on that 100% !
update of the new ecc wallet:
it will not be released this weekend. all rerlease dates as stated on the Griffith Code Section of the www.trustedcryptos.com will be delayed ONE WEEK.
Reason:
New wallet code base has some very inherent BAD problems and minor setbacks,
1. You WILL HAVE to resync. it will not read the old block index files and a resync is mandatory. because of this i will let some nodes do it first then paste the block index files so that everyone else doesnt have to wait for it.
2. there is a very bad problem with checking for proof of work blocks ||| aka, it doesnt work. it errors out and the only way i am getting it to sync right now for PoS testing is i am ignoring several PoW checkpoints.
for obvious reasons i want to address and fix that problem before i release the new wallet.
3. incomplete testing on whether or not the new code actually fixes what i thought it would fix. so i need to sync a wallet first and test the opening times before anything else. if the opening time isnt improved there is something else wrong and the new wallet wont do anything different anyway,
4. need to test that it can read the wallet.dat files. if it cant. then we have an obvious problem.
5. code base is a mess. a lot of hack fixes atm and i feel like the code is being held together by duct-tape. id prefer not to release it like that.
TL;DR code base messy, 2 Major bugs, new wallet will be delayed 1 week
considering ive done nothing for the past 72 hours besides work on this and sleep. i dont think a week is too long to ask (i do have school assignments during the week otherwise id say 3 days)
it will not be released this weekend. all rerlease dates as stated on the Griffith Code Section of the www.trustedcryptos.com will be delayed ONE WEEK.
Reason:
New wallet code base has some very inherent BAD problems and minor setbacks,
1. You WILL HAVE to resync. it will not read the old block index files and a resync is mandatory. because of this i will let some nodes do it first then paste the block index files so that everyone else doesnt have to wait for it.
2. there is a very bad problem with checking for proof of work blocks ||| aka, it doesnt work. it errors out and the only way i am getting it to sync right now for PoS testing is i am ignoring several PoW checkpoints.
for obvious reasons i want to address and fix that problem before i release the new wallet.
3. incomplete testing on whether or not the new code actually fixes what i thought it would fix. so i need to sync a wallet first and test the opening times before anything else. if the opening time isnt improved there is something else wrong and the new wallet wont do anything different anyway,
4. need to test that it can read the wallet.dat files. if it cant. then we have an obvious problem.
5. code base is a mess. a lot of hack fixes atm and i feel like the code is being held together by duct-tape. id prefer not to release it like that.
TL;DR code base messy, 2 Major bugs, new wallet will be delayed 1 week
considering ive done nothing for the past 72 hours besides work on this and sleep. i dont think a week is too long to ask (i do have school assignments during the week otherwise id say 3 days)
Griffith
Thanks for the update, we really appreciate everything you have done so far.
School is important as well (I don't wanna sound like an old guy, but it just is...)
Beside that, I'd rather have a decent wallet next weekend, than a quick, messy fix right now, peopel will understand that...
Regards
Goldmaxx
Jump to: