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

bathrobehero

legendary

Activity: 2002

Merit: 1051

ICO? Not even once.

Quote from: trader19 on May 03, 2015, 04:47:32 PM

just some math, for exmpl. average block speed 90sec/block ( 24h*60min*60sec=84600sec/day) 84600sec / 90sec/block= 960 BLOCKS per day now 960BLOCKS / 200 masternodes = 4.8CRAVE * 0.6666 = 2.88CRAVE per NODE per DAY on average.

That makes a lot of sense but it still doesn't explain why some masternodes received twice as many payments as others.

trader19

legendary

Activity: 1232

Merit: 1001

Quote from: trader19 on May 03, 2015, 04:39:18 PM

Quote from: bathrobehero on May 03, 2015, 04:36:46 PM

This is a graph on the number of payments on a single masternode:

That's an average of 3.96 blocks/day. With 1440 blocks being generated a day, that figure should only be that low if the number of masternodes would be as high as 360. With the masternode count being around 200, the payments frequency should be be much higher. There are masternodes that received over double of what I did. The masternode runs 24/7 on a VPS with plenty of active connections. Is it getting potentially exploited (low latency hosting, blocked nodes, etc)?

you forgot block speed average 89 sec/block makes less than 1000 blocks per day chain is moving slower than expected...

just some math, for exmpl. average block speed 90sec/block ( 24h*60min*60sec=84600sec/day) 84600sec / 90sec/block= 960 BLOCKS per day now 960BLOCKS / 200 masternodes = 4.8CRAVE * 0.6666 = 2.88CRAVE per NODE per DAY on average.

Kimowa

sr. member

Activity: 448

Merit: 250

Quote from: Kimowa on May 03, 2015, 04:38:08 PM

Quote from: bathrobehero on May 03, 2015, 04:36:46 PM

This is a graph on the number of payments on a single masternode:

That's an average of 3.96 blocks/day. With 1440 blocks being generated a day, that figure should only be that low if the number of masternodes would be as high as 360. With the masternode count being around 200, the payments frequency should be be much higher. There are masternodes that received over double of what I did. The masternode runs 24/7 on a VPS with plenty of active connections. Is the system is getting potentially exploited (low latency hosting, blocked nodes, etc)?

you cannot do any damage actual network is decentralized

+ no party benefit from that attack

trader19

legendary

Activity: 1232

Merit: 1001

Quote from: bathrobehero on May 03, 2015, 04:36:46 PM

This is a graph on the number of payments on a single masternode:

That's an average of 3.96 blocks/day. With 1440 blocks being generated a day, that figure should only be that low if the number of masternodes would be as high as 360. With the masternode count being around 200, the payments frequency should be be much higher. There are masternodes that received over double of what I did. The masternode runs 24/7 on a VPS with plenty of active connections. Is it getting potentially exploited (low latency hosting, blocked nodes, etc)?

you forgot block speed average 89 sec/block makes less than 1000 blocks per day Wink

chain is moving slower than expected...

Kimowa

sr. member

Activity: 448

Merit: 250

Quote from: bathrobehero on May 03, 2015, 04:36:46 PM

This is a graph on the number of payments on a single masternode:

That's an average of 3.96 blocks/day. With 1440 blocks being generated a day, that figure should only be that low if the number of masternodes would be as high as 360. With the masternode count being around 200, the payments frequency should be be much higher. There are masternodes that received over double of what I did. The masternode runs 24/7 on a VPS with plenty of active connections. Is the system is getting potentially exploited (low latency hosting, blocked nodes, etc)?

you cannot do any damage actual network is decentralized

bathrobehero

legendary

Activity: 2002

Merit: 1051

ICO? Not even once.

This is a graph on the number of payments on a single masternode:

That's an average of 3.96 blocks/day. With 1440 blocks being generated a day, that figure should only be that low if the number of masternodes would be as high as 360. With the masternode count being around 200, the payments frequency should be be much higher. There are masternodes that received over double of what I did. The masternode runs 24/7 on a VPS with plenty of active connections. Is the system is getting potentially exploited (low latency hosting, blocked nodes, etc)?

mammix2

legendary

Activity: 1302

Merit: 1004

Native I2P?

I got to say, this is very good! Well done guys Grin

trader19

legendary

Activity: 1232

Merit: 1001

Quote from: trader19 on May 03, 2015, 04:20:00 PM

Quote from: waffles99 on May 03, 2015, 02:24:57 PM

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

bilder hochladen kostenlos
Cool

big thx to rocoro for tutorial!!!

Quote from: rocoro on May 03, 2015, 03:46:35 PM

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:

Quote

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= and -samport=. 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/.

kostenlos bilder hochladen

Static i2p address Grin

waiting for connections.

coinspredator

sr. member

Activity: 432

Merit: 250

Quote from: trader19 on May 03, 2015, 04:20:00 PM

Quote from: waffles99 on May 03, 2015, 02:24:57 PM

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

bilder hochladen kostenlos
Cool

big thx to rocoro for tutorial!!!

Quote from: rocoro on May 03, 2015, 03:46:35 PM

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:

Quote

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= and -samport=. 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/.

I gonna make mine right now, thanks for your tutorial.

coinspredator

sr. member

Activity: 432

Merit: 250

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.

trader19

legendary

Activity: 1232

Merit: 1001

Quote from: waffles99 on May 03, 2015, 02:24:57 PM

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

bilder hochladen kostenlos
Cool

big thx to rocoro for tutorial!!!

Quote from: rocoro on May 03, 2015, 03:46:35 PM

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:

Quote

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= and -samport=. 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/.

tema

hero member

Activity: 715

Merit: 500

Quote from: rocoro on May 03, 2015, 03:46:35 PM

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:

Quote

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= and -samport=. 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/

Kimowa

sr. member

Activity: 448

Merit: 250

dev listens to community he clear advanced coder and developer Cool

trader19

legendary

Activity: 1232

Merit: 1001

Quote from: rocoro on May 03, 2015, 03:46:35 PM

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:

Quote

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= and -samport=. 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

sr. member

Activity: 448

Merit: 250

Quote from: rocoro on May 03, 2015, 03:46:35 PM

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:

Quote

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= and -samport=. 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

rocoro

legendary

Activity: 938

Merit: 1000

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:

Quote

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= and -samport=. 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/.

cryptohangman

full member

Activity: 181

Merit: 100

Quote from: Delita Heiral on May 03, 2015, 03:39:45 PM

hahahahahahahahaha

Quote from: industrialcoinmagic on May 03, 2015, 03:21:24 PM

Quote from: proletariat on May 03, 2015, 02:11:14 PM

Quote from: industrialcoinmagic on May 03, 2015, 01:32:39 PM

Quote from: stormia on May 03, 2015, 01:19:38 PM

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:

Quote from: industrialcoinmagic on April 24, 2015, 08:25:33 PM

Quote from: fonzerrellie on April 24, 2015, 08:14:47 PM

Quote from: industrialcoinmagic on April 24, 2015, 07:56:27 PM

Almost done with the native I2P integration Cheesy

I updated the code for the latest secp256k1 and will get that checked in soon as well. Kiss

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

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 Wink

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