[ANN] CRAVE 1st POS Masternodes | Dark Assets | I2P | Market =Embrace The Dark=

[webprods]

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 you

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.BTW.It's very easy open port .First you have to check out your firewall ( Control Panel ,Firewall, advance ,inbound rules,new rule,crave-qt.exe.property,ports ,must be set up for any port  ,be sure that all marks,private,domain,public. Next masternode port must be the same as port in crave.conf.I did that for all my nodes after error"no capeable masternode port.And all my nodes are listed but with very poor income after last wallet update.

[rocoro]

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?

[Micp]

I also had problems with the wallet I downloaded yesterday.
But it is only the 32712 taken to move, then normalizes and works normally.

[tm2013]

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?

No, I did not compile with the latest version. I installed the version before the current release and it compiles and works fine..

[rocoro]

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.  

[CDarvin81]

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?

No, I did not compile with the latest version. I installed the version before the current release and it compiles and works fine..

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. ..

[Wavelength]

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. ..

This worked for me yesterday.

[jasemoney]

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
  

    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.


https://github.com/industrialcoinmagic/darkpoold/blob/master/lib/config.py#L72

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.)

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

[EmilioMann]

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

[NEVER.SELL.CRAVE...EVER]

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 you

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.BTW.It's very easy open port .First you have to check out your firewall ( Control Panel ,Firewall, advance ,inbound rules,new rule,crave-qt.exe.property,ports ,must be set up for any port  ,be sure that all marks,private,domain,public. Next masternode port must be the same as port in crave.conf.I did that for all my nodes after error"no capeable masternode port.And all my nodes are listed but with very poor income after last wallet update.

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.

[pookielax31]

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

[pookielax31]

You want to start shouting my name emilioman Ill come present the facts

[nskendrovic]

Guys what do i need to do to stake this coin?

[NEVER.SELL.CRAVE...EVER]

Guys what do i need to do to stake this coin?

You need to be owner of them.After 8 hrs you'll start staking.
Don't forget to unlock your wallet fot staking only and keep it opened of course.

[EmilioMann]

shit shit blah blah
blah blah blah
blah blah i'm mongo blah blah

I thought i would share with you all here that the dev has responded to my PM, he said he would fix the github and give the contributors proper credit after he has finished working on more important things. This has given me a boost of confidence since this means that the dev is responsive to the community, furthermore one of my previous criticisms was based on there being a lack of anonymity features in the coin however seeing that darksend will be implemented in CRAVE is also great news which has quelled some of my previous concerns. You could certainly say that this skeptic has become a believer with some reservations of course it is still the early days. I will now be setting up a CRAVE masternode alongside my DASH masternode. Financial freedom and privacy for all, liberty or death.

[Blazin8888]

shit shit blah blah
blah blah blah
blah blah i'm mongo blah blah

I thought i would share with you all here that the dev has responded to my PM, he said he would fix the github and give the contributors proper credit after he has finished working on more important things. This has given me a boost of confidence since this means that the dev is responsive to the community, furthermore one of my previous criticisms was based on there being a lack of anonymity features in the coin however seeing that darksend will be implemented in CRAVE is also great news which has quelled some of my previous concerns. You could certainly say that this skeptic has become a believer with some reservations of course it is still the early days. I will now be setting up a CRAVE masternode alongside my DASH masternode. Financial freedom and privacy for all, liberty or death.

[EmilioMann]

Guys what do i need to do to stake this coin?

just wait 8 hours to beggining

[pookielax31]

Emilioman why is it that when your account goes off-line... Blazin888 goes online? Jumping between multiple handles to create traffic and talk shit i see

[pookielax31]

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

This points out the True deceitful intentions the developer originally had, right from the start he decided to give 0 credit to the projects that spent countless hours on their code...just to rip them off and give no credit... it also points to many same trends that other scam coins have pulled like this






https://github.com/industrialcoinmagic/crave/graphs/contributors

This is what a real project looks like its contributors trace right back through all of its codebase!

https://github.com/dashpay/dash/graphs/contributors

You will notice gavinandresen at the top there on any decent project git because they know what they are doing!


Here is an example of another incompetent dev and their pumped and dumped vaporware project


https://github.com/StealthSend/Stealth/

Its 9 months old it has nothing to do with time. go to the links and see for yourself what i'm saying.

Now go and check every failed coin you know that has been a pump and dump and compare with projects you know for certain are the real deal! Again time has nothing to do with them being a real deal either.





These projects all trace back to their origins.

 The fact he did this shows incompetence, laziness and sloppiness! Ill say it again, stop being a jerk and actually go find all yrou scam coins, check and compare! Thats the tip of the iceberg the next is comparing the code signature these guys have

[EmilioMann]

- First POS masternodes coin
- First mobile wallet with stake and masternodes
- First roadmap finished in only 2 weeks
- Amazing dev
- Amazing community

Running darkpoold on Ubuntu linux tutorial:

Code:

sudo apt-get update && upgrade
sudo apt-get install git python python3 python3-pip
sudo apt-get update && upgrade
git clone --recursive https://github.com/industrialcoinmagic/darkpoold
sudo pip3 install bottle appdirs==1.2.0 prettytable==0.7.2 python-dateutil==2.2 requests==2.1.0 cherrypy==3.2.4 json-rpc==1.1 pycoin==0.25 pytest==2.5.1
sudo pip3 install https://github.com/rogerbinns/apsw/archive/master.zip
sudo apt-get install sqlite3
sudo apt-get update && upgrade

Location for darkpoold.conf: /home/yourusername/.local/share/darkpoold/

Sample darkpoold.conf:

Code:

[Default]
rpc-user = crave-username
rpc-password = crave-password
backend-rpc-password = crave-password
backend-rpc-user = crave-user
backend-rpc-port = 9999
craved-rpc-user = crave-user
craved-rpc-password = crave-password
craved-rpc-port = 9999
craved-rpc-connect = localhost (or the IP of the node you have configured)

Needed crave.conf:

Code:

maxconnections=100
rpcuser=crave-username
rpcpassword=crave-password
rpcport=9999
gen=0
server=1
daemon=1
txindex=1
rpcallowip=127.0.0.1 

To run:
start an instance of craved or crave-qt and:

Code:

cd /darkpoold/
sudo ./darkpoold.py server

Wait for the chain to finish parsing, and after that, open a new terminal window, cd /darkpoold/, sudo ./darkpoold.py -h, and have fun
Donation addy: CAo7D2Z65cAREopaomYVPW4BKDidCSREJ3
Working Bootle coming soon, still working on that

Hi,

btw my little community project, code word cravedigger is to 90% developed.
Hope i get the code ready today.

screens for feedback, Layout is an example at the moment i work on the backend funktions..

ANNOUNCEMENT - Crave Adrenaline Node Cloud Service

Sologap and myself we are launching Master Node Service website where users can buy sell and trade nodes much like https://cex.io

Members can join and buy any amount of asset for masternodes and monitor ROI In real time

Assets can be locked or unlocked so members can always control their assets

This service is like renting hash but user will get receipt of stake from nodes they hold

Members can lock assets for 1 month or more driving up node profit or even longer keeping crave of network, higher amount of lock time = higher profit

Or you can keep unlocked at anytime for a withdrawal

We are talking to contacts and a few whales at current time, if you are looking to join us or partner to help create or fund service we can have discussion via pm or slack(preferred)

https://cravecoin.slack.com

Thanks crave community we hope you get in talks with us.

HOLY SHIT!
This coin has an amazing community and an amazing dev !
Thanks all