https://github.com/industrialcoinmagic/crave/blob/75f4b3d5fe3cd0816b91721cf01b2ea6f520fec0/src/stealth.h
Topic: [ANN] CRAVE 1st POS Masternodes | Dark Assets | I2P | Market =Embrace The Dark= - page 180. (Read 826716 times)
April 16, 2015, 12:06:38 PM
LOL your Developer has gone through and removed hundreds of references to DRK and SDC in the GitHub, why not give credit where credit is due.. And Emilioman you love to call SDC trash.. yet Crave has used plenty of code from the project... does that make Crave trash then? Both Drk and SDC are open source projects so its a bit weird/SCAMMISH that the dev wants to hide the fact that most of the crave code has been forked from decent projects that have been around for a while and that have good devs, or even give any credit where credit is due.
https://github.com/industrialcoinmagic/crave/blob/75f4b3d5fe3cd0816b91721cf01b2ea6f520fec0/src/stealth.h
https://github.com/industrialcoinmagic/crave/blob/75f4b3d5fe3cd0816b91721cf01b2ea6f520fec0/src/stealth.h
April 16, 2015, 11:54:58 AM
I've got no issues at all.
No sync problems (always downloaded whole blockchain from the beginning)
No stake problems (works like a charm for me).
I don't use any node,I don't use crave.conf
And one more time:do NOT talk to SDC/DASH trolls and losers
Well ..If you didn't use crave.conf ,so..what you're using.Share with us.Any idea will be great .Is that mean that you doing only stake ??Reason why I'm asking ,because I'm very close to shoot off all my nodes and change only for stake.Thank youNo sync problems (always downloaded whole blockchain from the beginning)
No stake problems (works like a charm for me).
I don't use any node,I don't use crave.conf
And one more time:do NOT talk to SDC/DASH trolls and losers
Yes,I've never created crave.conf
Yes,I only stake (I've got almost 11k Crave so it's alright for me-I'm too noob to create MNs because I don't know how to open the bloody 9999 port on my router
Thank you but I don't know how to open port 9999 on my router.
Even if I do it by guide for my ASUS DSL-N14U and check it online it says port is closed.
So because I'm noob about it I decided just to stake.
April 16, 2015, 11:46:56 AM
Emilioman you really are retarded..
lov u pookielax31 aka Mr. Boh on twitter
you make me more rich with your fudstorm and dump.
I bought more than 30 btc under 100k again.
This coin is real, this community is amazing and you and your dirty racist prejudiced shadowtrash community know it
April 16, 2015, 11:42:19 AM
sorry to backtrack.
BLUR 30 Days period only! Started March 28th at block 17,000. Ends at block 60,200. we are close to block 40,000 meaning over half the Burn period has gone by. At this rate expect the blur Burn period to end on April 28th or 29th. depending on blockchain speed.
https://github.com/industrialcoinmagic/darkpoold/blob/master/lib/burn.py#L75
https://github.com/industrialcoinmagic/darkpoold/blob/master/lib/config.py#L72
Red text showing BURN_START_MAINNET = BURN_START_MAINNET_TESTCOIN = BLOCK_FIRST_MAINNET_TESTCOIN = 17000 which is when burn period started.
also showing BURN_END_MAINNET = BURN_START_MAINNET + 43200
where burn start mainnet = 17000
therefore as we can see the ability to burn crave will end close to the end of this month at block 60200
There we may now put the questions to rest
BLUR 30 Days period only! Started March 28th at block 17,000. Ends at block 60,200. we are close to block 40,000 meaning over half the Burn period has gone by. At this rate expect the blur Burn period to end on April 28th or 29th. depending on blockchain speed.
https://github.com/industrialcoinmagic/darkpoold/blob/master/lib/burn.py#L75
Quote
total_time = config.BURN_END - config.BURN_START
partial_time = config.BURN_END - tx['block_index']
multiplier = config.BURN_MULTIPLIER * (1 + (.5 * Fraction(partial_time, total_time)))
earned = round(burned * multiplier)
above is showing the burn total time is based on a start and an end. and also that its a decreasing reward from start to finish.partial_time = config.BURN_END - tx['block_index']
multiplier = config.BURN_MULTIPLIER * (1 + (.5 * Fraction(partial_time, total_time)))
earned = round(burned * multiplier)
https://github.com/industrialcoinmagic/darkpoold/blob/master/lib/config.py#L72
Quote
BLOCK_FIRST_MAINNET_TESTCOIN = 17000
BURN_START_MAINNET_TESTCOIN = BLOCK_FIRST_MAINNET_TESTCOIN
BURN_END_MAINNET_TESTCOIN = 26280000 # Fifty years, at 1 minute per block.
BLOCK_FIRST_MAINNET = BLOCK_FIRST_MAINNET_TESTCOIN
BURN_START_MAINNET = BURN_START_MAINNET_TESTCOIN
BURN_END_MAINNET = BURN_START_MAINNET + 30*24*60 # 30 days burn period with 1 min target time per block.
MAX_BURN_BY_ADDRESS = 1000 * UNIT # 1K CRAVE.
BURN_MULTIPLIER = 5 # from 7.5 to 5 BLUR per 1 CRAVE.
Blue text is showing the base rate of blur awarded per cravecoin burned. It is subject to the first quotes BURN_MULTIPLIER, rewarding early burners by a maximum of 2.5 extra blur per crave burned. (hint not many got burned in the first week or two.)BURN_START_MAINNET_TESTCOIN = BLOCK_FIRST_MAINNET_TESTCOIN
BURN_END_MAINNET_TESTCOIN = 26280000 # Fifty years, at 1 minute per block.
BLOCK_FIRST_MAINNET = BLOCK_FIRST_MAINNET_TESTCOIN
BURN_START_MAINNET = BURN_START_MAINNET_TESTCOIN
BURN_END_MAINNET = BURN_START_MAINNET + 30*24*60 # 30 days burn period with 1 min target time per block.
MAX_BURN_BY_ADDRESS = 1000 * UNIT # 1K CRAVE.
BURN_MULTIPLIER = 5 # from 7.5 to 5 BLUR per 1 CRAVE.
Red text showing BURN_START_MAINNET = BURN_START_MAINNET_TESTCOIN = BLOCK_FIRST_MAINNET_TESTCOIN = 17000 which is when burn period started.
also showing BURN_END_MAINNET = BURN_START_MAINNET + 43200
where burn start mainnet = 17000
therefore as we can see the ability to burn crave will end close to the end of this month at block 60200
There we may now put the questions to rest
April 16, 2015, 11:41:32 AM
i would try the workaround like any other coin...
Backup you older wwallet.dat sync with a new one then relace it with your backup. Possible run repairwallet. ..
Backup you older wwallet.dat sync with a new one then relace it with your backup. Possible run repairwallet. ..
This worked for me yesterday.
April 16, 2015, 11:17:34 AM
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 updateso at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
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
Did you compile with latest secp256k1 ? Did you patch key.cpp?
Backup you older wwallet.dat sync with a new one then relace it with your backup. Possible run repairwallet. ..
April 16, 2015, 11:15:32 AM
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 updateso at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
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
Did you compile with latest secp256k1 ? Did you patch key.cpp?
Ok, I'll try that.
April 16, 2015, 11:12:50 AM
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 updateso at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
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
Did you compile with latest secp256k1 ? Did you patch key.cpp?
April 16, 2015, 11:12:27 AM
I also had problems with the wallet I downloaded yesterday.
But it is only the 32712 taken to move, then normalizes and works normally.
But it is only the 32712 taken to move, then normalizes and works normally.
April 16, 2015, 11:10:51 AM
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 updateso at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
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
Did you compile with latest secp256k1 ? Did you patch key.cpp?
April 16, 2015, 11:08:50 AM
I've got no issues at all.
No sync problems (always downloaded whole blockchain from the beginning)
No stake problems (works like a charm for me).
I don't use any node,I don't use crave.conf
And one more time:do NOT talk to SDC/DASH trolls and losers
Well ..If you didn't use crave.conf ,so..what you're using.Share with us.Any idea will be great .Is that mean that you doing only stake ??Reason why I'm asking ,because I'm very close to shoot off all my nodes and change only for stake.Thank youNo sync problems (always downloaded whole blockchain from the beginning)
No stake problems (works like a charm for me).
I don't use any node,I don't use crave.conf
And one more time:do NOT talk to SDC/DASH trolls and losers
Yes,I've never created crave.conf
Yes,I only stake (I've got almost 11k Crave so it's alright for me-I'm too noob to create MNs because I don't know how to open the bloody 9999 port on my router
April 16, 2015, 11:07:04 AM
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
April 16, 2015, 11:06:56 AM
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 updateso at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
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
you can use old version sologap has old precompiled version
April 16, 2015, 11:04:53 AM
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 updateso at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
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
April 16, 2015, 11:03:23 AM
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 updateso at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
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
April 16, 2015, 11:02:28 AM
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
April 16, 2015, 11:01:45 AM
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 updateso at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
April 16, 2015, 11:00:58 AM
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 updateso at least people who are having problems can sync
Don't mean to sound like an ass.. I just hope this crap gets fixed
Sorry, yes 32712 it starts for me, and I've seen it at 32713 also
April 16, 2015, 11:00:01 AM
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 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
April 16, 2015, 10:59:48 AM
Crave is about to reach a huge market capitalization, so of course we have whales manipulating the market and keeping crave in lower levels, do not be fooled whales are buying all yours cheap coins ... So keep calm, just buy and hold, coin already proved to be very strong, and a small spark could take crave above 600K in less than 2 hours.
Unhappily 95% of all traders are like cattle, they just buy and sell in panic, and whales loves this stupid comportment. Do not fall in panic, burn the manipulators, lets buy all their coins in the dips, this way they can not rebound in low levels and they will be burned to dead.
Unhappily 95% of all traders are like cattle, they just buy and sell in panic, and whales loves this stupid comportment. Do not fall in panic, burn the manipulators, lets buy all their coins in the dips, this way they can not rebound in low levels and they will be burned to dead.
Jump to: