The truth is this coin presently does not have any anonymization features.
You forgot to mention you can connect via Tor, but depends on your confidence of Tor I suppose. From op: Hidden service seed node on virtual port 30108:
d5jxp6ajbjbrpdhd.onion
If you have TOR you can either connect only to tor nodes:
./crave-qt -onlynet=Tor -listen=0 -irc=0 -proxy=127.0.0.1:9050 -addnode=d5jxp6ajbjbrpdhd.onion:30108
Or connect to it as well as normal nodes:
./crave-qt -proxy=127.0.0.1:9050 -tor=127.0.0.1:9050 -addnode=d5jxp6ajbjbrpdhd.onion:30108 |
|
|
|
That is just ignorance. Arch is clearly one of the best investments out there right now and there is really no rational argument to the contrary that I have seen.
Everyone thinks their coin is "the best". Problem is you all are idiots for supporting so many coins. This dev or one of the devs also works on vericoin. Gov't is behind creating tons of coins in an effort to divide us all and the cryptocurrency community in general. Stop falling for it. |
|
|
|
pump please  where is dev  you missed the train and now you have to wait till 2016 for next pump, so buy at cheap price and wait for next pump and become rich with this trick  Why does it seem pumpers are posting back in here again... hmmmm |
|
|
|
They'll be back in due time when ICM delivers and we realize all the other promises on these ninja coins are jokes.
Until then, enjoy cheaper priced crave!! |
|
|
|
Blackhat? This coin will probably steal from your other wallets |
|
|
|
Guys that is incorrect. You can't burn CRAVE for BLUR after the end of the burn period. We could possibly fork darkpoold to push the burn period out further.
That seems a bit strange to me, if it is blur that is supposed to be used for the markets, this takes away from the value proposition of crave. I would think that we should be able to burn crave for blur at anytime. Since this would mean people are expected to burn their crave in the first month of such a speculative project, considering that we can not even sell blur at this point, this is almost the same as burning money, we can not expect people to do this, it does not make sense for the long term or the present. I will say it here, I think we should be able to burn CRAVE for BLUR for the entire lifetime of this coin. It is not supposed to be used for the markets. BLUR is for crypto asssets. So we can buy things on the markets using crave instead? Only assets use blur, but not products? |
|
|
|
The bot on bittrex controls the price, we need to get rid of it. To whoever is running it, you are scum of the earth.
I wish a group of somewhat trusting people could team up to combat it But in markets it sucks |
|
|
|
Can someone who successfully sync'd from downloading, please upload their peers.dat for me to try?
Thanks
try adding a Crave.conf file with these nodes addnode=104.131.14.111 addnode=104.131.151.90 ... <snip> Thanks fonz !! |
|
|
|
|
Can someone who successfully sync'd from downloading, please upload their peers.dat for me to try?
Thanks
|
|
|
|
Half of all coins used for nodes i presume. 500 coins per masternode and over 500 mn should be more than half the supply, someone correct me if im wrong, That sounds about right |
|
|
|
you wont get enough weight to find a block with .1 of a coin... 1 coin will only ever be worth 1 in weight I believe
yeah just want to see if it gets any weight at all Anybody got something like that from masternode debug console?? CActiveMasternode::Dseep() - SendDarkSendElectionEntryPing vin = CTxIn(COutPoint(39d09e8a47, 1), scriptSig=) IRC got join GetSpork::Unknown Spork -1866429697 CheckBlock() : skipping transaction locking checks CheckBlock() : skipping masternode payment checks GetSpork::Unknown Spork -1866429697 CheckBlock() : skipping transaction locking checks CheckBlock() : skipping masternode payment checks What da f ..... 26 hours without payment from active masternode !!!!!!!!!!!!!!! SOMETHING MUST BE WROOOOOOOOOOOOOOOOOOOOONG I posted those same errors, but nobody responds about them ... yet |
|
|
|
|
Looks like just a plain coin, in terms of features and use.
Anything extra planned for it?
|
|
|
|
|
why does it seem like -reindex doesn't do anything
don't most coins have that?
|
|
|
|
Getting this when trying to compile daemon with latest secp256k1 installed: key.cpp:729:106: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_pubkey_tweak_add(const secp256k1_context_t*, unsigned char*, int, const unsigned char*)’
bool ret = secp256k1_ec_pubkey_tweak_add((unsigned char*)pubkeyChild.begin(), pubkeyChild.size(), out);
^
make: *** [obj/key.o] Error 1
I'm assuming because as was mentioned, crave daemon does not currently support latest secp256k1 ? Had to do this to get it to actually reset/rollback and successfully compile: git clone https://github.com/bitcoin/secp256k1
cd secp256k1
git reset a0d3b8
git add .
git reset --hard
./autogen.sh
./configure
make
sudo make install
cd ..
sudo ldconfig
cd crave/src
make -f makefile.unix USE_UPNP=
strip craved Thanks rocoro. I used the following to build the QT version. It worked like a charm. git clone https://github.com/bitcoin/secp256k1
cd secp256k1
git reset a0d3b8
git add .
git reset --hard
./autogen.sh
./configure
make
sudo make install
cd ..
sudo ldconfig
cd crave
qmake && make USE_UPNP=
If you want to use more cpu cores change the last line to: qmake && make -j X USE_UPNP= where X is the # of cores to use, so -j 4 would use 4 cores. One thing I had to do for QT version was change your last line... Should be: qmake "USE_UPNP=-" && make Otherwise during make it was still looking for miniupnp... had to tell it to not use UPNP during qmake step, not during make I don't use UPNP but for others if you installed miniupnp it should be fine. Just telling what worked for me.. thanks |
|
|
|
Thanks rocoro. I used the following to build the QT version. It worked like a charm.
Welcome...! did the qt version sync ok for you ? Or did it stick at 32712 |
|
|
|
ok i downloaded win wallet and im stuck at that 32712 block..how to fast fix this...repairwallet says everything is ok..but obviously it isnt :-P
What a surprise ... Keep closing the wallet and trying again, sometimes you can get past it that way. |
|
|
|
|
OUR FIGHT IS NOT AGAINST EACH OTHER.
THE FIGHT IS AGAINST FIAT.
BUY AND OWN MULTIPLE DIFFERENT COINS.
AND GET FUCKING ALONG !!!
|
|
|
|
I'm working on a patch to try to skip the check at block 32712...
so at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
I have the "block 32713 problem" with the last update All of you guys saying you are stuck at this block, isn't it something to do with the secp256k1 update? It won't compile with latest secp256k1, but it does compile fine if you roll back Some people are not even compiling and being stuck at that block So I don't think its a problem with secp256k1 I updated my wallet and I always sync fine with the last version of secp256k1 Did you compile with latest secp256k1 ? Did you patch key.cpp? No, I did not compile with the latest version. I installed the version before the current release and it compiles and works fine.. Ok, I'll try that. |
|
|
|
I'm working on a patch to try to skip the check at block 3712...
so at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
I have the "block 32713 problem" with the last update All of you guys saying you are stuck at this block, isn't it something to do with the secp256k1 update? It won't compile with latest secp256k1, but it does compile fine if you roll back Some people are not even compiling and being stuck at that block So I don't think its a problem with secp256k1 I updated my wallet and I always sync fine with the last version of secp256k1 Did you compile with latest secp256k1 ? Did you patch key.cpp? |
|
|
|
i have run 10 nodes and have no error what is the error?
tail -f debug.log and look at the messages about spork what has spork error got to do with anything spork used for going on different chain without doing anything to normal blockchain what is the actual error I think they were referring to this: GetSpork::Unkown Spork CheckBlock() : skipping transaction locking checks CheckBlock() : skipping masternode payment checks |
|
|
|
|
Show Posts
