We've got a new takeover thread.
This thread's gonna be locked.
Enjoy a new devs......I HOPE
https://bitcointalksearch.org/topic/ann-crave-1st-pos-masternodes-ibm-developers-urge-market-testnet-in-month-1221130
Topic: CRAVE-Afterparty............................or not YET? (Read 9802 times)
crave is far from enthusiasts
Why?Dont trust Crave?
crave is far from enthusiasts
now i am lost witch one is the good thread 
just to be sure use all of them, this is a mess!
lets mess up it more..
and no one in control, exchanges still down..
hell, lets start some more threads for shits and giggles! jk
now i am lost witch one is the good thread
just to be sure use all of them, this is a mess!
lets mess up it more..
and no one in control, exchanges still down..
thanks
I didn't see any activity in other so i think i will stick to this one
lol
I didn't see any activity in other so i think i will stick to this one
lol
now i am lost witch one is the good thread
This one isn't bad.You're good here
now i am lost witch one is the good thread
yes you can stop the network holding the keys. but that can be by passed with config file.
people who compile their own client can remove(change) the pubkey, and have clients safe
Because my 5 min of googling didn't come up with anything, how exactly is this done? or is that something better discussed in private? Why don't we just change the key(s) and suggest everyone use the new wallet? Or at least get a set of core people using a wallet with new/no keys just to keep things moving if there is an issue?
yes, this should be done.
i think this is no private info.
or do you want he to send this:
sendalert icm_gone_mad! (privkey) 0 70000 5000 10000 1
[quote author=cisahasa link=topic=1145727.msg12474247#msg12474247 date=1442765442
yes you can stop the network holding the keys. but that can be by passed with config file.
people who compile their own client can remove(change) the pubkey, and have clients safe
[/quote]
Because my 5 min of googling didn't come up with anything, how exactly is this done? or is that something better discussed in private? Why don't we just change the key(s) and suggest everyone use the new wallet? Or at least get a set of core people using a wallet with new/no keys just to keep things moving if there is an issue?
yes you can stop the network holding the keys. but that can be by passed with config file.
people who compile their own client can remove(change) the pubkey, and have clients safe
[/quote]
Because my 5 min of googling didn't come up with anything, how exactly is this done? or is that something better discussed in private? Why don't we just change the key(s) and suggest everyone use the new wallet? Or at least get a set of core people using a wallet with new/no keys just to keep things moving if there is an issue?
Someone bring me up to date on why not having the alert keys is a huge issue? I thought it just did alerts? Is there an embedded kill switch?
Also, whats so hard about just making a new set of keys and recompiling?
JJ
Also, whats so hard about just making a new set of keys and recompiling?
JJ
I can fork the source with a new alert key, if that's the issue. Just would need someone to build it, as I don't have a machine setup to build wallets right now.
i would ask if cryptovote wants to help.. he can do all needed things.
yes you can stop the network holding the keys. but that can be by passed with config file.
people who compile their own client can remove(change) the pubkey, and have clients safe
Thank you guys
some files are not uptodate and safe.
niitassin did not find those and did not fix it.
i think there is only one dev who i can name who knows what is the issue...
he is playing with similar coin, way more safe one.
but his coins has issues of his own, not related to crave.
(that is not 8-bit dev who am i talkning about)
other good devs seems to be not so interested about masternode code,
and i see the reason why not.
Someone bring me up to date on why not having the alert keys is a huge issue? I thought it just did alerts? Is there an embedded kill switch?
Also, whats so hard about just making a new set of keys and recompiling?
JJ
Also, whats so hard about just making a new set of keys and recompiling?
JJ
I can fork the source with a new alert key, if that's the issue. Just would need someone to build it, as I don't have a machine setup to build wallets right now.
i would ask if cryptovote wants to help.. he can do all needed things.
yes you can stop the network holding the keys. but that can be by passed with config file.
people who compile their own client can remove(change) the pubkey, and have clients safe
Thank you guys
Someone bring me up to date on why not having the alert keys is a huge issue? I thought it just did alerts? Is there an embedded kill switch?
Also, whats so hard about just making a new set of keys and recompiling?
JJ
Also, whats so hard about just making a new set of keys and recompiling?
JJ
I can fork the source with a new alert key, if that's the issue. Just would need someone to build it, as I don't have a machine setup to build wallets right now.
i would ask if cryptovote wants to help.. he can do all needed things.
yes you can stop the network holding the keys. but that can be by passed with config file.
people who compile their own client can remove(change) the pubkey, and have clients safe
Someone bring me up to date on why not having the alert keys is a huge issue? I thought it just did alerts? Is there an embedded kill switch?
Also, whats so hard about just making a new set of keys and recompiling?
JJ
Also, whats so hard about just making a new set of keys and recompiling?
JJ
I can fork the source with a new alert key, if that's the issue. Just would need someone to build it, as I don't have a machine setup to build wallets right now.
Someone bring me up to date on why not having the alert keys is a huge issue? I thought it just did alerts? Is there an embedded kill switch?
Also, whats so hard about just making a new set of keys and recompiling?
JJ
Also, whats so hard about just making a new set of keys and recompiling?
JJ
you are now ignoring some safety related things if continue with any current wallets..
icm can take this down if he wants.
no one has fixed that.
icm can take this down if he wants.
no one has fixed that.
May be but niitassin will destroy Crave for sure if we follow him any longer.That's for sure
agree, but you guys need a dev.
niitassin oxything was his last move, good try to kill a coin. so many things gone wrong there.
Where is the real thread?
The very first one has been locked by ICM (there's nothing we can do)
This is second one created by ICM: https://bitcointalk.org/index.php?topic=1110730.900
This is third one created by me: https://bitcointalk.org/index.php?topic=1145727.new#new
This is fourth one created by niitassin https://bitcointalksearch.org/topic/--1155824
That's it
you are now ignoring some safety related things if continue with any current wallets..
icm can take this down if he wants.
no one has fixed that.
icm can take this down if he wants.
no one has fixed that.
May be but niitassin will destroy Crave for sure if we follow him any longer.That's for sure
you are now ignoring some safety related things if continue with any current wallets..
icm can take this down if he wants.
no one has fixed that.
icm can take this down if he wants.
no one has fixed that.
Jump to: