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

[PhilipMorris]

I really think if these markets are to be functional they need to use btc, at least at first.

I understand your points, but in order to accept other currencies/blockchains we would need atomic cross-chain transactions.  I know there are a few people looking into that but as far as I know there are no POC's out yet let alone a proven solution.  For instance, how would we enforce a BTC 3 party multi-sig from within Crave.  Actually, I do know one way that we could do it, but it would require that users run a full BTC node in addition to the Crave wallet and it is relatively complex to build.  The fact that it is challenging doesn't mean a flat "no", but maybe it is something to put on the roadmap to look into after the market release with the understanding that it could be weeks or months of R&D work to build and test the solution.

Do not give ICM ideas!

Last time this was done, this happened:

Almost done with the native I2P integration   I updated the code for the latest secp256k1 and will get that checked in soon as well.   

right on, sounds interesting... is that for the market integration? lol I'm not a techie so it sounds like latin to me

It was something I decided to just do since people were fudding about it.  So, now its baked in. The multi-sig escrow workflow is the key for the market

And now we have native I2P wich wasn't on the roadmap   

Let's do it, after the market drop. 

Whats the ETA for the market ?

[Digital_Currency_LTD]

I really think if these markets are to be functional they need to use btc, at least at first.

I understand your points, but in order to accept other currencies/blockchains we would need atomic cross-chain transactions.  I know there are a few people looking into that but as far as I know there are no POC's out yet let alone a proven solution.  For instance, how would we enforce a BTC 3 party multi-sig from within Crave.  Actually, I do know one way that we could do it, but it would require that users run a full BTC node in addition to the Crave wallet and it is relatively complex to build.  The fact that it is challenging doesn't mean a flat "no", but maybe it is something to put on the roadmap to look into after the market release with the understanding that it could be weeks or months of R&D work to build and test the solution.

Do not give ICM ideas!

Last time this was done, this happened:

Almost done with the native I2P integration   I updated the code for the latest secp256k1 and will get that checked in soon as well.   

right on, sounds interesting... is that for the market integration? lol I'm not a techie so it sounds like latin to me

It was something I decided to just do since people were fudding about it.  So, now its baked in. The multi-sig escrow workflow is the key for the market

And now we have native I2P wich wasn't on the roadmap   

Let's do it, after the market drop. 

NICE!!!

[trader19]

I really think if these markets are to be functional they need to use btc, at least at first.

I understand your points, but in order to accept other currencies/blockchains we would need atomic cross-chain transactions.  I know there are a few people looking into that but as far as I know there are no POC's out yet let alone a proven solution.  For instance, how would we enforce a BTC 3 party multi-sig from within Crave.  Actually, I do know one way that we could do it, but it would require that users run a full BTC node in addition to the Crave wallet and it is relatively complex to build.  The fact that it is challenging doesn't mean a flat "no", but maybe it is something to put on the roadmap to look into after the market release with the understanding that it could be weeks or months of R&D work to build and test the solution.

Do not give ICM ideas!

Last time this was done, this happened:

Almost done with the native I2P integration   I updated the code for the latest secp256k1 and will get that checked in soon as well.   

right on, sounds interesting... is that for the market integration? lol I'm not a techie so it sounds like latin to me

It was something I decided to just do since people were fudding about it.  So, now its baked in. The multi-sig escrow workflow is the key for the market

And now we have native I2P wich wasn't on the roadmap   

Let's do it, after the market drop. 

HAHA u guys have been warned  don't give ICM ideas, look what happens  ICM on fire

[STEALTHMODE]

And we go on... Just great!

[EmilioMann]

Let's do it, after the market drop.  

MAN/WOMAN... YOU ARE SICK!  

[tkon3]

Calm down ICM pleaseeeeeee   

[STEALTHMODE]

https://twitter.com/industrialcoinm/status/594960825749786625 

[coinspredator]

Let's do it, after the market drop.  

MAN/WOMAN... YOU ARE SICK!  

Dev are you human ? I love crave... I gonna retire here. 

[Delita Heiral]

hahahahahahahahaha

I really think if these markets are to be functional they need to use btc, at least at first.

I understand your points, but in order to accept other currencies/blockchains we would need atomic cross-chain transactions.  I know there are a few people looking into that but as far as I know there are no POC's out yet let alone a proven solution.  For instance, how would we enforce a BTC 3 party multi-sig from within Crave.  Actually, I do know one way that we could do it, but it would require that users run a full BTC node in addition to the Crave wallet and it is relatively complex to build.  The fact that it is challenging doesn't mean a flat "no", but maybe it is something to put on the roadmap to look into after the market release with the understanding that it could be weeks or months of R&D work to build and test the solution.

Do not give ICM ideas!

Last time this was done, this happened:

Almost done with the native I2P integration   I updated the code for the latest secp256k1 and will get that checked in soon as well.   

right on, sounds interesting... is that for the market integration? lol I'm not a techie so it sounds like latin to me

It was something I decided to just do since people were fudding about it.  So, now its baked in. The multi-sig escrow workflow is the key for the market

And now we have native I2P wich wasn't on the roadmap   

Let's do it, after the market drop. 

[Kimowa]

best coin of 2015

shown by number of clone  and community

[trader678]

maybe to create multipool that will mine other coins and pay in crave
just a suggestion  

[Kimowa]

maybe to create multipool that will mine other coins and pay in crave
just a suggestion  

let dev work no more suggestion he is genius let him go

[cryptohangman]

hahahahahahahahaha

I really think if these markets are to be functional they need to use btc, at least at first.

I understand your points, but in order to accept other currencies/blockchains we would need atomic cross-chain transactions.  I know there are a few people looking into that but as far as I know there are no POC's out yet let alone a proven solution.  For instance, how would we enforce a BTC 3 party multi-sig from within Crave.  Actually, I do know one way that we could do it, but it would require that users run a full BTC node in addition to the Crave wallet and it is relatively complex to build.  The fact that it is challenging doesn't mean a flat "no", but maybe it is something to put on the roadmap to look into after the market release with the understanding that it could be weeks or months of R&D work to build and test the solution.

Do not give ICM ideas!

Last time this was done, this happened:

Almost done with the native I2P integration   I updated the code for the latest secp256k1 and will get that checked in soon as well.   

right on, sounds interesting... is that for the market integration? lol I'm not a techie so it sounds like latin to me

It was something I decided to just do since people were fudding about it.  So, now its baked in. The multi-sig escrow workflow is the key for the market

And now we have native I2P wich wasn't on the roadmap   

Let's do it, after the market drop. 

PROMOTIONAL TEAM 


DEV WORKING 

[rocoro]

For those interested in using the I2P feature,  this procedure most likely will help in setting it up.
Quote and thank you to other opensource coins' documentations:

Setting up your client to use I2P

Your traffic will be open for anyone to inspect if you run the Crave client over clearnet. If you would like to hide the fact that you are using Crave, as well as the physical location from where your Crave traffic originates, you should set up your wallet to connect only to the I2P darknet.

To do this, download and install the I2P router(see below). After starting the router, you will need to enable the SAM application bridge. In the I2P web interface (http://127.0.0.1:7657/configclients), click on the box to automatically run the application bridge at startup, and then click on "start". By default, the SAM application bridge listens to 127.0.0.1 on port 7656. If you need to change this behavior, this can be done in one of three ways:

•    From the preferences menu in the Crave graphical interface, click on I2P, and then modify the IP number and port for the SAM application bridge. For the changes to take effect, restart the application.
•    From the command line, start the Crave daemon (usually named craved) by specifying the following options: -samhost=<ip or host name> and -samport=<port>. For more options, use the command craved --help.
•    Edit the variable clientApp.1.args in the file clients.config that is located in your local I2P folder and then restart I2P.

Once this is done, start the Crave client, open the application preferences, click on the I2P menu, and then click on the button "use I2P only". Close the application and relaunch it. At this point, all your traffic will be encrypted and pass through the I2P network.

Please note that it will take several minutes to make connections to the I2P network when starting I2P for the first time.


Where to download I2P

The official I2P release can be downloaded here: https://geti2p.net/en/download.

The Abscond bundle is an easy to install software package with all you need to connect to I2P and let you use the most common features. It can be downloaded here: https://hideme.today/dev/.


 

[Kimowa]

For those interested in using the I2P feature,  this procedure mostly will help in setting it up.
Quote and thank you to other opensource coins' documentations:

Setting up your client to use I2P

Your traffic will be open for anyone to inspect if you run the Crave client over clearnet. If you would like to hide the fact that you are using Crave, as well as the physical location from where your Crave traffic originates, you should set up your wallet to connect only to the I2P darknet.

To do this, download and install the I2P router(see below). After starting the router, you will need to enable the SAM application bridge. In the I2P web interface (http://127.0.0.1:7657/configclients), click on the box to automatically run the application bridge at startup, and then click on "start". By default, the SAM application bridge listens to 127.0.0.1 on port 7656. If you need to change this behavior, this can be done in one of three ways:

•     From the preferences menu in the Crave graphical interface, click on I2P, and then modify the IP number and port for the SAM application bridge. For the changes to take effect, restart the application.
•     From the command line, start the Crave daemon (usually named craved) by specifying the following options: -samhost=<ip or host name> and -samport=<port>. For more options, use the command craved --help.
•     Edit the variable clientApp.1.args in the file clients.config that is located in your local I2P folder and then restart I2P.

Once this is done, start the Crave client, open the application preferences, click on the I2P menu, and then click on the button "use I2P only". Close the application and relaunch it. At this point, all your traffic will be encrypted and pass through the I2P network.

Please note that it will take several minutes to make connections to the I2P network when starting I2P for the first time.


Where to download I2P

The official I2P release can be downloaded here: https://geti2p.net/en/download.

The Abscond bundle is an easy to install software package with all you need to connect to I2P and let you use the most common features. It can be downloaded here: https://hideme.today/dev/.


 

crave first  i2p and tor native very big

[trader19]

For those interested in using the I2P feature,  this procedure most likely will help in setting it up.
Quote and thank you to other opensource coins' documentations:

Setting up your client to use I2P

Your traffic will be open for anyone to inspect if you run the Crave client over clearnet. If you would like to hide the fact that you are using Crave, as well as the physical location from where your Crave traffic originates, you should set up your wallet to connect only to the I2P darknet.

To do this, download and install the I2P router(see below). After starting the router, you will need to enable the SAM application bridge. In the I2P web interface (http://127.0.0.1:7657/configclients), click on the box to automatically run the application bridge at startup, and then click on "start". By default, the SAM application bridge listens to 127.0.0.1 on port 7656. If you need to change this behavior, this can be done in one of three ways:

•    From the preferences menu in the Crave graphical interface, click on I2P, and then modify the IP number and port for the SAM application bridge. For the changes to take effect, restart the application.
•    From the command line, start the Crave daemon (usually named craved) by specifying the following options: -samhost=<ip or host name> and -samport=<port>. For more options, use the command craved --help.
•    Edit the variable clientApp.1.args in the file clients.config that is located in your local I2P folder and then restart I2P.

Once this is done, start the Crave client, open the application preferences, click on the I2P menu, and then click on the button "use I2P only". Close the application and relaunch it. At this point, all your traffic will be encrypted and pass through the I2P network.

Please note that it will take several minutes to make connections to the I2P network when starting I2P for the first time.


Where to download I2P

The official I2P release can be downloaded here: https://geti2p.net/en/download.

The Abscond bundle is an easy to install software package with all you need to connect to I2P and let you use the most common features. It can be downloaded here: https://hideme.today/dev/.


 

hey dude, your amazing. thank you for tutorial! was googling about it..

[Kimowa]

dev listens to community he clear advanced coder and developer 

[tema]

For those interested in using the I2P feature,  this procedure most likely will help in setting it up.
Quote and thank you to other opensource coins' documentations:

Setting up your client to use I2P

Your traffic will be open for anyone to inspect if you run the Crave client over clearnet. If you would like to hide the fact that you are using Crave, as well as the physical location from where your Crave traffic originates, you should set up your wallet to connect only to the I2P darknet.

To do this, download and install the I2P router(see below). After starting the router, you will need to enable the SAM application bridge. In the I2P web interface (http://127.0.0.1:7657/configclients), click on the box to automatically run the application bridge at startup, and then click on "start". By default, the SAM application bridge listens to 127.0.0.1 on port 7656. If you need to change this behavior, this can be done in one of three ways:

•    From the preferences menu in the Crave graphical interface, click on I2P, and then modify the IP number and port for the SAM application bridge. For the changes to take effect, restart the application.
•    From the command line, start the Crave daemon (usually named craved) by specifying the following options: -samhost=<ip or host name> and -samport=<port>. For more options, use the command craved --help.
•    Edit the variable clientApp.1.args in the file clients.config that is located in your local I2P folder and then restart I2P.

Once this is done, start the Crave client, open the application preferences, click on the I2P menu, and then click on the button "use I2P only". Close the application and relaunch it. At this point, all your traffic will be encrypted and pass through the I2P network.

Please note that it will take several minutes to make connections to the I2P network when starting I2P for the first time.


Where to download I2P

The official I2P release can be downloaded here: https://geti2p.net/en/download.

The Abscond bundle is an easy to install software package with all you need to connect to I2P and let you use the most common features. It can be downloaded here: https://hideme.today/dev/.


 

Please place on https://cravetalk.org/

[trader19]

has anyone even tried to route crave traffic through i2p yet. less hype and more actual use please

bilder hochladen kostenlos
 

big thx to rocoro for tutorial!!!

For those interested in using the I2P feature,  this procedure most likely will help in setting it up.
Quote and thank you to other opensource coins' documentations:

Setting up your client to use I2P

Your traffic will be open for anyone to inspect if you run the Crave client over clearnet. If you would like to hide the fact that you are using Crave, as well as the physical location from where your Crave traffic originates, you should set up your wallet to connect only to the I2P darknet.

To do this, download and install the I2P router(see below). After starting the router, you will need to enable the SAM application bridge. In the I2P web interface (http://127.0.0.1:7657/configclients), click on the box to automatically run the application bridge at startup, and then click on "start". By default, the SAM application bridge listens to 127.0.0.1 on port 7656. If you need to change this behavior, this can be done in one of three ways:

•     From the preferences menu in the Crave graphical interface, click on I2P, and then modify the IP number and port for the SAM application bridge. For the changes to take effect, restart the application.
•     From the command line, start the Crave daemon (usually named craved) by specifying the following options: -samhost=<ip or host name> and -samport=<port>. For more options, use the command craved --help.
•     Edit the variable clientApp.1.args in the file clients.config that is located in your local I2P folder and then restart I2P.

Once this is done, start the Crave client, open the application preferences, click on the I2P menu, and then click on the button "use I2P only". Close the application and relaunch it. At this point, all your traffic will be encrypted and pass through the I2P network.

Please note that it will take several minutes to make connections to the I2P network when starting I2P for the first time.


Where to download I2P

The official I2P release can be downloaded here: https://geti2p.net/en/download.

The Abscond bundle is an easy to install software package with all you need to connect to I2P and let you use the most common features. It can be downloaded here: https://hideme.today/dev/.


 

[coinspredator]

This coin definitely looking to go at Top 5 soon, so guys helping to spread the word.


https://twitter.com/industrialcoinm/status/594960825749786625

C'mon guys let's retweet this 1 million of times.