coinspredator
|
|
May 03, 2015, 09:26:18 PM |
|
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/. I gonna make mine right now, thanks for your tutorial.
|
|
|
|
trader19
Legendary
Offline
Activity: 1232
Merit: 1001
|
|
May 03, 2015, 09:26:28 PM |
|
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/. kostenlos bilder hochladenStatic i2p address waiting for connections.
|
|
|
|
mammix2
Legendary
Offline
Activity: 1302
Merit: 1004
|
|
May 03, 2015, 09:30:03 PM |
|
Native I2P? I got to say, this is very good! Well done guys
|
1HfpFYxBUpQ941mKd4DEjsyA22HN4Kerzu
|
|
|
bathrobehero
Legendary
Offline
Activity: 2002
Merit: 1051
ICO? Not even once.
|
|
May 03, 2015, 09: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)?
|
Not your keys, not your coins!
|
|
|
Kimowa
|
|
May 03, 2015, 09:38:08 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
|
|
|
|
trader19
Legendary
Offline
Activity: 1232
Merit: 1001
|
|
May 03, 2015, 09:39:18 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...
|
|
|
|
Kimowa
|
|
May 03, 2015, 09:40:33 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
Offline
Activity: 1232
Merit: 1001
|
|
May 03, 2015, 09:47:32 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.
|
|
|
|
bathrobehero
Legendary
Offline
Activity: 2002
Merit: 1051
ICO? Not even once.
|
|
May 03, 2015, 09:48:36 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.
|
Not your keys, not your coins!
|
|
|
NEVER.SELL.CRAVE...EVER
|
|
May 03, 2015, 09:50:55 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. What about connection stability?
|
|
|
|
Kimowa
|
|
May 03, 2015, 09:51:55 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. What about connection stability? this correct i think
|
|
|
|
CraveIt
|
|
May 03, 2015, 09:52:39 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 Speaking of Adrenaline Nodes, kimowa when will profit get paid from your adrenaline hosting service
|
|
|
|
trader19
Legendary
Offline
Activity: 1232
Merit: 1001
|
|
May 03, 2015, 09:53:00 PM Last edit: May 03, 2015, 10:06:11 PM by trader19 |
|
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. i asked ICM once about this and the answer was The way the masternode payment algorithm works is it is based on a weird algorithm the darkcoin guy came up with where it calculates the distance of a masternode's hash from a certain generated hash. Maybe we could look at changing the randomization function so basicly its all about luck and being lucky atm.
|
|
|
|
Kimowa
|
|
May 03, 2015, 09:53:22 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 Speaking of Adrenaline Nodes, kimowa when will profit get paid from your adrenaline hosting service i have paid to some but many are cash out i will send yours now just pm me
|
|
|
|
CraveIt
|
|
May 03, 2015, 10:00:47 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 Speaking of Adrenaline Nodes, kimowa when will profit get paid from your adrenaline hosting service i have paid to some but many are cash out i will send yours now just pm me Done, Craving some sweet sweet Crave profits
|
|
|
|
striker7334 2.0
Sr. Member
Offline
Activity: 560
Merit: 300
Unprofessional shitcoin trader since 2011
|
|
May 03, 2015, 10:53:20 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: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. Very cool future plans excited about CRAVE's future glad I'm a bagholder!
|
|
|
|
Jengo
|
|
May 04, 2015, 12:37:55 AM |
|
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. Very cool future plans excited about CRAVE's future glad I'm a bagholder! It's unbelieveable what you're deving in this short timeframe ICM! You must be... a god!
|
|
|
|
waffles99
|
|
May 04, 2015, 03:37:07 AM |
|
I would imagine with i2p only nodes at least 50% of them on stable servers we should get the best calculations for profitability
|
|
|
|
borris123
|
|
May 04, 2015, 01:06:36 PM |
|
why are all my masternodes showing differnet amount of nodes on the adrenline tab?? some of my nodes are not showing now since i restarted it all with new i2p client which wouldnt connect to the network on some of them. i reverted back to the old one and now its doing that? and now when i look on node list some are not showing yet they are started? no settings were changed at all.
some of them sometimes when i click on the adrenline show only about 20 nodes??
|
|
|
|
Blazin8888
|
|
May 04, 2015, 04:54:29 PM |
|
Gonna be an interesting week. Let's see if ICM can deliver as promised before Wednesday.
|
|
|
|
|