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
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 just to say there is more things to fix at craves current code.. 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. |
|
|
|
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.
You are so boring. At this moment return of ICM is most desired scenario here and you call it something to fix. you have funny scenarios, thats just you.. really think icm will come back? |
|
|
|
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
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 |
|
|
|
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.
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. |
|
|
|
|
any new fights or ideas here?
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
Let's be honest it impossible to mine right now on all your BNs when you got more then 8 and you're using 1 even powerful VPS.
1 BN mining uses 1GB Ram and 1 CPU core, I'm trying to use for some time 2 BNs mining on 2 core CPU with 2 GB Ram and 4Gb Swap, both cores are fully used, but still I don't see any 4.05 BCR fees incoming. (bitcredit-cli setgenerate true 1 , 1 core per 1 BN) this is cold BN on VPS
So I'm using also few home hot BNs wallets (not the same as these 2 on cold VPS) and these works, 4.05 BCR are incoming for every BN. I know that all should work on 1 machine but it would be too much expensive and we are not escaping from "backing hot air" this way ...
If in future banknode=1 will mean setgenerate true without giving any option, then we will be again backing a hot air, VPS sellers will be very happy instead of ASIC makers.
BTW. how it will work, Intel Atom core will be enough to start mining the same way as Intel i5 just giving smaller hashrate, how about roseberry ?
100 Pi2 Banknodes would be 20x more decentralised than almost any other PoW currency. As for hot air, yes it's not perfect, but right now DASH for example has about 80GH/s chundering away, which is what, equivalent to about 40000 Ti750's or something ludicrous? 40000 * 30W = 1.2 Megawatts. And that's not counting the rest of the system, all the less power-efficient AMD cards, CPUs etc - 3+ Megawatts is probably closer to the truth. Dog alone knows what the actual power consumption of the Bitcoin network is, ASICs or not I bet it's orders of magnitude worse than DASH. 100 Pi's at <1W each seems rather more sensible... BCR can beat every other PoW currency in actual decentralisation for the cost of running a couple of light bulbs. Think about that hideously expensive energy delta as money going into backing BCR instead.  And yes, because BNs will not be allowed to mine consecutive blocks, a low power ARM device would be just fine, there's no point wasting any more energy. money to vps or asics.. someone tell the solution burst tried one.. i think i have a idea that could work and costs no energy.. |
|
|
|
Almost forgot about this one. Anything going on, or is it just another meaningless chain roaming wild on the internet?
yes, you can call this one dead. |
|
|
|
Wallets bittrex is OFFLINE and my CRAVE did not reach the bittrex 999.99998 crave the following address:
C2JhqhRdqHFT1HSQYqoQ8VjKU3Sz4sFMcx Richela Pleas HELP ME
Sorry, your coins are lost. Just kidding!Why do you think so??? there your coins are, dont listen bullshit |
|
|
|
|
cant read a single letter from this ann
|
|
|
|
Niitassin Before you take a break contact bittrex and help them with the wallet CRAVE. Because we do not have access to the wallet at CRAVE. It is DISABLED Bittrex.
I agree. Making sure Bittrex is okay should be priority #1. Whats the current consensus? Are we rolling back to the old wallet? If someone can provide some guidance, i'll get everything back online here... thanks, richie@bittrex i will answer this one consensus is to revert code before oxything https://github.com/laptoptip/crave/tree/f6b61d2a730828eb4644be52fb0e050e6933c570but dev should pump the keys and version to that one. |
|
|
|
about alert keys, also bitcoin has them, but who holds the keys?
they say that they have a failsafe system if one of key holders will go mad.
what is that failsafe system, just cancelling alert by another holder?
I think the failsafe system is to ignore the alert. The purpose seems to push critical updates so I could see the alert showing up in the UI and debug.log with the option to shut it off with a command or crave.config setting. yes there is config optinon to ignore it.. but most people wont be able to do it(knowhow) |
|
|
|
|
about alert keys, also bitcoin has them, but who holds the keys?
they say that they have a failsafe system if one of key holders will go mad.
what is that failsafe system, just cancelling alert by another holder?
|
|
|
|
|
from console:

makekeypair

{
"PrivateKey" : "308201130201010420e62aa5c9c1f910ad9b0b8e2a1b1ccbb1f7a5fc6c5f03d3da603707610697b 385a081a53081a2020101302c06072a8648ce3d0101022100ffffffffffffffffffffffffffffff fffffffffffffffffffffffffefffffc2f300604010004010704410479be667ef9dcbbac55a0629 5ce870b07029bfcdb2dce28d959f2815b16f81798483ada7726a3c4655da4fbfc0e1108a8fd17b4 48a68554199c47d08ffb10d4b8022100fffffffffffffffffffffffffffffffebaaedce6af48a03 bbfd25e8cd0364141020101a144034200041cf40e6019ecfcf2f50ec953c1230c3acf6975eaeca1 4c373ee97d716a4d4b3606c0359c61f6bc4791aaa010229d3316b60194981e24f6c8cf968d13bbd 93120",
"PublicKey" : "041cf40e6019ecfcf2f50ec953c1230c3acf6975eaeca14c373ee97d716a4d4b3606c0359c61f6b c4791aaa010229d3316b60194981e24f6c8cf968d13bbd93120"
}
|
|
|
|
|
this is not the way. stay on crave and fix
this way no one will trust you.
|
|
|
|
So I probably need to ditch my new rc3 qt and use old qt to rejoin the larger block chain. But which one? oxy? or earlier one? Anyone got download link?
link some page behind here.. i downloaded old chain from zero, did not take a long. and you cant join old chain with rc3, its a mess now. i would use ICM dev wallet for now. that is uptodate with explorers. trades are in maintenance.. |
|
|
|
|
i have no idea..
but if you can make working release, just put it out and let people choose.(win current wallet crashes for me)
|
|
|
|
please answer my question about populating network with those faulty masternodes..
this can lead for free masternode money..
or will i test it my self?
that does not need big computing power since part of code needed is released lately..
quete of yours:
"Also if you have noticed, there's over 800 nodes running the old wallet version that just popped up out of nowhere."
we could do bigger population by easy script.
I did not say masternodes, they were simply nodes and the issue resolved itself when the nodes were banned. right now i cant even see if they are still online or not as they are incompatible take a deep look at masternode rules.. there may be a loop hole.. did you find the hole==? |
|
|
|
|
Show Posts
