Bitcoin Forum
November 07, 2024, 12:25:18 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 [596] 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 ... 697 »
  Print  
Author Topic: [ANN] CRAVE 1st POS Masternodes | Dark Assets | I2P | Market =Embrace The Dark=  (Read 826730 times)
coinspredator
Sr. Member
****
Offline Offline

Activity: 432
Merit: 250



View Profile
May 03, 2015, 09:26:18 PM
 #11901

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

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=<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 Offline

Activity: 1232
Merit: 1001



View Profile WWW
May 03, 2015, 09:26:28 PM
 #11902

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

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=<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 hochladen

Static i2p address  Grin waiting for connections.

Join the Elastic revolution!  Elastic - The Decentralized Supercomputer
ELASTIC WEBSITE | NEW ANNOUNCEMENT THREAD | ELASTIC SLACK | ELASTIC FORUM
mammix2
Legendary
*
Offline Offline

Activity: 1302
Merit: 1004



View Profile
May 03, 2015, 09:30:03 PM
 #11903

Native I2P?

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

1HfpFYxBUpQ941mKd4DEjsyA22HN4Kerzu
bathrobehero
Legendary
*
Offline Offline

Activity: 2002
Merit: 1051


ICO? Not even once.


View Profile
May 03, 2015, 09:36:46 PM
 #11904

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
Sr. Member
****
Offline Offline

Activity: 448
Merit: 250



View Profile
May 03, 2015, 09:38:08 PM
 #11905

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 Offline

Activity: 1232
Merit: 1001



View Profile WWW
May 03, 2015, 09:39:18 PM
 #11906

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

Join the Elastic revolution!  Elastic - The Decentralized Supercomputer
ELASTIC WEBSITE | NEW ANNOUNCEMENT THREAD | ELASTIC SLACK | ELASTIC FORUM
Kimowa
Sr. Member
****
Offline Offline

Activity: 448
Merit: 250



View Profile
May 03, 2015, 09:40:33 PM
 #11907

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 Offline

Activity: 1232
Merit: 1001



View Profile WWW
May 03, 2015, 09:47:32 PM
 #11908

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

Join the Elastic revolution!  Elastic - The Decentralized Supercomputer
ELASTIC WEBSITE | NEW ANNOUNCEMENT THREAD | ELASTIC SLACK | ELASTIC FORUM
bathrobehero
Legendary
*
Offline Offline

Activity: 2002
Merit: 1051


ICO? Not even once.


View Profile
May 03, 2015, 09:48:36 PM
 #11909

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
Sr. Member
****
Offline Offline

Activity: 252
Merit: 250



View Profile
May 03, 2015, 09:50:55 PM
 #11910

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
Sr. Member
****
Offline Offline

Activity: 448
Merit: 250



View Profile
May 03, 2015, 09:51:55 PM
 #11911

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  Cool

CraveIt
Sr. Member
****
Offline Offline

Activity: 269
Merit: 250


View Profile
May 03, 2015, 09:52:39 PM
 #11912

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

 Cool Cool Cool Cool Cool
trader19
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001



View Profile WWW
May 03, 2015, 09:53:00 PM
Last edit: May 03, 2015, 10:06:11 PM by trader19
 #11913

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

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

Join the Elastic revolution!  Elastic - The Decentralized Supercomputer
ELASTIC WEBSITE | NEW ANNOUNCEMENT THREAD | ELASTIC SLACK | ELASTIC FORUM
Kimowa
Sr. Member
****
Offline Offline

Activity: 448
Merit: 250



View Profile
May 03, 2015, 09:53:22 PM
 #11914

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

 Cool Cool Cool Cool Cool

i have paid to some but many are cash out i will send yours now just pm me

CraveIt
Sr. Member
****
Offline Offline

Activity: 269
Merit: 250


View Profile
May 03, 2015, 10:00:47 PM
 #11915

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

 Cool Cool Cool Cool Cool

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  Shocked Shocked Shocked Shocked
striker7334 2.0
Sr. Member
****
Offline Offline

Activity: 560
Merit: 300


Unprofessional shitcoin trader since 2011


View Profile
May 03, 2015, 10:53:20 PM
 #11916

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









Let's do it, after the market drop.  Cheesy

Very cool future plans excited about CRAVE's future glad I'm a bagholder!  Cheesy

Jengo
Sr. Member
****
Offline Offline

Activity: 382
Merit: 250



View Profile
May 04, 2015, 12:37:55 AM
 #11917

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









Let's do it, after the market drop.  Cheesy

Very cool future plans excited about CRAVE's future glad I'm a bagholder!  Cheesy

It's unbelieveable what you're deving in this short timeframe ICM!
You must be... a god!
waffles99
Sr. Member
****
Offline Offline

Activity: 275
Merit: 250


View Profile
May 04, 2015, 03:37:07 AM
 #11918

I would imagine with i2p only nodes at least 50% of them on stable servers we should get the best calculations for profitability
borris123
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
May 04, 2015, 01:06:36 PM
 #11919

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
Hero Member
*****
Offline Offline

Activity: 672
Merit: 500



View Profile
May 04, 2015, 04:54:29 PM
 #11920

Gonna be an interesting week. Let's see if ICM can deliver as promised before Wednesday.
Pages: « 1 ... 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 [596] 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 ... 697 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!